BIND 10 #1047: introspection of current logging settings

[BIND 10 Development]

#1047: introspection of current logging settings
--------------------------------+-----------------------------------------
            Reporter:  jelte    |                        Owner:
                Type:  task     |                       Status:  new
            Priority:  major    |                    Milestone:  New Tasks
           Component:  logging  |                     Keywords:
           Sensitive:  0        |              Defect Severity:  N/A
         Sub-Project:  DNS      |  Feature Depending on Ticket:
Estimated Difficulty:  0        |          Add Hours to Ticket:  0
         Total Hours:  0        |                    Internal?:  0
--------------------------------+-----------------------------------------
 When doing #1004, it occurred to me that to efficiently test it, i need to
 be able to see what the currently set loggers and outputoptions are. This
 is actually also needed for error recovery (if a new logger setup fails
 for some reason).

 The current implementation backend (log4cplus) does allow a list of
 current loggers to be requested. So we need to (names may be different):
 - create getCurrentLoggerSpecifications() that reads that out and puts
 them in a vector (of type LoggerSpecification, including the internal list
 of OutputOptions)
 - add equality operators to LoggerSpecification and OutputOptions
 - add equality for vectors of both (presumably by also adding an ordering
 to the classes)

 Then we can add real tests for default_logconfig_update, and make it
 recover the previous settings if it fails

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