On Sun, 2003-04-06 at 12:53, D. D. Brierton wrote: > > It seems like NTPD is attempting to correct an 8 second drift in my > clock but is failing to do so, and indeed my clock is eight seconds out. > Where can I find further details about why the "synchronisation" is > being "lost"? Does NTPD write to a log anywhere? Why would its attempt > to correct the clock fail? Currently it is attempting to synchronise > with clock2.redhat.com. > I don't know if this is the exact reason for those error messages, but remember that ntpd has a hard time correcting large clock drifts, and 8 seconds is large in ntpd's world. So try stopping ntpd, and then force-resetting the clock with ntpdate (or even rdate). Then, restart it and see if ntpd can correct the much smaller difference that will now be present. Hope this helps, Jeremy
Attachment:
signature.asc
Description: This is a digitally signed message part
