[ntp:questions] NTP - orphan mode with SAME stratum ("tos orphan 6") FAIL to sync.
unruh-spam at physics.ubc.ca
Mon Apr 6 21:41:29 UTC 2009
Steve Kostecke <kostecke at ntp.org> writes:
>On 2009-04-06, Unruh <unruh-spam at physics.ubc.ca> wrote:
>> sheikdawoodrajali at gmail.com writes:
>>>When I tried running this test case again the next day with (approx
>>>25/30/40 minutes difference in 3 of the systems out of 7), the time
>>>sync didn't happened for a while (approx 1 hour) or so. x conditions
>>>remained the same on billboard results. Should I wait for some more
>>>time to see time-sync happening?
>> ntp can take 10 hours or more to sync.
>I believe you mean "ntp can take 10 hours or more to amortize a clock's
>offset within the limits of the hardware."
Yes, that is what I meant.
>"Sync" is usually defined as "calculating the offset between a clock and
>a reference standard, stepping or initiating a slew to correct the
>offset, and becoming ready to serve time to others". ntpd is capable of
>"syncing" in under 10 minutes. Even less if the initial offset is less
>than 128ms and/or 'iburst' is used on the server lines.
If serving a time that ntp knows to be wrong by say 120ms is OK, then
yes, I agree that ntp can sync in much less time.
More information about the questions