-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Opps... I misread the problem. :(
I have found that I get a more accurate time by using the us.pool.ntp.org as there is usually less of a network delay. Glad you found the solution to the immediate problem. Not sure about a better way to do time unless you want to check your clock against WWV once a day. Eric Eric H Christensen wrote: > You COULD restart your ntpd and hope that it grabs a new server. BTW, > if you edit the config file to the following: > > server 0.us.pool.ntp.org > server 1.us.pool.ntp.org > server 2.us.pool.ntp.org > > and that way you will select three US servers that you may have better > results from. > > Eric > > > > Jason Tower wrote: >>> got a dapper machine with the time too fast by 55 sec: >>> >>> [EMAIL PROTECTED]:~# ntpdate -b pool.ntp.org >>> 27 Jul 16:18:46 ntpdate[12420]: step time server 193.120.142.71 offset >>> \ -55.118258 sec >>> >>> unfortunately that command is not fixing the time as it should, running >>> 'date' still reports a time 55sec in the future. i tried ntpd but >>> doesn't work either: >>> >>> Jul 27 15:55:16 murphy ntpd[11630]: time reset -55.023169 s >>> >>> yet the clock is still off following the reset. note that this 55s is a >>> slow drift, it's only gaining a few seconds per day, but of course it >>> adds up. >>> >>> wtf do i have to do to get the system clock set to the correct time? >>> >>> jason -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEyWcIQ6BPgKVM2YgRAtO2AJ0YYMOzxA14Ygq+IVubbYv2Cp44rACfdTHL BsjnWfPzNIgalqETrjwyl8k= =dzWI -----END PGP SIGNATURE----- -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
