BIND 10 #99: bindctl will allow options for modules that aren't running
BIND 10 Development
do-not-reply at isc.org
Wed Aug 4 12:48:06 UTC 2010
#99: bindctl will allow options for modules that aren't running
---------------------------+------------------------------------------------
Reporter: jreed | Owner: zhanglikun
Type: defect | Status: assigned
Priority: major | Milestone: 05. 3rd Incremental Release: Serious Secondary
Component: bind-ctl | Resolution:
Keywords: | Sensitive: 0
Estimatedhours: | Hours:
Billable: 0 | Totalhours:
Internal: 0 |
---------------------------+------------------------------------------------
Changes (by jelte):
* estimatedhours: => 0.0
* internal: => 0
* billable: => 0
Comment:
Hmm. If the module has been shut down configmanager also doesn't know that
(again, until #123 has been done). But a bigger question is; do we want to
be able to change config options of modules that aren't running (i think
we might). In that case this will depend more on the 'static' configration
api (is there a ticket for that yet?)
But shall I for now simply let it return an error? ("Module not known or
not running")
(i'm guessing that would also fix #202)
--
Ticket URL: <http://bind10.isc.org/ticket/99#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list