kern/118626: Bad interaction between SIGPIPE and threads.

[Mark Andrews]

>Number:         118626
>Category:       kern
>Synopsis:       Bad interaction between SIGPIPE and threads.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Dec 12 21:20:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator:     Mark Andrews
>Release:        FreeBSD 6.3-PRERELEASE i386
>Organization:
ISC
>Environment:
System: FreeBSD drugs.dv.isc.org 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #18: Mon Dec 10 14:45:13 EST 2007 marka at drugs.dv.isc.org:/usr/obj/usr/src/sys/DRUGS i386


>Description:

	SIGPIPE is a crude mechanism and we really should have a
	way to turn this on and off on a per file descriptor basis
	especially in threaded applications where you can't just
	ignore the signal for specific writes like you would for
	a unthreaded application.

	The resolver library, and I presume other sockets based
	libraries, need to be able to disable SIGPIPE for specific
	writes yet still have the application fail when writes to
	stdout fail because the application has not caught SIGPIPE.

>How-To-Repeat:

>Fix:



>Release-Note:
>Audit-Trail:
>Unformatted: