On Sun, 3 Mar 2013, Anton Obukhov wrote:
Thanks for your suggestion Alex, but I'm using the non-blocking API exactly as you advised: I call libssh2_session_free with the same paramerters until either it returns something different than EAGAIN, or the timeout happens. In my case, when the remote device goes down ungracefully, any amount of seconds wait will result in timeout: I even tried 15 seconds. I suppose resource destruction should be instant. It looks like libssh is waiting for something inside there, whereas I want it to just free all resources...
That make it sound like a bug. Can you tell us how to repeat this problem? Can you single-step through the code and see where the problem lies?
Which libssh2 vesion are you using? -- / daniel.haxx.se _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
