From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4967 invoked from network); 27 Jul 2000 05:14:46 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 27 Jul 2000 05:14:46 -0000 Received: (qmail 27478 invoked by alias); 27 Jul 2000 05:14:32 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 12392 Received: (qmail 27470 invoked from network); 27 Jul 2000 05:14:25 -0000 To: zsh-workers@sunsite.auc.dk Subject: Re: wait for non-child PID References: <20000726190953.A22895@scowler.net> MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII From: Tanaka Akira Date: 27 Jul 2000 14:13:30 +0900 In-Reply-To: <20000726190953.A22895@scowler.net> (Clint Adams's message of "Wed, 26 Jul 2000 19:09:53 -0400") Message-ID: User-Agent: T-gnus/6.14.1 (based on Gnus v5.8.3) (revision 16) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.6 (i686-pc-linux-gnu) MULE/4.0 (HANANOEN) In article <20000726190953.A22895@scowler.net>, Clint Adams writes: > 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? A zsh can waits the process, but the zsh doesn't notice its status change because the zsh is not the parent of it and SIGCHLD cannot reached to the zsh. Is it useful? -- Tanaka Akira