4 ms·
On a server I'd usually want it to limp along too... Better fire an alert but keep happy customers than cause a massive outage just because of someone's overly
by londons_explore 5y ago
On a server I'd usually want it to limp along too... Better fire an alert but keep happy customers than cause a massive outage just because of someone's overly strict checkfail...
It depends really what your server does, and what the consequences of it doing the wrong thing are.
- michaelmrose 5y agoOr just don't put stuff that crashes in pid1
- afc 5y agoYeah, great idea: rather than worry about how to deal with software bugs, just never have bugs...
- michaelmrose 5y agorunit.c is 330 lines of code Keeping it small and simple to minimize bugs is perfectly viable and reasonable.
- a1369209993 5y agoExactly. This is why systemd is a terrible design. The fastest and most secure code, that never crashes and never needs patching, is code that doesn't exist.
- modshatereality 5y agoseriously, if you're doing allocations in pid1 you fucked up.
- bigiain 5y agoIf the consequences of one server wedging itself is a "massive outage" and "unhappy customers", then you probably don't really care about that outage or those customers. If you don't have enough redundancy and alerting and automated disaster recovery to keep your customer facing shit up when one server panics, you're just relying on luck to keep your customers happy. Fire an alert, remove that server from the load balancer, and fix the problem without your customers even noticing. Or make sure if you're running a hobby-project architected platform that your customer expectations and SLAs are clear up front, and let it go down until Monday morning when you'll get around to fixing it.