BIND 10 #640: cfgmgr hanging and command and configurations for no-longer-running components

[BIND 10 Development]

#640: cfgmgr hanging and command and configurations for no-longer-running
components
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:
                   Priority:  major  |  Sprint-20120207
                  Component:         |            Resolution:
  Unclassified                       |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  0.0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jelte):

 Just a few initial comments, these are indeed all related (except maybe
 that last one), and the problem is that configmanager is never told about
 modules being stopped, resulting in timeouts when it tries to contact
 them.

 There are a few levels of solutions IMO;
 - Make sure the ModuleCCSession also sends a message when it is closed, so
 that ConfigManager can remove it from its list of currently running
 modules. This will (or should) also result in bindctl at least erroring
 sooner and not with a timeout ('unknown module') when sending a direct
 command.
 - We may need to add another message from boss 'I don't know if you have
 noticed, but process X has disappeared.', but this may require another
 addition (need to match module names to process names somewhere if we
 don't already)
 - The second issue then becomes one that we wanted for a long time as
 well; offline configuration, though this time only 'partly' offline; i.e.
 configmanager should be able to check and change configuration values of
 modules that are not running). But I am not entirely sure on what its
 behaviour should look like (e.g. why should an admin be bothered with
 config values for things he isn't running)

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