Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 21 Apr 2003 10:03:14 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: bug: tcp RST instead of FIN if child exits after parent closes path Message-ID: <20030421140314.GB3873@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3EA3F7EC DOT 833E28B AT precidia DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EA3F7EC.833E28B@precidia.com> User-Agent: Mutt/1.4.1i On Mon, Apr 21, 2003 at 09:53:48AM -0400, Brian White wrote: >There have been feelings that the source of this problem is with the >Windows socket interface, but it doesn't seem to fit with the >descriptions others people have provided. My original report is >attached. I don't see any indication that this is other than a Windows problem. If it isn't then the supposition is that somehow Cygwin is noticing child terminations or socket closings, noticing that the child has sockets and is somehow doing something to the socket. It's conceivable that there is some setting that we could use in cygwin to magically make this work but no one has stepped forward to indicate what that would be. Perhaps I'm missing something, but it seems like this issue has been discussed previously in this mailing list. cgf -- 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/