29 Apr
2014
29 Apr
'14
11:59 a.m.
"Bendler, Ehren" <ebendler@ciena.com> writes: [...]
If this is the intended behavior, that's fine too. We can deploy our own patch to the afsocket module if it isn't going to be changed in a release.
No, this is definitely not the intended behaviour. Some change between 3.3.5 and 3.5.7 broke the fix, I'll go ahead and restore the intended behaviour. Thanks for reporting the issue! Unfortunately, I can't help with the other issue at the moment, but I'll try to revisit it later. -- |8]