BIND 10 #134: xfrout not killed by SIGTERM

[BIND 10 Development]

#134: xfrout not killed by SIGTERM
--------------------------+-------------------------------------------------
 Reporter:  jreed         |        Owner:  shane   
     Type:  defect        |       Status:  assigned
 Priority:  major         |    Milestone:          
Component:  Unclassified  |   Resolution:          
 Keywords:                |    Sensitive:  0       
--------------------------+-------------------------------------------------

Comment(by shane):

 Replying to [comment:9 shane]:
 > The problem with this approach is that it will only shutdown the server
 after all xfrout have completed. This could take several seconds or even
 HOURS, depending on what is going on. (Imagine a server sending the .CN
 zone)

 Likun just pointed out that the code sets a shutdown event, so it actually
 exits after the next message is sent (which could in principle be a while
 due to TCP, but will usually be very quick).

 So, I propose that we apply his patch because it improves behavior, but
 leave this ticket open pending the discussion about shutdown on
 bind10-dev. I'll take ownership until that is done.

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