3 ms·
I now expect a few features from anything that aims at replacing my init and service manager. Beyond booting the system, I want to manage daemons: * ease of us
by idoubtit 7y ago
I now expect a few features from anything that aims at replacing my init and service manager. Beyond booting the system, I want to manage daemons:
* ease of use: I don't want to deal with background/foreground processes, storing PID in files and hacks like the old start-stop-daemon.sh.
* reliable services: if it stops, restart it automatically. But stop hammering if it fails repeatedly.
* sandboxing: this service must have no access to the network nor to /home, etc.
This "lightweight replacement" does not have this small subset of features, so it's more an alternative init than a replacement of systemd.