Messages in this thread | | | From | Tuomo Valkonen <> | Subject | Re: The ext3 way of journalling | Date | Mon, 14 Jan 2008 09:48:00 +0000 (UTC) |
| |
On 2008-01-14, Bernd Petrovitsch <bernd@firmix.at> wrote: > Yes, that is a usual bug/problem in common distributions[0] as there is > no real guarantee that your clock is not far off.
It isn't, right after boot. But while the system is on, it sometimes starts advancing very fast, 15min a day or so. To my knowledge, the time the CMOS clock is not used then, but rather the kernel tracks the time based on scheduler interrupts, with ntpd occasionally correcting. However, ntpd refuses to correct when the time has drifted too much, causing even further drift.
> That the reason to activate `ntpdate` unconditionally: It sets the > current time to an (somewhat) accurate value and `ntpd` handles the > rest.
Nope, as explained above. ntpdate at boot wouldn't help much, because the time is (approximately) correct after boot. It only drifts after it.
-- Tuomo
| |