[ale] uptime?

[Gary Maltzen]

FWIW, it is NOT me having those problems. I *am* part of a WINNT server management team and our servers do *not* need routine rebooting; I was just responding to another subscribers dilemma with alternative solutions.

The point of having routine reboot is to clear pending problems (like memory leaks) before they become show-stoppers. That issue is relatively platform-independent; if, for example, one of your Apache modules has memory leaks you can either solve the problem "programmatically" (modify the code) or "administratively" (periodic reboot).

I *am* encouraging use of Linux/Apache at work. In fact, my second "fait-accompli" was installation of Apache under NT so staff could see the output of our WebTrends analysis at their personal workstation. (The first was installation of MRTG under Linux to monitor our Cisco router).

Please do not make the mistake of ascribing to me either an NT-centric or Linux-centric orientation. I am not interested in participating in OS wars; I'm interested in providing an appropriate and efficacious solution to a given problem.

Gary/MCSE
Compuserve WINNT Sysop


>You are forgetting the fact that those apps need the OS (WinNT) to be
>functioning reliably in order for them to work.  The only reason one
>would need those apps is because the WinNT kernel and associated apps
>can be very unreliable.  
>
>Maybe you should you have a second computer to monitor your first, and
>then have it reboot the other one when it is locked up?  Perhaps you
>could use a video camera to detect the presence of a BSoD on the other
>box.  However, it is more likely that the WinNT system w/ the video
>camera will fail first. Hell, it would probably be cheaper (from a
>purely fiscal conservative standpoint) it hire a slacker kid from McD's
>to just watch the monitors and press the power switch when one of them
>turns 'blue'.  LoL  (someone, somewhere, probably does this).

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.