I am a sysadm, having a few NT servers, couple AIX boxes, and a bunch of Linux boxes.
I agree that on NT, rebooting is often the only way to fix things. And in many cases when you change some configuration, you are forced to reboot. I see this forced rebot as a way to force the sysadm to clean up the leftover junk from MS apps.
On a unix box (including one Linux box running 358 days on a 486dx2 named 'crasher' when it was running Windows), reboot does NOT solve the problem. A reboot might delay the time it takes until the symptoms are there again, but for suredoes not solve the problem.
I do not see uptime as a pride thing. But I do see uptime as something related to general stability of the OS. If an application can force you to reboot, I would not call it a good multi-tasking protected memory OS. I especially hate how user space apps can kill NT (NT 4 and 2000 are worse than Win 3.51 as more junk drivers are running in priviledged mode).
On a unix box, doing a/etc/rc.d/init.d/whateverprogram restart or a kill -HUP usually solves the problem.
I see average uptime as some indication of OS stability. The only valid reasons for reboots are hardware upgrades and kernel upgrades. And kernel upgrades are usually a sign of OS instability or something else. So the only thing that is really an excuse for reboots are hardware upgrades.
People also forget, that the earth in its orbit around the sun is getting about as close as it gets in the eliptical orbit. This also accounts for some of the global warming!
Slashdot Mirror
I am a sysadm, having a few NT servers, couple AIX boxes, and a bunch of Linux boxes.
/etc/rc.d/init.d/whateverprogram restart
I agree that on NT, rebooting is often the only way to fix things. And in many cases when you change some configuration, you are forced to reboot. I see this forced rebot as a way to force the sysadm to clean up the leftover junk from MS apps.
On a unix box (including one Linux box running 358 days on a 486dx2 named 'crasher' when it was running Windows), reboot does NOT solve the problem. A reboot might delay the time it takes until the symptoms are there again, but for suredoes not solve the problem.
I do not see uptime as a pride thing. But I do see uptime as something related to general stability of the OS. If an application can force you to reboot, I would not call it a good multi-tasking protected memory OS. I especially hate how user space apps can kill NT (NT 4 and 2000 are worse than Win 3.51 as more junk drivers are running in priviledged mode).
On a unix box, doing a
or a kill -HUP usually solves the problem.
I see average uptime as some indication of OS stability. The only valid reasons for reboots are hardware upgrades and kernel upgrades. And kernel upgrades are usually a sign of OS instability or something else. So the only thing that is really an excuse for reboots are hardware upgrades.
People also forget, that the earth in its orbit around the sun is getting about as close as it gets in the eliptical orbit. This also accounts for some of the global warming!