BIND 10 #1180: msgq dies on socket send error
BIND 10 Development
do-not-reply at isc.org
Mon Oct 24 08:42:45 UTC 2011
#1180: msgq dies on socket send error
-------------------------------------+-------------------------------------
Reporter: shane | Owner: vorner
Type: | Status: reviewing
defect | Milestone:
Priority: major | Sprint-20111025
Component: msgq | Resolution:
Keywords: | Sensitive: 0
Defect Severity: | Sub-Project: Core
Medium | Estimated Difficulty: 3
Feature Depending on Ticket: | Total Hours: 0
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by jelte):
* owner: jelte => vorner
Comment:
Replying to [comment:7 vorner]:
> Hello
>
> Maybe the message should be „Dropping the connection and message“
instead of just message.
>
made it "dropping message and closing connection"
> Should it have a changelog that the bug should be gone now?
>
ohyeah, how about:
XXX. [defect] jelte
msgq no longer crashes if the remote end is closed while msgq tries to
send data. It will now simply drop the message and close the connection
itself.
> I also noticed that the import pprint is not needed, there are only two
commented-out calls to it. Should it be cleaned out?
>
removed
> And, finally, the branch does not compile for me. It fails in some dhcp-
related C++ tests, even after merging with master. Should we wait for it
to clean up? Do you have an idea if Tomek knows?
>
luckily i missed this :) I'm assuming this has been fixed now, but either
way this change should be orthogonal (except that perhaps now you haven't
verified whether msgq now even runs at all)
--
Ticket URL: <http://bind10.isc.org/ticket/1180#comment:8>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list