X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX19S1PI8KgcN6jGgQ8569pBS
Date:	Sun, 2 Sep 2012 12:20:40 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Forks paralysing the CYGWIN system...
Message-ID:	<20120902162040.GB7287@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<501B5C75C69C9B4EA832DDD95302EFFA81BA97AE AT ICT-EXMBX-2 DOT lsbu DOT ac DOT uk> <501B5C75C69C9B4EA832DDD95302EFFA81BA97FE AT ICT-EXMBX-2 DOT lsbu DOT ac DOT uk>
MIME-Version:	1.0
In-Reply-To:	<501B5C75C69C9B4EA832DDD95302EFFA81BA97FE@ICT-EXMBX-2.lsbu.ac.uk>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Sun, Sep 02, 2012 at 03:23:02PM +0000, Walker, Leon E wrote:
>I may be able to shed further light on the fork problems I have been
>experiencing.
>
>I think it has to do with the number of CYGWIN processes on the system
>as I was monitoring during one of the fork storms as it were.
>
>I think the system is running out of a resource such as Process Control
>Blocks or File Control Blocks or file handles or something like that.
>This comes as a bit of surprise because I'm running on 64-bit Windows
>Server 2008 with 8Gb and seemingly has ample resources but then again
>perhaps there is parameter In windows or in CYGWIN to increase the
>limits...  if we can identify which resource is running low?
>
>It also occurred to me whether it was possible to change the CYGWIN
>code so that if the forks fails say for the condition identified
>earlier, would it be possible to instead of issuing a messages and
>possibly disrupting the running script, the code could be modified to
>silently wait internally until the fork succeeds?

Check out the CYGWIN environment varialbe "proc_retry" setting:
http://cygwin.com/cygwin-ug-net/using-cygwinenv.html .  I don't know if
it will address your problem or not but it is worth a try.

Regarding your tweaking of your virus checker: I would be surprised if
just excluding cygwin directories was adequate for working around this
kind of problem.  The virus checker still needs to be hooked into
process creation somehow and that's what screws Cygwin up.

Also, you may not know this, but Cygwin is free software.  Go ahead
and provide a patch if you think you have a way to fix a problem.

cgf

--
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 -