Config Tool Order of Execution

[GoogleCodeExporter]

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.

Original issue reported on code.google.com by Cooke...@gmail.com on 2 Dec 2012 at 6:55

[GoogleCodeExporter]

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.

Original comment by Cooke...@gmail.com on 3 Jan 2013 at 9:07

[GoogleCodeExporter]

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

Original comment by Cooke...@gmail.com on 16 Aug 2013 at 3:30

• Changed state: Invalid