On Wed, 16 Sep 2009, Xu, Qiang (FXSGSC) wrote:
Then you don't use a libssh2 version built with debug
enabled. configure --enable-debug is your friend!
Yes, I forgot to use this flag to configure it. Thanks for reminding.
Now I get a lot of information, most of them binary.
Binary? That sounds wrong...
So I think ~0 is not a good idea.
I actually use ~0 a lot when I test stuff with great success.
[libssh2] 0.178181 Failure Event: -37 - Would block waiting for banner
[libssh2] 0.186328 Failure Event: -37 - Would block exchanging encryption keys
[libssh2] 0.192722 Failure Event: -37 - Would block exchanging encryption keys
Fingerprint: 0B F2 D3 94 9D 0F 75 BE 69 15 33 42 B8 0D 88 CA
[libssh2] 0.268435 Failure Event: -37 - Would block requesting userauth list
Authentication methods: publickey,gssapi-with-mic,password
libssh2_sftp_init()!
[libssh2] 0.276924 Failure Event: -37 - Would block
[libssh2] 0.276947 Failure Event: -37 - Would block starting up channel
[libssh2] 0.292252 Failure Event: -37 - Would block to request SFTP subsystem
[libssh2] 0.327202 Failure Event: -25 - SFTP packet too large
[libssh2] 0.327250 Failure Event: -30 - Timeout waiting for response from SFTP
subsystem
Unable to init SFTP session
all done
===================================================
There are so many "Failure event". Which one is the most critical?
The -37 ones are just EAGAIN so they can mostly be ignored. The first one
after that is a "SFTP packet too large" which in my ears sounds very
interesting to research further...
--
/ daniel.haxx.se
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
