| 8. Policy rules for support for init systems must: | | (a) Specify the use of a non-forking startup protocol (for | upstart and systemd), I'm not sure about upstart, but systemd is perfectly happy with daemons which double fork (Type=forking in systemd parlance). It is mildly discouraged, because:
1. it is hard to get right 2. it is more code than the other options 3. it is easier to start the program manually if non-forking protocol is used For new code, other protocols are certainly better. But for existing daemons which work correctly, points 1 and 2 don't matter, and 3 is not important enough. This requirement might force mantainers to modify some hairy internals in the startup code of daemons to avoid double forking. This seems pointless, as in most cases it wouldn't result in any noticable difference in speed or behaviour or correctness. I think this should be changed to: | 8. Policy rules for support for init systems must: | | (a) Encourage the use of a non-forking startup protocol (for | upstart and systemd), Zbyszek -- To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140102215430.gh2...@in.waw.pl
