BIND 10 #2732: the logger configuration should validate the name property against a list of valid module.library names
BIND 10 Development
do-not-reply at isc.org
Wed Feb 13 13:03:50 UTC 2013
#2732: the logger configuration should validate the name property against a list
of valid module.library names
-------------------------------------+-------------------------------------
Reporter: cas | Type:
Status: new | defect
Milestone: New Tasks | Priority:
Keywords: | medium
Sensitive: 0 | Component:
Sub-Project: Core | Unclassified
Estimated Difficulty: 0 | CVSS Scoring:
Total Hours: 0 | Defect Severity: N/A
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
with the current (1.0.0-beta) logging configuration it is easy to create a
non working logging configuration. the "name" property seem to allow any
kind of text and is not validating the "name" against a list of valid
modules and module.library pairs.
A misunderstanding of the concept of "name" (not a good name for the
property, something like "selector" would be better) or a typo will create
a logger configuration that silently fails. That is very hard to
troubleshoot, esp. for logger configurations that will only produce log
output in special error conditions.
a "config commit" should validate the "name" property and should report an
error if the value does not match a possible valid "module.library"
combination. The error should give information on how to obtain a list of
all valid values for the "name" property.
--
Ticket URL: <http://bind10.isc.org/ticket/2732>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list