On Wed, 22 Apr 2009, double wrote:
>> No, libssh2_poll_channel_read() or libssh2_poll() won't save you and
>> they're both also defective and deemed deprecated.
>
> There are only problems with reading from libssh2. Would it be a solution to
> call "select()" to the libssh2-socket before calling
Hi Daniel,
Thank you very much for your answer!
> No, libssh2_poll_channel_read() or libssh2_poll() won't save you and they're
> both also defective and deemed deprecated.
>
There are only problems with reading from libssh2. Would it be
a solution to call "select()" to the libssh2-socket bef
On Wed, 22 Apr 2009, double wrote:
>>> Is there an easy way to set a timeout to libssh2?
>> Not really (the way I think you mean).
>
> Thank you very much for your answer. I am using libssh2 in a blocking
> manner. Could I use "libssh2_poll_channel_read" or "libssh2_poll" to prevent
> this dead
Daniel Stenberg schrieb:
On Tue, 21 Apr 2009, double wrote:
Is there an easy way to set a timeout to libssh2?
Not really (the way I think you mean).
Without modifying libssh2, you can switch to using it in a non-blocking manner
as then you can do the time-out logic yourself in your ap
On Tue, 21 Apr 2009, double wrote:
> There are tons of old processes on my server. If I send them a sigterm (15),
> the process prints a backtrace and exits. The issue, the backtrace tells me,
> that the process died in the function "libssh2_channel_read_ex" (after
> calling libssh2_channel_exe
Hello,
There are tons of old processes on my server. If I send
them a sigterm (15), the process prints a backtrace
and exits.
The issue, the backtrace tells me, that the process died
in the function "libssh2_channel_read_ex" (after calling
libssh2_channel_exec).
Is there an easy way to set a timeo
