X-Spam-Check-By:	sourceware.org
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: fork failure patch for cygrunsrv
Date:	Mon, 19 Jun 2006 10:03:59 +0100
Message-ID:	<016601c6937f$4d55dc00$a501a8c0@CAM.ARTIMI.COM>
MIME-Version:	1.0
X-Mailer:	Microsoft Office Outlook 11
In-Reply-To:	<127543258B0B9054522CC18C@qjunbur.quns.cam.ac.uk>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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 18 June 2006 20:30, Robin Walker wrote:

> --On 16 June 2006 16:49 -0400 "Hochstedler, Ben (GE Healthcare)" wrote:
> 
>> fork() can fail when the system runs out of non-interactive heap space
>> (because there's not enough heap memory to allocate to the launched
>> process).
> 
> If we, as end-users, suffer from fork() failing for the above reason, which
> parameter should be adjusted so that there is enough heap memory available
> for fork() not to fail like this?

  Read the referred MSDN article; it has a registry setting to adjust.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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

- Raw text -