From: Soares Chen <soares.chen@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: Zsh scripts leave defunct processes when running under docker exec
Date: Sun, 15 Feb 2015 22:03:05 +0800 [thread overview]
Message-ID: <CACUDQOHGXoOHLLrtYETuDYeAHzUq=B3LrpJ3bjj0Ge6hHGJMfw@mail.gmail.com> (raw)
In-Reply-To: <150214105834.ZM4462@torch.brasslantern.com>
On Sun, Feb 15, 2015 at 2:58 AM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> I don't know if Chet is reading this and wants to chime in, but I suspect
> bash is not expecting to take over the PID=1 role of init, either.
I'm not sure how bash work differently from zsh, but my example script
works fine if changing the first line to run using bash.
I have talked to people at Docker. From my understanding, Linux has a
feature called subreaper that can take over the role of init and
become the parent of orphaned descendant processes. In this case on
top of having different PID namespaces, `docker exec` is spawning a
process called nsenter to act as the subreaper. It is responsible to
reap defunct processes by handling SIGCHLD. With it being the
subreaper, all orphaned/defunct processes are captured by nsenter
instead of propogating to the actual init process inside the
container.
So current Docker didn't handle SIGCHLD properly and therefore causing
all orphaned processes to become defunct. It is probably not a problem
of zsh, just that its way of implicitly exec and orphaning child
processes in the final command causing this bug to become obvious in
Docker.
Thank you Bart for explaining and now I know a little better on how
zsh, Docker, and Linux works!
Soares
next prev parent reply other threads:[~2015-02-15 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 4:43 Soares Chen
2015-02-11 6:53 ` Bart Schaefer
2015-02-11 10:11 ` Peter Stephenson
2015-02-11 16:13 ` Bart Schaefer
2015-02-13 10:39 ` Daniel Shahaf
2015-02-14 18:58 ` Bart Schaefer
2015-02-15 14:03 ` Soares Chen [this message]
2015-02-15 18:20 ` Peter Stephenson
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='CACUDQOHGXoOHLLrtYETuDYeAHzUq=B3LrpJ3bjj0Ge6hHGJMfw@mail.gmail.com' \
--to=soares.chen@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).