Date: Thu, 30 Dec 2004 11:50:23 -0800 (PST) From: dtalk-ml@prairienet.org To: Federico Galvez-Durand Besnard <Federico.Besnard@bluewin.ch> Cc: freebsd-stable@freebsd.org Subject: Re: clock running fast Message-ID: <20041230113814.L17743@atlantis.flyingjoke.org> In-Reply-To: <41D458DF.3020706@bluewin.ch> References: <41D43A7A.2000500@bluewin.ch> <20041230110953.T17743@atlantis.flyingjoke.org> <41D458DF.3020706@bluewin.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Federico Galvez-Durand Besnard wrote: >Set /etc/localtime to your correct timezone before doing anything in >your machine. Remove /var/db/ntpd.drift before you reboot or restart >your ntpd. [ rc.conf and ntp.conf snipped ] Thank you for the suggestions. Unfortunately, I've been through all that, including the rude values of minpoll and maxpoll, using multiple servers, and starting with a fresh drift file. I'm pretty sure ntpd isn't the problem. In addition, the hardware clock itself appears to be plenty accurate, as it is always correct within a second or two when I check it directly in BIOS ... and two other 5.3-STABLE hosts on the same network, with the same ntpd configuration, but on different hardware, do not have this problem, which began when I updated (reinstalled) to 5.3-STABLE from 5.2. - -- David Talkington dtalk-ml@prairienet.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB1FwQ5FKhdwBLj4sRArSqAJwK8MAvUfB69ixoHNzu8700Pvd52QCgl0dD 07gb7ipg0ENIcUN/PPHhXpw= =Lv+T -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041230113814.L17743>