Hi, By default sessions are blocking. We have made a lot of progress in non-blocking connections and it's believed to work. However blocking doesn't mean 100% cpu. Could you provide a backtrace ? Also, which version of libssh are you using ?
Thanks, Aris Le 14/11/12 19:09, Jonathan Walker a écrit : > Hello, > > > > I noticed the following note under the doc describing the function > */ssh_set_blocking/* > > > > *Bug: <http://api.libssh.org/stable/bug.html#_bug000003>* > > nonblocking code is in development and won't work as expected > > > > Are SSH sessions by default in blocking or non-blocking mode? I notice > in rare cases that the */ssh_connect/* function is getting stuck and > taking up 100% CPU on my system. I was wondering if the above note may > have anything to do with this? Presumably blocking mode should not mean > that the function gets stuck in a loop? I’ll try to capture logs, but > the issue is not reproducible with a known set of steps. > > > > Thanks, > > Jonathan > > > ------------------------------------------------------------------------ > This e-mail and any files transmitted with it are ShoreTel property, are > confidential, and are intended solely for the use of the individual or > entity to whom this e-mail is addressed. If you are not one of the named > recipient(s) or otherwise have reason to believe that you have received > this message in error, please notify the sender and delete this message > immediately from your computer. Any other use, retention, dissemination, > forwarding, printing, or copying of this e-mail is strictly prohibited
