Bureaucrats, cc_docs_admin, cc_staff
2,306
edits
Prolonging terminal sessions: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
<languages /> | |||
<translate> | |||
For working on the clusters, most users will need to use [[SSH]] to connect to the cluster for job submission and monitoring, editing files and so forth. Keeping this SSH connection alive for a long period of time, ranging from hours to days, may be necessary for some users and this page proposes a variety of techniques for keeping such a terminal session alive. | For working on the clusters, most users will need to use [[SSH]] to connect to the cluster for job submission and monitoring, editing files and so forth. Keeping this SSH connection alive for a long period of time, ranging from hours to days, may be necessary for some users and this page proposes a variety of techniques for keeping such a terminal session alive. | ||
| Line 6: | Line 6: | ||
One simple solution is to modify the configuration of your SSH client to prolong the connection. On MacOS and Linux the client configuration is found in <tt>$HOME/.ssh/config</tt> while in Windows it is located in <tt>C:\Users\<username>\.ssh\config</tt>. Note that the file may not exist initially, so you will need to create it; you should add the lines | One simple solution is to modify the configuration of your SSH client to prolong the connection. On MacOS and Linux the client configuration is found in <tt>$HOME/.ssh/config</tt> while in Windows it is located in <tt>C:\Users\<username>\.ssh\config</tt>. Note that the file may not exist initially, so you will need to create it; you should add the lines | ||
</translate> | |||
<source> | <source> | ||
Host * | Host * | ||
ServerAliveInterval 240 | ServerAliveInterval 240 | ||
</source> | </source> | ||
<translate> | |||
This addition will ensure the transmission of a sign-of-life signal over the SSH connection to any remote server (such as an Alliance cluster) every 240 seconds, i.e. four minutes, which should help to keep your SSH connection alive even if it is idle for several hours. | This addition will ensure the transmission of a sign-of-life signal over the SSH connection to any remote server (such as an Alliance cluster) every 240 seconds, i.e. four minutes, which should help to keep your SSH connection alive even if it is idle for several hours. | ||
| Line 70: | Line 72: | ||
}} | }} | ||
You can attach to one of your sessions using the command <tt>screen -d -r <session name></tt>. | You can attach to one of your sessions using the command <tt>screen -d -r <session name></tt>. | ||
</translate> | |||