On 12/13/2011 2:00 PM, David J Taylor wrote:
"Richard B. Gilbert" <[email protected]> wrote in message
news:[email protected]...
[]
Like it or not, NTPD, when started, will need up to TEN HOURS to
settle down with the best time that you are going to get! This is not
a hardship if you run NTPD 24x365 (366 in leap years). If you have to
shutdown frequently and can't wait for NTPD to reach steady state then
NTP is the wrong tool for you!
[]
Richard,
You may find that up to 10 hours is needed in your systems, perhaps
where you are looking for microsecond precision, but here I see much
quicker settling.
Example: a Windows-7/32 netbook PC when rebooted this morning in a
wireless network took about 15 minutes to settle to its ultimate
accuracy of about 1.5ms RMS offset, Windows-7 and Wi-Fi are not known
for helping timekeeping performance! This with: ntpd 4.2.4p6@DLH-QPC-o
May 30 3:58:32.88 (UTC) 2009 (273), a local stratum-1 server, and
careful configuration of ntp.conf.
Cheers,
David
More recent versions of NTP may do better that what I have observed over
the years. My systems run 24x365 except when Atlantic City Electric
decides they can't be bothered to supply electricity. My UPS takes care
of the brownouts and brief dropouts.
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
