Messages in this thread | | | Date | Mon, 14 Jan 2008 09:15:55 +0200 | From | Tuomo Valkonen <> | Subject | Re: The ext3 way of journalling |
| |
On 2008-01-13 18:11 -0500, Theodore Tso wrote: > It's much more likely that this early in your boot cycle, your clock is > sometimes incorrect.
I doubt it. I get this nearly _always_ when the system crashes, which accounts for the vast majority of the times I boot it. (I wish swsusp didn't suck so much..)
> Is the "9192" number roughly constant, or is it always changing?
No. That's the number I got last time, but typically I've got something in the 3xxxx range.
> If your machine is on the network, then the "ntpdate" > program could be setting your time so that it looks correct, but > that's after e2fsck is run.
ntpdate isn't run by any of the init scripts. ntpd is, but like I already mentioned, I doubt it would correct vastly incorrect time, not even being able to track and correct when it advances fast.
-- Tuomo
| |