BIND 10 #304: bindctl error after "Boss shutdown"

[BIND 10 Development]

#304: bindctl error after "Boss shutdown"
---------------------------+------------------------------------------------
      Reporter:  jreed     |        Owner:     
          Type:  defect    |       Status:  new
      Priority:  major     |    Milestone:     
     Component:  bind-ctl  |   Resolution:     
      Keywords:            |    Sensitive:  0  
Estimatedhours:  0.0       |        Hours:  0  
      Billable:  1         |   Totalhours:  0  
      Internal:  0         |  
---------------------------+------------------------------------------------

Comment(by stephen):

 The issue goes deeper than just the error after "Boss shutdown".  It is
 about whether bindctl should be able to run independently of the rest of
 the system.

 The particular case I'm thinking of is ability to alter parameters without
 starting the system. At the time of writing, the parameters controlling
 whether the authoritative or recursive server starts are parameters of
 Boss; as shipped, the authoritative server will start by default.  Unless
 you edit the .spec files, configuring BIND 10 to run the recursive server
 requires starting BIND 10 (and so starting auth), running bindctl to
 change the parameters, stopping BIND 10, then starting BIND 10.

 I think it should be possible to run bindctl independently of the rest of
 the system - it should connect to the message queue process if one is
 available or create it if not.

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