BIND 10 #530: [kean] msgq error message for unable to create socket

[BIND 10 Development]

#530: [kean] msgq error message for unable to create socket
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:  kean
                Type:  defect        |                       Status:
            Priority:  medium        |  reviewing
           Component:  msgq          |                    Milestone:
            Keywords:                |  Sprint-20131015
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DNS           |                 CVSS Scoring:
Estimated Difficulty:  0.0           |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  UnAssigned => kean


Comment:

 Hi Kean

 Here are my review comments:

 Your commits look ok (I think we discussed the verbose changes on Jabber),
 but do they address the following points in the ticket description:

 > bind10 should also not have any traceback. It should say that the msgq
 exited.

 Would it still generate traceback or not?

 > And why SIGKILL? (versus friendlier signal)

 Why SIGKILL? What happens that causes the ticket description's log?

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