On May 15, 2006, at 10:21 AM, Timothy J. Miller wrote:
Michael Kluskens wrote:
After studying the problem I discovered the problem is that the
standard OS X NTP configuration does not free run well at all so
all the machines I was pointing at my OS X machines had
127.127.1.0 (local clock) at a high enough stratum that they
totally rejected the OS X NTP servers.
I believe that this is actually correct behavior for NTP local
clock; mobo clocks are pretty unreliable (high drift rates), so you
want any NTP server offering local clock only to be high stratum so
that it will get ignored in favor of better clock sources when
available.
I probably was incorrect in that statement, the OS X NTP had no
stratum at all, it appears to have replied that it was unsynced so
the other machines flat out rejected it and used their own local
clock as there is no other clock available on isolated networks.
Michael
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Fed-talk mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/fed-talk/email@hidden
