> > # date && hwclock -r > > dom nov 16 13:53:50 CET 2008 > > dom 16 nov 2008 12:50:07 CET -0.432112 seconds > > It seems that hwclock still thinks that the clock is set to local > time; you can check this with "tail -n1 /etc/adjtime". (hwclock does > not read the setting in /etc/default/rcS, it simply uses the setting > remembered from the last successful hardware clock adjustment, unless > you override this with an explicit command line option.) It > furthermore is off by more than three minutes, which either means you > did not reboot in quite a while or that something goes wrong with the > hardware clock during startup and shutdown.
You were right, hwclock was set to local time. I reboot once a day, and here is an extract of this morning's bootlog: # grep clock /var/log/syslog Nov 16 12:04:04 macco kernel: [ 0.829478] rtc_cmos 00:02: setting system clock to 2008-11-16 11:03:45 UTC (1226833425) Nov 16 12:04:20 macco chronyd[3021]: System clock wrong by 223.601170 seconds, adjustment started I don't understand why the hwclock was off. I can't see any error messages in my logs, but those 224 seconds sound a lot like the 3-minute offset the hwclock had. We shall see what happens at the next reboot. > Try this as root: > > hwclock --utc -w > > then compare "date" and "hwclock -r" again. # hwclock --utc -w # hwclock -r && date dom 16 nov 2008 15:41:33 CET -0.622554 seconds dom nov 16 15:41:33 CET 2008 Thanks, Davide -- Time flies like an arrow. Fruit flies like a banana. -- If anything can go wrong it wSegmentation fault core dumped -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]