From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28445 invoked by alias); 17 Dec 2014 07:31:44 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 33987 Received: (qmail 5866 invoked from network); 17 Dec 2014 07:31:42 -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=Ko/6AtSI c=1 sm=1 tr=0 a=FT8er97JFeGWzr5TCOCO5w==:117 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=A92cGCtB03wA:10 a=kUUa_hi7vCAAAkvKIKQA:9 a=CjuIK1q_8ugA:10 From: Bart Schaefer Message-id: <141216233206.ZM19494@torch.brasslantern.com> Date: Tue, 16 Dec 2014 23:32:06 -0800 In-reply-to: Comments: In reply to Chirantan Ekbote "Bug in interaction with pid namespaces" (Dec 16, 3:07pm) References: X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Bug in interaction with pid namespaces MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Dec 16, 3:07pm, Chirantan Ekbote wrote: } } I think I've found an issue with the way zsh interacts with pid } namespaces [1]. Specifically the problem is that when zsh is launched } immediately following the creation of a new pid namespace it doesn't } take ownership of the process group There seem to be a few other potential problems with this using zsh as the init process in a namespace; for example: - the suspend command should never stop the shell (even with -f) - the shell should refuse normal exit when NOHUP is set and there are any jobs still running (because as I understand it, it's not possible for any processes in the namespace to survive after the init exits) How far down this path do we want to go?