This probably isn't the same problem your having but my clock starting GAINING time just before my power supply blew up and killed my motherboard. IIRC you can check the output from dmesg and see if the CPU clock reported matches your CPU clock speed. If not, that may be your problem and there is a program around somewhere (don't recall it's name) that lets you apply a correction factor to the system clock.
Yes, the correct term is probably "gaining time", English is not my mother tongue. But I think this is not an issue with my power supply (I hope) as this Shuttle is ~6 months old. The output of dmesg seems just fine... I guess I'll just go the cron route as hwclock works the way it's supposed to, thanks for the input.
]]>Lol, I was checking the kernel config to see where the option was at and I noticed I hadn't loaded the module. I have my clock synced every hour tho with rdate.
]]>Cheers,
Dominik
The hardware clock keeps it's time just fine, so I could set a cron job to do "hwclock --hctosys", but that just seems kind of redundant. Any ideas what could be causing this? This is a mere nuisance, but it sometimes causes me to leave for a lecture too early
]]>