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        |  reopened
           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):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Hi Kean

 Replying to [comment:6 kean]:
 > The SIGKILL is deliberate because it is a "forceful" shutdown. See
 src/bin/init.py.in round about line 848.

 The question is: WHY was SIGKILL used? What happened that required doing a
 forceful shutdown?

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