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=sM
	dWRLVPumqwRa9uqjYIuBlYy1I3RR48C1/vwyU9rtPdVOmCW944LDpb1hJBjhttm1
	X5CUdDO11P2/mqOV0wRjzVdaUnECIa4VE5AAirYfBjSl58TAq+NeSuwFbEQxBbZr
	A3oDcV2r6XOHgjNCf/9OOPQfAETQXsl5/LGPjx8AY=
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=4+sZADUU
	STJWEzTOXIgJs1CrT4w=; b=T8kmJrc8ZH4uD0ZtJxbflqawg7oB9FREw1Nhbfri
	oX+B/iyn+m80/vWPn2Pm5jqTF98PZ3ACOP+zVt84Fk+cjczN/7F/fdpvjl+W9deQ
	n6NauM/s98CwR37d3Ja3ns0WT4ea0Ilm3zJauYVpLn5Q75rgJtV4+zrPT4hiduWC
	pfQ=
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.7 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-pd0-f171.google.com
MIME-Version: 1.0
X-Received: by 10.68.221.162 with SMTP id qf2mr17019124pbc.148.1418303104311; Thu, 11 Dec 2014 05:05:04 -0800 (PST)
In-Reply-To: <20141211103316.GD3810@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>	<CAOSUUSrZYv63-fkKpZG+wDddRGpD1PbzYRazUNQ1xhAJ7ik+mQ AT mail DOT gmail DOT com>	<20141211103316 DOT GD3810 AT calimero DOT vinschen DOT de>
Date: Thu, 11 Dec 2014 13:05:04 +0000
Message-ID: <CAOSUUSpLD+5=yC5XfuRLN4CenHiYKSWdp_3nHEDUUMdotYgq_g@mail.gmail.com>
Subject: Re: proc_retry question
From: xmoon 2000 <xmoon2000 AT googlemail DOT com>
To: cygwin <cygwin AT cygwin DOT com>
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes

On 11 December 2014 at 10:33, Corinna Vinschen
<corinna-cygwin AT cygwin DOT com> wrote:
> On Dec 11 09:02, xmoon 2000 wrote:
>> 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.
>>
>> 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.
>
> It's a SEGV.  It's probably not related to having too many processes.
> Cygwin processes only care for their immediate child processes usually
> and there's a restriction to 256 or so.
>
>> 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?
>
> Apart from BLODA influence, or apart from debugging what causes the
> SEGV, no.  If you can provide a simple testcase, stripped to the bare
> minimum of code to reproduce the issue, it may help.
>
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Maintainer                 cygwin AT cygwin DOT com
> Red Hat


Corinna,

I can't do a SCSE because it relies on files and a whole data structure here.

Any chance you could RemoteView my system?

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