BIND 10 #2550: logging stdout fallback includes debug even without -v

BIND 10 Development do-not-reply at isc.org
Tue Dec 11 10:48:01 UTC 2012


#2550: logging stdout fallback includes debug even without -v
---------------------------------------+----------------------------------
                   Reporter:  jelte    |                 Owner:
                       Type:  defect   |                Status:  new
                   Priority:  medium   |             Milestone:  New Tasks
                  Component:  logging  |              Keywords:
               CVSS Scoring:           |             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        |
---------------------------------------+----------------------------------
 After #2445, if bind10 starts and can't even get a decent configuration,
 all initial logging is dumped to stdout. However, due to some intricacies
 in the logging system, this includes *any* log message (so also DEBUG even
 if -v was not used). See that last few comments at #2445.

 Right now I don't really know a good solution to this, but we should fix
 this at some point :)

 A possible solution is to not use 'if verbose then
 logger.setLogLevel(debug)' but rather initialize the logging system
 depending on the command arguments (if verbose init(debug)'. But there are
 probably some nasty subtleties there.

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


More information about the bind10-tickets mailing list