Channel life span

[Damien Miller]

On Mon, 10 Oct 2011, David Goulet wrote:

> So, I did try, using a third part lib for SSH (libssh2), to recreate
> a direct-tcpip channel and *keep* the channel open (not sending the
> EOF) in order to send data later on (where the time between writes on
> the channel is unknown). However, here is what's happening. After the
> first write to the channel, I read the data back (reply), and keep the
> channel open (don't send the EOF on my side). A quick 5 seconds later,
> I get this on the sshd (server side):
>
> debug2: channel 1: read<=0 rfd 8 len 0
> debug2: channel 1: read failed

Whatever you are talking to on the server has closed its standard output
or otherwise done something that triggered a failed read. The code that
emits this message is channels.c:channel_handle_rfd() and if you read it,
you'll see that there is no other way that this message can be generated.

-d