X-Spam-Check-By: sourceware.org
Date: Sun, 18 Jun 2006 20:29:51 +0100
From: Robin Walker <rdhw AT cam DOT ac DOT uk>
Reply-To: Robin Walker <rdhw AT cam DOT ac DOT uk>
To: "Hochstedler, Ben (GE Healthcare)" <ben DOT hochstedler AT med DOT ge DOT com>,
   cygwin AT cygwin DOT com
Subject: Re: fork failure patch for cygrunsrv
Message-ID: <127543258B0B9054522CC18C@qjunbur.quns.cam.ac.uk>
In-Reply-To: <93BD0000E4D72D458F0E8CDE6BA971A833D8BE@CINMLVEM11.e2k.ad.ge.com>
References:  <93BD0000E4D72D458F0E8CDE6BA971A833D8BE AT CINMLVEM11 DOT e2k DOT ad DOT ge DOT com  >
X-Mailer: Mulberry/4.0.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 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?

-- 
Robin Walker (Junior Bursar), Queens' College, Cambridge CB3 9ET, UK
rdhw AT cam DOT ac DOT uk  http://www.queens.cam.ac.uk/  Tel:+44 1223 335528

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