Date: Sat, 10 May 2008 11:50:19 +0100 From: Rui Paulo <rpaulo@FreeBSD.org> To: Rene Maroufi <info@maroufi.net> Cc: freebsd-i386@FreeBSD.org Subject: Re: i386/123462: clock is to fast Message-ID: <48257DEB.1040509@FreeBSD.org> In-Reply-To: <200805092200.m49M04Eo098042@freefall.freebsd.org> References: <200805092200.m49M04Eo098042@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Rene Maroufi wrote: > The following reply was made to PR i386/123462; it has been noted by GNATS. > > From: Rene Maroufi <info@maroufi.net> > To: Bruce Cran <bruce@cran.org.uk> > Cc: bug-followup@FreeBSD.org > Subject: Re: i386/123462: clock is to fast > Date: Fri, 9 May 2008 23:56:54 +0200 > > On Fri, May 09, 2008 at 10:26:46PM +0100, Bruce Cran wrote: > > ntp is designed to compensate for that sort of drift, but it should be > > run continuously: the best setup is to run ntpdate once on boot to make > > any large adjustments but also to run ntpd so it can track and correct > > any drift. > > No, I tested this with ntpd too, but ntpd can't correct the time. The > time difference between the real time and the PC clock grows with ntpd > too. > Can you boot with "kern.hz=100" and check whether or not it makes a difference? Thanks, -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48257DEB.1040509>