Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	Christopher January <ccj00 AT doc DOT ic DOT ac DOT uk>
To:	cygwin AT cygwin DOT com
Subject:	Re: A real fork() on NT
Date:	Mon, 4 Feb 2002 15:12:32 +0000
X-Mailer:	KMail [version 1.3.1]
References:	<006e01c1a96a$f60429a0$aace0544 AT CX535256D> <027701c1ad0d$e1f9d030$0100a8c0 AT advent02> <20020204022415 DOT GA1366 AT redhat DOT com>
In-Reply-To:	<20020204022415.GA1366@redhat.com>
MIME-Version:	1.0
Message-Id:	<E16XknJ-0006BF-00@duck.doc.ic.ac.uk>

> >I've got the book; I have a DLL that exports a function called fork and
> >I'm seeing what can be done to get it to work with kdeinit.  A lot of
> >programs do: if (fork() == 0) exec(...) and this could be replaced by
> >spawn(...) anyway, but kdeinit does a bit more work.
>
> So, use vfork().  We already have an implementation that does the right
> thing in that case.
That wouldn't work.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -