Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 1 Feb 2002 22:22:43 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: A real fork() on NT Message-ID: <20020202032243.GD6842@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <006e01c1a96a$f60429a0$aace0544 AT CX535256D> <20020130131416 DOT D11608 AT cygbert DOT vinschen DOT de> <013a01c1ab96$839eefc0$0100a8c0 AT advent02> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <013a01c1ab96$839eefc0$0100a8c0@advent02> User-Agent: Mutt/1.3.23.1i On Sat, Feb 02, 2002 at 03:05:47AM -0000, Chris January wrote: >>That isn't really new. I'd like to point you to the example 6.1, >>"Forking a Win32 Process" on p. 161ff of Gary Nebbett's excellent book >>"Windows NT/2000 Native API Reference", published by MTP, ISBN >>1-57870-199-6, which also describes the problem with kernel32.dll >>initialization of the child process. > >Are you referring to the CsrpConnectToServer function? I have a >working implementation which replaces this with >CsrClientConnectToServer which is exported from the DLL. Are their any >other pitfalls I should be aware of? The book has a sample implementation of fork for NT. Buy the book if you are interested. I doubt that either Corinna or I want to transcribe the book for this mailing list. And, I'm pretty sure that neither of us has that much experience with the routines in the book. I did play with the implementation and realized that it would take quite a bit of work to perfect for cygwin. For one thing, it doesn't seem to concern itself with dlls. I don't remember if there were other issues. cgf -- 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/