🕷️ Crawler Inspector

# Screen From UMIACS [Jump to navigation](https://wiki.umiacs.umd.edu/umiacs/index.php/Screen#mw-head) [Jump to search](https://wiki.umiacs.umd.edu/umiacs/index.php/Screen#searchInput) ## Contents - [1 Introduction](https://wiki.umiacs.umd.edu/umiacs/index.php/Screen#Introduction) - [2 Usage](https://wiki.umiacs.umd.edu/umiacs/index.php/Screen#Usage) - [3 Common Keyboard Shortcuts](https://wiki.umiacs.umd.edu/umiacs/index.php/Screen#Common_Keyboard_Shortcuts) - [4 Important Notes](https://wiki.umiacs.umd.edu/umiacs/index.php/Screen#Important_Notes) - [5 .screenrc](https://wiki.umiacs.umd.edu/umiacs/index.php/Screen#.screenrc) - [6 Useful Links](https://wiki.umiacs.umd.edu/umiacs/index.php/Screen#Useful_Links) ### 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. Screen is also useful when a process may be slow and other processes need to be running. ### Usage To invoke screen, simply use the following command in a terminal: ``` # screen ``` Alternatively, to start a program with screen: ``` # 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: ``` # username@tron02:~$ screen -ls # There are screens on: # 26598.screenTest1 (Detached) # 18457.pts-0.tron02 (Detached) # 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’ ``` # username@tron02:~$ screen -r 26598 ``` or ``` # username@tron02:~$ screen -r screenTest1 ``` ### 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 + c (Creates a new window.) - Ctrl-A + d (detach from current session) - 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 + Shift-A Rename the current screen window - Ctrl-A + \<SPC\> / Ctrl-A + \<BKSPC\> (Switch to the next / previous window.) - Ctrl-A + k (Kill the current window.) - Ctrl-A + \\ (Kill the screen session and all its windows.) See the documentation [here](http://www.gnu.org/software/screen/manual/screen.txt) to see a full list of Ctrl-A commands (Section 5.1: Default Key Bindings). ### Important Notes 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 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 [here](http://www.gnu.org/software/screen/manual/screen.txt) for more information about screen commands (Section 5.2: Command Summary). ### Useful Links - [The main page at www.gnu.org.](http://www.gnu.org/software/screen/) - [GNU Screen documentation](http://www.gnu.org/software/screen/manual/screen.txt) (also accessed through **man screen**). Retrieved from "<https://wiki.umiacs.umd.edu/umiacs/index.php?title=Screen&oldid=10377>" ## Navigation menu ### Personal tools - [Log in](https://wiki.umiacs.umd.edu/umiacs/index.php?title=Special:UserLogin&returnto=Screen "You are encouraged to log in; however, it is not mandatory [o]") ### Namespaces - [Page](https://wiki.umiacs.umd.edu/umiacs/index.php/Screen "View the content page [c]") - [Discussion](https://wiki.umiacs.umd.edu/umiacs/index.php?title=Talk:Screen&action=edit&redlink=1 "Discussion about the content page (page does not exist) [t]") English ### Views - [Read](https://wiki.umiacs.umd.edu/umiacs/index.php/Screen) - [View source](https://wiki.umiacs.umd.edu/umiacs/index.php?title=Screen&action=edit "This page is protected. You can view its source [e]") - [View history](https://wiki.umiacs.umd.edu/umiacs/index.php?title=Screen&action=history "Past revisions of this page [h]") More ### Search ### Navigation - [Main Page](https://wiki.umiacs.umd.edu/umiacs/index.php/Main_Page "Visit the main page [z]") - [Getting Started](https://wiki.umiacs.umd.edu/umiacs/index.php/GettingStarted) - [Core Services](https://wiki.umiacs.umd.edu/umiacs/index.php/CoreServices) - [Lab Facilities](https://wiki.umiacs.umd.edu/umiacs/index.php/LabFacilities) - [Placing Orders](https://wiki.umiacs.umd.edu/umiacs/index.php/Orders) - [Support](https://wiki.umiacs.umd.edu/umiacs/index.php/HelpDesk) ### Tools - [What links here](https://wiki.umiacs.umd.edu/umiacs/index.php/Special:WhatLinksHere/Screen "A list of all wiki pages that link here [j]") - [Related changes](https://wiki.umiacs.umd.edu/umiacs/index.php/Special:RecentChangesLinked/Screen "Recent changes in pages linked from this page [k]") - [Special pages](https://wiki.umiacs.umd.edu/umiacs/index.php/Special:SpecialPages "A list of all special pages [q]") - [Printable version]("Printable version of this page [p]") - [Permanent link](https://wiki.umiacs.umd.edu/umiacs/index.php?title=Screen&oldid=10377 "Permanent link to this revision of this page") - [Page information](https://wiki.umiacs.umd.edu/umiacs/index.php?title=Screen&action=info "More information about this page") - This page was last edited on 22 April 2022, at 15:16. - [About UMIACS](https://wiki.umiacs.umd.edu/umiacs/index.php/UMIACS:About) - [](https://www.mediawiki.org/)

### 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. Screen is also useful when a process may be slow and other processes need to be running. ### Usage To invoke screen, simply use the following command in a terminal: ``` # screen ``` Alternatively, to start a program with screen: ``` # 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: ``` # username@tron02:~$ screen -ls # There are screens on: # 26598.screenTest1 (Detached) # 18457.pts-0.tron02 (Detached) # 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’ ``` # username@tron02:~$ screen -r 26598 ``` or ``` # username@tron02:~$ screen -r screenTest1 ``` ### 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 + c (Creates a new window.) - Ctrl-A + d (detach from current session) - 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 + Shift-A Rename the current screen window - Ctrl-A + \<SPC\> / Ctrl-A + \<BKSPC\> (Switch to the next / previous window.) - Ctrl-A + k (Kill the current window.) - Ctrl-A + \\ (Kill the screen session and all its windows.) See the documentation [here](http://www.gnu.org/software/screen/manual/screen.txt) to see a full list of Ctrl-A commands (Section 5.1: Default Key Bindings). ### Important Notes 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 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 [here](http://www.gnu.org/software/screen/manual/screen.txt) for more information about screen commands (Section 5.2: Command Summary). ### Useful Links - [The main page at www.gnu.org.](http://www.gnu.org/software/screen/) - [GNU Screen documentation](http://www.gnu.org/software/screen/manual/screen.txt) (also accessed through **man screen**).