BIND 10 #735: Investigate BIND-9 Logging

[BIND 10 Development]

#735: Investigate BIND-9 Logging
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  stephen
  stephen                            |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20110503
  critical                           |            Resolution:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  4.0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
  logging                            |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by stephen):

 > But there are still some issues, you mentioned some of them (problems
 with runtime adding and removing of loggers, need have a copy in git and
 CVS or something), some of you didn't, like the need to pass and update
 configuration online.
 To address these points:
 * The BIND 9 logging design document suggests that run-time addition and
 removal of configurations is possible.  (Does anyone know for sure?)
 * It might be easiest to treat libisc like third-party software: supply a
 copy with BIND 10 (in the "ext" directory) from the latest release of BIND
 9 and update it only when a new version is released.

 > And how much is it flexible? If we wanted to have some other fancy
 logging destination (eg. sending over msgq to a component, printing it on
 line printer, ...), would it be hard?
 I don't think so.  And I guess that the BIND 9 team would appreciate us
 providing extra functionality.

 > Also, I don't like dragging in the whole library just because of
 logging. In general, I personally prefer using something generally
 available (eg. external library), because we don't need to maintain it and
 it can be reused in the system by something else.
 I'm not too keen on that either.  However, "libisc" is a single component
 of BIND 9 and it is simpler to pull the whole lot in than pick and choose
 the bits we want.

 > I guess there's no reason to point out issues regarding the experimental
 code, right?
 Right! :-)  I just wanted to make sure that it was possible so did only
 the minimum needed.

 > Anyway, should we close this, or discuss it on some call or something?
 I'm never sure with tickets that say „investigate“, with the coding ones
 it's easy, when it's merged, its done.
 The possibility of using log4cplus has come up
 (https://lists.isc.org/pipermail/bind10-dev/2011-April/002202.html); I'll
 leave this ticket open as a reminder that we need to make a decision by
 the next sprint planning meeting.

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