Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Mon, 25 Sep 2000 20:53:27 -0400
To: cygwin-developers AT sources DOT redhat DOT com
Subject: Re: small problem with exec
Message-ID: <20000925205327.A1882@cygnus.com>
Reply-To: cygwin-developers AT sources DOT redhat DOT com
Mail-Followup-To: cygwin-developers AT sources DOT redhat DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i

Egor Duda wrote:
>exec() inherits open file handles, and some of them can possibly be
>sockets.  cygwin has global variable to track the number of open
>sockets    (number_of_sockets)   which   increments   when  socket  is
>created and decrements when socket gets freed.  after fork this
>variable is initialized properly, but after exec it is 0.  when exec'ed
>process closes socket, cygwin prints "socket count < 0" warning.
>
>should number_of_sockets be eliminated or passed in child_info_spawn?

It should be eliminated.  The dynamic loading of winsock functions eliminated
the need for this some time ago.  I actually thought I got rid of this already.

It's gone now at least.

Thanks for catching this.  I am surprised that I haven't noticed the error message
that you noted.

cgf