Re: Reading multiple channels under the same session

[Alberto Garcia <agarciaillera@xxxxxxxxx>]

That's probably happening because the python code is creating too many
connections at the same time right?

But, yes, as you said that looks like somewhere in your code you are
forgetting to close the fd of the sockets that already did his job.

On Wed, Jan 30, 2019 at 3:29 PM <g4-lisz@xxxxxxxxxxxx> wrote:

> till@elite:~/libssh$ ssh user@localhost -p2022 -D 11223 -N
> user@localhost's password:
> accept: Too many open files
> accept: Too many open files
> accept: Too many open files
>
> I call this a success... Don't ask me how many sessions were open at the
> same time. But it's probably also because not all sockets were closed.
> I'm still working on this.
>
> Cheers,
> Till
>
> On 30.01.19 23:34, g4-lisz@xxxxxxxxxxxx wrote:
> > On 30.01.19 22:50, Alberto Garcia wrote:
> >
> >> Hi,
> >>
> >> what about waiting to call ssh_event_remove_fd()
> >> until my_channel_close_function() is reached?
> > We have to remove the socket fd from the poll event in the same loop
> > round when it's closed. We should avoid polling on a closed handle.
> >
> > It's all a question of the timing / synchronisation.
> >
> > My design mistake is to modify channel stuff from within the callbacks.
> > Some of these ssh_  functions trigger the callbacks again, so it's kind
> > of unforeseeable what's going to happen...
> >
> > I'm moving all this stuff out of the callback functions now...
> >
> > Till
> >
> >
>
>

-- 
Alberto García Illera

GPG Public Key <https://goo.gl/yshdwh>