"Keith G. Murphy" wrote:
> It may actually be due to the *documented* behavior of adjtime.
> ...
This makes a lot of sense. I vaguely remember something about this
happening when I found my clock out by months.
In this case, I imagine it would be a good idea to set a drift
threshhold wherein ad
John Carline wrote:
>
> Judith Elaine Bush wrote:
>
> > I have three identical new thin clients with as identical a set-up as i
> > can manage to create -- and one shows this problem. It's particularly
> > annoying as i had the system set to reboot at a certain time every day
> > (mainly to clean
Alexander Stavitsky wrote:
> I had this problem couple of days ago. It appeares that
> /etc/adjtime got corrupted somehow. Now I am wondering if that
> is a bug. Anyway, try removing /etc/adjtime and setting the correct time
> with date or ntpdate. In my case the problem went away.
It's gone away
Judith Elaine Bush wrote:
> I have three identical new thin clients with as identical a set-up as i
> can manage to create -- and one shows this problem. It's particularly
> annoying as i had the system set to reboot at a certain time every day
> (mainly to clean up any flakiness from Netscape) --
I have three identical new thin clients with as identical a set-up as i
can manage to create -- and one shows this problem. It's particularly
annoying as i had the system set to reboot at a certain time every day
(mainly to clean up any flakiness from Netscape) -- and the system
would set itself
Alexander Stavitsky wrote:
> On Sun, Aug 15, 1999 at 01:18:41PM +0930, Matthew Tuck wrote:
> > I'm having a problem where my clock seems to jump all over the place.
>
> > It's not a hardware
> > fault because I can set it under Windows and it will stay correct. It
> > seems every time I boot
On Sun, Aug 15, 1999 at 01:18:41PM +0930, Matthew Tuck wrote:
> I'm having a problem where my clock seems to jump all over the place.
> At the moment I have to set it every start up, when I remember that is.
> I have searched the archives and not found anything.
>
> Basically the clock is out by
One possibility is you need a new battery.
--
Eric G. Miller
Powered by the POTATO (http://www.debian.org)!
8 matches
Mail list logo