Matt Bernstein writes:
> Two of our machines (one running 2.4.18-xfs-ipsec, one
> running 2.4.19-pre10-ac2) started spitting this message
> before some commands (might be in Debian procps 2.0.7-8)
> after an uptime of about 248 days (certainly in the latter
> case, probably the same in the former).
>
> This smells a bit as about 248 is about half of about 497,
> which was a trigger (which I managed to hit :) in the
> mid 2.1.x series for the uptime counter to wrap.
Yep. Debian-unstable has procps-3.1.5 now, which won't emit
this message with 2.4.xx and 2.5.xx kernels. Your system is
still inconsistant though, so rebooting would be a good idea.
(processes may appear to have been started in the future and
run for negative time)
The recent 2.5.xx kernels should be able to handle huge
uptimes better; you'll need the procps-3.1.6 release for
the most recent 2.5.xx kernels though.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Feb 23 2003 - 22:00:22 EST