From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11322 invoked from network); 27 Jul 2000 10:14:19 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 27 Jul 2000 10:14:19 -0000 Received: (qmail 22761 invoked by alias); 27 Jul 2000 10:14:06 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 12404 Received: (qmail 22754 invoked from network); 27 Jul 2000 10:14:04 -0000 Date: Thu, 27 Jul 2000 06:12:29 -0400 From: Chet Ramey To: schizo@debian.org Subject: Re: wait for non-child PID Cc: akr@m17n.org, zsh-workers@sunsite.auc.dk Reply-To: chet@po.CWRU.Edu Message-ID: <1000727101229.AA16652.SM@nike.ins.cwru.edu> Read-Receipt-To: chet@po.CWRU.Edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-In-Reply-To: Message from schizo@debian.org of Wed, 26 Jul 2000 19:09:53 -0400 (id <20000726190953.A22895@scowler.net>) > > % wait 1 > > > > blocks forever. (It is interruptible.) > > > > bash detects that the PID is not child of the shell. > > I'm glad that zsh's wait will wait on processes that aren't children of the > shell. Is there a reason that it shouldn't? Because the shell will never get a SIGCHLD to notify it that the process has changed state. A process only gets SIGCHLD when its immediate children change state. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet) Chet Ramey, CWRU chet@po.CWRU.Edu http://cnswww.cns.cwru.edu/~chet/