BIND 10 #743: Conversion of config library to use the new logging interface
BIND 10 Development
do-not-reply at isc.org
Wed May 11 13:33:15 UTC 2011
#743: Conversion of config library to use the new logging interface
-------------------------------------+-------------------------------------
Reporter: | Owner: UnAssigned
stephen | Status: reviewing
Type: | Milestone:
enhancement | Sprint-20110517
Priority: minor | Resolution:
Component: | Sensitive: 0
configuration | Sub-Project: DNS
Keywords: | Estimated Difficulty: 5.0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
logging |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by jelte):
* owner: jelte => UnAssigned
* status: assigned => reviewing
Comment:
Ready for review.
While creating messages and extended descriptions, I noticed a few
potential issues which i fixed along the way:
- If the config manager does not accept the modules specification, or if
the
'get current config' command returns with an error, the system used to
ignore that fact apart from printing an error, and continue running. It
seems much better to explicitely fail, since the module would be running
independent of what its config is supposed to be, which would be really
unstable
- If the module cannot parse a command it gets over the command channel,
it used to send back an error. If we have multiple modules listening on
the same channel, this would result in multiple errors being returned
It will now log an error, but it will not send back an answer
should this need a changelog:
[func] C++ client side of configuration now uses BIND10 logging system. It
also has improved error handling when communicating with the rest of the
system.
--
Ticket URL: <http://bind10.isc.org/ticket/743#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list