-
-
Notifications
You must be signed in to change notification settings - Fork 166
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
Comments
No this isn't possible, but you can use tmux or screen to detach your session from et. |
Can I make a feature request for that? tmux and screen are inconvenient wrt. scrolling etc |
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. |
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. |
@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. |
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. |
Is this possible?
Say that you kill an
et
session on the client side. Can you reconnect to the same 'session' on the server?The text was updated successfully, but these errors were encountered: