[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ssh_channel_read - expected behavior?
[Thread Prev] | [Thread Next]
- Subject: Re: ssh_channel_read - expected behavior?
- From: Andreas Schneider <asn@xxxxxxxxxxxxxx>
- Reply-to: libssh@xxxxxxxxxx
- Date: Mon, 24 Sep 2012 10:06:02 +0200
- To: libssh@xxxxxxxxxx
On Thursday 20 September 2012 06:03:16 you wrote: > Hello, Hey, > My colleague and I updated our LibSSH library to the most recent source tree > around mid-August (we manually built the library). We noticed that the > function "ssh_channel_read" began to behave a bit differently from the > previous 0.5.0 library. I also noticed from the release note of 0.5.2 the > following: o > Fixed possible infinite loop in channel_read(). > > This leads me to believe that there was indeed a functionality change. We > have been noticing that the function periodically returns even if no bytes > have been read. I would assume that this is to prevent getting stuck in > the infinite loop as addressed in the note. Could I get a bit more detail > on the expected functionality of this function call? Can we expect that > the function return within x seconds (even if no bytes have been read)? We added supports for timeouts, I think the default is 30 seconds. Is that the time you notice it?. -- andreas -- Andreas Schneider GPG-ID: F33E3FC6 www.cryptomilk.org asn@xxxxxxxxxxxxxx
RE: ssh_channel_read - expected behavior? | Jonathan Walker <jwalker@xxxxxxxxxxxx> |
ssh_channel_read - expected behavior? | Jonathan Walker <jwalker@xxxxxxxxxxxx> |