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

[BIND 10 Development]

#850: two bind10's, two msgq's, all using same socket file
------------------------------------+---------------------------------
           Reporter:  jreed         |                      Owner:
               Type:  defect        |                     Status:  new
           Priority:  major         |                  Milestone:
          Component:  Boss of BIND  |                   Keywords:
          Sensitive:  0             |  Estimated Number of Hours:  0
Add Hours to Ticket:  0             |                  Billable?:  1
        Total Hours:  0             |                  Internal?:  0
------------------------------------+---------------------------------
 I started a second bind10:
 {{{

 $ bind10  --cmdctl-port 8001 -c /tmp/foo --brittle --verbose
 <
 bind10 20110223 (BIND 10 20110322)
 [bind10] Checking for already running b10-msgq
 [bind10] Starting b10-msgq
 [bind10] Started b10-msgq (PID 20001)
 ...
 }}}

 I now have two msgq's running. They are using the same socket:
 {{{

 reed 20001  0.0  1.3 48644 11444 ttyp4 I     7:27AM   0:00.20
 /usr/pkg/bin/python3.1 /home/reed/opt/bind10/libexec/bind10-devel/b10-msgq
 root 29964  0.0  0.5 48644  4408 ttyp4 I    Mon02PM   0:00.20
 /usr/pkg/bin/python3.1 /home/reed/opt/bind10/libexec/bind10-devel/b10-msgq

 reed     python3.1  20001  3 stream
 /home/reed/opt/bind10/var/bind10-devel/msgq_socket -
 root     python3.1  29964  3 stream
 /home/reed/opt/bind10/var/bind10-devel/msgq_socket -
 }}}

 This happens even if I start second process as root.

 Using "bindctl --port 8001" I am able to attach to correct configuration.
 I get correct list of modules and also Stats show shows me the desired
 details.

 Why didn't bind10 detect my running msgq?  It should fail, because
 potential of broadcast messages getting sent to wrong modules.

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