Charles-François Natali neolo...@free.fr added the comment:
The problem I have with the solution that is currently implemented is that
subprocess is waiting for the spawned child although the child is not running
anymore.
In my case this issue occured when invoking samba or the small
Felix Steffenhagen fe...@sutus.com added the comment:
The problem I have with the solution that is currently implemented is that
subprocess is waiting for the spawned child although the child is not running
anymore.
In my case this issue occured when invoking samba or the small sample daemon
New submission from Felix Steffenhagen fe...@sutus.com:
subprocess.Popen.communicate() hangs for daemonized subprocesses that leave a
pipe open. The python caller, invoking the daemon subprocess, runs as long as
the daemon process. This happens on POSIX platforms with python 2.7 as well as
Changes by Felix Steffenhagen fe...@sutus.com:
--
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13422
___
___
Python-bugs-list
Charles-François Natali neolo...@free.fr added the comment:
subprocess.Popen.communicate() hangs for daemonized subprocesses that
leave a pipe open. [...] which leaves stderr pipe open.
Of course: the daemon process (spawned by the second fork()) inherits the
subprocess's stderr (since file
Gregory P. Smith g...@krypto.org added the comment:
This looks like a bug in your daemon not in subprocess. Your daemon is
intentionally not closing its inherited stderr fd.
--
nosy: +gregory.p.smith
resolution: - invalid
status: open - closed
___
Felix Steffenhagen fe...@sutus.com added the comment:
The behavior that the daemon is not closing stderr is intentional to reproduce
the issue. This problem occured to me when I was invoking the samba init script
on a Gentoo system.
Invoked from a bash, the initscript was terminating fine. But
