* Per Jessen <per@computer.org> [03-15-16 11:32]:
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [03-15-16 10:50]:
Patrick Shanahan wrote:
[...]
OK, semi-solved. The problem apparently lies with the chrooted jail. If I unset NTPD_RUN_CHROOTED, ntpd operates as desired. I checked my other local boxes and none are running chrooted.
Then the remaining question, why is it failing when running chrooted?
Your chroot jail wasn't properly set up - somehow. I assume you were the one who changed the system to NTPD_RUN_CHROOTED="yes"? Or are you on TW?
Cannot recall but believe chroot was selected on original tw install of ntp. I manually changed NTPD_RUN_CHROOTED= to "no" and restart ntpd and see successful operation.
The original chroot setup was done by yast during install so if borked, yast is culprit ....
Uh, I suspect the jail setup is done by the start script. That's how it used to be anyway. If it isn't done on start-up, the latest changes to the network aren't included.
That may well be but this system restart with NTPD_RUN_CHROOTED="yes" leaves ntpd failing to connect with/without ipv6 and a change to NTPD_RUN_CHROOTED="no" w/o a restart is successful. ???
Right - so whatever is supposed to set up the chroot jail isn't working, I would say. On Leap421, that is /usr/sbin/start-ntpd.
Which is as provided in ntp-4.2.8p4-2.1.x86_64 I would expect that *many* op's would be affected and wondering ???? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org