Screen - Revision history

Mhanby@uab.edu: /* Screen Example */

2015-02-20T16:38:55Z

Screen Example

← Older revision		Revision as of 16:38, 20 February 2015
Line 9:		Line 9:
	* Start up an interactive job using qlogin to download a large dataset that will take approximately 24 hours to complete:		* Start up an interactive job using qlogin to download a large dataset that will take approximately 24 hours to complete:
	qlogin -l h_rt=24:00:00,vf=128M		qlogin -l h_rt=24:00:00,vf=128M
			wget --no-check-certificate https://some.data.site.org/impute/1000GP_Phase3.tgz
	* Oops, the IT folks just updated your workstation with security patches that require it to reboot. Rebooting means closing the connection to Cheaha, killing your qlogin interactive job		* Oops, the IT folks just updated your workstation with security patches that require it to reboot. Rebooting means closing the connection to Cheaha, killing your qlogin interactive job

Mhanby@uab.edu: /* Screen Example */

2015-02-20T16:38:19Z

Screen Example

← Older revision		Revision as of 16:38, 20 February 2015
Line 9:		Line 9:
	* Start up an interactive job using qlogin to download a large dataset that will take approximately 24 hours to complete:		* Start up an interactive job using qlogin to download a large dataset that will take approximately 24 hours to complete:
	qlogin -l h_rt=24:00:00,vf=128M		qlogin -l h_rt=24:00:00,vf=128M
	* Oops, the IT ~~guys~~ just updated your workstation with security patches that require it to reboot. Rebooting means closing the connection to Cheaha, killing your qlogin interactive job		* Oops, the IT folks just updated your workstation with security patches that require it to reboot. Rebooting means closing the connection to Cheaha, killing your qlogin interactive job

	So, how would screen or tmux solve this? If we'd have started a screen session before running the qlogin command, the job would have continued to run because screen keeps the shell alive even if our ssh connection to cheaha is disconnected. Here's how to do it:		So, how would screen or tmux solve this? If we'd have started a screen session before running the qlogin command, the job would have continued to run because screen keeps the shell alive even if our ssh connection to cheaha is disconnected. Here's how to do it:

Mhanby@uab.edu: Added a new Screen example

2015-02-20T16:37:48Z

Added a new Screen example

@@ Line 1: / Line 1: @@
-If you are experiencing disconnects with the Cheaha head node due to flaky network connections or you want to maintain a shell context over time, then the screen command may be helpful.
+If you are experiencing disconnects with the Cheaha head node or you want to maintain a shell context over time, then the screen or tmux commands may be helpful.
-Screen allows you to create terminal sessions on the head node that you can disconnect and reconnect across individual ssh sessions.   For example, if you start a qlogin session within one of these terminals then your qlogin session will last as long as the time slice you have requested or until you explicitly exit the session.
+You can use either Screen or Tmux to create shell sessions on the head node (or other Linux systems) that can be disconnected without terminating the shell. They both do the same thing but have different syntax and command keys, so pick one and learn to use it.
-The screen users manual is helpful http://www.gnu.org/software/screen/manual/screen.html.
+=== Screen Example ===
 Note that if you are using X window tunneling with your qlogin session this won't work without extra manual effort for a qlogin session within screen.
 This page is a stub, please help expand it.

Jpr@uab.edu: Create stub page in response to support request

2013-12-30T16:24:29Z

Create stub page in response to support request

New page

If you are experiencing disconnects with the Cheaha head node due to flaky network connections or you want to maintain a shell context over time, then the screen command may be helpful.

Screen allows you to create terminal sessions on the head node that you can disconnect and reconnect across individual ssh sessions. For example, if you start a qlogin session within one of these terminals then your qlogin session will last as long as the time slice you have requested or until you explicitly exit the session.

The screen users manual is helpful http://www.gnu.org/software/screen/manual/screen.html.

Note that if you are using X window tunneling with your qlogin session this won't work without extra manual effort for a qlogin session within screen.

This page is a stub, please help expand it.