Mail Archives: cygwin-developers/2002/07/29/15:20:25

Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Mon, 29 Jul 2002 15:20:37 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: TCP problems
Message-ID: <>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <010901c23724$96e5d430$6132bc3e AT BABEL> <3D4581E4 DOT BB580995 AT ieee DOT org> <005801c23730$02304170$6132bc3e AT BABEL>
Mime-Version: 1.0
In-Reply-To: <005801c23730$02304170$6132bc3e@BABEL>
User-Agent: Mutt/

On Mon, Jul 29, 2002 at 07:44:44PM +0100, Conrad Scott wrote:
>The idea would be to detect the last close of a given socket
>system wide; so it wouldn't matter whether the parent or child or
>whatever was the last to close the socket.

If you're just talking about system-wide closes then you could use
the technique currently employed in where events are used
as flags indicating when the "other side" of a pipe is closed.


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019