BIND 10 #110: bind10 should always exit safely, even on bad startup

BIND 10 Development do-not-reply at isc.org
Fri Oct 1 08:14:17 UTC 2010


#110: bind10 should always exit safely, even on bad startup
-------------------------------+--------------------------------------------
      Reporter:  jreed         |        Owner:                      
          Type:  defect        |       Status:  new                 
      Priority:  major         |    Milestone:  feature backlog item
     Component:  Boss of BIND  |   Resolution:                      
      Keywords:                |    Sensitive:  0                   
Estimatedhours:                |        Hours:                      
      Billable:  0             |   Totalhours:                      
      Internal:  0             |  
-------------------------------+--------------------------------------------
Changes (by vorner):

  * estimatedhours:  => 0.0
  * internal:  => 0
  * billable:  => 0


Comment:

 Could you have a look at the branches/trac300 if it is solved there? Every
 process there is added to a list and if the startup fails, all processes
 are killed. The old code didn't catch all exceptions (like
 KeyboardInterrupt) and had long windows that didn't catch anything.

 In theory, there's a short window where the process can survive ‒ if you
 send the signal between the fork call and the place where the process is
 added to the list (which is the next line of code). It should be short and
 I do not see an easy way to solve it, do you think this is OK?

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


More information about the bind10-tickets mailing list