On 15.04.2017 11:42, Steve Litt wrote:

> Once upon a time, daemon self-backgrounding was necessary, and this

nohup (or something similar) was not sufficient ?

I don't know when start-stop-daemon was incarnated (related to
daemontools ?), but IMHO it seems to handle the daemonizing quite well.

IMHO, a daemon should not daemonize itself, but always leave that to
the some supervisor or startup tool. And if it can handle one connection
per process, it should even leave socket listening to something
inted-alike. Even, for multi-connection clients, opening the listener
socket should be left to it. (people can still optionally provide
wrappers that glue everything together to an completely-standalone
server machinery, for convenience).


--mtx