What's the longest PC uptime you've ever had?


What's the longest PC uptime you've ever had?  

123 members have voted

  1. 1. Longest uptime before restarting

    • 1 Week or Less
      33
    • 1-2 Weeks
      19
    • 2-3 Weeks
      8
    • 3-4 Weeks
      9
    • Longer than 4 Weeks (Specify in reply if you like)
      54


Recommended Posts

Prolly a month at the most. I usually restart to go back to XP and vice versa.

My old P2 print server had nearly 2 years uptime. Only crashed once, and I was able to recover it by SSH'ing into it and killing a rogue process. It must've survived a fair few power cuts and physical moves too (a P2 doesn't put much strain on a UPS designed for a P4 :p).

Shame it's been made redundant by my new printer.

Edit - just powered it up again and the never-updated installation of Vector Linux still works :D

uptime == Anyone who posts an uptime of a Windows Based box.. that is showing over 30 days is basically saying My system can be exploited. Since Microsoft has been releasing Criticals every 2nd Tuesday of the month for over a year now. So don't be proud of your high uptime, cause I'm going to root your box.

Three years ago I had my old P3 667Mhz system running for 72 days straight until a power cut during a thunderstorm shut it off.

I had it running as a general file dump and a torrent and printer server. The computer was 5 years old at the time. It still runs well today and even has the original 20Gb Seagate HD.

uptime == Anyone who posts an uptime of a Windows Based box.. that is showing over 30 days is basically saying My system can be exploited. Since Microsoft has been releasing Criticals every 2nd Tuesday of the month for over a year now. So don't be proud of your high uptime, cause I'm going to root your box.
While I think it is unwise to not update (and reboot to apply, if necessary) your system, it is absurd to say you can be rooted if your uptime is over 30 days old.
  1. Not all patches involve exploits that are remote
  2. Even if the exploit is remote, it may not involve a system level compromise
  3. Even the remote/system exploits may rely on other factors, like use of the Microsoft JET engine or such.

And finally, those are only known/patched vulnerabilities. So, at any time, any system could potentially be compromised by a non-public exploit.

That totally removes significance to the "30 day" rule. ;)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.