BIND 10 #1716: use DEBUG for BIND10_LOST_SOCKET_CONSUMER and BIND10_SOCKET_CREATED instead of INFO
BIND 10 Development
do-not-reply at isc.org
Thu Apr 25 17:22:07 UTC 2013
#1716: use DEBUG for BIND10_LOST_SOCKET_CONSUMER and BIND10_SOCKET_CREATED
instead of INFO
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: very low | Milestone: Next-
Component: Boss of BIND | Sprint-Proposed
Keywords: | Resolution:
Sensitive: 0 | CVSS Scoring:
Sub-Project: Core | Defect Severity: Low
Estimated Difficulty: 2 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by jreed):
* milestone: => Next-Sprint-Proposed
Comment:
BIND10_SOCKET_CREATED is not useful normal info. Adding to next sprint
proposed again.
Also BIND10_SOCKET_GET probably should be debug too. As it is, it
doesn't tell you what component needs that socket.
--
Ticket URL: <http://bind10.isc.org/ticket/1716#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list