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
Date: Wed, 20 Sep 2000 13:50:15 +0400
From: Egor Duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.45) Personal
Reply-To: Egor Duda <cygwin-developers AT sources DOT redhat DOT com>
Organization: DEO
X-Priority: 3 (Normal)
Message-ID: <5248443297.20000920135015@logos-m.ru>
To: cygwin-developers AT sources DOT redhat DOT com
Subject: small problem with exec
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

  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?

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19