J. Scott Thayer wrote:
On Thursday 23 March 2006 06:52, Daniel Bauer wrote:
<snip>
This seems to be a common problem with some installations including my Acer laptop with 9.3. You can find references to it in the archives and no one has ever presented an adequate explanation or solution. Now you knew saying that no one had presented an adequate solution would fire someone up :)
I too have been presented with this anomoly only on SuSE 9.0 and have, after many frusrated hours, been unable to get my clock to behave itself and not report the incorrect time. My clock seemed to advance notibly after a few shutdowns. I monitored the shutdown log ie the one that displays as the machine is shutting down, and noticed that the hardware clock was reset to the current system time. When the system was restarted it would get the CMOS time and increment it by, I assume, the /etc/adjtime file. This ended up putting my clock ahead of time which was compounded when I next shut the machine down. I did not rectify the problem and ended up routinely deleting /etc/adjtime and then resetting the time via Yast. On SuSE 9.2 I have not had this problem and I can therefore only assume that it does not write the SuSE time back to the CMOS clock. Of course if you should have a permanent internet connection, then I would setup for your machine to use NTP. HIH but I would still like to know if what I think was causing it, is causing your time drift.