>> Of course, we shouldn't expect everyone to use systemd-run because >> that's locking into an init system which should quite obviously be >> avoided. > > That, again. > > The person who suggested using systemd merely pointed out that the task > of turning a regular process into daemon is trivially solvable using > systemd-run. This kind of implies that if the OP uses systemd, they > could just read the appropriate manual page and have their task solved.
When I read it, it came across a bit different from that. It sounded like that was to be considered "the" approach instead of one option. Related to a bit further down... >> It does seem like daemonize serves a very unique purpose where >> start-stop-daemon is a bit overkill or cumbersome. It's obviously >> something that would never be used in an init script where >> start-stop-daemon is actually appropriate. However, I can see a few >> situations where I would launch this from a script. Not only that... >> but I can see myself rewriting some scripts to make use of this if it >> were included in Debian. > > Two points: > > * It seems you have missed a message in this thread mentioning the > `daemon` package which is in Debian (since ages) and is able to > daemonize a regular program. You're right. I missed (spaced on) that note. Which helped contribute to my feelings above. I guess my argument is invalid. I'm sorry for the noise then! > * Not to bash the maintainers of `start-stop-daemon` but this program > is sort of a hack as it can't do most of what's expected from a > daemonizer: it can't capture the standard output streams of the > child it spawns and redirect them to syslog, and it can't restart the > child when that dies. It can be a pain in the bum, but does (mostly) work... I need to start playing with daemon! -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAL4L7=d7dpzvsfixytjkkammqqgaqgwuma7a0axylkmhyx-...@mail.gmail.com
