On Tuesday 04 November 2014 09:58:32 Doug Judd wrote:
> I confronted this issue as well. The documentation is lacking in this
> area. It appears that most of the APIs, when they return SSH_AGAIN, it
> means that you need to wait until the underlying socket becomes ready for
> reading. I found this to be true for both connection establishment APIs
> and command execution APIs. I suppose that if you issue commands that are
> large, ssh_channel_request_exec() could return SSH_AGAIN and require you to
> wait until the socket becomes ready for writing, however, I'm not 100% sure
> on this.
Patches to fix the documentation are very welcome!
-- andreas
--
Andreas Schneider GPG-ID: CC014E3D
www.cryptomilk.org [email protected]
