www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/1998/02/02/11:58:46

From: ian AT cygnus DOT com (Ian Lance Taylor)
Subject: Re: rxvt and latest Ian's changes.
2 Feb 1998 11:58:46 -0800 :
Message-ID: <199802021941.OAA11988.cygnus.cygwin32.developers@subrogation.cygnus.com>
References: <EnrnA7 DOT 5tr AT bbc DOT com>
Reply-To: gnu-win32-developers AT cygnus DOT com
To: cygwin32-developers AT cygnus DOT com

   From: cgf AT bbc DOT com (Christopher Faylor)
   Date: Mon, 2 Feb 1998 19:25:19 GMT

   In article <199802021727 DOT MAA11798 AT subrogation DOT cygnus DOT com>,
   Ian Lance Taylor  <gnu-win32-developers AT cygnus DOT com> wrote:
   >Unfortunately, this does not handle the case of the master opening the
   >pty, then a child opening the pty, and then closing the pty, and then
   >another child opening the pty.  This works on Unix, but I do not know
   >how to make it work on Windows.  I don't happen to know of any
   >programs that rely on this behaviour, but there may be some.

   I just took a look at the code again, and maybe I'm missing something,
   but is there any reason why the handles could not be handed back to
   the master when all of the slaves close the pty?  The master would
   then have an extra couple of handles that may or may not ever be used
   again but if a child requests the pty it would be able to retrieve
   the handles.

The desired effect is to close all the write handles to the pipe, so
that the master, which is hanging in read, gets an EOF.  Copying the
handles back to the master will not achieve this effect.

Ian

- Raw text -


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