Issue 345 in roster-dns-management: Config Tool Order of Execution

[roster-dns...@googlecode.com]

Status: Accepted
Owner: ----
Labels: Type-Defect Priority-Medium Component-Config-Manager

New issue 345 by Cooke...@gmail.com: Config Tool Order of Execution
http://code.google.com/p/roster-dns-management/issues/detail?id=345

The current order of execution for the Config Manager tools (of interest)
is:
1. dnscheckconfig
2. dnsservercheck

In performing tests, it appears that dnscheckconfig requires a check on the
test and bind directory, as well as a connection check to the server. With
this being said, it appears that dnsservercheck should be executed before
dnscheckconfig. It also appears that dnscheckconfig performs the same
server check feature of dnsservercheck, which defeats the purpose of a
separate dnsservercheck tool.

We should consider changing the order of execution for the tools. We
should also investigate dnscheckconfig to ensure that it is not performing
the same operations as dnsservercheck.

[roster-dns...@googlecode.com]

Comment #1 on issue 345 by Cooke...@gmail.com: Config Tool Order of
Execution
http://code.google.com/p/roster-dns-management/issues/detail?id=345

We should test if the current order of execution will still work as of
r1084. The change that was made to dnscheckconfig may rely upon changing
the order that dnscheckconfig and dnsservercheck are executed.

[roster-dns...@googlecode.com]

Updates:
Status: Invalid

Comment #2 on issue 345 by Cooke...@gmail.com: Config Tool Order of
Execution
http://code.google.com/p/roster-dns-management/issues/detail?id=345

The current order of execution has been decided to work properly.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings