Re: dntpd

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:This is crazy:
:
:# grep ntpd /var/log/all.log
:Jun 24 02:06:39 ylem dntpd[629]: issuing frequency adjustment: 338.189ppm
:Jun 24 02:22:27 ylem dntpd[629]: issuing offset adjustment: 3.743491
:Jun 24 02:53:35 ylem dntpd[629]: issuing offset adjustment: 2.301601
:Jun 24 06:45:12 ylem dntpd[629]: issuing frequency adjustment: 554.987ppm
:Jun 24 11:09:01 ylem dntpd[629]: issuing frequency adjustment: 339.188ppm
:Jun 24 14:13:07 ylem dntpd[629]: issuing COARSE offset adjustment: -3587.777365, 24-Jun-2007 14:13:07.027
:Jun 24 14:37:39 ylem dntpd[629]: issuing frequency adjustment: 1447.123ppm
:Jun 24 15:48:12 ylem dntpd[629]: issuing COARSE offset adjustment: 3598.513848, 24-Jun-2007 15:48:12.709
:Jun 24 15:53:26 ylem dntpd[629]: issuing frequency adjustment: 1358.734ppm
:Jun 24 15:58:43 ylem dntpd[629]: issuing frequency adjustment: 1290.414ppm
:Jun 24 16:04:00 ylem dntpd[629]: issuing frequency adjustment: 1240.480ppm
:Jun 24 16:09:15 ylem dntpd[629]: issuing frequency adjustment: 1200.177ppm
:Jun 24 16:14:31 ylem dntpd[629]: issuing frequency adjustment: 1166.282ppm
:
:There's no servers directive, so here's what dntpd.conf looks like:

    Hmm.  Wait a second... 3587?  3598?  That's 3600 seconds == one hour.
    It sounds like one or more servers is off by an hour.  But the ppm
    adjustments are also pretty crazy.  It's over 1 millisecond per second!

    Did you reboot inbetween any of those reports?  It could be you told
    the kernel the real time clock was operating in local time instead of
    GMT and the kernel isn't writing it out properly.  Do you have
    a /etc/wall_cmos_clock file?  If you do, that could be the problem.

    Its possible that I am not parsing something properly, but insofar as
    I know the NTP protocol just passes a raw timestamp.

						-Matt