Vizion wrote:
On Monday 28 November 2005 16:00, Wojciech Puchar:
[ ... ]
Why not synchronize by running ntpd?
or rdate?
sure if you know the host you are using as a reference is itself reliably
referenced!
There's nothing wrong with rdate, but the NTPv4 protocol includes tests and
detection measures for broken clocks which eliminate most "falsetickers".
Running ntpd will try to generate an ntp.drift file which will compensate for
the drift of the native clock, so if the problematic system is off by a
consistent factor, ntpd can compensate for that, within limits.
On the other hand, if the drift is variable or the clock hardware is just
completely busted, then I'd replace the motherboard, or at least break apart
the system and look for bad solder joints, leaky caps, etc, and try
reconnecting everything again....
--
-Chuck
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
