Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Tue, 13 Aug 2002 12:02:38 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: vfork / setsid interaction Message-ID: <20020813160238.GA11009@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <1029248291 DOT 12157 DOT 96 DOT camel AT lifelesswks> <3D591779 DOT 6030906 AT hekimian DOT com> <20020813165230 DOT H17250 AT cygbert DOT vinschen DOT de> <20020813153445 DOT GI9193 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020813153445.GI9193@redhat.com> User-Agent: Mutt/1.3.23.1i On Tue, Aug 13, 2002 at 11:34:45AM -0400, Christopher Faylor wrote: >If there is a problem with calling setsid in vfork and not having things >correctly restored when vfork "returns", that should be pretty easy to >fix. Btw, if someone (Joe?) can provide a simple test case demonstrating the problem I'll be happy to fix it. cgf