BIND 10 #1987: 'wait for' command in bindctl execute handling (or something similar)
BIND 10 Development
do-not-reply at isc.org
Mon May 21 18:58:41 UTC 2012
#1987: 'wait for' command in bindctl execute handling (or something similar)
-------------------------------------+-------------------------------------
Reporter: jelte | Owner:
Type: task | Status: new
Priority: medium | Milestone: New
Component: Unclassified | Tasks
Sensitive: 0 | Keywords:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
As pointed out on bind10-users
(https://lists.isc.org/pipermail/bind10-users/2012-May/000339.html), the
execute command has a limitation (which is partially called by not
supporting commands/configuration for non-running moduels);
it is not possible to start a module and immediately configure it, since
the module is just started, it is not known by bindctl yet, so
configuration and commands to said module would result in a 'Module
Unknown' error.
The proposed solution is to add a !wait for <module> [time] command, which
would call
self.__update_all_modules() (we currently have no more efficient update
mechanism), and then check if the module that is waited for has appeared
yet.
The optional time argument would give a timeout, at which point execute
should just give up.
If we have this as a command, we should consider adding 'config commit' to
init_auth_server, and then call that new command for each module
init_auth_server starts, so that anyone who includes init_auth_server in
other scripts can be assured that the new modules are running afterwards.
--
Ticket URL: <http://bind10.isc.org/ticket/1987>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list