SAVE A SOUL ...uptime

[Tony Hammitt]

It's running 2.2.17pre20, which was later renamed 2.2.17.  Which, yes, 
is a pretty old kernel.  I just haven't had time to upgrade (not kidding 
either).  My wife had a baby 15 months ago, back when the kernel was 
less than a year old and I haven't had time to play with anything else 
since :)

I think that I heard that Intel systems would only make it 497 days, but 
this is an alpha, so I wouldn't know..  I'm really waiting for reviews 
of gentoo alpha to say that it's stable before doing anything else with 
the box.

Jason wrote:

>I don't know if I would want an uptime that long...  
>
>That is awesome though...  I have a server at work that is going on 350 days 
>and went down because the data center lost power and the generators didn't 
>kick in...bummer!!  It was at about 150 days at that point.
>
>685 days means you are on a really old kernel....  No?
>
>I'd sacrifice the uptime for an up to date kernel
>
>Jason
>
>On Sunday 24 November 2002 5:57 pm, Duane Attaway wrote:
>  
>
>>On Sun, 24 Nov 2002, Tony Hammitt wrote:
>>    
>>
>>>On to linux stuff... Uptime contest. Can anyone beat this on a currently
>>>running, in-use-daily desktop system?
>>>
>>>$ w
>>>3:20pm up 685 days, 18:41, 3 users, load average: 0.00, 0.00, 0.00
>>>      
>>>
>>I'm not even close, but I'm trying to figure out why my uptime counter
>>reset after 45 days:
>>
>>attaway root # w
>> 17:49:33  up 12 days, 18:33,  5 users,  load average: 0.09, 0.10, 0.09
>>USER     TTY      FROM              LOGIN@   IDLE   JCPU   PCPU  WHAT
>>root     vc/6     -                 8Oct02  4days  0.50s  0.38s  -bash
>>dattaway pts/0    satellite        Thu12pm  5.00s 25.22s 25.15s  pine
>>dattaway pts/1    satellite        Fri 7am 10:15m  3.10s  0.33s  -bash
>>dattaway pts/2    satellite        Thu 4pm 29:55m  2:45m  0.20s 
>>/usr/sbin/sshd root     pts/3    satellite         5:47pm  1.00s  0.21s 
>>0.10s  w
>>
>>Look at the first login date.  I can't understand why the /proc/uptime
>>counter would reset itself.  No failed processes, no panics, no dropped
>>connections (pine, shells, etc,) just a confusing uptime that made me
>>think the computer reset itself.  It never did.  The last syslog restart
>>entry was 57 days ago.  Odd.
>>
>>What can make the uptime counter reset?
>>
>>
>>
>>    
>>
>
>  
>