[ntp:questions] Re: ntpd local synchronization fails?
smith at cag.zko.hp.com
Tue Nov 15 00:38:50 UTC 2005
Wilhelm Greiner wrote:
> * Harlan Stenn <stenn at ntp.isc.org> schrieb:
>> Please tell us the output of 'ntpq -p' on the broken multicast client
> Look at the posting above, there where those and syslog output
> but i repaste:
> [root at ntp log]# ntpq -p
> remote refid st t when poll reach delay offset jitter
> LOCAL(0) LOCAL(0) 6 l 50 64 377 0.000 0.000 0.015
> *192.168.1.9 192.168.100.5 2 m 2 64 377 0.015 -21.714 16.686
> mfg Wilhelm
It has syncronized to the lower stratum (real) server. That's what
it's supposed to do.
Were you thinking that if it is not synchronized to the local clock,
the local clock would not be set? That's not the case. The local
clock is always set UNLESS NTP is synchronized to the local clock.
If this is only a client, it shouldn't have the local clock configured
as a server in the first place.
More information about the questions