BIND 10 #2617: MSGQ_RECV_ERR errors on clean shutdown
BIND 10 Development
do-not-reply at isc.org
Mon Jan 21 10:11:09 UTC 2013
#2617: MSGQ_RECV_ERR errors on clean shutdown
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: low | Milestone: Next-
Component: msgq | Sprint-Proposed
Keywords: | Resolution:
Sensitive: 0 | CVSS Scoring:
Sub-Project: Core | Defect Severity: Low
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by shane):
Okay, makes sense. We can check to see if it is EOF and create a new debug
message, MSGQ_RECV_EOF, for that.
We should also print out the details of the socket.error message that we
get, such as the errno and description, when that happens. (I suspect that
we will also need to make some errno debug level, such as ECONNRESET or
the like.)
--
Ticket URL: <http://bind10.isc.org/ticket/2617#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list