BIND 10 #2225: Implement counters into Xfrout (3/3)

[BIND 10 Development]

#2225: Implement counters into Xfrout (3/3)
-------------------------------------+-------------------------------------
            Reporter:  naokikambe    |                        Owner:
                Type:  enhancement   |  naokikambe
            Priority:  medium        |                       Status:
           Component:  xfrout        |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130219
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  7             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => naokikambe


Comment:

 Hi Kambe san

 Replying to [comment:51 naokikambe]:
 > Replying to [comment:46 muks]:
 > > Only "senderr" seems to be mentioned in the manpage, but not the
 > > hierarchy up to senderr.
 >
 > I updated descriptions of `zones`, `socket` and `unixdomain` in the spec
 file, and updated the man page. I redefined them as directories. Could you
 refer to trac2225_xfrout(aed7be6)?

 If you render this page to HTML, does it show `open` under `unixdomain` or
 does it show both of them as part of the same list? What I mean is that it
 has to show the hierarchy. So you can either type them as
 "socket/unixdomain/open" in the manpage, or use nested lists to show
 "open" under "unixdomain", and "unixdomain" under "socket". Otherwise, if
 it is all a flat list of keys, it won't be clear to the reader where to
 find "open".

 To illustrate, it should not be like this:

 * socket
 * unixdomain
 * open
 * openfail
 * close
 * ...

 but like this:

 * socket
  * unixdomain
   * open
   * openfail
   * close
   * ...

 or if that's not possible, even like this:

 * socket/unixdomain/open
 * socket/unixdomain/openfail
 * socket/unixdomain/close
 * socket/unixdomain/...

 Is this reasonable?

 > > I'm still not able to run all of the lettuce
 > > tests due to unrelated crashes, but xfrin_notify_handling.feature runs
 > > OK.
 >
 > Is the issue specific to your environment? :(

 This seems to be. It is unrelated to this branch. But I could run
 `xfrin_notify_handling.feature` successfully.

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