Bug#714526: still an issue - makes callers hang

[Julien Palard <julien@palard.fr>]

o/

On Sun, 15 Feb 2015 11:32:17 +0000 Colin Watson <cjwatson@debian.org> wrote:
> Noted; but it'd be a fairly reasonable workaround to just use "ssh
> -Snone", wouldn't it?

I just ran on this "bug", on openssh-client 1:6.7p1-5 after setting up
ssh multiplexing on purpose. So using ssh -Snone is not an option, my
script is doing a multiple ssh connections and using multiplexing is a
big win for me, but I can't use python's subprocess communicate (and
other functions using it like check_output), as it won't return,
sometimes, waiting for stderr to exit.

Also on a daily basis, out of the python world, I think it's unexpected
to have, in our shells, some processes keeping an opened stderr and
probably writing to it a few hours / days later. It looks missleading /
unexpected, so it looks wrong.

-- 
Julien Palard