Re: non-blocking code and EAGAIN

[Andreas Schneider <asn@xxxxxxxxxxxxxx>]

On Thursday, 9 February 2017 03:58:59 CEST Matthew Avery wrote:
> Hi,
> How is libssh able to handle non-blocking sockets if errno==EAGAIN isn't
> handled specially? Upon lightly examining socket.c it seems like if errno
> is < 0 on read or write then the connection goes into an error mode
> (data_except is set which subsequently sets the status to SSH_CLOSED_ERROR)

Sounds like a bug which needs fixing :)


Can you provide a patch?


Thanks,


	Andreas


-- 
Andreas Schneider                   GPG-ID: CC014E3D
www.cryptomilk.org                asn@xxxxxxxxxxxxxx