[SOLVED] what can be done when remote ssh connection dropped and konsole become not responding ?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
what can be done when remote ssh connection dropped and konsole become not responding ?
I am learning ssh on KDE to remote ssh server.
Question1:
while i was connected to remote ssh server, when i need to rush to leave home, i would just "suspend the local machine into ram" . Is it ok like this ? will the "hanging" connection give loop hole to some hacker ? or it will not, since it is ssh.. what is the proper procedure to disconnect remote ssh ? " quit " command ?
Question2:
After i woke up the local computer from ram suspend, the konsole will be not responding to anything... it will not try to reconnect.. the console just doing nothing.. i have to close the konsole windows and reopen another konsole window in order to start a new ssh connection.
What are the way to "reset" the hanging console apart from close the window and reopen window ?
Question3:
There is one case i encountered, the ssh still connected after woke from suspension, any idea how ? Why only 1 time it ever "still connected" while other cases, not ?
1) You can usually disconnect the remote session by exiting the program. If it is the shell, type "exit". Or you use an escape sequence, "~.", to disconnect. See "man ssh" and scroll down to the section on escape characters.
2) More information is needed. Was there a program running prior to the suspend?
3) The timeout had not been exceeded. You can set ClientAliveCountMax and ClientAliveInterval in the SSH server's configuration file or you can set ServerAliveCountMax and ServerAliveInterval in the client's configuration file. See "man sshd_config" or "man ssh_config". The client's configuration file is usually ~/.ssh/config but you might have to create it yourself.
1) You can usually disconnect the remote session by exiting the program. If it is the shell, type "exit". Or you use an escape sequence, "~.", to disconnect. See "man ssh" and scroll down to the section on escape characters.
2) More information is needed. Was there a program running prior to the suspend?
The escape character and other escape characters are mostly not working.. however " ~? " this one work. lol.
No, there was no program running, only empty shell.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.