Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3E9C42AF.F8A6AEA1@precidia.com>
Date: Tue, 15 Apr 2003 13:34:39 -0400
From: Brian White <bcwhite AT precidia DOT com>
Organization: Precidia Technologies  http://www.precidia.com/
X-Accept-Language: en
MIME-Version: 1.0
To: Max Bowsher <maxb AT ukf DOT net>
CC: cygwin AT cygwin DOT com
Subject: Re: tcp RST instead of FIN if child exits after parent closes path
References: <3E9C374E DOT 4256358D AT precidia DOT com> <004001c30372$9b95d9b0$235e893e AT pomello>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> [a good analysis, but the subject says it all, really, once a typo is fixed
> (s/exists/exits)]

Oops!  :-)


> Re: tcp RST instead of FIN if child exits after parent closes path
> 
> This is a bug/feature of Windows Sockets. I think it would be possible to
> craft a workaround in Cygwin, but it would require some non-trivial IPC.
> (IIUC, you would need to maintain a cross-process refcount for the socket).

Hmmm...  From my work with Amanda, the child process can continue to
send data via the socket even after the parent has closed it's handle
on that path, so there must be some sort of reference counting already.

                                          Brian
                                 ( bcwhite AT precidia DOT com )

-------------------------------------------------------------------------------
Seize the moment!  Live now.  Make "now" always the most important time. -- JLP

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/