Daniel Hagerty wrote:
remote refid st t when poll reach delay offset jitter
==============================================================================
*LOCAL(0) .LOCL. 10 l 10 64 377 0.000 0.000 0.001
NetworkServices .INIT. 16 u - 1024 0 0.000 0.000 0.000
and on the other:
remote refid st t when poll reach delay offset jitter
==============================================================================
NetworkServices .STEP. 16 u 81 1024 366 0.807 -73.003 309.922
*LOCAL(0) .LOCL. 10 l 4 64 377 0.000 0.000 0.001
The important thing this is telling you is that each machine is
getting its time from "LOCAL", which is a *fake* reference clock that
uses the local clock. No synchronization exists.
In general, use of the LOCAL reference clock is an error. Legitimate
uses are rare. You probably aren't one of the intended use cases.
I like to set up my ntp configurations so that I have a few authoritative
systems listed "servers", and then include a few of my local systems as
peers. Then I establish fudge entries on those local systems with high
stratum settings (say 12 or so).
That way, if the 'real' servers become unreachable (because of a network
outage, or firewall issue) then my local systems will have agreement on
what time it is. For most stuff (like make) it doesn't really matter if
the
time is right, it just needs to be the same as the other machines around it.
YMMV, but this has worked well for me.
-R. Gary
_______________________________________________
bblisa mailing list
[email protected]
http://www.bblisa.org/mailman/listinfo/bblisa
