Date: Thu, 30 Dec 2004 11:37:04 -0800 From: Javier Henderson <Javier@KJSL.COM> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: David Talkington <dtalk@u.washington.edu> Subject: Re: clock running fast Message-ID: <20041230193704.GS64741@mta-a.kjsl.com> In-Reply-To: <20041230193244.GB2987@odin.ac.hmc.edu> References: <41D43A7A.2000500@bluewin.ch> <20041230110953.T17743@atlantis.flyingjoke.org> <20041230193244.GB2987@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > /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? -jav
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041230193704.GS64741>