[UUG/MLUG] Fixed the time problem!

[Jay Buffington <EMAIL:PROTECTED>]

Thanks for the advice, Chris.  After running `rdate time.nist.gov` I ran
`hwclock --systohc --utc` and my problem was totally gone.  hwclock set
the hardware clock to the same time as the system clock, but corrected
for for greenwich time. 

Glad to have that working :)


Jay

"Christopher J. Kaiser" wrote:
> 
> Using gmt wouldn't screw up the date, just set the clock <back> by five
> hours.  However, I think the comment about the system clock is probably
> it.  IIRC you can reset the software clock without automatically
> resetting the hardware clock.  Sounds to me like that's whats going on.
> Since it can't keep track of time in suspend mode, everytime you resume
> the computer goes and reads the (incorrect) time from the hardware clock
> and resets to the result.
> 
> Chris
> 
> EMAIL:PROTECTED wrote:
> >
> > That was my thought too.  Perhaps setting your bios clock to GMT would
> > help?  Or maybe modifing your suspend script to include a call to write
> > the system to the BIOS or something to that effect.
> >
> > Nimrod
> >
> > On Fri, 8 Oct 1999, David Lloyd wrote:
> >
> > > That wouldn't be GMT, would it?
> > >
> > > Dave Lloyd
> > >
> > > On Wed, 13 Oct 1999, Jay Buffington wrote:
> > >
> > > > I guess I should have mentioned that this is on my laptop.
> > > >
> > > > After paying a little attention I've noticed that this only happens
> > > > whenever I suspend the machine.  After the suspend its always 5 days, 9
> > > > hours, 6 minutes fast, plus or minus a few seconds.  I run rdate
> > > > time.nist.gov and the time is corrected, but this is annoying.
> > > >
> > > > Here is the output of a few experiments I ran:
> > > >
> > > > $ date
> > > > Fri Oct  8 13:12:59 CDT 1999
> > > > $ apm --suspend
> > > > $ date
> > > > Wed Oct 13 22:19:09 CDT 1999
> > > >
> > > >
> > > > $ date
> > > > Fri Oct  8 13:21:49 CDT 1999
> > > > $ apm --suspend
> > > > $ date
> > > > Wed Oct 13 22:27:54 CDT 1999
> > > >
> > > > Notice what happens when I don't reset the clock before running the
> > > > experiment:
> > > > $ date
> > > > Wed Oct 13 22:29:43 CDT 1999
> > > > $ apm --suspend
> > > > $ date
> > > > Wed Oct 13 22:30:10 CDT 1999
> > > >
> > > > It doesn't make the clock faster!
> > > >
> > > >
> > > > $ date
> > > > Fri Oct  8 13:27:44 CDT 1999
> > > > $ apm --suspend
> > > > $ date
> > > > Wed Oct 13 22:34:05 CDT 1999
> > > >
> > > >
> > > > What the heck could be causing this?
> > > >
> > > > Thanks
> > > > Jay
> > > >
> > > > Jay Buffington wrote:
> > > > >
> > > > > If any of you guys have noticed sometimes they have really funky time
> > > > > stamps.  Like the message I sent out this afternoon says October 17th.
> > > > >
> > > > > Nimrod suggested that I use the rdate utility to set my adjtime to a
> > > > > good value... I've been doing that.. But i think it is some thing else.
> > > > >
> > > > > Does anyone have an idea how I can go about figuring out what is wrong.
> > > > > Its not like my clock is just gradually get faster, one minute it will
> > > > > be right on the next 10 days fast.
> > > > >
> > > > > I'll try to keep my eye on it to try to figure out exactly when its
> > > > > getting fast and what might be causing it.
> > > > >
> > > > > `date` currently reports the correct time... So i hope this message will
> > > > > go out with the correct timestamp.
> > > > >
> > > > > Anyone have any ideas whats causing this sporadic behavior?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Jay
> > > >
> > >
> 
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Christopher J. Kaiser
> Assistant Professor
> Animal Sciences Unit
> University of Missouri
> Columbia, MO 65211
> EMAIL:PROTECTED
> phone: 573.882.5479
> fax: 573.884.4606
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~