[ale] Clock problems with two SuSE setups

[Jeff Lightner]

Are you using ntp to keep your "system" time in sync with known clocks
such as GPS devices or U.S. Naval Observatory servers tick and tock?

If so you might want to use hwclock command to update the hardware
clocks from the system time periodically.  The only time the hwclock is
really used is at boot up to set the initial system time at boot.   I've
seen folks in another forum have issues and doing this seemed to resolve
things for them.

-----Original Message-----
From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of John
To: ale at ale.org
Mills
Sent: Monday, June 04, 2007 11:21 AM
To: Atlanta Linux Enthusiasts
Subject: [ale] Clock problems with two SuSE setups

ALErs-

I updated my SuSE-9.2, -10.1 and -10.2 systems by RPM to
'timezone-2.5-34.1' to adapt to our [brilliant] new daylight savings
calendar. I don't know if it's related to the change, but I've recently
noticed that my two laptops' system clocks are wildly off when I start
them, and badly off (10s of minutes) even if I just reboot Linux without

cycling power.

I first suspected a hardware problem in the -9.2 machine where I first 
noticed the problem, but with two bad actors I tend to blame some 
installation or configuration issue. I tried running the clocks in local

time but that didn't help, so now they're back on UTC and still giving 
trouble.

I have no reason to suppose this is specific to SuSE setups; that's just

what I have here, and the two laptops are the ones frequently restarted.

Has anyone on the list dealt with this type of problem?

TIA.
 - Mills

_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale