BIND 10 #1077: Update descriptions of logging code messages
BIND 10 Development
do-not-reply at isc.org
Thu Jul 7 10:55:25 UTC 2011
#1077: Update descriptions of logging code messages
-------------------------------------+-------------------------------------
Reporter: | Owner: vorner
stephen | Status: reviewing
Type: | Milestone:
enhancement | Sprint-20110712
Priority: | Resolution:
trivial | Sensitive: 0
Component: | Sub-Project: DNS
logging | Estimated Difficulty: 2.0
Keywords: | Total Hours: 0
Defect Severity: N/A |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: UnAssigned => vorner
Old description:
> From [https://lists.isc.org/pipermail/bind10-dev/2011-June/002384.html
> this email]:
>
> LOGIMPL_ABOVEDBGMAX and BELOWDBGMIN have typo "DEBGUGn" -- what is this
> string? Where documented? Is this used by admins too? If developer only,
> should message for "BADDEBUG" say to open a bug ticket?
>
> MSG_BADSEVERITY allow "NONE" also?
>
> MSG_BADSTREAM incomplete description.
>
> MSG_DUPLNS Where is $NAMESPACE directive documented?
>
> MSG_DUPMSGID, MSG_IDNOTFND, MSG_NOMSGID, MSG_INVMSGID, MSG_NOMSGTXT
> (maybe MSG_NSINVARG and MSG_NSNOARG and MSG_NSEXTRARG too?) (maybe
> MSG_PRFEXTRARG and MSG_PRFINVARG too?): maybe there should be a developer
> option to kill BIND 10 startup if this happens.
>
> MSG_INVMSGID incomplete description
>
> MSG_IDNOTFND multiple paragraph description okay?
>
> should the developer MSG_ problems say to open a bug ticket report?
New description:
From [https://lists.isc.org/pipermail/bind10-dev/2011-June/002384.html
this email]:
LOGIMPL_ABOVEDBGMAX and BELOWDBGMIN have typo "DEBGUGn" -- what is this
string? Where documented? Is this used by admins too? If developer only,
should message for "BADDEBUG" say to open a bug ticket?
MSG_BADSEVERITY allow "NONE" also?
MSG_BADSTREAM incomplete description.
MSG_DUPLNS Where is $NAMESPACE directive documented?
MSG_DUPMSGID, MSG_IDNOTFND, MSG_NOMSGID, MSG_INVMSGID, MSG_NOMSGTXT (maybe
MSG_NSINVARG and MSG_NSNOARG and MSG_NSEXTRARG too?) (maybe MSG_PRFEXTRARG
and MSG_PRFINVARG too?): maybe there should be a developer option to kill
BIND 10 startup if this happens.
MSG_INVMSGID incomplete description
MSG_IDNOTFND multiple paragraph description okay?
should the developer MSG_ problems say to open a bug ticket report?
--
--
Ticket URL: <http://bind10.isc.org/ticket/1077#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list