2 ms·
Right, like I said I don't think any init system has actually figured this out but that is what as an admin I actually care about rather than startup times or t
by bandrami 3y ago
Right, like I said I don't think any init system has actually figured this out but that is what as an admin I actually care about rather than startup times or the aesthetic properties of the configuration files. You would need some kind of semantics that define what it means for a system to be "ready". In practice we tended to lean towards some kind of polling of the service itself (which is at least slightly better than "sleep 3" or whatever).
Now, it's true that if applications would adopt systemd's Notify system this could really help, but this is equivalent to saying "if software were different it might be better".
- ilyt 3y agoYeah its PITA problem. Like, service can fork, return okay then die after a second coz someone set memory size wrong. No real sensible way for init system to prevent it. Or takes 5 minutes to load then hits some bad data and crashes. We just set services on auto-restart, monitor it and flag alert if service is restarting too often.