BIND 10 #1673: Decode exit status in boss
BIND 10 Development
do-not-reply at isc.org
Tue Mar 6 14:21:23 UTC 2012
#1673: Decode exit status in boss
-------------------------------------+-------------------------------------
Reporter: | Owner: muks
vorner | Status: reviewing
Type: | Milestone:
enhancement | Sprint-20120306
Priority: major | Resolution:
Component: Boss | Sensitive: 0
of BIND | Sub-Project: Core
Keywords: | Estimated Difficulty: 3
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by muks):
Replying to [comment:7 vorner]:
> First, maybe it would need a changelog? Or do you think it is such a
small change it doesn't need one?
It is a small change I think.. doesn't change any functionality (for the
user to watch out for).
> Also, I believe it might be useful to output the signal name even if it
core dumped (if it coredumps or not is an additional information for the
signal number ‒ so it can SEGFAULT and dump or ABORT and dump or TERM and
not dump, etc).
Good idea. Let me check if something like WTERMSIG() would return a valid
signal# after a waitpid() in the case of a core dump.
--
Ticket URL: <http://bind10.isc.org/ticket/1673#comment:9>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list