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

[BIND 10 Development]

#642: SIGHUP and other signals cause boss to leave BIND 10 processes lying around
-------------------------------------+-------------------------------------
                 Reporter:  shane    |                Owner:  shane
                     Type:  defect   |               Status:  reviewing
                 Priority:  minor    |            Milestone:  A-Team-
                Component:  Boss of  |  Sprint-20110316
  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 vorner):

 * owner:  vorner => shane


Comment:

 Hello

 I'm not sure if it really works. If I start bind10 on the background (with
 &) and I close the terminal, all processes survive for a while, but then
 start to die out one by one. I guess it's because they can no longer write
 to the terminal that got closed.

 It works if I send a TERM signal. But in that case (and in the other cases
 as well), it probably shouldn't terminate with 0 status.

 And the tests are quite repetitive. Would it be possible to have some kind
 of common „body“ of the test and just call it with the name of the signal
 to test?

 Thanks

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