Poll: What do you use for Unix process management/monitoring?

Re:Poll: What do you use for Unix process management/monitor... by jacques_chester on Tuesday July 23, 2013 @06:20AM (#6089139)

> I make sure I write processes that don't fail.

Please name one major, non-trivial network system software that has gone for 5 years, 122 days without a fault in production anywhere.

Engineers in other disciplines make best efforts not to fuck up. And then they accept that they, or others, will fuck up anyhow and they plan for that.

So do we. And so we should. Betting it all on Red 19 is a strategy of roulette, not serious work.

[ Parent | on HN ]

Re:Poll: What do you use for Unix process management/monitor... by harrytuttle on Tuesday July 23, 2013 @06:23AM (#6089143)

We don't bet on that, we aim for that.

[ Parent | on HN ]

Re:Poll: What do you use for Unix process management/monitor... by jacques_chester on Tuesday July 23, 2013 @06:32AM (#6089168)

I can sense we're about to have a circular argument based on where to draw the boundaries of responsibility.

My point is that betting entirely on one strategy for mitigating faults is unnecessarily risky. Especially when additional levels of mitigation are easily installed and configured. In your other post you even point out a series of things that you do.

I don't see why process management is of a different kind.

Edit: removed unnecessary grandstanding.

[ Parent | on HN ]