BIND 10 #1049: bind10 should not resort to SIGKILL
BIND 10 Development
do-not-reply at isc.org
Tue Mar 20 08:21:25 UTC 2012
#1049: bind10 should not resort to SIGKILL
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: | Status: new
defect | Milestone: Next-Sprint-
Priority: | Proposed
medium | Resolution:
Component: Boss | Sensitive: 0
of BIND | Sub-Project: DNS
Keywords: | Estimated Difficulty: 0.0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by shane):
The concern is that use of SIGKILL is masking real problems. Which is why
I proposed:
* Add a flag to disable SIGKILL on shutdown (or perhaps one to set the
interval before falling back to SIGKILL?)
We know that some processes inappropriately block signals (xfrin and
xfrout I believe). These should be fixed to no longer do that blocking,
which is why I proposed:
* Fix any processes that currently block or catch SIGTERM (besides the
boss)
Finally, we need to make sure that all of our processes are actually
receiving and handling shutdown requests (I think they are), which is why
I proposed:
* Insure all processes properly handle shutdown requests
There is a discussion about whether the 0.1 second delay before SIGKILL is
appropriate. Personally I think the delay needs to be small - nothing is
more annoying for an administrator than having to wait for a system to
shutdown. But I don't think there is any specific actions for that, at
least not without discussion on bind10-dev.
--
Ticket URL: <http://bind10.isc.org/ticket/1049#comment:8>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list