clock running fast

[Federico Galvez-Durand Besnard]

Hmmm, are you using the same localtime in all machines?
I remember having the same problem several years ago, in 3.x, with a 
server. The clock kept walking. Hardware was OK. It came back to normal 
after setting localtime correctly.
Remember, if you are in Pacific Time you are GMT+8 (some people wrongly 
uses GMT-8), it means you have to add 8h to your localtime in order to 
get GMT. Your NTPD will never be stable with a wrong localtime setting.
Fico//

dtalk-ml at prairienet.org wrote:

> -----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 at prairienet.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (FreeBSD)
>
> iD8DBQFB1FwQ5FKhdwBLj4sRArSqAJwK8MAvUfB69ixoHNzu8700Pvd52QCgl0dD
> 07gb7ipg0ENIcUN/PPHhXpw=
> =Lv+T
> -----END PGP SIGNATURE-----
>