Bureaucrats, cc_docs_admin, cc_staff
2,306
edits
Prolonging terminal sessions: Difference between revisions
Jump to navigation
Jump to search
→Screen
(→Screen) |
|||
| Line 10: | Line 10: | ||
This addition will ensure the transmission of a sign-of-life signal over the SSH connection to the cluster every four minutes (240 seconds), 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 the cluster every four minutes (240 seconds), which should help to keep your SSH connection alive even if it is idle for several hours. | ||
=Screen= | =Terminal multiplexers= | ||
The programs <tt>screen</tt> and <tt>tmux</tt> are examples of a terminal multiplexer - a program which allows you to detach your terminal session entirely, where it will keep on running on its own until you choose to reattach to it. With such a program, you can logout from the cluster, turn off the workstation or hibernate the laptop you use to connect to the cluster and when you're ready to start working again the next day, reattach to your session and start from right where you left off. In the context of our clusters, one thing you will need to keep in mind is that we have several login nodes for each cluster and your <tt>screen</tt> or <tt>tmux</tt> session is specific to a login node. If you wish to reattach to a session, you will first need to ensure you're connected to the right login node which of course means remembering which login node you had been using before. Equally so, we make no guarantee that a particular login node won't be rebooted, which will kill any detached terminal sessions on that node. | |||
==Screen== | |||
=TMUX= | =TMUX= | ||