Hey
I was pointed to this yesterday (and I've adjusted to this in libcurl), so I
thought I should just point this out to people here that might write apps for
uploading on windows:
http://support.microsoft.com/kb/823764
--
/ daniel.haxx.se
-
Hello,
Exec "uptime" on a remote machine (LAN) does not
return the "stdout" output, if "libssh2_channel_read()"
is not called fast enough.
Instead, "libssh2_channel_read()" returns zero.
This issue may be reproduced via the attached c-file.
If the "sleep(3)" right before "libssh2_channel_read()"
On Wed, 29 Apr 2009, double wrote:
> Exec "uptime" on a remote machine (LAN) does not return the "stdout" output,
> if "libssh2_channel_read()" is not called fast enough. Instead,
> "libssh2_channel_read()" returns zero.
>
> This issue may be reproduced via the attached c-file. If the "sleep(3)"
On this note, I still have a problem (only in 1.1) that is similar to
this. libssh2_channel_read() returns 0 on occasion when connected to
a OS X machine (10.4 or 10.5 at least) I'd connect and execute a
couple commands and sometimes I wouldn't get any data for something
like a simple "ls
On Wed, 29 Apr 2009, Jeremy Knope wrote:
> On this note, I still have a problem (only in 1.1) that is similar to this.
> libssh2_channel_read() returns 0 on occasion when connected to a OS X
> machine (10.4 or 10.5 at least) I'd connect and execute a couple commands
> and sometimes I wouldn't
Delaying before reading looks like it makes it fail 100%. I tried 5
commands (ls) in a row with 1 second delay and it had 0 bytes of data
every time.
Without the delay I got data, then none, then 3rd time it blocked on
read locking my application up (I'm using it in blocking mode)
The bloc
Hi,
double wrote:
> This issue may be reproduced via the attached c-file.
> If the "sleep(3)" right before "libssh2_channel_read()"
> is removed, everything works fine.
Wtf bug. :\
//Peter
--
Register Now & Save for Ve