BIND 10 #3228: Rethink logging capability in libdhcp++
BIND 10 Development
do-not-reply at isc.org
Wed Nov 13 13:38:22 UTC 2013
#3228: Rethink logging capability in libdhcp++
-------------------------------------+-------------------------------------
Reporter: tomek | Owner:
Type: | Status: new
enhancement | Milestone: DHCP
Priority: | Outstanding Tasks
medium | Keywords:
Component: | Sensitive: 0
libdhcp | Sub-Project: DHCP
CVSS Scoring: | Estimated Difficulty: 0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Lack of logging capability was very painful when we were trying to debug
sockets opening and address binding during dry-run demo.
We need to rethink logging capability there. Direct use of log4cplus is
one way, but it has a downside of adding dependency to solutions that are
based on it.
Another possible way to consider would be to define a buffer that
libdhcp++ could write to. It would contain an error messages. Those can be
printed by higher layers if error is reported. This is very easy to
implement and does not take much space, so it is ok for embedded
environments.
--
Ticket URL: <http://bind10.isc.org/ticket/3228>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list