Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconnect to session after killing client #222

Closed
tsoernes opened this issue Aug 21, 2019 · 6 comments
Closed

Reconnect to session after killing client #222

tsoernes opened this issue Aug 21, 2019 · 6 comments

Comments

@tsoernes
Copy link
Contributor

Is this possible?
Say that you kill an et session on the client side. Can you reconnect to the same 'session' on the server?

@MisterTea
Copy link
Owner

No this isn't possible, but you can use tmux or screen to detach your session from et.

@tsoernes
Copy link
Contributor Author

Can I make a feature request for that? tmux and screen are inconvenient wrt. scrolling etc

@MisterTea
Copy link
Owner

Use tmux control center (OSX) or HTM (other OSes) to get native scroll back.

Making the et client survive being killed would be very difficult.

@dandv
Copy link
Contributor

dandv commented Nov 6, 2019

I'd also like the ability to reconnect to a session. My client machine ran out of battery, and now I have an orphan "session" on the remote server.

@MisterTea
Copy link
Owner

MisterTea commented Nov 6, 2019

@dandv you can pass the "-x" switch to have et kill all other sessions by the same user before starting a new connection, or you can kill the orphan session manually.

It would be a huge amount of work to make et survive client app failure in a way that didn't compromise security.

@luismarques
Copy link

I just wanted to share that I also ran into this issue. I suggest that, at a minimum, the manual indicates that it's not possible to reconnect to a server if the client has died. But ideally this really should be possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants