3 ms·
practically every system is running service manager of some sort (supervisord, daemontools, runit, or infamously systemd etc), and with a service manager daemon
by zokier 2y ago
practically every system is running service manager of some sort (supervisord, daemontools, runit, or infamously systemd etc), and with a service manager daemonization is something between completely useless and actively harmful. as cks explains in the post, daemonization is truly relevant only if you are starting your daemons directly somehow somewhere, and that went out of fashion somewhere in the turn of the century.
- kazinator 2y agoPrograms that deamonize should have a way (e.g. command line option) to opt-out of it, or opt-in. Unconditional daemonizing interferes with debugging, for instance. That's bad. But don't forget that the service managers themselves have to daemonize. :) The programs which they launch don't have to daemonize only because their parent did that already.
- Joel_Mckay 2y agoInteresting, I think we treat system services differently than utilities. A given host assigned capabilities should not require manual intervention, but should allow manual interaction for testing and debugging. Insisting one method is superior, is often from people that have never hit the terminal spawn limit on a host. Best of luck, =3