Well it seems my uptime has reset itself. It happened roughly 7 hours before it hit 50 days. I know this is not really a big deal but I do find it weird. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/
expatriate wrote:
yoo hoo wrote:
Well it seems my uptime has reset itself. It happened roughly 7 hours before it hit 50 days. I know this is not really a big deal but I do find it weird.
Looks like a 32-bit counter overrun to me.
Here's what my firewall says about that: [jknott@dell jknott]$ uptime 7:19pm up 103 days, 1:03, 2 users, load average: 0.15, 0.03, 0.01 I've seen well over 6 months in the past. Maybe he had a power hit?
On Tuesday 27 January 2004 01.21, James Knott wrote:
expatriate wrote:
yoo hoo wrote:
Well it seems my uptime has reset itself. It happened roughly 7 hours before it hit 50 days. I know this is not really a big deal but I do find it weird.
Looks like a 32-bit counter overrun to me.
Here's what my firewall says about that:
[jknott@dell jknott]$ uptime 7:19pm up 103 days, 1:03, 2 users, load average: 0.15, 0.03, 0.01
I've seen well over 6 months in the past. Maybe he had a power hit?
You have never seen six months on a kernel with the increased tick rate (HZ) patch
On Monday 26 January 2004 18.44, yoo hoo wrote:
Well it seems my uptime has reset itself. It happened roughly 7 hours before it hit 50 days. I know this is not really a big deal but I do find it weird.
This is because you're running a kernel where the "ticks" (the internal counter the kernel uses to keep time) are ten times more than a regular kernel. A regular kernel resets the uptime after roughly 497 days, because the counter can't hold bigger values. Your kernel reaches this level after a tenth, or about 49.7 days The higher tick rate is supposed to give a better desktop experience
participants (4)
-
Anders Johansson -
expatriate -
James Knott -
yoo hoo