Subject: Re: NTP gone haywire.
To: John Klos <john@sixgirls.org>
From: Chris Tribo <t1345@hopi.dtcc.edu>
List: port-mac68k
Date: 01/01/2002 21:17:41
On Tue, 1 Jan 2002, John Klos wrote:

> Hi,
>
> > 	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?
>
> It seems more likely that your Mac's time was off by 1000 seconds or more.
> This is not unexpected with the time & interrupt problem that Macs running
> BSD have.
								^- 680x0

	While that certainly is possible, I've had this system online
since 1.5.2 was released and that hasn't happened to me before. Even when
I run a tape backup of the entire hard drive, it "only" loses about 200
seconds in an hour. And ntp updated itself twice during that period. While
200 is a heck of a lot, it's nowhere near 1000... My load averages rarely
go over 0.2

	Chris