> proper daemons (fork, cd /, close([stdin, stdout, stderr]) and the rest), some are a little worse to say the least. And more often than not, the later is your

> proper daemons (fork, cd /, close([stdin, stdout, stderr]) and the rest), some are a little worse to say the least. And more often than not, the later is your super business critical important app built in house by incompetent developers. "proper daemons" are broken by design. Perhaps your "incompetent developers" know something that you don't? https://cr.yp.to/daemontools/faq/create.html https://cr.yp.to/daemontools/faq/create.html How can I supervise a daemon that puts itself into the background? When I run inetd, my shell script exits immediately, so supervise keeps trying to restart it. Answer: The best answer is to fix the daemon. Having every daemon put itself into the background is bad software design.