On Sep 2, 2006, at 5:27 PM, Parag Mehta wrote:
thanks for the info. that seems to have fixed the problem, but
wouldn't
that cause the time on the server to keep changing based on the offset
difference received from various time servers ?
Yes, but NTPd has some fairly clever algorithms to figure out the
best timeserver available based on reachability, network RTT delay,
and offsets compared with the other NTP servers. If you want your
machine to keep time more reliably than what you get by sync'ing with
a dozen stratum-1 or -2 NTP sources, you'll need to set up a
reference clock via GPS or whatever yourself.
For human purposes, and for most network protocols like filesharing,
a time offset of less than 10 milliseconds is good enough.
--
-Chuck
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
