Screen - Revision history

Jayid07: /* Usage */

2022-04-22T15:16:09Z

Usage

← Older revision		Revision as of 15:16, 22 April 2022
Line 21:		Line 21:

	The output will be similar to this:		The output will be similar to this:
	# username@~~opensub02~~:~$ screen -ls		# username@tron02:~$ screen -ls
	# There are screens on:		# There are screens on:
	# 26598.screenTest1 (Detached)		# 26598.screenTest1 (Detached)
	# 18457.pts-0.~~opensub02~~ (Detached)		# 18457.pts-0.tron02 (Detached)
	# 2 Sockets in /var/run/screen/S-username.		# 2 Sockets in /var/run/screen/S-username.

	To reconnect to a specific screen session you may use either the screen number or name to reconnect using ‘screen -r’		To reconnect to a specific screen session you may use either the screen number or name to reconnect using ‘screen -r’
	# username@~~opensub02~~:~$ screen -r 26598		# username@tron02:~$ screen -r 26598

	or		or

	# username@~~opensub02~~:~$ screen -r screenTest1		# username@tron02:~$ screen -r screenTest1


	===Common Keyboard Shortcuts===		===Common Keyboard Shortcuts===

Mbaney at 15:46, 7 May 2021

2021-05-07T15:46:17Z

← Older revision		Revision as of 15:46, 7 May 2021
Line 21:		Line 21:

	The output will be similar to this:		The output will be similar to this:
	# ~~claw~~@~~idaho~~:~$ screen -ls		# username@opensub02:~$ screen -ls
	# There are screens on:		# There are screens on:
	# 26598.screenTest1 (Detached)		# 26598.screenTest1 (Detached)
	# 18457.pts-0.~~idaho~~ (Detached)		# 18457.pts-0.opensub02 (Detached)
	# 2 Sockets in /var/run/screen/S-~~claw~~.		# 2 Sockets in /var/run/screen/S-username.

	To reconnect to a specific screen session you may use either the screen number or name to reconnect using ‘screen -r’		To reconnect to a specific screen session you may use either the screen number or name to reconnect using ‘screen -r’
	# ~~claw~~@~~idaho~~:~$ screen -r 26598		# username@opensub02:~$ screen -r 26598

	or		or

	# ~~claw~~@~~idaho~~:~$ screen -r screenTest1		# username@opensub02:~$ screen -r screenTest1


Line 40:		Line 40:
	* Ctrl-A + c (Creates a new window.)		* Ctrl-A + c (Creates a new window.)
	* Ctrl-A + d (detach from current session)		* Ctrl-A + d (detach from current session)
	* Ctrl-A + [0-9] (Switches to the window ~~corresonding~~ to the number, window 0 is the first window initialized by screen.)		* Ctrl-A + [0-9] (Switches to the window corresponding to the number, window 0 is the first window initialized by screen.)
	* Ctrl-A + " (Presents a selection of screen windows from which to choose.)		* Ctrl-A + " (Presents a selection of screen windows from which to choose.)
	* Ctrl-A + Shift-A Rename the current screen window		* Ctrl-A + Shift-A Rename the current screen window

Jhaslup at 17:50, 15 January 2019

2019-01-15T17:50:28Z

← Older revision		Revision as of 17:50, 15 January 2019
Line 1:		Line 1:
	=== Introduction ===		=== Introduction ===
	GNU Screen, or "screen", is a window management program available on UMIACS Linux hosts that allows multiplexing of a single terminal between multiple virtual consoles. Screen is also capable of separating programs from the shell that initially started it which allows a program to continue running even if the connection to the host has been lost. For this reason screen is typically used when a network connection is unstable and the process must remain running even if an SSH connection has dropped.		GNU Screen, or "screen", is a window management program available on UMIACS Linux hosts that allows multiplexing of a single terminal between multiple virtual consoles. Screen is also capable of separating programs from the shell that initially started it which allows a program to continue running even if the connection to the host has been lost. For this reason screen is typically used when a network connection is unstable and the process must remain running even if an SSH connection has dropped. Screen is also useful when a process may be slow and other processes need to be running.

	=== Usage ===		=== Usage ===

Claw: /* .screenrc */

2015-01-06T23:23:48Z

.screenrc

← Older revision		Revision as of 23:23, 6 January 2015
Line 55:		Line 55:

	=== .screenrc ===		=== .screenrc ===
	Similar to .bashrc, the file .screenrc in a user's home directory can be used to customize a screen session's startup behavior. Commands listed in this file will be executed upon starting screen, and can be useful to set up your environment to display important information such as the window number and name, the ~~hostname~~ you're connected to, or altering the key sequences for screen commands. See the link [http://www.gnu.org/software/screen/manual/screen.txt here] for more information about screen commands (Section 5.2: Command Summary).		Similar to .bashrc, the file .screenrc in a user's home directory can be used to customize a screen session's startup behavior. Commands listed in this file will be executed upon starting screen, and can be useful to set up your environment to display important information such as the window number and name, the name of the host you're connected to, or altering the key sequences for screen commands. See the link [http://www.gnu.org/software/screen/manual/screen.txt here] for more information about screen commands (Section 5.2: Command Summary).

	=== Useful Links ===		=== Useful Links ===
	* [http://www.gnu.org/software/screen/ The main page at www.gnu.org.]		* [http://www.gnu.org/software/screen/ The main page at www.gnu.org.]
	* [http://www.gnu.org/software/screen/manual/screen.txt GNU Screen documentation] (also accessed through '''man screen''').		* [http://www.gnu.org/software/screen/manual/screen.txt GNU Screen documentation] (also accessed through '''man screen''').

Claw at 23:23, 6 January 2015

2015-01-06T23:23:17Z

← Older revision		Revision as of 23:23, 6 January 2015
Line 55:		Line 55:

	=== .screenrc ===		=== .screenrc ===
	Similar to .bashrc, the file .screenrc in a user's home directory can be used to customize a screen session's startup behavior. Commands listed in this file will be executed upon starting screen, and can be useful to set up your environment the ~~same way~~ for ~~each session~~. See the link [http://www.gnu.org/software/screen/manual/screen.txt here] for more information about screen commands (Section 5.2: Command Summary).		Similar to .bashrc, the file .screenrc in a user's home directory can be used to customize a screen session's startup behavior. Commands listed in this file will be executed upon starting screen, and can be useful to set up your environment to display important information such as the window number and name, the hostname you're connected to, or altering the key sequences for screen commands. See the link [http://www.gnu.org/software/screen/manual/screen.txt here] for more information about screen commands (Section 5.2: Command Summary).

	=== Useful Links ===		=== Useful Links ===
	* [http://www.gnu.org/software/screen/ The main page at www.gnu.org.]		* [http://www.gnu.org/software/screen/ The main page at www.gnu.org.]
	* [http://www.gnu.org/software/screen/manual/screen.txt GNU Screen documentation] (also accessed through '''man screen''').		* [http://www.gnu.org/software/screen/manual/screen.txt GNU Screen documentation] (also accessed through '''man screen''').

Claw at 23:18, 6 January 2015

2015-01-06T23:18:37Z

← Older revision		Revision as of 23:18, 6 January 2015
Line 50:		Line 50:

	=== Important Notes ===		=== Important Notes ===
	If you start a program within a ~~screen~~ session that has only one window then when the program exits the screen session will terminate as well. This has the potential to hide any output you may want from your program since the screen session will exit. To solve this issue you can either make sure your shell is not set to auto-logout, or ensure that you have multiple windows open in the screen session so that it will not terminate when the program exits.		If you start a screen session that will run a program within a session that has only one window, such as by issuing the command
			# screen program.c
			then when the program exits the screen session will terminate as well. This has the potential to hide any output you may want from your program since the screen session will exit. To solve this issue you can either make sure your shell is not set to auto-logout, or ensure that you have multiple windows open in the screen session so that it will not terminate when the program exits.

	=== .screenrc ===		=== .screenrc ===
	Similar to .bashrc, the file .screenrc in a user's home directory can be used to customize ~~each~~ screen session's startup behavior. Commands listed in this file will be executed upon starting screen. See the link [http://www.gnu.org/software/screen/manual/screen.txt here] for more information about screen commands (Section 5.2: Command Summary).		Similar to .bashrc, the file .screenrc in a user's home directory can be used to customize a screen session's startup behavior. Commands listed in this file will be executed upon starting screen, and can be useful to set up your environment the same way for each session. See the link [http://www.gnu.org/software/screen/manual/screen.txt here] for more information about screen commands (Section 5.2: Command Summary).

	=== Useful Links ===		=== Useful Links ===
	* [http://www.gnu.org/software/screen/ The main page at www.gnu.org.]		* [http://www.gnu.org/software/screen/ The main page at www.gnu.org.]
	* [http://www.gnu.org/software/screen/manual/screen.txt GNU Screen documentation] (also accessed through '''man screen''').		* [http://www.gnu.org/software/screen/manual/screen.txt GNU Screen documentation] (also accessed through '''man screen''').

Claw at 23:16, 6 January 2015

2015-01-06T23:16:01Z

← Older revision		Revision as of 23:16, 6 January 2015
Line 48:		Line 48:

	See the documentation [http://www.gnu.org/software/screen/manual/screen.txt here] to see a full list of Ctrl-A commands (Section 5.1: Default Key Bindings).		See the documentation [http://www.gnu.org/software/screen/manual/screen.txt here] to see a full list of Ctrl-A commands (Section 5.1: Default Key Bindings).

			=== Important Notes ===
			If you start a program within a screen session that has only one window then when the program exits the screen session will terminate as well. This has the potential to hide any output you may want from your program since the screen session will exit. To solve this issue you can either make sure your shell is not set to auto-logout, or ensure that you have multiple windows open in the screen session so that it will not terminate when the program exits.

	=== .screenrc ===		=== .screenrc ===

Claw at 21:13, 5 January 2015

2015-01-05T21:13:04Z

← Older revision		Revision as of 21:13, 5 January 2015
Line 47:		Line 47:
	* Ctrl-A + \ (Kill the screen session and all its windows.)		* Ctrl-A + \ (Kill the screen session and all its windows.)

	See the documentation ~~linked in this page~~ to see a full list of Ctrl-A commands (5.1 Default Key Bindings).		See the documentation [http://www.gnu.org/software/screen/manual/screen.txt here] to see a full list of Ctrl-A commands (Section 5.1: Default Key Bindings).

	=== .screenrc ===		=== .screenrc ===
	Similar to .bashrc, the file .screenrc in a user's home directory can be used to customize each screen session's startup behavior. Commands listed in this file will be executed upon starting screen. See the link ~~to documentation on~~ screen ~~at the bottom of this page~~ for more information about screen commands (5.2 Command Summary).		Similar to .bashrc, the file .screenrc in a user's home directory can be used to customize each screen session's startup behavior. Commands listed in this file will be executed upon starting screen. See the link [http://www.gnu.org/software/screen/manual/screen.txt here] for more information about screen commands (Section 5.2: Command Summary).

	=== Useful Links ===		=== Useful Links ===
	* [http://www.gnu.org/software/screen/ The main page at www.gnu.org.]		* [http://www.gnu.org/software/screen/ The main page at www.gnu.org.]
	* [http://www.gnu.org/software/screen/manual/screen.txt GNU Screen documentation] (also accessed through '''man screen''').		* [http://www.gnu.org/software/screen/manual/screen.txt GNU Screen documentation] (also accessed through '''man screen''').

Claw at 21:06, 5 January 2015

2015-01-05T21:06:52Z

← Older revision		Revision as of 21:06, 5 January 2015
Line 1:		Line 1:
	=== Introduction ===		=== Introduction ===
	GNU Screen, or "screen", is a window management program available on UMIACS ~~UNIX~~ hosts that ~~splits~~ a terminal ~~into~~ multiple ~~windows~~ that ~~can each be used for~~ a ~~separate process~~. ~~This can be very useful~~ when a ~~process will be running for a long time. The process~~ is ~~allocated to a virtual terminal created by screen,~~ and ~~it will run in~~ the ~~background while other terminals are being used or~~ if ~~the~~ SSH ~~session ends~~.		GNU Screen, or "screen", is a window management program available on UMIACS Linux hosts that allows multiplexing of a single terminal between multiple virtual consoles. Screen is also capable of separating programs from the shell that initially started it which allows a program to continue running even if the connection to the host has been lost. For this reason screen is typically used when a network connection is unstable and the process must remain running even if an SSH connection has dropped.

	=== Usage ===		=== Usage ===
	To invoke screen, simply use the following command:		To invoke screen, simply use the following command in a terminal:
	~~'''~~screen~~'''~~		# screen

	Alternatively, to start a program with screen:		Alternatively, to start a program with screen:
	~~'''~~screen vi program.c~~'''~~		# screen vi program.c
			This will invoke screen and, in the newly-created window, start editing the file program.c in vi.

			You can have as many screen sessions as you’d like on a single host, however, keeping track of many sessions can become difficult. As a way to solve this screen offers the capability to give each session a unique name when you start it using the following:
			# screen -S [session name]

			If you need to end your ssh session, but want your processes to keep running you can detach the screen session with:
			# screen -d
			Then exit as normal.

			If you have multiple screen sessions you can detach and reattach them at any time. To list the current screen sessions running on a host use:
			# screen -ls

			The output will be similar to this:
			# claw@idaho:~$ screen -ls
			# There are screens on:
			# 26598.screenTest1 (Detached)
			# 18457.pts-0.idaho (Detached)
			# 2 Sockets in /var/run/screen/S-claw.

			To reconnect to a specific screen session you may use either the screen number or name to reconnect using ‘screen -r’
			# claw@idaho:~$ screen -r 26598

			or

			# claw@idaho:~$ screen -r screenTest1

	~~This will invoke screen and, in the newly-created window, start editing the file program.c in vi.~~

			===Common Keyboard Shortcuts===
	Ctrl-A is the metacharacter for commands in screen; press it before every key command. Some useful commands in screen:		Ctrl-A is the metacharacter for commands in screen; press it before every key command. Some useful commands in screen:

	* Ctrl-A + C (Creates a new window.)		* Ctrl-A + c (Creates a new window.)
	* Ctrl-A + d (detach from current session)		* Ctrl-A + d (detach from current session)
	* Ctrl-A + [0-9] (Switches to the window corresonding to the number, window 0 is the first window initialized by screen.)		* Ctrl-A + [0-9] (Switches to the window corresonding to the number, window 0 is the first window initialized by screen.)
	* Ctrl-A + " (Presents a selection of screen windows from which to choose.)		* Ctrl-A + " (Presents a selection of screen windows from which to choose.)
			* Ctrl-A + Shift-A Rename the current screen window
	* Ctrl-A + <SPC> / Ctrl-A + <BKSPC> (Switch to the next / previous window.)		* Ctrl-A + <SPC> / Ctrl-A + <BKSPC> (Switch to the next / previous window.)
	* Ctrl-A + k (Kill the current window.)		* Ctrl-A + k (Kill the current window.)
	* Ctrl-A + ~~Ctrl-~~\ (Kill screen and all its windows.)		* Ctrl-A + \ (Kill the screen session and all its windows.)

	See the documentation linked in this page to see a full list of Ctrl-A commands (5.1 Default Key Bindings).		See the documentation linked in this page to see a full list of Ctrl-A commands (5.1 Default Key Bindings).

	~~To start a long-running process:~~
	~~'''screen'''~~
	~~then run your process.~~

	~~If you want multiple sessions, name each session:~~
	~~'''screen -S [session name]'''~~

	~~If you need to end your ssh session, but want the process to keep running detach it:~~
	~~'''screen -d'''~~

	~~When you ssh back in, reattach your session:~~
	~~'''screen -r'''~~

	~~If you have named your session:~~
	~~'''screen -r [session name]'''~~

	=== .screenrc ===		=== .screenrc ===

Tmoore: /* Usage */

2014-10-28T21:35:44Z

Usage

← Older revision		Revision as of 21:35, 28 October 2014
Line 34:		Line 34:

	When you ssh back in, reattach your session:		When you ssh back in, reattach your session:
	'''screen -R'''		'''screen -r'''

	If you have named your session:		If you have named your session: