BIND 10 #2639: b10-msg utility for looking up message information at the command line

BIND 10 Development do-not-reply at isc.org
Fri Jan 18 12:39:07 UTC 2013


#2639: b10-msg utility for looking up message information at the command line
-------------------------------------+-------------------------------------
                   Reporter:  shane  |                 Owner:
                       Type:         |                Status:  new
  enhancement                        |             Milestone:  New Tasks
                   Priority:         |              Keywords:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  logging                            |  Estimated Difficulty:  0
               CVSS Scoring:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 Seen in a message on the bind-users list:

    > By the way, all of the BIND10 logging
    > messages are unique and we provide a paragraph or more documentation
 for
    > each of its 933 possible log identifiers!)

    I haven't checked whether you have that, but that screams for a CLI
    utility to show the paragraph without having to browse documentation.
 :)

 https://lists.isc.org/pipermail/bind-users/2013-January/089541.html

 So the idea would be to have a simple utility so that you could execute
 like this:

 {{{
 $ b10-msg BIND10_SELECT_ERROR
 There was a fatal error in the call to select(), used to see if a child
 process has ended or if there is a message on the message bus. This should
 not happen under normal circumstances and is considered fatal, so BIND 10
 will now shut down. The specific error is printed.
 }}}

 We can think of possible extensions to this (like an interface which
 supports tab-expansion, or searches by regular expression, and so on), but
 I think this basic approach would cover 95% of use cases.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2639>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list