[ntp:questions] Re: NTP broadcastclient update times?

W. D. NewsGroups at US-Webmasters.com
Fri Oct 15 14:25:02 UTC 2004


Terje Mathisen wrote:
> 
> W. D. wrote:
> 
> > Harlan Stenn wrote:
> >
> >>Please post the output of "ntpq -p" on that server.
> >>
> >>H
> >
> >
> > Here is the output from "ntpq -p" from the broadcastclient:
> >
> >      remote           refid      st t when poll reach   delay   offset
> > jitter
> > ==============================================================================
> > *192.168.2.122   128.9.176.30     2 u   60   64  377    0.262   -1.501
> > 0.206
> 
> OK, so you have an (estimated) offset of 0.2 ms from a one-way
> connection? That's pretty good you know!


Thanks for your reply.  

When you say one-way, you are talking about the NTP broadcast
messages over the LAN, yes?

Why is it that the clock on this computer can be over 1 second
off then?


Fragment of ntp.log:

14 Oct 01:21:19 ntpd[88]: synchronized to 192.168.2.122, stratum=2
14 Oct 01:29:55 ntpd[88]: time reset +1.643005 s
14 Oct 01:31:07 ntpd[88]: synchronized to 192.168.2.122, stratum=2
14 Oct 01:41:44 ntpd[88]: no servers reachable
14 Oct 01:49:15 ntpd[88]: synchronized to 192.168.2.122, stratum=2
14 Oct 01:55:43 ntpd[88]: time reset -1.314898 s
14 Oct 01:56:55 ntpd[88]: synchronized to 192.168.2.122, stratum=2
14 Oct 02:18:12 ntpd[88]: time reset +0.485238 s
14 Oct 02:19:25 ntpd[88]: synchronized to 192.168.2.122, stratum=2
14 Oct 02:53:42 ntpd[88]: time reset +0.638312 s
14 Oct 02:54:56 ntpd[88]: synchronized to 192.168.2.122, stratum=2
14 Oct 03:18:24 ntpd[88]: time reset -0.400259 s
14 Oct 03:19:36 ntpd[88]: synchronized to 192.168.2.122, stratum=2



More information about the questions mailing list