Date: Mon, 28 Nov 2005 22:43:36 -0500 From: Chuck Swiger <cswiger@mac.com> To: Vizion <vizion@vizion.occoxmail.com> Cc: Wojciech Puchar <wojtek@tensor.3miasto.net>, freebsd-questions@freebsd.org Subject: Re: system time "slowing down" ? Message-ID: <438BCE68.10601@mac.com> In-Reply-To: <200511281608.56425.vizion@vizion.occoxmail.com> References: <20051128234053.GA75541@ns2.wananchi.com> <200511281549.38757.vizion@vizion.occoxmail.com> <20051129005948.P69275@chylonia.3miasto.net> <200511281608.56425.vizion@vizion.occoxmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Vizion wrote: > On Monday 28 November 2005 16:00, Wojciech Puchar: [ ... ] >>> Why not synchronize by running ntpd? >> >> or rdate? > > sure if you know the host you are using as a reference is itself reliably > referenced! There's nothing wrong with rdate, but the NTPv4 protocol includes tests and detection measures for broken clocks which eliminate most "falsetickers". Running ntpd will try to generate an ntp.drift file which will compensate for the drift of the native clock, so if the problematic system is off by a consistent factor, ntpd can compensate for that, within limits. On the other hand, if the drift is variable or the clock hardware is just completely busted, then I'd replace the motherboard, or at least break apart the system and look for bad solder joints, leaky caps, etc, and try reconnecting everything again.... -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?438BCE68.10601>