January 24, 2017 4:31 PM, "Iznogoud" <iznogoud at nobelware.com> wrote: > Right, I anderstand. But we will disagree on two things and I prefer to leave > it at that: (a) using the filesystem, especially with a complex directory > structure _and_ with non-intuitive operations like linking, unliking and > rm-ing is far from elegant in my book, and (b) unix is all about configuration > files, which are not complicated if one studies documents and manual pages. I have no idea how you decided we disagree about configuration files. My question was about daemonizing applications, not about configuring them. Your configuration files are a red herring. Please read my original question. > Ansible, jailing processes, automation and virtualization have requirements > and some things can be made simpler with the (seamingly) complex (in my book) > operations. But I am of the idea that this sort of "requirement" should not > be feeding back to the structure of a really well functioning OS. I could be > dead wrong about this and I am an Ansible iliterate at best. Maybe that is > why I run Slackware. Ansible has nothing to do with Slackware, so your comment makes no sense. You seem to be saying "linux is a really well functioning OS, so we shouldn't make any changes to it." That is an interesting attitude. To recap: I asked about daemonizing applications, and got one useful response ("monit", which is more about monitoring daemons than daemonizing them, though it does have rudimentary capabilities for them), and a bunch of responses from you which were off topic and did not answer my question. I'm still researching this, and looking for opinions. At the moment "runit" is still in the lead, though if the debian package replaces init out of the box, I will probably choose something different. John