11 Dec
2004
11 Dec
'04
15:29
Sid Boyce wrote:
Changing XNTPD_OPTIONS="-u ntp" to XNTPD_OPTIONS="" fixed it.
Which probably changes the user to root instead of ntp.
Hmmmmm......there is a user ntp though, whether it needed a password set ?????
Did you have capability compiled as a module or in the kernel? Does it work if you modprobe capability before starting xntpd (if it is a module)? I suspect the difference is a suse patch to the kernel on the laptop, and the kernel.org kernel on this box, with the capability code, which I believe handles these privileged processes access to these secure kernel capabilities. YMMV. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871