BIND 10 #2245: msgq stops too early (cache-enable true causes crash at startup)

[BIND 10 Development]

#2245: msgq stops too early (cache-enable true causes crash at startup)
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  New Tasks
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  Unclassified                       |  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):

 So, for which problem is this ticket?

 First of, the value should have not been saved in this invalid version.

 Second, I don't think that the order of SIGTERMs really matters. This is
 _emergency_ shutdown. Does it really matter if the processes crash when
 they would be killed right after that anyway? Sure, the order of SIGTERMs
 could be special-cased for msgq, but I don't see any problem except maybe
 little bit of aesthetic feeling.

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