BIND 10 #1077: Update descriptions of logging code messages

[BIND 10 Development]

#1077: Update descriptions of logging code messages
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  stephen                            |                Status:  reviewing
                       Type:         |             Milestone:
  enhancement                        |  Sprint-20110712
                   Priority:         |            Resolution:
  trivial                            |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  logging                            |  Estimated Difficulty:  0.0
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by stephen):

 * owner:  stephen => UnAssigned
 * status:  assigned => reviewing


Comment:

 As noted, a number of the problems were already fixed in an earlier
 ticket:

 '''src/lib/log/logimpl_messages.mes'''
 > 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?
 Already fixed.

 '''src/lib/log/log_messages.mes'''
 (Note that a previous ticket changed the prefix from MSG_ to LOG_)

 > MSG_BADSEVERITY allow "NONE" also?
 Added "NONE".

 > MSG_BADSTREAM incomplete description.
 Updated.

 > MSG_DUPLNS Where is $NAMESPACE directive documented?
 In the README file in the src/lib/log directory. ($NAMESPACE is only of
 interest to developers.) However, the description has been updated.

 > 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_NOMSGID, MSG_INVMSGID, MSG_NOMSGTXT, MSG_NSINVARG, MSG_NSNOARG,
 MSG_NSEXTRARG, MSG_PRFEXTRARG and MSG_PRFINVARG (actually, their LOG_
 equivalents) only apply to the message compiler. This is used in the build
 process, and any errors in that soon become apparent.

 MSG_DUPMSGID (now LOG_DUPLICATE_MESSAGE_ID) indicates that multiple
 symbols of the same name have been detected. A new ticket (#1093) has been
 raised for the suggestion that the condition cause the program to
 terminate.

 MSG_IDNOTFND (now LOG_NO_SUCH_MESSAGE) is generated when a local message
 file is read but an ID in it does not correspond to one of the compiled-in
 IDs. This is most likely a typo in the local message file, so it is a
 warning and does not cause BIND 10 to exit.

 > MSG_INVMSGID incomplete description
 Updated in a previous ticket.

 > MSG_IDNOTFND multiple paragraph description okay?
 Yes.

 > should the developer MSG_ problems say to open a bug ticket report?
 Done in a previous ticket.

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