From: Alex Riesen <riesen@synopsys.COM>
To: linux-kernel@vger.kernel.org
Subject: 2.5.4-pre1: zombies in exit()
Date: Thu, 7 Feb 2002 08:32:39 +0100 [thread overview]
Message-ID: <20020207083239.B26413@riesen-pc.gr05.synopsys.com> (raw)
Hi,
what i did is:
$ find /some/nfs/volume -type f -print0 | xargs -0 cat > /dev/null &
$ find /some/nfs/volume -type f -print0 | xargs -0 cat > /dev/null &
$ find /some/nfs/volume -type f -print0 | xargs -0 cat > /dev/null &
$ find /some/nfs/volume -type f -print0 | xargs -0 cat > /dev/null &
$ wait
and on other xterm:
~/some-kernel$ make dep bzImage modules -j2
and another one:
~/some-kernel$ make dep bzImage modules
kernels finished, i've pressed Ctrl-C on the console with wait
(i wanted check interactivity, and was pretty amazed).
Started QPS(a tool like gtop) just to see two of the find's
are still there. Zombies, yes, sleeping in exit().
Closing the console removed the zombies. That's stock bash-2.05a,
and it hadn't such problems before (although i'm going to try to
reproduce that situation in exactly same way under 2.4.18-pre8-K2
todays night).
-alex
reply other threads:[~2002-02-07 7:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020207083239.B26413@riesen-pc.gr05.synopsys.com \
--to=riesen@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox