BIND 10 #1190: complete logging conversion for msgq

[BIND 10 Development]

#1190: complete logging conversion for msgq
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  Next-Sprint-
                   Priority:  low    |  Proposed
                  Component:  msgq   |            Resolution:
                   Keywords:         |             Sensitive:  0
            Defect Severity:  Low    |           Sub-Project:  Core
Feature Depending on Ticket:         |  Estimated Difficulty:  0
        Add Hours to Ticket:  0      |           Total Hours:  0
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 The problem is that msgq (currently) can't get configurations,
 including logging related one.  Fixing this point will be much bigger
 than of this task, so we should either

 - handle these as a larger feature set ("msgq-ng"); it will be beyond
   the scope of beta.
 - introduce some workaround

 Regarding the latter, maybe we can do this:

 - use bind 10 logging lib without any user-defined config
 - by default it dumps to a hardcoded separate file at the info level
 - if -v is specified the log level will be increased to (max?) debug

 and, also maybe adding a command line option to allow customizing some
 of theses (log destination, log level).

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