BIND 10 #1829: CC Session timeouts / ConfigManager not responding (on OpenBSD)
BIND 10 Development
do-not-reply at isc.org
Fri Mar 23 23:45:30 UTC 2012
#1829: CC Session timeouts / ConfigManager not responding (on OpenBSD)
-------------------------------------+-------------------------------------
Reporter: jreed | Owner: jinmei
Type: | Status: accepted
defect | Milestone:
Priority: | Sprint-20120403
medium | Resolution:
Component: | Sensitive: 0
Unclassified | Sub-Project: Core
Keywords: | Estimated Difficulty: 0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
trac1829 is ready for review (this time I wrote a test first:-)
I also made it a bit more reliable by ensuring header part can also be
sent incrementally if necessary (it's less likely to be necessary
in practice, but can still happen if, e.g. the other end is too busy).
Another note, not directly related to this ticket: I checked the same
scenario with test code written in C. It didn't happen. I guess
it's due to something internal to (OpenBSD's?) Python network/socket
library. So we don't have to update the C++ version (at least it's
not urgent).
This is proposed changelog:
{{{
409.? [bug] jinmei
Python CC library now ensures write operations transmit all given
data (unless an error happens). Previously it didn't check the
size of transmitted data, which could result in partial write on
some systems (notably on OpenBSD) and subsequently cause system
hang up or other broken state. This fix specifically solves start
up failure on OpenBSD.
(Trac #1829, git TBD)
}}}
--
Ticket URL: <http://bind10.isc.org/ticket/1829#comment:7>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list