Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [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.
I've checked my systems running 12.3 and 13.[12], none of them have ntp chroot'ed by default
I added /etc/resolv.conf and /etc/services to the chroot files and obtain following strace: http://wahoo.no-ip.org/~paka/ntp.trace.txt
Seems to have disappeared.
yast publishes a complaint that systemd cannot find a service state for ntp and that the service, ntp, does not exist. Should be hunting for ntpd.
Yes, that's a little odd.
Real question should probably be why yast does not provide the necessary files for the chroot ntp to succeed....
Yes and no - more likely why ntp was chroot'ed in the first place, but as the later releases did not do it, there's probably not much point in pursuing the issue. -- Per Jessen, Zürich (7.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org