Hi Martin,
the operating system I'm using is SUSE Linux 10, kernel 2.6.13.
You're right, I was missing something. After you told me that it
couldn't be Python preforming wait() on SIGCHLD, I decided to
investigate further.
My application requires access to a Informix database, and uses
> From my experience, this primitive will fail with 'no child processes'
> at the waitpid call if the forked child dies very quickly - before the
> parent is scheduled back for execution. This seems to happen because
> Python has a default SIGCHLD handler that, in this case, will reap the
> proce
Hi,
I am working with the subprocess.py module in Python 2.4.4 and I am
confused about it's functionality. It uses the standard pipe-fork-exec
method to start a subprocess:
# create pipes
pid = fork()
if pid == 0:
# child
exec(...)
# parent
status = waitpid(pid, 0
