Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date:	Fri, 30 Jul 2004 12:18:48 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: cygwin 1.4.0 - fork stops working ("permission denied")
Message-ID:	<20040730101848.GD1762@cygbert.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20040729184537 DOT 93419 DOT qmail AT web51607 DOT mail DOT yahoo DOT com>
Mime-Version:	1.0
In-Reply-To:	<20040729184537.93419.qmail@web51607.mail.yahoo.com>
User-Agent:	Mutt/1.4.2i

On Jul 29 11:45, George Morin wrote:
> I am currently running an application which uses
> fork/exec to run various background jobs. Every once
> in a while (less than .5%) I've found that fork fails
> and with strerror have received a permission denied
> error. From that point on, all subsequent forks will
> fail. In between my fork and exec the child process
> changes directories and redirects stdin, stdout and
> stderr. I have been unable to reproduce the above
> behaviour in a scaled down program. I believe this
> code has worked without incident on a unix box and has
> only recently been discovered now that the code has
> been ported to cygwin. I poked around google and the
> archives and haven't found an acceptable solution. I
> haven't noticed any unusual behaviour with my process
> ids (I'm not using AOF) or system resources. I'm
> running cygwin with Win2k and gcc 3.3.1. Can someone
> please offer suggestions for further investigation or
> perhaps a possible workaround? I have been able to use
> spawn() instead of fork/exec and it seemed to work
> fine but I don't know how to include the preprocessing
> that was done between the fork and exec. Any help is
> appreciated.
> 
> Thanks for your consideration,
> -Garrick

Sure you're running Cygwin 1.4.0?  What does uname -a report?  Or better,
read http://cygwin.com/problems.html and follow the instructions.

Your description is not enough to give any hint.  Did you try your
application under 1.5.10?  Can you create a simple(tm) testcase(tm)
to reproduce the problem?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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