> Jon Lewis <jlewis@inorganic5.fdt.net> writes:
> >I had a system with long uptime (248 days) running 2.0.23 (ping protection
> >and a few other patches added) get weird on me the other day.
> >
> >root 1 99.9 0.1 868 84 ? S 22:00 1349:41 init
> >root 14 99.9 0.0 840 32 ? S 22:00 625:47 update (bdflush)
>
> Taking a stab in the dark, you just crossed the boundary where
> the jiffies clock rolls past 2^31. If init and update are using the
> times() system call to keep track of when they should be doing things
> (to be immune to changes in the wall clock), then things can go nuts
> at this point, since time_t is declared to be type "long". There could
Interesting. I do have 1.2.13 boxes that have crossed that uptime, and
one that's currently at 428 days. I've got 2.0.27 boxes that are only a
few months from this halfway point as well. It would be a real shame if
kernel bugs limit uptimes to no more than 8 months.
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/message.
Florida Digital Turnpike |
________Finger jlewis@inorganic5.fdt.net for PGP public key_______