Subject: NTP gone haywire.
To: None <port-mac68k@netbsd.org>
From: Chris Tribo <t1345@hopi.dtcc.edu>
List: port-mac68k
Date: 01/01/2002 17:32:43
	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[3865]: time error 600133076 over 1000 seconds;
set clock manually
<daemon quits>



	Chris