Hmmm..

I use ntpdate.  It's easy and accurate enough for most people use.
as easy as

ntpdate ntp1.wherever.yak >> /var/log/ntpdate

BTW, you should be aware that mac's are notoriously bad for keeping 
time.  See http://www.macbsd.com/macbsd/macbsd-docs/faq/faq-3.html#ss3.17 
for an explanation....

Cheers,

Simon.


At 10:34 13/03/00 -0500, Andy Finnell wrote:
>on 3/13/2000 1:12 AM, Donald Lee at donlee_ppc@icompute.com wrote:
> >
> > I'm now trying to run on a PowerCenter 132, and its clock is off by about
> > an hour a day (?).  NTP seems to be overwhelmed by the error,
> > but I'm also investigating the kernel support, and it seems not
> > to be there.
> >
> > It appears that the primary problem with the clock skew is that the
> > Open Firmware is giving a bad number for the timebase, but I was
> > hoping that ntpd could help me out.
> >
> > Ideas anyone?
>
>I don't know why, but I can say my PowerCenter Pro 180 has a very similar
>problem.  I always have a major clock skew (several hours).  I had a similar
>problem when I ran mklinux, and I was told then that my open firmware
>reported the wrong bus speed ( 40mhz instead of 60mhz).
>
>     -andy