BIND 10 #1049: bind10 should not resort to SIGKILL

BIND 10 Development do-not-reply at isc.org
Wed Nov 23 14:49:26 UTC 2011


#1049: bind10 should not resort to SIGKILL
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  Year 3 Task
                   Priority:  major  |  Backlog
                  Component:  Boss   |            Resolution:
  of BIND                            |             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 jreed):

 Note it is not just SIGKILL, but now I have example of nine SIGTERMs being
 sent and then six SIGKILLs. The SIGTERMs should not happen for msgq
 controlled components ("shutdown" sent to each).

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


More information about the bind10-tickets mailing list