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
Date: Thu, 20 Mar 2003 09:40:59 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [PATCH] fhandler_socket::sendto and EPIPE
Message-ID: <20030320084059.GH21269@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0303191809550 DOT 6272-200000 AT eos>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.44.0303191809550.6272-200000@eos>
User-Agent: Mutt/1.4i

On Wed, Mar 19, 2003 at 06:17:49PM -0600, Brian Ford wrote:
> 2003-03-19  Brian Ford  <ford AT vss DOT fsi DOT com>
> 
> 	* fhandler_socket.cc (sendto): Handle SIGPIPE for ECONNRESET.

Hmm, while this looks okay on the first glance, reading SUSv3 and the
Linux man pages tell another story.  SUSv3 has an explicit error code
ECONNRESET which has nothing to do with the EPIPE error.  The Linux
man page explicitely mentions that EPIPE is generated if "the *local*
end of a socket has been shut down [...]".  So I think this patch is
not correct, sorry.

OTOH, both texts tell us that this error code is only valid for connection
oriented socket.  A test for this is missing in the Cygwin sendto function.
I'll add this.

Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/