-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-10-30 at 15:31 -0500, Ed McCanless wrote:
Studying this has reminded me of an occurance about 4 - 5 days ago. At boot, (I still turn of at night) I noticed the time being slow by more than one hour, and re-set the clock.
Unfortunately, setting the time in linux is not as straight forward as it should be. For instance, you set the system (OS) time using a command. When the computer is powered off, that time is copied to the CMOS clock, but, as it is different, the program is too clever and thinks that it has to compensate for the difference, and stores a compensation factor in /etc/adjtime. The next time you boot, the factor kicks in and corrects the time... to an incorrect value. So, the procedure is to set up the system time (OS time), copy it to the cmos, and finally, erase the /etc/adjtime file. Simple, eh? Ufff... :-P Another way, is to set the clock in the bios setup page before booting. That way Linux doesn't notice a thing.
We've had some power outages recently, and I gave it little thought (not thinking of the CMOS battery.) But, if the change came that early, I can't figure any reason for that either. It would be more comforting if the change were only early or late by 12 hrs. I guess I will run the checks you advised, and wait for the next time change.
That's 6 months away! Too long to wait, I would surely forget it. If you are that interested, you can run checks setting the time incorrectly to some minutes before the time shift (by the procedure above). But beware! Linux doesn't like at all somebody playing with "his" clock, and behaves in some nasty or unexpected ways (depends). Cron jobs starting suddenly, etc. I did that once... entertaining ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFRphmtTMYHG2NR9URAiUlAJ4uBMnAAFP5mwba0t2Q12fvYZ1h6ACfWx5H tL9vZNnrW3psII2hXj0rhF0= =+xVz -----END PGP SIGNATURE-----