BIND 10 #123: 'stopping' messages and 'alive' channel

[BIND 10 Development]

#123: 'stopping' messages and 'alive' channel
---------------------------------------------+------------------------------
      Reporter:  jelte                       |        Owner:  jelte
          Type:  enhancement                 |       Status:  new  
      Priority:  major                       |    Milestone:       
     Component:  Inter-module communication  |   Resolution:       
      Keywords:                              |    Sensitive:  0    
Estimatedhours:  0.0                         |        Hours:       
      Billable:  0                           |   Totalhours:       
      Internal:  0                           |  
---------------------------------------------+------------------------------

Comment(by stephen):

 > (though this involves giving bob a list of modules to run, and that will
 involve having
 > some form of dependencies)
 Bob already has a list of modules to run, it's hard-coded into it.

 From the discussion here, how about the following:

  1. Boss should start up the critial modules (message queue, configuration
 manager) then read the other modules it should start from the
 configuration database.
  2. Each module should have the following attributes:
     * Whether it should be run when BIND10 starts.
     * Whether it should be automatically restarted if it dies.
     * List of modules that must be running before this one can start.
  3. Boss controls the starting and stopping of processes.

 The last means that regardless of the settings of the options, a command
 such as "Xfrin shutdown" can be taken as an instruction not to restart the
 program (in this case Xfrin) when it shuts down.  It also suggests that we
 need to think about adding the commands "start" and "restart" to give
 additional process control.

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