Subject: Re: NTP gone haywire.
To: None <email@example.com>
From: Donald Lee <firstname.lastname@example.org>
Date: 01/01/2002 19:50:47
I managed to get ntpd working on my 68K macs, but only certain
versions would stay up. It appears that if the clock gets off
"too much" or is deemed "too unstable", then ntpd gives up.
I don't remember what builds I ended up using, I just kept
trying different ones until one stayed up. ;->
I got my version from the "main" ntp site - I think it was at
I should mention that under heavy load, ntpd is not capable of
correcting the clock, as it drifts too fast. I only saw this when
*really* abusing the machine for testing purposes.
> I had this in my syslog, did anyone else run into tryouble with
>NTP? While there doesn't appear to be any way to figure out what happened,
>shouldn't ntp drop a bogus reading and not exit the daemon. I have four
>ntp servers in my conf file, three that refer to the same server and one
>satellite system. Any thoughts? NTP is running just fine now, I'm just
>curious why it died. It's pretty unlikely that all the systems reported an
>incorrect time, or am I not understanding NTP's operation correctly?
>Dec 31 19:45:11 myhost ntpd: time error 600133076 over 1000 seconds;
>set clock manually