This is the mail archive of the
mailing list for the Cygwin project.
Re: A real fork() on NT
- From: Christopher Faylor <cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 2 Feb 2002 00:40:57 -0500
- Subject: Re: A real fork() on NT
- References: <006e01c1a96a$f60429a0$aace0544@CX535256D> <E16VsW4-0001P8email@example.com> <20020130131416.D11608@cygbert.vinschen.de> <013a01c1ab96$839eefc0$0100a8c0@advent02> <000b01c1abaa$4e70f460$0100a8c0@gregmo>
- Reply-to: cygwin at cygwin dot com
On Fri, Feb 01, 2002 at 09:27:21PM -0800, Greg Mosier wrote:
>P.S. I would have dropped this awhile back with the exception of the cron
>application. It appears to fork quite nicely under Win98, my OS. Now maybe
>I'm wrong here, but seems to me if one app can fork that surely another
>should be able to, no?
Cygwin fork works just fine. It's slow but it should work as well as UNIX
fork for a ported application. The only exception that I can think of is
if you use dlopen to load a non-cygwin DLL. In that case there is a problem
with relocation of the DLL after a fork.
If you consider the number of applications that have been ported to cygwin,
it would be pretty amazing if there was some basic problem with fork.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html