BIND 10 #1901: be consistent with bind10 or boss or bob name
BIND 10 Development
do-not-reply at isc.org
Thu Apr 19 18:02:54 UTC 2012
#1901: be consistent with bind10 or boss or bob name
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: medium | Milestone: New
Component: Boss of BIND | Tasks
Sensitive: 0 | Keywords:
Sub-Project: Core | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
1) The bind10 process log message identifier is "BIND10". That is
consistent.
2) The name of the bind10 logger is "b10-boss". Note that the logger API
documentation says "This should be set to the name of the program." It is
not.
3) The child logger name is also "boss" (i.e. [b10-boss.boss]).
4) The bind10 specification is named bob.spec.
5) The bob.spec defines module name as "Boss".
6) The bob.spec command descriptions use a mix of "BIND 10" and "boss".
7) The code has a BoB class.
8) Some stats collected for bind10 are identified with "Boss" owner.
9) Control channel is identified as "boss".
10) API docs and code use "boss" term.
11) The bind10 log messages uses "boss" many times including once as part
of a bind10 message identifier.
The "boss" or "bob" name is not based on process name and may be confusing
to users.
We need to choose a name (b10-boss? bind10? bob? b10-bob? b10-bind10?)
Whatever we decide should be consistently used in logging, documentation,
configurations, etc.
(jinmei and I discussed this a little in jabber.)
--
Ticket URL: <http://bind10.isc.org/ticket/1901>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list