From owner-freebsd-bugs@FreeBSD.ORG Thu Dec 13 22:13:08 2007 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 059E416A417 for ; Thu, 13 Dec 2007 22:13:08 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) by mx1.freebsd.org (Postfix) with ESMTP id AC76213C45A for ; Thu, 13 Dec 2007 22:13:07 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.2/8.14.1) with ESMTP id lBDMD5r2073439 for ; Fri, 14 Dec 2007 09:13:05 +1100 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200712132213.lBDMD5r2073439@drugs.dv.isc.org> To: freebsd-bugs@FreeBSD.ORG From: Mark Andrews Mail-Followup-To: Mark Andrews , freebsd-bugs@FreeBSD.ORG In-reply-to: Your message of "Thu, 13 Dec 2007 12:06:26 CDT." <20071213170626.GA25873@VARK.MIT.EDU> Date: Fri, 14 Dec 2007 09:13:05 +1100 Sender: marka@isc.org Cc: Subject: Re: kern/118626: Bad interaction between SIGPIPE and threads. X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Dec 2007 22:13:08 -0000 > On Thu, Dec 13, 2007, Mark Andrews wrote: > > The following reply was made to PR kern/118626; it has been noted by GNATS. > > > > From: Mark Andrews > > To: bug-followup@FreeBSD.org, marka@isc.org > > Cc: sobomax@freebsd.org > > Subject: Re: kern/118626: Bad interaction between SIGPIPE and threads. > > Date: Thu, 13 Dec 2007 11:41:16 +1100 > > > > I'll definitely try it. > > > > The man page for socket(2) should be updated to reference SO_NOSIGPIPE > > where it talks about SIGPIPE being generated. > > The commit log says SO_NOSIGPIPE exists for compatibility, but it > looks fully implemented and supported. I've cc'd the original > author to find out if there's any good reason not to document it. It's documented in setsockopt(2). It just also needs to be documented in socket(2). I'm happy to close this ticket regardless of what is decided to do about the documentation. The socket option appears to work (got writev to return EPIPE), so thanks for the pointer. libbind will be updated to use it when available. Now to get other vendors to follow suite as it is something that has been needed for a long time and consistancy is good. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org