[ntp:questions] Wrong time after changing hardware

Marc Muehlfeld marc.muehlfeld at web.de
Tue Jul 24 07:50:52 UTC 2007


Hi,

Per Hedeland schrieb:
> Note that the location can also be specified via the commandline (-f
> option), overriding what is in ntp.conf AFAIK. I.e. check the
> commandline of your running ntpd too.
I allready checked. There are no parameters inside the runlevel script for the 
drift file. It's started with the following options:
/usr/sbin/ntpd -p /var/lib/ntp/var/run/ntp/ntpd.pid -u ntp -i /var/lib/ntp



 > In any case the driftfile spec you
> have there is pretty "weird" - I've seen some Linux distros use
> /var/lib/ntp/drift (i.e. a file called 'drift' in the /var/lib/ntp
> directory), which makes some sense when running ntpd as non-root, but
> your pathname is just "stupid" (no offense intended:-).
The path is just the one out of the box after installing the xntp-4.2.0a-46 
package from Suse 10.0. The ntpd runs chroot and as user "ntp" by default.



 > And, the fact
> that the old file had 0.000 means that it wasn't used by ntpd either,
> the 0.000 having been put there by misguided Linux installation
> procedures.
I also reinstalled and it wasn't touched. But the file is used. When I look at 
/var/log/messages, I see the following on a restart
Jul 24 09:32:27 myserver ntpdate[15037]: adjust time server 80.86.83.133 
offset 0.000961 sec
Jul 24 09:32:27 myserver ntpd[15042]: ntpd 4.2.0a at 1.1191-r Fri Sep  9 17:17:17 
UTC 2005 (1)
Jul 24 09:32:27 myserver ntpd[15042]: precision = 1.000 usec
Jul 24 09:32:27 myserver ntpd[15042]: Listening on interface wildcard, 0.0.0.0#123
Jul 24 09:32:27 myserver ntpd[15042]: Listening on interface wildcard, ::#123
Jul 24 09:32:27 myserver ntpd[15042]: Listening on interface lo, 127.0.0.1#123
Jul 24 09:32:27 myserver ntpd[15042]: Listening on interface eth0, 192.168.0.1#123
Jul 24 09:32:27 myserver ntpd[15042]: kernel time sync status 0040
Jul 24 09:32:27 myserver ntpd[15042]: frequency initialized 0.000 PPM from 
/var/lib/ntp/drift/ntp.drift



> ... the most important info: Output of 'ntpq -p', after ntpd has been
 > running for a significant while.
I'll send this later. I just restarted shortly ago.



Regards
Marc




More information about the questions mailing list