Date: Sun, 16 Jun 1996 09:12:00 -0600 From: Nate Williams <nate@sri.MT.net> To: Mats Lofkvist <mal@algonet.se> Cc: nate@sri.MT.net, current@FreeBSD.org Subject: Re: NTP gurus Message-ID: <199606161512.JAA26200@rocky.sri.MT.net> In-Reply-To: <199606160855.KAA27613@aristotle.algonet.se> References: <199606150254.UAA23487@rocky.sri.MT.net> <199606160855.KAA27613@aristotle.algonet.se>
next in thread | previous in thread | raw e-mail | index | archive | help
> Understanding that my server may not be completely accurate, I am still > using it to keep the rest of the machines in my domain in sync. At most > they are a half a minute off from each other, vs. 10's of minutes in the > past. > > Eh, do you mean milliseconds, not minutes? I would consider half a _second_ > very bad with ntp running. A few milliseconds is good. On some of the boxes I'm not running 'xntpd', but instead I am running ntpdate once/day. On those boxes the drift can get to be seconds/day. (I'm seeing 10-12 seconds/day on the SPARCS). > The drift value is the amount ntp is skewing the system clock frequency > in parts per million. I got the following results when tweaking > TIMER_FREQ on my 486 (from my config): > > # value ntp drift > # 1193182 -550 ppm? > # 1193634 -180 ppm > # 1193849 +- 3 ppm > # .. > I don't think the drift value matters very much when ntp is running, Right, but apparently Bruce is trying to determine the most accurate timer in the system, and ntp is one way of determing the accuracy of the clock. Thanks for the info! Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606161512.JAA26200>