Message-ID: <4B9A4F51.5090104@rosshemail.com>
Date: Fri, 12 Mar 2010 09:27:29 -0500
From: Ross Hemingway <rossh@rosshemail.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: fork problems on x64
References: <4B99D2E9.60108@rosshemail.com> <4B9A3F85.4050506@cygwin.com>
In-Reply-To: <4B9A3F85.4050506@cygwin.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

> On 3/12/2010 12:36 AM, Ross Hemingway wrote:
>> I have the same problems with multiple apps - Exim and UW-ipop.  They
>> both fail with the same faults:
>> fork: Resource temporarily unavailable
>>
>> The Exim will send a few mails, but will fail after a few minutes use.
>> UW-ipop fails the first time its called into use. Both are loaded as
>> services into an x64 2008 R2 server.
>>
>> I notice the mail list has other "x64 fork" problem reports. My
>> suspicion is the fault is in the core cygwin dll. Any thoughts please?
 >>
 >
>   Larry Hall (Cygwin) wrote:
> 
> Did you try rebaseall?
> 

I tried that just now.   No changes.  The other utilities I run or test 
seem to work OK.  It would appear its just when a fork is called for, 
that the resource fault occurs.

It might be a file / location permissions fault too, though I have 
checked for this without anything obvious.  Both Exim and inetd services 
run from an admin level account, so they should be OK for resource access.

I'm happy to try or test anything reasonable that can be suggested??


Regards
--
Ross Hemingway

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