X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=bl
	MK4ERnxYAhwwzf6C/sEdqcicti8FlOkjiPQpFe/r45I4BM3bQDbBEj08uCUmFdFX
	leZCDOacZ50F7Zy0CBvmdpqgfHBvgCSN3soHOHp82HNfTf50g7oJ4H6iD+N/QQ5M
	VaZTuFcVG9/mjdTsNbACipwlOzafuwbn0feqnc0YA=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=urM778y1
	/Bt3+Ez9aToKir6aG1Q=; b=k0kmOT/DSh4NBpKTRZZHPAC1gPEEIcxVBymgik8l
	p40x53ipedeJKin8cySU+v1KwvsPDlq/etMsqmHD6FNx4Z3XPHjx3YfFawJnzQSD
	/aBkAXcOz5hjijBi35e+MVgHmHXJIcDF/rvMSr+FbonB0/SgVxNzLhcsQ+Nnbt4I
	X9w=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-pa0-f44.google.com
MIME-Version:	1.0
X-Received:	by 10.68.132.225 with SMTP id ox1mr14786456pbb.85.1418288570048; Thu, 11 Dec 2014 01:02:50 -0800 (PST)
In-Reply-To:	<20141208162733.GW3810@calimero.vinschen.de>
References:	<CAOSUUSrPjEAJQNsPKKKPKOVKsVzzR_gsrEApTzZd3nmv-HMQdA AT mail DOT gmail DOT com> <20141208144003 DOT GP3810 AT calimero DOT vinschen DOT de> <CAOSUUSo6Wbn4wwLbT_3SnMDFP31MxpKXm2bSLak4dxk72jeekQ AT mail DOT gmail DOT com> <20141208155009 DOT GU3810 AT calimero DOT vinschen DOT de> <CAOSUUSpsy=rvbsmFM4d-UN09Sy8PECqE+usNP08Gv6E9frScAg AT mail DOT gmail DOT com> <20141208162733 DOT GW3810 AT calimero DOT vinschen DOT de>
Date:	Thu, 11 Dec 2014 09:02:50 +0000
Message-ID:	<CAOSUUSrZYv63-fkKpZG+wDddRGpD1PbzYRazUNQ1xhAJ7ik+mQ@mail.gmail.com>
Subject:	Re: proc_retry question
From:	xmoon 2000 <xmoon2000 AT googlemail DOT com>
To:	cygwin <cygwin AT cygwin DOT com>
X-IsSubscribed:	yes

On 8 December 2014 at 16:27, Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote:
> On Dec  8 16:03, xmoon 2000 wrote:
>> On 8 December 2014 at 15:50, Corinna Vinschen <> wrote:
>> > On Dec  8 14:48, xmoon 2000 wrote:
>> >> On 8 December 2014 at 14:40, Corinna Vinschen <> wrote:
>> >> > On Dec  8 12:40, xmoon 2000 wrote:
>> >> >> I have set proc_retry = 10.
>> >> >>
>> >> >> I still get the following error message but showing rety 10:
>> >> >>
>> >> >>
>> >> >>       0 [main] sh 35392 fork: child -1 - forked process 35736 died
>> >> >> unexpectedly, retry 10, exit code 0xC0000005, errno 11
>> >> >> /q/onlyPastEnd.sh: fork: retry: Resource temporarily unavailable
>> >> >>
>> >> >> Does this mean it got an error and cygwin will now retry 10 times?
>> >> >>
>> >> >> OR does it mean it retry-ed 10 and failed?
>> >> >
>> >> > It tried 10 times and failed.
>> >>
>> >> Are you certain about that?
>> >
>> > No.  Sorry, it's the other way around.  If retry is 10, no retry
>> > occured.  AFAICS that's because you get an C000005 status code, which is
>> > STATUS_ACCESS_VIOLATION.  In case of this error code, Cygwin does
>> > explicitely not retry.
>>
>> Do this suggest that I need to do the rebaseall - as documented in:
>> http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-fork-failures
>
> You can try, but this looks a bit different.  A SEGV at fork time could
> be a bug in Cygwin or a result of having another Cygwin DLL in the path
> for some reason.
>
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Maintainer                 cygwin AT cygwin DOT com
> Red Hat


Corinna,

I tried "rebasing" but with no luck.

The problem appears when I am running 60 scripts in parallel on a 32
core machine. Plus, each script runs subscripts with several pipes.
So, I think this is a "too many processes" type of issue.

Usually, windows handle my "over-coring" well and my machine just
works through what it needs to do. But when I try this from Cygwin, it
seems to cause issues.

Any thoughts or suggest for how I could get around this?

Moon

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -