Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Tue, 4 Jun 2002 13:23:30 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Socket Handles duplicated twice after fork
Message-ID: <20020604132330.E1886@cygbert.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com
References: <Pine.GSO.4.30L.0206031415390.8254-100000@department-of-alchemy.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.30L.0206031415390.8254-100000@department-of-alchemy.mit.edu>
User-Agent: Mutt/1.3.22.1i

On Mon, Jun 03, 2002 at 02:20:36PM -0400, David E Euresti wrote:
> This is in response to an old post.
> 
> The basic problem is that after a fork the child gets four open socket
> handles instead of only two.  This code shows the problem slightly.  You
> need Process explorer to see the problem.

I have no idea where these handles are coming from since that
is contrary to what Cygwin's socket code is doing.  I've a
workaround for that but better I'd like to know the cause of the
additional handles...

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

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

