From: "Toralf Förster" <toralf.foerster@gmx.de>
To: UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] 1 zombie process after starting a 23 bit UML guest
Date: Fri, 09 May 2014 23:47:38 +0200 [thread overview]
Message-ID: <536D4CFA.2020802@gmx.de> (raw)
In-Reply-To: <536D45B3.8040606@gmx.de>
On 05/09/2014 11:16 PM, Toralf Förster wrote:
> Today I realized that current kernels produces a zombie proces :
>
> tfoerste@n22 ~ $ ps aux | grep 'Z' | grep '<defunct'
> tfoerste 10918 0.0 0.0 0 0 ? Zs 23:11 0:00 [linux-v3.12-48-] <defunct>
>
> The last kernel which does not produce such a zombie is kernel 3.11
>
> I do not use a xterm for any output, just "con0=fd:0,fd:1 con=pts". However I'm unsure if this is an already known issue (and I just forgot it) or whether I should kick my test box to bisect the guelty commit id between 3.11 and 3.12
>
My mistake,
the zombie process is created, if I start the UML just as a back ground process.
If I prepend my command line with "nohup" in such a case then a zombie process isn't made.
--
Toralf
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2014-05-09 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 21:16 [uml-devel] 1 zombie process after starting a 23 bit UML guest Toralf Förster
2014-05-09 21:47 ` Toralf Förster [this message]
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=536D4CFA.2020802@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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