From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23103 invoked by alias); 8 Mar 2012 04:26:03 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 16871 Received: (qmail 7778 invoked from network); 8 Mar 2012 04:25:52 -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 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <120307202510.ZM13097@torch.brasslantern.com> Date: Wed, 07 Mar 2012 20:25:10 -0800 In-reply-to: <4F57B5BA.6060201@case.edu> Comments: In reply to Chet Ramey "Re: job control problem" (Mar 7, 2:23pm) References: <2c45df49.32a93.135e774fca6.Coremail.hanpingtian@163.com> <120306214608.ZM11429@torch.brasslantern.com> <4F57666B.70704@case.edu> <120307094838.ZM12735@torch.brasslantern.com> <4F57B5BA.6060201@case.edu> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: chet.ramey@case.edu Subject: Re: job control problem Cc: zsh-users@zsh.org MIME-version: 1.0 Content-type: text/plain; charset=us-ascii } > } Bash-4.2 will sleep for 1, 2, 4, then 8 seconds if a fork fails, trying } > } after each sleep to reap dead children. } > } > Hmm, that seems like it could be a problem in some rare cases. } } What rare cases were you thinking of? Any in which the shell is itself fork-bombing the system. Sure, you can always work out a way to do so intentionally, but the shell retrying on failure would seem to make it way too easy to do it accidentally.