thanks, i'll be waiting :) On Thu, Feb 11, 2010 at 4:34 PM, Aris Adamantiadis <[email protected]> wrote: > Hi > > Stephan's remark is relevant as I'm thinking about a totaly threadsafe > API for 0.5 or 0.5.x and this approach is not fully threadsafe. > > Thanks for pointing this out. But as Vic noticed, care must be taken > when using threading with libssh. > > Regards, > > Aris > > Vic Lee a écrit : >> Hi, >> >> One ssh_session can be used in only one thread, that's the current >> rule. :) I use ssh_select to operate multiple channels in one thread and >> I am good with this approach. >> >> Vic >> >> On Thu, 2010-02-11 at 16:00 +0300, Stephan Kountso wrote: >>> Many of channel_* functions return SSH_ERROR on error. But there is >>> exists only one function to get the reason of any errors: >>> ssh_get_error with only argument "ssh session", not channel. >>> >>> So, my questions are: >>> 1) how to handle ssh channel errors? >>> 2) if also with ssh_get_error, then how about thread-safety? Multiply >>> threads on multiply channels cause corruption on ssh_get_error. >>> >> >> >> >> > > >
-- С уважением, Кунцьо Степан aka StepLg
