In my example the dash process still exists until both sleeps have been
finished. I have written a small testcase in C to check if its an
applications fault if there are zombie processes:
#include
#include
int main()
{
FILE *pipe;
if((pipe = popen("echo", "r")) == 0)
{
Catching SIGCHLD in dash does not help in this case, since dash is
already gone (execve'ed) by the time the SIGCHLD would come.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/915158
Title:
Process is
Maybe as a feature dash could catch the SIGCHLD signal to handle the
zombie process much faster.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/915158
Title:
Process is not closing
To manage notific
You can see the same problem with any shell with a command like
(sleep 3 & exec /bin/sleep 6)
because most versions of /bin/sleep do not clean up zombies (here, a
zombie from an inherited child process).
Dash does not consider the existence of a background process a reason to
fork for an externa
I have found a command which will cause a process to turn into a zombie
process:
dash -c '(sleep 3 & sleep 6)'
If "sleep 3" finishes it will turn into a zombie process and only close
if "sleep 6" finishes. With bash all is working fine (but bash is
creating "bash -c (sleep 3 & sleep 6)" 2 times)
It is not possible for me to say exactly which package is causing this
problem. It can affect every application so it is a global problem.
Maybe it is related to bash or the Linux kernel.
** Package changed: ubuntu => bash (Ubuntu)
--
You received this bug notification because you are a member o
** Attachment added: "2012_01_12_05_41_48-1.png"
https://bugs.launchpad.net/ubuntu/+bug/915158/+attachment/2668971/+files/2012_01_12_05_41_48-1.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/915
