BIND 10 #1005: check logger names in cfgmgr

[BIND 10 Development]

#1005: check logger names in cfgmgr
--------------------------------+-----------------------------------------
            Reporter:  jelte    |                        Owner:
                Type:  defect   |                       Status:  new
            Priority:  major    |                    Milestone:  New Tasks
           Component:  logging  |                     Keywords:
           Sensitive:  0        |              Defect Severity:  N/A
         Sub-Project:  Core     |  Feature Depending on Ticket:
Estimated Difficulty:  0        |          Add Hours to Ticket:  0
         Total Hours:  0        |                    Internal?:  0
--------------------------------+-----------------------------------------
 You can configure any logger, but if you mistype the name, it will happily
 create a logger for a module that does not exist, and the ones that do
 will use defaults.

 So the plugin config checker should really check the name and see if it
 makes sense.

 However, there are a few problems;
 - right now the way those python checking scripts are called they have no
 knowledge of what modules there are, so they can't really check the names
 of the loggers.
 - even if they could, you would only be able to configure logging for
 modules that are running (which is another symptom of the bigger 'can't
 configure non-running modules')

 so right now, i think we should modify the calling design so you can
 actually check, but not error on a 'wrong' name, only log an error (yes
 that sounds weird, in effect this error log message would go to the
 'previous' config, or the default if nothing has been configured yet).

-- 
Ticket URL: <http://bind10.isc.org/ticket/1005>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development