Bug#752055: ambiguous option name Type=forking

2015-05-13 Thread Harald Dunkel
-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

Bug#752055: ambiguous option name Type=forking

2015-05-04 Thread Harald Dunkel
-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

Bug#752055: ambiguous option name Type=forking

2014-11-17 Thread intrigeri
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

Bug#752055: ambiguous option name Type=forking

2014-06-19 Thread Harald Dunkel
-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,