BIND 10 #530: [kean] msgq error message for unable to create socket
BIND 10 Development
do-not-reply at isc.org
Thu Nov 14 09:12:09 UTC 2013
#530: [kean] msgq error message for unable to create socket
-------------------------------------+-------------------------------------
Reporter: jreed | Owner: muks
Type: defect | Status:
Priority: medium | reviewing
Component: msgq | Milestone:
Keywords: | Sprint-20131015
Sensitive: 0 | Resolution:
Sub-Project: DNS | CVSS Scoring:
Estimated Difficulty: 0.0 | Defect Severity: N/A
Total Hours: 0 | Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by kean):
* owner: kean => muks
* status: reopened => reviewing
Comment:
if you look at the code I pointed you to you will see how the decision is
made. A few lines above it in the shutdown() method, it first sends
SIGTERM by calling {{{self.__kill_children(False)}}} and then if there are
any remaining components, it does a "forceful" shutdown by calling
{{{self.__kill_children(True)}}}. There are probably ways that can be
improved but that was an "aside" question in the bug, not the purpose of
the fix. If we want to change that code and put in a sleep to give the
SIGTERM time to do its thing then by all means lets do so but then it
belongs in another bug (IMHO). It was you who told me that bugs need to be
very targeted in nature and this bug was about the msgq socket error
messages not about why SIGKILL was used (again, except as an aside). If
you disagree I am happy to address the SIGKILL issue too.
--
Ticket URL: <http://bind10.isc.org/ticket/530#comment:8>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list