BIND 10 #1819: add boss nokill flag
BIND 10 Development
do-not-reply at isc.org
Mon Mar 26 06:09:46 UTC 2012
#1819: add boss nokill flag
-------------------------------------+-------------------------------------
Reporter: jelte | Owner: muks
Type: task | Status: reviewing
Priority: | Milestone:
medium | Sprint-20120403
Component: Boss | Resolution:
of BIND | Sensitive: 0
Keywords: | Sub-Project: DNS
Defect Severity: N/A | Estimated Difficulty: 3
Feature Depending on Ticket: | Total Hours: 0
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by muks):
Replying to [comment:8 vorner]:
> Hello
>
> The code looks OK. However, I think two important things are missing:
> * Documentation (at least in the man page, I don't think needs to be in
the guide, as it is more a testing tool).
This is added now.
> * Some kind of tests. I'm not sure if it's easy to test in the unit
tests, but the lettuce tests could do something like that. Creating a
script/component that does not shut down by the `shutdown` command should
be easy (just a while true ; do sleep 1 ; done would be enough, it does
not need to listen on the message queue) and see it is not killed.
I've added testcases for both the options parsing and also check if kill()
is invoked for the BoB.kill flag (building from existing work which checks
that killing happens when no option is passed). Also added some comments
to existing testcase so it can be followed quickly.
--
Ticket URL: <http://bind10.isc.org/ticket/1819#comment:13>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list