https://dev1galaxy.org/viewtopic.php?id=5867
Taking a dependency on systemd is a strange choice for a project who's entire point is ripping out Poettering's second-to-last train wreck.
Is there any reason why all individual tools should learn how to daemonize (in addition to or in replacement of running in the foreground)? There's external tools that can take care of that uniformly, and using the latest/greatest syscalls for it. That seems better than every application including this code. As highlighted in the thread, there are other programs that can launch+daemonise another a process (like the aptly named [daemon(1)](https://manpages.debian.org/unstable/daemon/daemon.1.en.html) tool). Seems more like the UNIX way, from the outset.
Also, it’s incredibly complicated. (I looked at the source.)
Here’s a writeup of a simple daemon: https://pavaka.github.io/simple-linux-daemon-tutorial/
Given that it’s typed once (by the daemon author, and not the end user), it seems like a big win vs. daemon(1) to me.
