<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Daniel Hagerty wrote:
<blockquote cite="mid:c2itz5rckt0.fsf@perdition.linnaean.org"
type="cite">
<blockquote type="cite">
<pre wrap=""> 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
</pre>
</blockquote>
<pre wrap=""><!---->
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.</pre>
</blockquote>
I like to set up my ntp configurations so that I have a few
authoritative<br>
systems listed "servers", and then include a few of my local systems as
<br>
peers. Then I establish fudge entries on those local systems with high <br>
stratum settings (say 12 or so). <br>
<br>
That way, if the 'real' servers become unreachable (because of a network<br>
outage, or firewall issue) then my local systems will have agreement on
<br>
what time it is. For most stuff (like make) it doesn't really matter
if the <br>
time is right, it just needs to be the same as the other machines
around it.<br>
<br>
YMMV, but this has worked well for me.<br>
-R. Gary<br>
</body>
</html>