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
Wed Apr 20 11:35:56 UTC 2011


#642: SIGHUP and other signals cause boss to leave BIND 10 processes lying around
-------------------------------------+-------------------------------------
                   Reporter:  shane  |                 Owner:  shane
                       Type:         |                Status:  reviewing
  defect                             |             Milestone:
                   Priority:  minor  |  Sprint-20110503
                  Component:  Boss   |            Resolution:
  of BIND                            |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  0.0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by shane):

 * subproject:   => DNS
 * severity:   => N/A


Comment:

 Ug... okay, this is most likely caused by the boss process itself
 terminating when writing output during shutdown.

 I have added checks for problems writing throughout the shutdown code, and
 also changed the test to look at that case. I also actually tried the code
 by running it in the same way you have been. :)

 One note - unless something actually writes output to stdout there is no
 error. This will happen eventually due to the stats program logging
 debugging, or sometimes some other task, but may take a while. AFAIK,
 there is no way to avoid this in a portable fashion. We could check for
 hangup using POLLHUP, but that wouldn't work in OS X, so we'd have to also
 code a version with kqueues, which is probably a bit beyond the scope of
 this exercise, which has already gotten quite big!

 Note that a lot of this problem should go away when we switch to our
 actual logging system, instead of just writing to stdout.

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


More information about the bind10-tickets mailing list