BIND 10 #1521: Make boss process close children on SIGHUP and internal fatal errors
BIND 10 Development
do-not-reply at isc.org
Wed Dec 21 10:45:30 UTC 2011
#1521: Make boss process close children on SIGHUP and internal fatal errors
-------------------------------------+-------------------------------------
Reporter: jelte | Owner:
Type: defect | Status: new
Priority: major | Milestone: New
Component: Boss of BIND | Tasks
Sensitive: 0 | Keywords:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
There are some scenarios where child processes of the boss are not cleaned
up well, notable cases are sending a SIGHUP and uncaught exceptions in the
boss code.
In either case, we should always close all child processes if the boss
exits, so if it isn't available yet, we need exception-free process
cleanup code (and point the correct handlers to it).
For SIGHUP, this has been more-or-less addressed in #642, but at the time
it turned out to be more work than we had time for. The changes made there
are probably not applicable anymore, but have been kept around for
reference in branches/trac642-historic.
--
Ticket URL: <http://bind10.isc.org/ticket/1521>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list