The ssh_set_blocking() call currently has the following disclaiming in the "master" documentation:
nonblocking code is in development and won't work as expected This surprised me. Since there are dozens of functions that support non-blocking mode (by returning SSH_AGAIN when necessary), I thought non-blocking mode would've been an established feature. This must mean that the "remote shell" functionality is also limited, as its virtually useless without being in nonblocking mode. Does anyone know the status of this? Thanks. Dustin Oprea
