Subject: Re: clocks (was Re: usleep() and system clock resolution)
To: None <perry@piermont.com>
From: James Tuman Nelson <jimtnelson@earthlink.net>
List: netbsd-help
Date: 05/20/2000 07:13:44
That is what I was thinking. I changed the BIOS recently, and perhaps
there is some incompatibility with the hardware. The other possibility
is that the battery is dying.
I will look into this ntp.
Thanks for your help.
Jim
"Perry E. Metzger" wrote:
>
> James Tuman Nelson <jimtnelson@earthlink.net> writes:
> > While we are on the subject of system clock, would anyone know why my
> > system clock would fail to keep accurate time within hours? The time
> > seems to slip by several minutes or hours over the course of a day, but
> > not while I am checking over the course of several minutes. It seems to
> > go to sleep for some time, or suspend time keeping. Has anyone had
> > this problem?
>
> It probably isn't "going to sleep". Your system depends on the timers
> constantly running, and if they somehow "stopped" I doubt the machine
> would function. Since there isn't a widespread bug report on such a
> thing, it is probably just an inaccurate clock. I'd try running ntp or
> something to keep it in line.
>
> --
> Perry E. Metzger perry@piermont.com
> --
> "Ask not what your country can force other people to do for you..."