Screen terminal multiplexer - Revision history

Armarmgc: /* Where to find more examples */ fixed list formatting

2024-11-09T05:18:51Z

Where to find more examples: fixed list formatting

← Older revision		Revision as of 05:18, 9 November 2024
Line 143:		Line 143:

	== Where to find more examples ==		== Where to find more examples ==
	- Archlinux forums (https://bbs.archlinux.org/viewtopic.php?id=55618)		* Archlinux forums (https://bbs.archlinux.org/viewtopic.php?id=55618)
	- GithubGist (https://gist.github.com/search?utf8=%E2%9C%93&q=screenrc)		* GithubGist (https://gist.github.com/search?utf8=%E2%9C%93&q=screenrc)
	- Github (https://github.com/search?utf8=%E2%9C%93&q=screenrc)		* Github (https://github.com/search?utf8=%E2%9C%93&q=screenrc)

	[[Category:Shell]]		[[Category:Shell]]

Zcrayfish: Fixed double redirect.

2023-08-28T04:17:11Z

Fixed double redirect.

← Older revision		Revision as of 04:17, 28 August 2023
Line 77:		Line 77:

	= Other terminal multiplexers =		= Other terminal multiplexers =
	A similar tool is {{pkg\|tmux}} which is documented [[~~Tmux_terminal_multiplexer~~\|here]].		A similar tool is {{pkg\|tmux}} which is documented [[tmux\|here]].

Jodumont: .screenrc example + links

2018-01-24T10:35:21Z

.screenrc example + links

@@ Line 78: / Line 78: @@
 = Other terminal multiplexers =
 A similar tool is {{pkg|tmux}} which is documented [[Tmux_terminal_multiplexer|here]].
 [[Category:Shell]]

Jodumont: remove bash because it might be with ash ;)

2018-01-24T10:27:13Z

remove bash because it might be with ash ;)

← Older revision		Revision as of 10:27, 24 January 2018
Line 66:		Line 66:
	STARTED_SCREEN=1 ; export STARTED_SCREEN		STARTED_SCREEN=1 ; export STARTED_SCREEN
	screen -RR && exit 0		screen -RR && exit 0
	echo "Screen failed! continuing with normal ~~bash~~ startup"		echo "Screen failed! continuing with normal startup"
	fi		fi
	</pre>		</pre>

Mhavela: /* Close or kill a session */ Fixed typo

2012-10-24T15:07:41Z

Close or kill a session: Fixed typo

← Older revision		Revision as of 15:07, 24 October 2012
Line 50:		Line 50:
	Confirm by clicking {{key\|y}} when prompted.		Confirm by clicking {{key\|y}} when prompted.

	You can also 'kill' ~~you~~ session by entering:		You can also 'kill' your session by entering:
	{{cmd\|exit}}		{{cmd\|exit}}

Mhavela: Mhavela moved page Screen on console to Screen terminal multiplexer: The previous name could be misunderstood. This new name specifies that this is a terminal multiplexer.

2012-10-24T14:23:26Z

Mhavela moved page Screen on console to Screen terminal multiplexer: The previous name could be misunderstood. This new name specifies that this is a terminal multiplexer.

← Older revision	Revision as of 14:23, 24 October 2012
(No difference)

Mhavela: Fixed some typos and added link to tmux documentation

2012-10-24T14:11:00Z

Fixed some typos and added link to tmux documentation

← Older revision		Revision as of 14:11, 24 October 2012
Line 1:		Line 1:
	{{pkg\|screen}} is a good tool for remote support. It can also be used to start a command you want to keep running after you close your console session (you can later on attach to your running ~~{{pkg\|screen}}~~ session). When you enter a {{pkg\|screen}} session you will not notice too much.<BR>		{{pkg\|screen}} is a terminal multiplexer. It's a good tool for e.g. remote support. It can also be used to start a command you want to keep running after you close your console session (you can later on attach to your running session). When you enter a {{pkg\|screen}} session you will not notice too much.<BR>
	To know if you are inside a {{pkg\|screen}} session, use the notes in '[[#Get_help\|get help]]' section mentioned below.		To know if you are inside a {{pkg\|screen}} session, use the notes in '[[#Get_help\|get help]]' section mentioned below.

Line 28:		Line 28:
	or		or
	{{cmd\|screen -x pts-3}}		{{cmd\|screen -x pts-3}}
	{{tip\|If you see <code>Attaching from inside of screen?</code>, you are ~~allready~~ inside a screen session.}}		{{tip\|If you see <code>Attaching from inside of screen?</code>, you are already inside a screen session.}}

	== Controlling a screen session ==		== Controlling a screen session ==
	While inside a {{pkg\|screen}} session, you can ~~controll~~ it using keyboard shortcuts. We will only describe some of those alternatives.		While inside a {{pkg\|screen}} session, you can control it using keyboard shortcuts. We will only describe some of those alternatives.

	{{tip\|To enter a keyboard shortcut that controls the current {{pkg\|screen}} session, you should click {{key\|A}} while holding down {{key\|CTRL}}<br>In the below examples this procedure is described as <code>^A</code>}}		{{tip\|To enter a keyboard shortcut that controls the current {{pkg\|screen}} session, you should click {{key\|A}} while holding down {{key\|CTRL}}<br>In the below examples this procedure is described as <code>^A</code>}}
Line 43:		Line 43:
	Sometimes it's useful to just detach from a session without killing it.<br>		Sometimes it's useful to just detach from a session without killing it.<br>
	{{cmd\|^A d}}		{{cmd\|^A d}}
	{{tip\|Try starting <code>ping 127.0.0.1</code> while inside a screen session and then ~~detatch~~ from the session.<br>After some while re-connect to the session using <code>screen -x</code>.<br>Note that the "seq" value ~~indikates~~ that ping had continued running while you where ~~detatched~~ from the session.}}		{{tip\|Try starting <code>ping 127.0.0.1</code> while inside a screen session and then detach from the session.<br>After some while re-connect to the session using <code>screen -x</code>.<br>Note that the "seq" value indicates that ping had continued running while you where detached from the session.}}

	=== Close or kill a session ===		=== Close or kill a session ===
Line 75:		Line 75:
	Remove this part from above configuration to force SSH sessions into a screen session.<BR>		Remove this part from above configuration to force SSH sessions into a screen session.<BR>
	{{Note\|Console users will also be forced into a screen session when folowing these instructions}}		{{Note\|Console users will also be forced into a screen session when folowing these instructions}}

			= Other terminal multiplexers =
			A similar tool is {{pkg\|tmux}} which is documented [[Tmux_terminal_multiplexer\|here]].

	[[Category:Shell]]		[[Category:Shell]]

Mhavela: /* Extra */ Serial port using screen

2012-10-24T13:03:15Z

Extra: Serial port using screen

← Older revision		Revision as of 13:03, 24 October 2012
Line 54:		Line 54:

	= Extra =		= Extra =
			== Connect to serial console ==
			{{pkg\|screen}} is a good tool when you need to connect to a serial console ''(e.g. if you want to configure a switch using it's serial port)''. Connecting to a serial console could look like this:
			{{cmd\|screen /dev/ttyS0 9600}}

	== Force console users into a screen session ==		== Force console users into a screen session ==
	In some cases you might want to force only console users into a screen session.<BR>		In some cases you might want to force only console users into a screen session.<BR>

Mhavela: /* General */

2012-10-24T10:06:24Z

General

← Older revision		Revision as of 10:06, 24 October 2012
Line 2:		Line 2:
	To know if you are inside a {{pkg\|screen}} session, use the notes in '[[#Get_help\|get help]]' section mentioned below.		To know if you are inside a {{pkg\|screen}} session, use the notes in '[[#Get_help\|get help]]' section mentioned below.

	~~= General =~~		= Install =
	== Install ==
	In order to use {{pkg\|screen}} you will have to install it:		In order to use {{pkg\|screen}} you will have to install it:
	{{cmd\|apk add screen}}		{{cmd\|apk add screen}}

Mhavela: Restructuring a bit. Adding some notes and examples that indicates how screen can be used

2012-10-24T10:05:49Z

Restructuring a bit. Adding some notes and examples that indicates how screen can be used

← Older revision		Revision as of 10:05, 24 October 2012
Line 1:		Line 1:
	'screen' is a good tool for remote support. It can also be used to start a command you want to keep running after you close your console session (you can later on attach to your running 'screen' session). When you enter a 'screen' session you will not notice too much.<BR>		{{pkg\|screen}} is a good tool for remote support. It can also be used to start a command you want to keep running after you close your console session (you can later on attach to your running {{pkg\|screen}} session). When you enter a {{pkg\|screen}} session you will not notice too much.<BR>
	To know if you are inside a 'screen' session, use the notes in '[[#Get_help\|get help]]' section mentioned below.		To know if you are inside a {{pkg\|screen}} session, use the notes in '[[#Get_help\|get help]]' section mentioned below.

	= Install =		= General =
			== Install ==
			In order to use {{pkg\|screen}} you will have to install it:
	{{cmd\|apk add screen}}		{{cmd\|apk add screen}}

	= ~~Use screen~~ =		= Usage =

	== Start a new session ==		== Start a new session ==
			To enter a {{pkg\|screen}} session you just enter:
	{{cmd\|screen}}		{{cmd\|screen}}

	== List existing sessions ==		== List existing sessions ==
			When you have started some session(s) you can list them:
	{{cmd\|screen -list}}		{{cmd\|screen -list}}
	You might get a list that looks like this:		You might get a list that looks like this:
Line 20:		Line 25:

	== Attach to a existing session ==		== Attach to a existing session ==
	Lets say you want to attach to a existing session (e.g. the above "11131.pts-3.mhlab01" session).		Lets say you want to attach to a existing session (e.g. the above <code>11131.pts-3.mhlab01</code> session).
	{{cmd\|screen -x 11131}}		{{cmd\|screen -x 11131}}
	or		or
	{{cmd\|screen -x pts-3}}		{{cmd\|screen -x pts-3}}
			{{tip\|If you see <code>Attaching from inside of screen?</code>, you are allready inside a screen session.}}

			== Controlling a screen session ==
			While inside a {{pkg\|screen}} session, you can controll it using keyboard shortcuts. We will only describe some of those alternatives.

			{{tip\|To enter a keyboard shortcut that controls the current {{pkg\|screen}} session, you should click {{key\|A}} while holding down {{key\|CTRL}}<br>In the below examples this procedure is described as <code>^A</code>}}
			=== Get help ===
			One of the most useful commands is the one that gives you 'help'.<br>
			While in your {{pkg\|screen}} session, click:
			{{cmd\|^A ?}}
			''(Do not press/hold {{key\|CTRL}} when clicking {{key\|?}})''

			=== Detach from a session ===
			Sometimes it's useful to just detach from a session without killing it.<br>
			{{cmd\|^A d}}
			{{tip\|Try starting <code>ping 127.0.0.1</code> while inside a screen session and then detatch from the session.<br>After some while re-connect to the session using <code>screen -x</code>.<br>Note that the "seq" value indikates that ping had continued running while you where detatched from the session.}}

	== Close or kill a session ==		=== Close or kill a session ===
	~~When you are inside a~~ '~~screen~~' session ~~you can 'kill' it by using~~:		To 'kill' a session:
	{{cmd\|~~CTRL+~~A k}}		{{cmd\|^A k}}
	or you ~~might just type~~:		Confirm by clicking {{key\|y}} when prompted.

			You can also 'kill' you session by entering:
	{{cmd\|exit}}		{{cmd\|exit}}

	~~== Get help ==~~
	~~'screen' has various options/commands.<BR>~~
	~~When your inside a 'screen' session you can get help and see what options you have by using:~~
	~~{{cmd\|CTRL+a ?}}~~
	~~''(Do not press/hold 'CTRL' when entering ''''?'''')''~~

	= Extra =		= Extra =
Line 41:		Line 58:
	In some cases you might want to force only console users into a screen session.<BR>		In some cases you might want to force only console users into a screen session.<BR>
	Note that the this configuration will not force SSH-users into a screen.<BR>		Note that the this configuration will not force SSH-users into a screen.<BR>
	Edit `/etc/profile` and add the following code to it:		Edit {{path\|/etc/profile}} and add the following code to it:
	<pre>		<pre>
	if [ -n "$PS1" ] && [ -z "$STARTED_SCREEN" ] && [ -z "$SSH_TTY" ]; then		if [ -n "$PS1" ] && [ -z "$STARTED_SCREEN" ] && [ -z "$SSH_TTY" ]; then