From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20989 invoked by alias); 6 Mar 2012 10:17:19 -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: 16841 Received: (qmail 27160 invoked from network); 6 Mar 2012 10:17:16 -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.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, HTML_MESSAGE,T_DKIM_INVALID,UNPARSEABLE_RELAY autolearn=no version=3.3.2 Received-SPF: pass (ns1.primenet.com.au: SPF record at a.spf.163.com designates 220.181.13.60 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Received:Date:From:To:Message-ID:Subject: MIME-Version:Content-Type; bh=wxMe72PsaIRbjxDhAtA7Ys0C8Zrvx+97Cc YGTOcKp7c=; b=cfhaHz7pp1dDkR2/kb4cFXQODn7jXEpWR11pf6QmITl2FRo5L9 BkF0/Zm8pjxgki0H3m2l7rs6dfD9sDsZOItC7AdT/6Qxjzt4M0xwx0WV3OAKVaxV sP5d+QxxWTqzdSqV5AMvU96KWlAKCSwM1WT4NilpZvoT+ryUbVMpUYerA= Date: Tue, 6 Mar 2012 18:01:38 +0800 (CST) From: hanpingtian To: zsh-users@zsh.org Message-ID: <2c45df49.32a93.135e774fca6.Coremail.hanpingtian@163.com> Subject: job control problem MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_585613_1708794412.1331028098213" X-Originating-IP: [96.126.98.8, 96.126.98.8] X-Priority: 3 X-Mailer: Coremail Webmail Server Version SP_ntes V3.5 build 111202(16086.4213.4207) Copyright (c) 2002-2012 www.mailtech.cn 163com X-CM-CTRLDATA: sMc3AGZvb3Rlcl9odG09OTgxOjgx X-CM-TRANSID:PMGowEC5ckGC4FVPOwlSAA--.5862W X-CM-SenderInfo: xkdq1x5qjwxtrq6rljoofrz/xtbBERJphUij-O8QzAAAsL X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU== ------=_Part_585613_1708794412.1331028098213 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: 7bit Hello, I feel zsh's job control is a little weak than bash. For example, this script: % cat t.sh for ((i=1;i<=10000;i++)) do sleep 1 & done wait With zsh: % zsh -x ./t.sh ... ./t.sh:3: fork failed: resource temporarily unavailable +./t.sh:6> wait +./t.sh:3> sleep 1 it will fail with the fork() failure very soon. But with bash: % bash -x ./t.sh ... + (( i++ )) + (( i<=10000 )) ./t.sh: fork: retry: Resource temporarily unavailable + sleep 1 + sleep 1 + sleep 1 + sleep 1 + sleep 1 + sleep 1 + sleep 1 + sleep 1 ./t.sh: fork: retry: Resource temporarily unavailable + (( i++ )) ... It can run more longer by retry and retry. And I noticed that when trying to run a lot of jobs in background can cause zsh quit or frozen. ------=_Part_585613_1708794412.1331028098213--