www.libssh2.org | Daily snapshots | Mailing list archive | Docs | Examples | github

Archive Index This month's Index

Subject: Re: sharing experiences with nonblocking exec and NVAL from libssh2_channel_wait_closed() with community

Re: sharing experiences with nonblocking exec and NVAL from libssh2_channel_wait_closed() with community

From: Peter Stuge <peter_at_stuge.se>
Date: Sat, 25 Feb 2012 20:19:18 +0100

Steven Dake wrote:
> The reason for the enter back into the read state is that
> libssh2_channel_wait_closed() checks for eof, and even though the code
> has already checked and passed the EOF state, further packets appear to
> be sent on the channel.

I'm not sure if that is allowed. What packets are sent?

> This seems like some kind of odd race condition to me,

Can you show libssh2 trace output from this happening?

//Peter
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2012-02-25

the libssh2 team