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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=QJrkVG4WOklc2z4GANPG97VM7b1IumZjYxFRq9lYaCB5wJmfs8LxL
	84Mo71fo9OXBjUS0s+WmtqkbqXGImKulw5MWSRIPdhISewqQlxXDxZAjnXGBOH+L
	2peM6QpHbMbebaGxI/2+BFJrpG4osUOI4OtP/D1ZAn+rcz3sGnhk1M=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=UslA5zwAr9hwnALruPY/GmP1OAc=; b=exbyLMZ4NDwh4j9m/XwbcyPcZwW0
	mMzH9LOisOTx4J6qh0u6VUSB9LUrgN2cSQe7b8JctOlBQpicpvq2CELTzuk/pYHH
	gAyQzMqXZpegHdzfMSKT1y4VzhH8II795Ni8RSD2XXkVjYv17UW6BIkOB0b8xmMz
	xlFir96tkRab36I=
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=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO: calimero.vinschen.de
Date: Thu, 11 Dec 2014 11:33:16 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: proc_retry question
Message-ID: <20141211103316.GD3810@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="RHtQWnsJolAsiBtD"
Content-Disposition: inline
In-Reply-To: <CAOSUUSrZYv63-fkKpZG+wDddRGpD1PbzYRazUNQ1xhAJ7ik+mQ@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

--RHtQWnsJolAsiBtD
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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 =3D 10.
> >> >> >>
> >> >> >> I still get the following error message but showing rety 10:
> >> >> >>
> >> >> >>
> >> >> >>       0 [main] sh 35392 fork: child -1 - forked process 35736 di=
ed
> >> >> >> 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 time=
s?
> >> >> >>
> >> >> >> 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, whic=
h 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.
>=20
> I tried "rebasing" but with no luck.
>=20
> 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.
>=20
> 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

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--RHtQWnsJolAsiBtD
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUiXLrAAoJEPU2Bp2uRE+gWtYP/iUOWjawGu6tfvbu5dIbEptx
+VNlPWG9pVxX34dzyYQsqt2Twv3/UVoSp/Hp3OVGSqmY0b03XGV8eV/oO/64xKjz
chMWbVeQRT92vuObnK3oxWJFMP8x6WJ8g63ZCsl+4EvY1ydBNCTzJVmYqvYzHfaJ
+KTnI7n8JvJ6dle3uo7a3vVNPCA0F95Iygn1wO+5g12dPV/1kCu9BgrBMFxpEcso
pHCAK1buaRwc/QPEMMTqyPY/0n90U/dWcdjoytpZajXkDCLdVA0kT5bq6Gys6s0V
Wve5wzq+6+50wR4b6Dh+HcCvg8z1DSV4MfyhhBFzux0NEIKDqBUPo147350mZf3h
2uapTSFVAm+p9ji4oiFwJ6FKp+u+FL8Ny8iT54bKy3ucqwEMrE2t9F99PR1VGd4Y
ogV7I9JFtRkhyAK556rU8qKjzX+u1AerwG13IPMJd2HanvAd/nVLWhP3XfHEQeKL
IH8GDtboIfFj0ud21ih4f+LKejMY4AROQWd9orAoheqmPffCpVErU+YEn+Ckx1r3
QiiW60HhrUS812pbmo9kAXjX5GZVq0y4wsjIECuuyPJNz7Am5ML/h8FA31XsegN4
diJAkxKl/V4oBe32GhkxPappsgBq1fWWNdVX33Feik5x6Ss/rUWkpPjZ6kVjwQLD
KvqajtnD8PUt//a9wxS1
=eyLf
-----END PGP SIGNATURE-----

--RHtQWnsJolAsiBtD--