[ntp:questions] Reference Clock / shared memory driver

stuart clark stuart.clark at baesystems.com
Thu Jan 29 04:57:21 UTC 2009


On Jan 29, 2:51 pm, Unruh <unruh-s... at physics.ubc.ca> wrote:
> "Richard B. Gilbert" <rgilber... at comcast.net> writes:
>
> ...
>
> >Also note that ntpd needs at least thirty minutes after a cold start to
>
> More like 10 hours if it is to get down to usec accuracy. A few hours for
> msec accuracy.
>
> >beat the clock into submission!  Depending on how cold the cold start
> >was it may take longer; e.g. if you've been storing your computer in an
> >unheated garage with the temperatures below -20 degrees F, ntpd might
>
> And that is with a warm clock.

Sorry i dont understand.

I if use the server 192.168.1.10 with a clinet clock one hour in front
of the server, then after less than two minutes the client clock is
set to the server clock.... BUT

if i use the 127.127.28.2 with a client clock one hour in front it
doesnt seem to update within the same "less than two minutes". maybe i
have to wait longer???

If so then is there something "special" about how the client ntpd uses
the shared memory that is different to the way it uses an ip address
ie the 192.168.1.10???

cheers




More information about the questions mailing list