----- Original Message ----- From: "Peter Stuge" <pe...@stuge.se> To: libssh2-devel@cool.haxx.se Sent: Monday, April 16, 2012 8:06:57 PM Subject: Re: libssh2 thread safety
Peter Stuge wrote: > Jasmeet Bagga wrote: > >>> [libssh2] 0.956992 Socket: Recved 0 bytes banner > >>> [libssh2] 0.956996 Failure Event: -43 - Failed getting banner > >>> [libssh2] 0.957045 Transport: Disconnecting: reason=11, desc=, lang= > >> > >> The log shows that the problem is very very early. > > > > JFYI, the problem was that the remote device has a very low rate > > limit for ssh connections and it was abruptly terminating ssh > > connections (after the TCP connection succeeded), leading to the > > above seen errors. > > Sure. > > So one thing that could be improved about libssh2 here is the > reported error. Currently you get LIBSSH2_ERROR_SOCKET_RECV but it > could be made more clear that the connection was unexpectedly closed. > > Do you have some suggestion for a more useful error code? How about the attached? I think this is better //Peter _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
