Detecting closing of underlying session connection about net-ssh-gateway HOT 6 CLOSED

It seems like checking for @session.closed? in this loop: https://github.com/net-ssh/net-ssh-gateway/blob/master/lib/net/ssh/gateway.rb#L196-L201 could be the start of detecting a closed connection.

If @delano or @jamis have any perspective on how they'd like to alert the gateway, I'd be happy to send a PR.

from net-ssh-gateway.

Could be as simple as adding a method on the gateway instance to check for @session.closed?, leave it up to the user to watch for closed connections.

from net-ssh-gateway.

Can you detail the concrete usecase?

from net-ssh-gateway.

Servers A, B, and C. A => B => C, with B acting as a tunnel/gateway. If B or C close the connection from their end, there does not appear to be away to ask the ruby gateway instance if the connection is still active, to take action (like restarting a process or killing a DB connection).

from net-ssh-gateway.

Thanks. Net-ssh-gateway is in maitanance mode, and AFAIK we have no plans to extend it to support your usecase.
You should be able to subclass Gateway and get access to @session but it's tricky business because of the locking, another option might be forking the library. Then we can discuss if/in what way we can integrate those changes.

from net-ssh-gateway.

I can send a PR @mfazekas.

from net-ssh-gateway.