Hello,

I would like to understand those messages :
    kernel time sync status 0040
    . . .
    kernel time sync disabled 0041

Are they errors messages or not, that's my question ;o)

I got them on a Linux 2.4.25 #1 SMP i686.

$ tail -f /var/log/messages
Feb 19 08:52:48 k2 ntpd[834]: ntpd 4.1.80-rc1-r Fri Jul 11 01:05:22 CEST 
2003 (1)
Feb 19 08:52:49 k2 ntpd[834]: precision = 1.000 usec
Feb 19 08:52:49 k2 ntpd[834]: no IPv6 interfaces found
Feb 19 08:52:49 k2 ntpd[834]: kernel time sync status 0040
Feb 19 08:52:51 k2 ntpd[834]: frequency initialized -12.565 PPM from 
/etc/ntp/drift
.. . .
Feb 19 08:57:07 k2 ntpd[834]: time reset -1.201410 s
Feb 19 08:57:07 k2 ntpd[834]: kernel time sync disabled 0041

Cheers
Cyrille

Cyrille <cyrilleml@kbuilder.net> writes:

> Hello,
> 
> I would like to understand those messages :
>     kernel time sync status 0040
>     . . .
>     kernel time sync disabled 0041

Those are time status bits in hex. Compare to those in
<include/sys/timex.h> or RFC 1305.

> 
> Are they errors messages or not, that's my question ;o)
> 
> I got them on a Linux 2.4.25 #1 SMP i686.
> 
> $ tail -f /var/log/messages
> Feb 19 08:52:48 k2 ntpd[834]: ntpd 4.1.80-rc1-r Fri Jul 11 01:05:22
> CEST 2003 (1)
> Feb 19 08:52:49 k2 ntpd[834]: precision = 1.000 usec
> Feb 19 08:52:49 k2 ntpd[834]: no IPv6 interfaces found
> Feb 19 08:52:49 k2 ntpd[834]: kernel time sync status 0040
> Feb 19 08:52:51 k2 ntpd[834]: frequency initialized -12.565 PPM from
> /etc/ntp/drift
> . . .
> Feb 19 08:57:07 k2 ntpd[834]: time reset -1.201410 s
> Feb 19 08:57:07 k2 ntpd[834]: kernel time sync disabled 0041

The average delay from starting the daemon to posing to this newsgroup
was about 5 minutes. Could it be that the delay was too small?

The standard recommendation is to read the chapter about NTP basics in
the FAQ before reporting. Usually it works before you have finished
reading.

Regards,
Ulrich