Date: Sat, 15 Jun 1996 12:39:35 -0600 From: Nate Williams <nate@sri.MT.net> To: Garrett Wollman <wollman@lcs.mit.edu> Cc: Nate Williams <nate@sri.MT.net>, current@FreeBSD.org Subject: Re: NTP gurus Message-ID: <199606151839.MAA24995@rocky.sri.MT.net> In-Reply-To: <9606151740.AA25187@halloran-eldar.lcs.mit.edu> References: <199606150254.UAA23487@rocky.sri.MT.net> <9606151740.AA25187@halloran-eldar.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Wollman writes: > <<On Fri, 14 Jun 1996 20:54:58 -0600, Nate Williams <nate@sri.MT.net> said: > > > Anyway, back to my question. How do I determine 'how accurage' my > > system's clock is based on /etc/ntp.drift? What are good numbers to > > have? > > Actually, the best thing to look at (because it's updated on an > on-going basis) is the output of `ntpq -c rv'. For example, on my > system: [ Excellent description deleted ] Wonderful! Thanks for the great description Garrett. > freq=27394.97, error=3.20 So does that mean that my box is pretty accurate then? freq=1636.28, error=0.08 I'm setting machdep.i8254_freq equal to the number kicked out by the clock stuff Bruce used, which implies to me (using the above numbers) that the clock is fairly accurate on this box. In any case, it's much more accurate than the clock on my 'ntp server' box. freq=-13014.10, error=6.74 Thanks! Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606151839.MAA24995>