BIND 10 #642: SIGHUP and other signals cause boss to leave BIND 10 processes lying around

BIND 10 Development do-not-reply at isc.org
Mon Apr 18 13:16:24 UTC 2011


#642: SIGHUP and other signals cause boss to leave BIND 10 processes lying around
-------------------------------------+-------------------------------------
                 Reporter:  shane    |                Owner:  vorner
                     Type:  defect   |               Status:  reviewing
                 Priority:  minor    |            Milestone:
                Component:  Boss of  |  Sprint-20110419
  BIND                               |           Resolution:
                 Keywords:           |            Sensitive:  0
Estimated Number of Hours:  0.0      |  Add Hours to Ticket:  0
                Billable?:  1        |          Total Hours:  0
                Internal?:  0        |
-------------------------------------+-------------------------------------
Changes (by shane):

 * owner:  shane => vorner


Comment:

 Based on this analysis and feedback (there was not much) I decided the
 best thing is simply to shut down if the output TTY goes away.

 The code exits if it has a problem writing - or indeed any uncaught
 exception (which is probably should have anyway).

 I consolidated some of the tests as requested. Please have another look,
 thanks.

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


More information about the bind10-tickets mailing list