BIND 10 #134: xfrout not killed by SIGTERM

BIND 10 Development do-not-reply at isc.org
Thu Apr 22 14:38:07 UTC 2010


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

Comment(by zhanglikun):

 Hi Jeremy and Shane, Please help review my patch for this ticket. What I
 did is:
 1. Avoid to call function shutdown() of xfrout twice. One is caused by
 SIGINT and the other is caused by "shutdown" message sent by boss.
 2. Xfrout do select for the connection from auth process in one thread, so
 when we shutdown Xfrout, this thread should be stopped(with join()). But
 sometimes this thread is blocked by select(), so I set the poll intervals
 of select is 0.1 second, and let boss sleep for 0.5s (old value is 0.1s)
 after sending "shutdown" message. Does this make sense?


 3. Xfrout shutdown logic:
       join all the threads of xfrout
       remove unix socket file which is shared by auth process.

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


More information about the bind10-tickets mailing list