BIND 10 #850: [kean] two bind10's, two msgq's, all using same socket file

[BIND 10 Development]

#850: [kean] two bind10's, two msgq's, all using same socket file
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:
            Priority:  medium        |  closed
           Component:  Boss of BIND  |                    Milestone:
            Keywords:                |  Sprint-20131015
           Sensitive:  0             |                   Resolution:  fixed
         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 kean):

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


Comment:

 A recent change I made (#433) makes this no longer possible. If there is
 an existing socket and it responds to commands (i.e it is not simply a
 danging socket left on the filesystem after a crash) then the second msgq
 will refuse to start.

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