On 15/03/16 09:58 AM, Patrick Shanahan wrote:
* Freek de Kruijf <freek@opensuse.org> [03-15-16 11:06]:
Op dinsdag 15 maart 2016 08:44:19 schreef Patrick Shanahan:
* Per Jessen <per@computer.org> [03-15-16 06:32]:
Carlos E. R. wrote:
The funny thing is that I thought I was not, but the files there are up to date. There is a /var/lib/ntp/var/run/ntp/ntpd.pid which does point to ntpd, so it is running there. And indeed, in /etc/sysconfig/ntp I have:
NTPD_RUN_CHROOTED="yes" To make sure, try "ls -l /proc/$(pidof ntpd)" and look at root.
When chroot'ed your ntpd will be running with '-i' specified.
In Leap 42.1, sysconfig::NTPD_RUN_CHROOTED is "no". Same in 13.2, 13.1 and 12.3. Interestingly, in Leap421, /usr/bin/start-ntpd appears to have a hardcoded NTPD_RUN_CHROOTED="yes". I might not have read that script right. 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? Might have to do with an unreachable file in the chroot needed for network access like /etc/resolv.conf Well, resolv.conf does *not* appear /var/lib/ntp/etc/
How would that be added?
tks, Yast:Sysconfig Editor/Network/NTP/NTPD_CHROOT_FILES -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org