BIND 10 #681: [kean] msgq dies on SIGPIPE

[BIND 10 Development]

#681: [kean] msgq dies on SIGPIPE
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  msgq          |  assigned
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20131015
         Sub-Project:  Core          |                   Resolution:
Estimated Difficulty:  4.0           |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  Low
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by kean):

 Ignoring SIGPIPE is the correct thing to do in my opinion. SIGPIPE is
 delivered when one of the clients terminates the connection rather than
 the daemon terminating it. Of course there is some question as to why the
 client is breaking the connection early but the delivery of SIGPIPE is a
 very heavy-handed aspect of the sockets API. Hundreds upon hundreds of
 applications that deal with remote connections just ignore SIGPIPE because
 they take care of detecting a remote disconnect in other ways (return
 values from select / poll / recv / read / write etc).

-- 
Ticket URL: <http://bind10.isc.org/ticket/681#comment:13>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development