Mail Archives: cygwin-developers/2002/07/29/17:44:08

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
Message-ID: <011b01c23748$9396c5e0$6132bc3e@BABEL>
From: "Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
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> <20020729192037 DOT GA19335 AT redhat DOT com>
Subject: Re: TCP problems
Date: Mon, 29 Jul 2002 22:40:36 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

"Christopher Faylor" <cgf AT redhat DOT com> wrote:
> If you're just talking about system-wide closes then you could
> the technique currently employed in where events are
> as flags indicating when the "other side" of a pipe is closed.

That's a nice trick: each time the write-end of the pipe is
duplicated so is the handle to a named event created when the pipe
was created; so, if you try and fail to open the event, all
instances of the write-end have been closed.  Very simple and it
survives applications being killed via the task manager too.

I'll see if I can use that trick to simplify the UNIX domain
socket patch I submitted.  I can't immediately see how, since I
want the code to block until something in particular happens, but
it would simplify the detection of the last close.


// Conrad

p.s. I like the name of the event too: "stupid_pipe" ;-)

- Raw text -

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