From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-34544-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 26652 invoked by alias); 14 Feb 2015 18:58:49 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 34544
Received: (qmail 19160 invoked from network); 14 Feb 2015 18:58:38 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
	autolearn=ham version=3.3.2
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.1 cv=CoYIqc8G c=1 sm=1 tr=0	a=FT8er97JFeGWzr5TCOCO5w==:117
 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8	a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10
 a=0HtSIViG9nkA:10	a=mjfhUf4F8nJ6PhpxFywA:9 a=CjuIK1q_8ugA:10
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <150214105834.ZM4462@torch.brasslantern.com>
Date: Sat, 14 Feb 2015 10:58:34 -0800
In-reply-to: <20150213103919.GD1848@tarsus.local2>
Comments: In reply to Daniel Shahaf <d.s@daniel.shahaf.name>
 "Re: Zsh scripts leave defunct processes when running under docker exec" (Feb
 13, 10:39am)
References:
 <CACUDQOE1y34_b_OF8g4kf7JJisyBc0T5Chr_E8xkZiyO_kTRGQ@mail.gmail.com>
	<CAH+w=7YBD6ocsd6+PL-AgpkDt4-O2AHPQa06U2=b7s2LfeORQw@mail.gmail.com>
	<20150211101130.2ac4d9b5@pwslap01u.europe.root.pri>
	<150211081345.ZM17542@torch.brasslantern.com>
	<20150213103919.GD1848@tarsus.local2>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-workers@zsh.org
Subject: Re: Zsh scripts leave defunct processes when running under docker exec
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

On Feb 13, 10:39am, Daniel Shahaf wrote:
} Subject: Re: Zsh scripts leave defunct processes when running under docker
}
} Bart Schaefer wrote on Wed, Feb 11, 2015 at 08:13:45 -0800:
} > That would help, but I don't think that's everything, because zsh would
} > still not reap background grandchildren of children which exited first.
} 
} Note that in the example, it is bash which runs as pid 1, not zsh.
} The zsh process running the script and the interactive one spawned by
} 'docker exec' have pid != 1.

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.