Date: Fri, 14 Mar 1997 11:44:32 -0800 (PST) From: "Eric J. Schwertfeger" <ejs@bfd.com> To: mark thompson <thompson@tgsoft.com> Cc: freebsd-questions@freebsd.com Subject: Re: ntpdate Message-ID: <Pine.BSF.3.95.970314113834.3425A-100000@harlie.bfd.com> In-Reply-To: <199703141817.KAA06916@squirrel.tgsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 Mar 1997, mark thompson wrote: > I have ntpdate running out of cron every couple of hours. Each time it > runs, it adjusts the clock back about .4 seconds... this would be about > 5 seconds a day or 2 minutes a month. > I am quite willing to believe that the clock in my PC gains 2 minutes a > month. What puzzles me is that the comments in ntpdate seem to suggest > that *it* believes that the system will compensate the hardware clock to > make this error disappear, kinda like those self-adjusting car clocks. Ha, got one here that gains 2 minutes in 2 hours :-) And yes, we tried replacing the CMOS battery. If you want the error to correct itself, run xntpd, not ntpdate. ntpdate runs once, adjusts the clock, then goes away. xntpd constantly runs, eventually backs of to checking every 15 minutes, and will skew the timer between checks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970314113834.3425A-100000>