BIND 10 #2249: order of shutdowns should not allow msgq or cfgmgr to exit before other components

[BIND 10 Development]

#2249: order of shutdowns should not allow msgq or cfgmgr to exit before other
components
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  New Tasks
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:  Boss   |           Sub-Project:  Core
  of BIND                            |  Estimated Difficulty:  0
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by vorner):

 It should be safe to stop the config manager first. Components aren't
 supposed to use it at shutdown, they only ask for configuration on startup
 and when it changes.

 The msgq can be a problem, but if a component shuts down cleanly, it
 should happen before the msgq gets the SIGTERM. We may want to check the
 length of the delay before sending SIGTERMs.

 However, it looks strange that msgq would stop first. It either crashed,
 or the process refused to stop by message and needed to be killed anyway.
 There's currently no way to stop msgq „nicely“, so it always waits for the
 second stage (sending SIGTERMs).

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