Print

[apemberton]

I have noticed that my Sheevaplugs and Guruplugs System Clock and Hardware clocks gradually drift over time and I'm wondering if this is causing some disk problems or update failures. The System clock is updated by ntp so is locked to the time standards but the hardware clock creeps over long periods to several minutes difference to the System clock. I use 'hwclock -r' and 'date' to show the difference.

Although probably unrelated, I have had serious problems when the System clock (for unknown reasons) shows some date in 1938 or 1941 (ntp won't start and gives bad date stamps on the disks).

To tackle drift, I have modified /etc/cron.daily/ntp to include the following lines:-

Code: [Select]

# Resynchronise the hardware clock daily to compensate for drift

hwclock --systohc


Is this a good idea?

[tennnn]

I'm very pleased to have been about it.

[Confusticated]

I have had serious problems when the System clock (for unknown reasons) shows some date in 1938 or 1941

Check the battery, mine only seem to last for about three years until they need replacing.

To tackle drift, I have modified /etc/cron.daily/ntp to include the following lines:-

Code:

Code: [Select]

# Resynchronise the hardware clock daily to compensate for drift

hwclock --systohc

Is this a good idea?

Perfectly acceptable and correct IMHO, but be aware that any future update to the ntp package may result in the loss of your changes and you may have to re-edit the file.
I cannot say for sure as it is dependant on the way the package is updated, you will just have to remember to check.

[apemberton]

Errmmm.....

This post was hit by a spammer! My original post was in August 2012 and was left to rot! Anyway, the battery was replaced which fixed the problem.

[Confusticated]

Yes I missed it back then, I answer when I can so that those that DO bother to search before posting can be saved repeating the question and having to wait.
Thanks for confirming the battery renewal.