zsh-users
 help / color / mirror / code / Atom feed
From: Chet Ramey <chet.ramey@case.edu>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@zsh.org, chet.ramey@case.edu
Subject: Re: job control problem
Date: Wed, 07 Mar 2012 08:45:15 -0500	[thread overview]
Message-ID: <4F57666B.70704@case.edu> (raw)
In-Reply-To: <120306214608.ZM11429@torch.brasslantern.com>

On 3/7/12 12:46 AM, Bart Schaefer wrote:

> schaefer[501] bash --version
> GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin11)
> Copyright (C) 2007 Free Software Foundation, Inc.
> schaefer[502] bash /tmp/t.sh
> 1
> ...
> 67
> /tmp/t.sh: fork: Resource temporarily unavailable
> schaefer[503] echo $?
> 128
> 
> No "retry" mentioned.  What am I missing?

Bash-4.2 will sleep for 1, 2, 4, then 8 seconds if a fork fails, trying
after each sleep to reap dead children.  It will give up after that and
report the fork failure.  You'll see messages like this:

$ ls
bash: fork: retry: No child processes
bash: fork: retry: No child processes
bash: fork: retry: No child processes
bash: fork: retry: No child processes
bash: fork: Resource temporarily unavailable

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/


  reply	other threads:[~2012-03-07 13:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 10:01 hanpingtian
2012-03-07  5:46 ` Bart Schaefer
2012-03-07 13:45   ` Chet Ramey [this message]
2012-03-07 17:48     ` Bart Schaefer
2012-03-07 19:23       ` Chet Ramey
2012-03-08  4:25         ` Bart Schaefer
2012-03-07  9:16 ` hanpingtian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F57666B.70704@case.edu \
    --to=chet.ramey@case.edu \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).