Bug#752055: ambiguous option name Type=forking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/05/15 09:35, m...@linux.it (Marco d'Itri) wrote: On May 04, Harald Dunkel ha...@afaics.de wrote: I know the difference between doing a fork(2) and creating a daemon. Instead of pointing to foreign documentation I would suggest to call it type=daemon, if systemd creates a daemon, This is part of the Systemd API and will not be changed for frivolous reasons. It will definitely not be changed as a Debian-specific patch. frivolous? :-) or to explain in the man page, why creating a daemon has been called forking, ignoring all the other man pages you have listed. It looks clear enough to me, but maybe you can persuade the upstream maintainers to accept a documentation patch. Probably you are right to stay compatible with upstream. I wouldn't like to make things worse. Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVUyjxAAoJEAqeKp5m04HL/GkH/2sYq3i+VzrZm8UE7Vb7MXAC xEgZASbdLx3dE6ZEY7oKFpBF3LGp/b+E5BJ3g2zWtp+W5HUv7gEmV9ik1/9wxgAg 6hL3Md9g7cmckcsCLieTPxny/g11Oc0xWGo3Krd2oJbp83q2q5yH2C1Vr09hlTXV 99TVlrPkqNQ8yAv4PiPpVWmxU7yZ7r26fJybQBYhrXPVwrF7/TwybDkQAMIJqXUJ XXAga3JeUJTLR8OoW9+tKte9Abc/UDC8UJacC8HcziRBpDeds8wXAJSqkQQVffvn R825ycy6L4yKOq61vm7M9dgKafBjn9PXC+G9XgpUErgsjT55dQ8bwfa7ACBDtzo= =YaXZ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752055: ambiguous option name Type=forking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I know the difference between doing a fork(2) and creating a daemon. Instead of pointing to foreign documentation I would suggest to call it type=daemon, if systemd creates a daemon, or to explain in the man page, why creating a daemon has been called forking, ignoring all the other man pages you have listed. To reduce confusion and to keep a common terminology I would recommend option 1. Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVR9bBAAoJEAqeKp5m04HLFBcH/3XWAze++quHcn4QKjAnB3nQ XvQ8U2DLhbfulZ4diemPmPHfTO7JPCyQ67Oyt49LgJw2k4zHIqMPdfMNB5uw15Od vjrFvvHUxkvlt7cADUlyY2rTslM54kg1iv44urvSHEm4gpspSsWorm9DkmV2HmnO OXJ04sUehs8buTapRmgUR/o8boaW8IZU7W/h3CsCefr6EsVdSfsH8SWs9IPTx27y CWUzhQcqkj6j1TjlGJkjJ6Nsn9649muEaPGM483I778CJsLJ1FHuFrUzUi0MMXWv yqe6R+vO8GuesTGptqn0Cuyw9dqhbt1k65sXgLXzhEFzTnS9LHjLCxQA7YKK+mw= =bvMj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752055: ambiguous option name Type=forking
Hi Harald, Harald Dunkel wrote (19 Jun 2014 07:24:03 GMT) : Doing a fork and becoming a daemon process are not the same. Something like Type=forking in the *.service file is ambiguous. Does systemd provide a controlling terminal to the ExecStart job that has to be dropped, before forking again? Please clarify. daemon(7) has more details, including the fact that traditional SysV Daemons must: 6. In the child, call setsid() to detach from any terminal and create an independent session. 7. In the child, call fork() again, to ensure that the daemon can never re-acquire a terminal again. Now, this information can easily be found using $web_search_engine, but I agree that it should be easier to find it when reading systemd.service(5). If the section about Type=forking in this manpage did point to daemon(7), would your concerns be addressed? The man page has a pretty weird description of the behavior of traditional UNIX daemons. I agree it's vague, but apparently it has some well-accepted meaning. https://en.wikipedia.org/wiki/Daemon_(computing)#Creation reads: the common method for a process to become a daemon, when the process is started from the command line or from a startup script such as an init script or a SystemStarter script, involves: * Dissociating from the controlling tty (I realize that pointing to Wikipedia feels weird here.) Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752055: ambiguous option name Type=forking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: systemd Version: 204-10 Doing a fork and becoming a daemon process are not the same. Something like Type=forking in the *.service file is ambiguous. Does systemd provide a controlling terminal to the ExecStart job that has to be dropped, before forking again? Please clarify. The man page has a pretty weird description of the behavior of traditional UNIX daemons. Many thanx Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJTopATAAoJEAqeKp5m04HLA4UH+gMXJVAmJ6hSkuUNCisiyyqX ZIdmh2qD1no1wPcR8iSFjqt4W1N1kd2JstO5sI0QjT8BIs8KxiZ8xs2EeUQGowZL hfZZGizZh6+31l2jP5LuSe/Kymm/ZfDUstVzLm/EyzuFUSgW7YChz0TVGJidzjmz 82uVIy23iM0xtTFhYXEe6r1hJZ8mbczB06y6qZfStHF5upXWSkdLI1XC5hrqlEh9 LGC2iC6V7ZiUL5lPasBoeau7RH2/k6wVU0aT6m2VF0hh2lDJi0obU+cZ3OJzZDVO 8kZQ9CiTkoirIFJbPTrZTHnRtQiA1PB6Iv87SBoRtaqKxTNvbLbbk4i+Wjl9bOc= =il+L -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
