Uptime before you have to reboot?

[PsychoAndy]

how do you find uptime in 2k pro?

 

[sohcrates]

<< how do you find uptime in 2k pro? >>



you can double click on your network icon and see how long your network connection has been active.

or you can download a little proggy called uptime.exeand run that...there's other ways too, but they elude me right now.

oh yeah, and my record uptime was a little over 4 months on a machine. i had to shut it off because i moved out of the apartment! grrrr...heheehe

 

[Rent]

I've had my 98SE Box up for 9+ days before. Otherwise, I generally reboot it every 3 to 4 days.

I really don't see why some people throw such a big sh1t fit about rebooting.

 

[NogginBoink]

Many of my enterprise-class customers have Windows NT/2K machines that haven't been rebooted in six months or more. For many of my customers, reboots are the result of OS updates and not stability issues. So if these same customers had chosen to defer OS updates, it's conceivable that their uptimes would be extened into a timeframe measured in years.

Of course, defering OS updates like that is not practical.

OS updates, however, can be scheudled. In this thread we haven't differentiated scheduled vs unscheduled reboots, but I think we'd all agree that the unscheduled reboots are of greater concern.

The number one cause of unscheduled reboots (in my experience) is blue screens. The number one cause of blue screens: antivirus software. (That, and HP 4000/8000 drivers on NT4 Terminal Server machines.) Interestingly, *all* antivirus vendors seem to be about equally guilty of crashing machines. The good news is that there are FAR fewer crashes from antivirus software than there were three years ago.

If you have performance problems when running apps, and you truly want to troubleshoot and resolve the issue instead of rebooting, fire up performance monitor and look for processes with extensive numbers of open handles, memory usage that keeps going up, etc. Although it's very rare that an app will truly bring down the OS, it's not so difficult for an app to consume so many resources that the OS is useless from a practical standpoint. If you find such an app and kill it, OS performance should resume to normal levels.

 

[Snapster]

Uptime in 2k was great, months at a time. The only times I did shut it off was when I went on holiday or to update core system files.

Xp.......I'm still counting

 

[mpitts]

<< I've had my 98SE Box up for 9+ days before. Otherwise, I generally reboot it every 3 to 4 days.

I really don't see why some people throw such a big sh1t fit about rebooting. >>



You would understand if it was a server that was your responsibility. We run our own mail server here at work (which I installed and administer) and if it goes down for five seconds people freak out.

At home it doesn't matter much, but for enterprise/buisness servers it does.

 

[sohcrates]

for the home environment, the only real jollies i get from massive uptime come in the form of running "sysinfo" commands in IRC channels..whereby everyone thinks i'm cool cause i have a big uptime!

suprisingly...the fun of that wears off pretty quick....

 

[MikeO]

13 days so far. Usually I only reboot when I have to (installed program asks to reboot or something similar). Oh yeah, running Win2k.

 

[Geekbabe]

<< Many of my enterprise-class customers have Windows NT/2K machines that haven't been rebooted in six months or more. For many of my customers, reboots are the result of OS updates and not stability issues. So if these same customers had chosen to defer OS updates, it's conceivable that their uptimes would be extened into a timeframe measured in years.

Of course, defering OS updates like that is not practical.

OS updates, however, can be scheudled. In this thread we haven't differentiated scheduled vs unscheduled reboots, but I think we'd all agree that the unscheduled reboots are of greater concern.

The number one cause of unscheduled reboots (in my experience) is blue screens. The number one cause of blue screens: antivirus software. (That, and HP 4000/8000 drivers on NT4 Terminal Server machines.) Interestingly, *all* antivirus vendors seem to be about equally guilty of crashing machines. The good news is that there are FAR fewer crashes from antivirus software than there were three years ago.

If you have performance problems when running apps, and you truly want to troubleshoot and resolve the issue instead of rebooting, fire up performance monitor and look for processes with extensive numbers of open handles, memory usage that keeps going up, etc. Although it's very rare that an app will truly bring down the OS, it's not so difficult for an app to consume so many resources that the OS is useless from a practical standpoint. If you find such an app and kill it, OS performance should resume to normal levels. >>




Very,very good points !!!!


I'm quite spoiled by the overall stability and robustness of WIN2K

 

[BooneRebel]

Indefinitely. On my personal workstation (W2K), it doesn't come down unless there's a power outage or I install a software package that -has- to have a reboot (replacing system files, etc.) On the server side I've got one box that's been up for 167 days, the only downtime is for maintenance issues.

 

[Supermercado]

I don't reboot unless I've just installed a program that requires it, the power goes out, or Half-Life causes a lock-up. It usually turns out to be about every 4-5 days that I have to reboot. Running Win2k.

 

[Platypus]

<< The only times I've ever had to reboot my Linux systems is for kernel upgrades, and one time I screwed up a comp beyond repair (experimentation as root is NOT OK) and had to reboot to re-install everything.

My record is 31 days. I hope to get a nice 180-day uptime streak sometime. >>




No.. experimentation as root is quite ok, you just have to pay for your consequences. What good would it be if you couldn't learn from yourself?


Edit: my record uptime was 79 days(bsd), then the power went out. After that reboot, 42 days ago, it has been running since.

 

[BigJohnKC]

I never reboot my win2kpro rig at home unless some program crashes or something I installed needs to reboot the machine. I think the last time I rebooted was when I installed Kazaa after Morpheus quit working. :| It usually gets rebooted every couple of weeks or so.

 

[nightowl]

The only reason that I reboot my main PC here at school is because APM no longer turns off my monitor after a specified time. Other than that I could keep it up for weeks now that I reformatted a 2 months ago.

 

[Orsorum]

About 3-4 days, on average.

 

[jhu]

my router's been up for 57 days so far

 

[Platypus]

<< The only reason that I reboot my main PC here at school is because APM no longer turns off my monitor after a specified time. Other than that I could keep it up for weeks now that I reformatted a 2 months ago. >>



Correct me if I am wrong, but can't you just turn off your monitor without rebooting your box?

 

[nightowl]

Yes, I could just turn off my monitor, but I do not always remember to turn it off when I leave for class. Mainly, I like the convience of the monitor turning itself off.

 

[Cattlegod]

29 days 18h up time for my system. only reason i rebooted was i had to change out some hardware.

 

[pulse8]

11 days 16 hours and going strong!

A new record for me!

I hope the next time I shut it down is to install my P4 Northwood.

 

[Gunbuster]

95 day(s), 8 hour(s), 10 minute(s), 59 second(s)

 

[Hyperblaze]

My biggest uptime for my computer was 72 days.

This was using Mandake Linux 7.2

 

[Amused]

XP pro here. I've never had to reboot because of performance issues or errors. Only when I load software, change a setting that requires a restart, or shut it down to muck around inside my case.

This is a HUGE change from win 98. It's nice to have the stability of 2K, and the game performace of 9x in one OS

 

[BeauJangles]

My computer will stay up as long as i want, I usually shut it down before I go to bed each night though. (XP pro, btw).

 

[Jerboy]

five times a day. Frindoze Me