BIND 10 #2445: suppress initial log

[BIND 10 Development]

#2445: suppress initial log
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |  jinmei
            Priority:  medium        |                       Status:
           Component:  Boss of BIND  |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20121218
         Sub-Project:  Core          |                   Resolution:
Estimated Difficulty:  4             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:28 jelte]:
 > Hmm, that's actually slightly tricky, and we have a little bit of a
 trade-off here.
 [...]
 > For now I'm removing the setLogLevel(TRACE), so it will dump DEBUG on
 -v, and not dump them in normal mode, but then, in the -v is not given,
 and working configuration that sets it to DEBUG, some initial DEBUG
 messages get lost....

 In that case I'd rather suggest the previous behavior.  When something
 goes wrong in initial setup and the loggers fall back to the last
 resort, we'll probably want to see verbose messages.

 A more possible solution I can think of is to somehow delay the log
 initialization (or reinitialize it) after parsing the command line
 options, and initialize it with corresponding log level (by extending
 the interface further to make it possible).  But I think we should
 complete the ticket now and defer any solution to this problem to a
 separate task - actually we originally intended to just do a
 lightweight "hack" in this ticket, but spent much larger time than
 we'd have needed for it (I'm much more happier with the resulting more
 complete solution, though).

 So, I suggest resetting to 0a9dafb and merge it (and open a new ticket
 for the remaining issue).

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