Date: Thu, 30 Dec 2004 21:34:33 +0100 From: Federico Galvez-Durand Besnard <fico@del.ufrj.br> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: freebsd-stable@freebsd.org Subject: Re: clock running fast Message-ID: <41D46659.7010808@del.ufrj.br> In-Reply-To: <20041230201318.GE2987@odin.ac.hmc.edu> References: <41D43A7A.2000500@bluewin.ch> <20041230110953.T17743@atlantis.flyingjoke.org> <20041230193244.GB2987@odin.ac.hmc.edu> <20041230193704.GS64741@mta-a.kjsl.com> <20041230201318.GE2987@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis wrote: >On Thu, Dec 30, 2004 at 11:37:04AM -0800, Javier Henderson wrote: > > >>>>/usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \ >>>>- -f /var/db/ntpd.drift >>>> >>>> >>>It's generally recommended that you never trust your own clock since >>>it's completely crap as time sources go. It's also recommended that you >>>use at least 5 time sources to avoid problems with bad clocks. >>> >>> >>But isn't that what the drift file is for, to improve the accuracy of >>the local clock during those times when the configured NTP servers aren't >>available? >> >> > >Yes, but it can only do so much. The clock crystals in your average PC >are OK as clocks, but much better as thermometers so the drift >calculations are only approximate. > >-- Brooks > > > Yeap, but only if your NTPD is running fine and stable, otherwise drift-file can be very messy. Check your dmesg for NTPD log before you trust drift-files.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41D46659.7010808>