BIND 10 #3027: the existance of child configuration elements doesn't imply the existance of the parents

BIND 10 Development do-not-reply at isc.org
Fri Jul 5 13:04:10 UTC 2013


#3027: the existance of child configuration elements doesn't imply the existance
of the parents
-------------------------------------+-------------------------------------
            Reporter:  bconry        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  New
           Component:  Unclassified  |  Tasks
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by bconry):

 Replying to [comment:1 vorner]:
 > I'm not sure about the leading slash. Does it work as „config show_json
 Init“?
 >
 > Surely, it should reject invalid input, not get confused about it like
 this.

 It behaves the same with, and without, the leading slash.

 {{{
 > config show_json Init
 null
 }}}

 For those trying to reproduce it, this was starting with a completely
 empty configuration file.

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


More information about the bind10-tickets mailing list