Re: [opensuse] SEMI-SOLVED, re: ntpd failing

Patrick Shanahan [22.03.2016 13:50]:

* Per Jessen [03-22-16 03:09]: [...]

...

...

I've never run ntp chrooted, so I don't know all the files that have to be specified.. but resolv.conf is surely not the only one. Take a look back at some of the other replies; I am sure I saw a couple that have that information.

I also never run ntpd chroot'ed, but try adding /etc/services to the jail too. I've only seen it mentioned when I was out googling, I can't explain why it should help with your situation above.

I don't run chroot'ed on my other boxes and didn't *knowingly* on this but it is yast *default* on this box ???? But box was originally 12.1, iirc, and became tw when Greg KH started the project and continued since. When ntpd became chroot (and default as chroot) I have no idea, but it was not that way originally.

Today I got exactly this problem on a re-installed SLES 11 SP4 host. According to entry 9.2.4.2.5.3. on page http://support.ntp.org/bin/view/Support/KnownOsIssues I linked /etc/services to the chroot dir and everything worked. However, the other 15 SLES 11 SP4 don't have this link, and they work fine. And they have all the same version of the ntp package (ntp-4.2.8p4-5.1). Just to make things more confusing: it also works fine when the "server" entries in /etc/ntp.conf are IP addresses instead of host names. In this case, I do not need a services file inside the chroot.

Real question should probably be why yast does not provide the necessary files for the chroot ntp to succeed....

That is what I questioned the support engineer for, and he decided to ask his ntp specialist :) Maybe someone finds out why the problem exists on one host only... Just my 2¢, Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org