BIND 10 #1180: msgq dies on socket send error

[BIND 10 Development]

#1180: msgq dies on socket send error
-------------------------------------+-------------------------------------
                   Reporter:  shane  |                 Owner:  UnAssigned
                       Type:         |                Status:  reviewing
  defect                             |             Milestone:
                   Priority:  major  |  Sprint-20111025
                  Component:  msgq   |            Resolution:
                   Keywords:         |             Sensitive:  0
            Defect Severity:         |           Sub-Project:  Core
  Medium                             |  Estimated Difficulty:  3
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => UnAssigned
 * status:  assigned => reviewing


Comment:

 Ready for review. As discussed on the planning call, I only caught the
 exception, and only SIGPIPE, and did not add any tests for this. If
 someone sees an easy way to do so, we can, but i'd prefer spending time
 looking at a replacement :)

 Minor other notes; this module also doesn't use our logging framework, so
 as the error response (apart from dropping the send action and closing the
 socket), I just added a print(), as the rest of this code uses. Also, my
 editor found some whitespace it automatically removed.

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