[ale] uptime?

[Gary Maltzen]

 I'm sorry you find support for that suggestion offensive. Sometimes there are more pressing issues at hand and an "acceptable" solution beats no solution.

 Note: I work in a real company that depends on it's revenue stream for it's livelihood.

 Frankly, although we have not yet had to employ RtRR(c), we would if it meant we would minimize interruption to our client base. Certainly we would try to fix the problem, but we won't take our systems down while we are investigating the problem - and whether or not we have time to investigate that problem depends on our priority mix.

 I have several friends undergoing chemo-therapy for cancer; this is an "acceptable" (if unperfect) solution - they and I continue to enjoy each other's company. A scientifically "managed" solution (no results until the "correct" solution was found) would leave me with somewhat fewer friends.

>> The point of having routine reboot is to clear pending 
>> problems (like memory leaks) before they become 
>> show-stoppers. 
>
>I did find this one comment by you utterly offensive.  Especially to
>those of us who consider systems management a science, not a science
>project.  Just the thought of "Reboot-to-Restore-Resources" RtRR (c)
>being associated with good job skills sends a shiver up my spine. 
>Imagine if you had to periodically shut your $30,000 car off, as you
>were driving down the interstate, to reset unintended leaks.  You would
>have a vicious attitude towards Detroit for insulting you with such a
>lousy design.  Hmmm, Maybe that's why sales guys from Redmond remind me
>of car salesmen. :)

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