BIND 10 #1074: Use debug levels consistently

[BIND 10 Development]

#1074: Use debug levels consistently
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  stephen
  stephen                            |                Status:  reviewing
                       Type:         |             Milestone:
  enhancement                        |  Sprint-20111025
                   Priority:  minor  |            Resolution:
                  Component:         |             Sensitive:  0
  logging                            |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  6.0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => stephen


Comment:

 log_dbglevels.h: don't know yet if i completely agree with the intro, but
 practice may have to show that. For instance, "covers things like
 startup-steps and config messages", i think it should also be things like
 bad
 responses from nameservers that do not interrupt operations, but may be
 useful
 for fixing bigger setups etc. from that would follow that 30< for
 applications,
 and 30> for libraries may be too strict a definition.

 if such things are to be DEBUG as well, we probably need to add one or
 more
 consts for it as well, but we'll see that when we get there (may become
 more
 relevant once we refocus on resolver)

 changed "N.B." to "\note" btw. (and removed a few spaces), please verify
 commit.

 Should we consider replacing the module-specific levels with the general
 ones everywhere?

 Would we want to check all constants in log_test.py? (not sure)

 These are just discussion points, and the code looks ok, so if the answer
 is
 'no' to all, it can be merged :)

-- 
Ticket URL: <http://bind10.isc.org/ticket/1074#comment:11>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development