Hi everyone, I'm developing a c++-class for local and remote forwarding. I got it to work after days of testing and debugging. While doing so I noticed that the library is behaving very strangely after closing a channel.
Here is what I do: - open a Session - open a direct TCPIP channel - send and receive some data on the channel - close the channel (libssh2_channel_close + libssh2_channel_free) Up to this point everything works as expected. If I try to open another direct TCPIP channel to any host and port the session is killed immediately. There is no error message at all. The channel is not created and using "netstat" I can watch how the session socket is closed. The way I see it, this is a major bug because the session should stay alive until I tell it to close. My workaround is to use a separate session for every channel. Even though this is a very crude way, it works stable. Did anyone experience the same behavior? Is somebody using the described operation without any error? As anyone any suggestions? Kind regards, Stefan Kögel p.s.: could somebody please fix libssh2_poll for linux? I'd love to read channels in non-blocking mode without getting stuck for a long time! -------------------------------------------------------------- using openSUSE 11.1 2.6.27.7-9-pae and libssh2-1.0 ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ libssh2-devel mailing list libssh2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libssh2-devel
