Date: Fri, 12 Mar 2010 16:22:51 +0000
From: jurriaan AT rivierenland DOT xs4all DOT nl
To: cygwin AT cygwin DOT com
Subject: Re: fork problems on x64
Message-ID: <20100312162251.GA4067@onderneming10.xs4all.nl>
References: <4B99D2E9 DOT 60108 AT rosshemail DOT com> <4B9A3F85 DOT 4050506 AT cygwin DOT com> <4B9A4F51 DOT 5090104 AT rosshemail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B9A4F51.5090104@rosshemail.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

From: Ross Hemingway
Date: Fri, Mar 12, 2010 at 09:27:29AM -0500
>
> 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??
>
You don't happen to have anything like virus scanners running do you?

Kind regards,
Jurriaan
-- 
HORROR FILM WISDOM:
13. If you are using a gun to combat the all-consuming evil, it is a good
idea to quickly find a new means of defense, because no matter how much
ammo you have, you'll run out just before you kill the monster (unless
your name is Ash, in which case, you'll never have to reload).


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