BIND 10 #1180: msgq dies on socket send error
BIND 10 Development
do-not-reply at isc.org
Tue Aug 16 10:44:10 UTC 2011
#1180: msgq dies on socket send error
-------------------------------------+-------------------------------------
Reporter: shane | Owner:
Type: defect | Status: new
Priority: major | Milestone: Next-
Component: Unclassified | Sprint-Proposed
Sensitive: 0 | Keywords:
Sub-Project: DNS | Defect Severity:
Estimated Difficulty: 0 | Medium
Total Hours: 0 | Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Jeremy reported an error to the bind10-dev list:
https://lists.isc.org/pipermail/bind10-dev/2011-August/002558.html
The included trace ends like this:
{{{
"/b/work/BIND10-systest/20110812084501-MacOS/build/src/bin/msgq/b10-msgq",
line 344, in __send_data
return sock.send(data)
socket.error: [Errno 32] Broken pipe
}}}
We need to wrap this, so that msgq does not exit.
--
Ticket URL: <http://bind10.isc.org/ticket/1180>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list