https://bugzilla.novell.com/show_bug.cgi?id=339451
User jdebert@garlic.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=339451#c3
j debert changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jdebert@garlic.com
--- Comment #3 from j debert 2008-01-20 11:12:27 MST ---
The system clock depends on CPU timing clocks. If the CPU clock varies, so will
the system clock. What is really needed is for the kernel to optionally read
the hardware clock for such systems, especially since variable clocked systems
are becoming far more common. Really no excuse now since hardware clocks are
also more accurate, generally.
Crude workaround:
1. Use cron to periodically reset the system clock:
#/sbin/hwclock --hctosys
(use option --utc if your hwclock is set to UTC.)
I reset my system clock every minute. My typical drift
is -3 seconds per minute.
This works if your hardware clock is accurate, which it should be. Else,
use NTP or rdate to reset the clock frequently but not more frequently
the server's policy allows, of course.
2. In /etc/sysconfig/clock. change the following line:
SYSTOHC="yes"
to
SYSTOHC="no"
to keep the system from writing the wrong time to the hardware
clock on shutdown.
3. YMMV
4. $SYSTOHC apparently not available until 10.2.
Or, disable SpeedStep, PowerNow, or whatever clock speed changing method is
used, in BIOS settings, if possible. This will noticeably shorten the battery
run time on laptops, etc.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.