Subject: Re: ntpd - does it work? What about NTP kernel option?
To: Donald Lee <donlee_ppc@icompute.com>
From: gabriel rosenkoetter <gr@eclipsed.net>
List: port-macppc
Date: 03/15/2000 15:43:49
On Tue, Mar 14, 2000 at 10:51:57PM -0600, Donald Lee wrote:
> seems to have done the trick.  I'm now gaining 0.12 seconds or
> thereabouts every 4 hours.  That's less than a second a day.
> Not wonderful, but acceptable.

That's kind of a mess... and you really shouldn't have to go mucking
around in OF to get NetBSD to keep proper time. After all, MacOS keeps
(fairly good) time with OF just the way it is. (Or does it?)

> I may tweak it a bit more to get closer, or I might try running
> ntpd now, but my original question has not been addressed by anyone
> on the list.

Which question is that? If ntpd works or not? If so, it helps to
actually put the question in the message, rather than in the
subject... ;^>

ntpd works, xntpd (in my experience) works better. (My experience
means {Net,Open,Free}BSD, Solaris, and Linux 2.x.)

> Does the NTP option in the kernel work properly?  It appears not
> to be enabled by default, and that tells me that it has some downside.
> If I build a kernel with the NTP option, will it work?

Works perfectly, should be on by default, but changes to GENERIC move
slowly. (I should have mentioned in my descript of xntpd the other day
that I use this option; it is important.)

> I'm guessing that the comments on the mac68K list about ntpd not
> working has more to do with the "missing ticks" problems than
> something fundamentally wrong with the code.  Is that right?

Correct. 68ks have drastic hardware interrupt problems which Apple
ignores but (and I forget the reasons why) we can't. (Oh, wait, it's
that MacOS doesn't care if everything stops for a disk spinup...
right.)

       ~ g r @ eclipsed.net