BIND 10 #1858: sockcreator doesn't die
BIND 10 Development
do-not-reply at isc.org
Mon Apr 2 09:06:23 UTC 2012
#1858: sockcreator doesn't die
-------------------------------------+-------------------------------------
Reporter: | Owner:
jinmei | Status: new
Type: | Milestone: Next-Sprint-
defect | Proposed
Priority: | Resolution:
medium | Sensitive: 0
Component: Boss | Sub-Project: Core
of BIND | Estimated Difficulty: 0
Keywords: | Total Hours: 0
Defect Severity: N/A |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by vorner):
Hello
Two notes:
* As something failed during the shutdown (I don't know what it was, but
there was an exception during the shutdown). Then the shutdown is aborted
and it goes to the emergency shutdown. This should be changed and I
believe there's a ticket for it somewhere ‒ if we're shutting down, we
should try to „accumulate“ the exceptions, but shut down as many things as
possible the usual way.
* The fact that it fails to deliver the SIGKILL is a problem. I don't
completely like aborting the KILLs generally, as that could leave some
other things running without boss and there's less chance of administrator
noticing that. On the other hand, termination of boss should cause the
socket creator to shut down, as it will lose the stdin it reads commands
from and fail.
Anyway, we might want to examine an ability to keep the „bind low ports“
privilege only and run as the user the rest runs at. That would solve the
problem of undeliverable KILL.
--
Ticket URL: <http://bind10.isc.org/ticket/1858#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list