Message-ID: <4485EB68.9F685880@dessent.net>
Date: Tue, 06 Jun 2006 13:54:00 -0700
From: Brian Dessent <brian@dessent.net>
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: cygwin fork problem maybe?
References: <4485E5F3.7010700@tlinx.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: cygwin@cygwin.com
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Linda W wrote:

> Windows just doesn't support forking at all, as far as I know.
> activeperl emulates forking using win32 threads. I don'tknow how cygwin
> handles it, but my guess is that it's not very well :-(

This smells like total FUD.  This person that admittedly does not use
Cygwin nor obviously know anything about Cygwin says that it's a fork
problem and that's that?  Fork may be a problem for Activestate but
Cygwin fully emulates fork just fine, as does Cygwin's perl.  The Cygwin
DLL goes to extreme lengths to make sure this work.  Just about every
Cygwin compiled app that invokes a subprogram uses fork in some form,
for example every shell command you type is a fork/exec.

"my guess is that it's not very well" without any specific indication as
to why or how fork is even related seems like nonsense to me.  I
certainly don't know why this module is failing, but just because
Activestate's implementation of fork is terrible doesn't mean Cygwin's
is too.

Brian

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