On Wed, 18 Aug 1999, Frederick Bruckman wrote:

> Keep in mind that, although the real time clock typically loses no more
> than a second per month, the NetBSD clock loses up to 3 hours _per_
> _day_. MacOS < 8.0 also lost time badly. Once you set the real time
> clock in MacOS, either OS will be most accurate just after booting. 

Just for reference, my system (Quadra 800 40/500+520, GENERIC kernel,
NetBSD 1.4) doesn't seem to have this problem.  My system usually goes two
or three weeks between reboots, and the most time I've seen it lose (from
logging in remotely and comparing it against my SPARCstation 10 at work)
is two or three minutes over that many weeks.  It doesn't work too hard
(the monitor is usually off, I remote login and do some compiling or
network access, experiment with some stuff, etc., and I'm going to take
another shot at getting IPNAT working), so perhaps that's the reason why. 
In any case, I haven't personally detected a problem yet. 

/*======================================================================
"Don't die wondering..."                http://www.cldc.howard.edu/~cpg
                                              email: cpg@scs.howard.edu
chris out-              Christopher P. Gill
  peace.        C.L.D.C. Senior System Operator (Ret.)
======================================================================*/