Mailinglist Archive: opensuse (4498 mails)

[Darryl Gregorash <raven@xxxxxxxxxxxxx>]

On 2006-11-02 07:55, Hylton Conacher(ZR1HPC) wrote:
> <snip>From the /var/log/ntp file I have extracted the below snapshot:
>
> 2 Nov 15:32:20 ntpd[4652]: synchronized to LOCAL(0), stratum 10
> 2 Nov 15:32:20 ntpd[4652]: kernel time sync disabled 0041
> 2 Nov 15:33:25 ntpd[4652]: synchronized to 202.135.38.18, stratum 2
> 2 Nov 15:33:25 ntpd[4652]: kernel time sync enabled 0001
>
> Besides the 'kernel time sync disabled/enabled messages, to me it looks
> like the clock is being synced. Would I be right?
>
>
>
I did give an example of such a thing in my first post -- buried in the
middle of the tome :-)

See Carlos's latest post for what should come next. Those are indicative
of a properly functioning ntp client. If you keep seeing changes in the
server you're synchronized to (the second last line in your log snippet
above), then you have problems reaching the servers in your
configuration, but it's not indicative of a problem with ntpd itself.

You're last point is quite correct. In more detail (which I hope isn't
overly confusing), the "kernel sync disabled" only means the daemon has
no external source, and so does not ask the kernel to do anything to
alter the clock rate. (Because, of course, any clock, no matter how poor
it is, is always synchronized to itself! :-) ) The "enabled" line means
that ntpd believes it has acquired a stable external time source, and
the kernel can begin using the received data to make adjustments to the
system clock rate, to keep the system and external clocks synchronized.

I believe your ntp daemon is probably functioning quite well, but
without the statistics logs (and I still do not know how to get those
working again) I cannot prove it to you :-)