🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 195 (from laksa178)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa195.int.ahrefs:8124/' \
  -H 'Content-Type: text/plain' \
  -H 'X-ClickHouse-Database: crawler3' \
  -H 'Authorization: Basic YXBpOg==' \
  -d 'SELECT getAhrefsURLFromUnparsed(src_unparsed) AS found_url, ifNull(toUnixTimestamp(download_stamp), 0) AS crawl_time, ifNull(toUnixTimestamp(props_url_first_seen), 0) AS first_indexed_time, download_http_code AS http_code, src_unparsed AS src_unparsed, src_root_hash AS src_root_hash, history_drop_reason AS history_drop_reason, meta_title AS meta_title, meta_descriptions AS meta_descriptions, attrs_boilerpipe_text AS attrs_boilerpipe_text, attrs_markdown AS attrs_markdown, attrs_readable_markdown AS attrs_readable_markdown, meta_canonical AS meta_canonical FROM crawler3.page_info_local FINAL PREWHERE (src_root_hash, src_unparsed) IN ((getAhrefsRootHashFromUnparsed(getAhrefsUnparsedNoserviceFromURL(\'https://cat.pdx.edu/platforms/linux/remote-access/persistent-screen/\')), getAhrefsUnparsedNoserviceFromURL(\'https://cat.pdx.edu/platforms/linux/remote-access/persistent-screen/\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/persistent-screen\/","crawl_time":1774063849,"first_indexed_time":1561735073,"http_code":200,"src_unparsed":"edu,pdx!cat,\/platforms\/linux\/remote-access\/persistent-screen\/ s443","src_root_hash":"536666605424911595","history_drop_reason":null,"meta_title":"Keeping your shell sessions persistent with Screen – Computer Action Team","meta_descriptions":["Persistent Shell Sessions with Screen Screen is a program that facilitates the management of multiple shell sessions. When you run screen from a Linux command line, it will open a screen session on top of your current command line window, with a few important benefits:"],"attrs_boilerpipe_text":"Skip to content\nHome\nUsers\nFor New Users\nComputer Accounts\nFacilities\nLab Reservation Calendars\nGuidelines\nCS Tutors\nPlatforms\nWindows\nLinux\nMac\nMobile\nServices\nPrinting\nNetwork\nSoftware\nStorage\nScanning Solutions\nWeb Services\nEmail Services in MCECS\nAbout\nContact\nHome\nPlatforms\nLinux\nRemote Access to Linux Services\nKeeping your shell sessions persistent with Screen\nKeeping your shell sessions persistent with Screen\nadmin\n2020-12-29T17:14:01-08:00\nScreen\nis a program that facilitates the management of multiple shell sessions. When you run screen from a Linux command line, it will open a screen session\non top of\nyour current command line window, with a few important benefits:\nScreen windows behave similarly to multiple tabs on a web browser, letting you switch to other “sessions” with a few keystrokes.\nScreens give you the ability to “disconnect” your screen session, leaving your running programs intact and allowing you to reconnect at a later time to resume your work. You can imagine this like minimizing a window instead of closing it. This is invaluable if you have a long running process and wish to start it and return to check on its progress from time to time.\nIf your terminal session is closed (via ssh or through a Linux X Windows session), all work that you’re doing stays around. The screen session will become “detached” but is still active. This means that you can pick up right where you left off easily. This adds a layer of security for your important work, and also provides the ability to easily work on the same project from many different machines.\nTo open a screen session, type “screen” from the command line like you would for any other command. Once run, you will be placed inside a new screen session, which looks a lot like a normal terminal window.\nOnce within screen, the main command that you use to manage your shell window(s) is “ctrl-a” combined with any number of other keys. For example, “ctrl-a” followed by “?” will bring up the screen help menu. You will use “ctrl-a” followed by something for virtually everything within your screen session.\nFrom within a screen session, you can also open multiple windows and easily tab switch between them. New windows can be made with “ctrl-a” -> “c”; it’s important to understand that each screen “window” is actually an entirely new shell at the command line. When you create a new window you’ll see that all of your windows are listed at the bottom of the window, and the active window is highlighted in green. It should look something like this:\nIn order to switch through all of your active windows,  you can use “ctrl-a” -> “n” to go to the next window and “ctrl-a” -> “p” to go to the previous window. Each window also has an associated number, as you can see on the bottom of the above screenshot. An alternative to switching windows is to use “ctrl-a” followed by the tab number to jump right to that window.\nYou can also detach from a screen session manually with “ctrl-a” -> “d” and then reattach by typing “screen -r” at the command line when you log back into the system.\nImportantly, reconnecting with screen -r will open the screen session that you’ve most recently closed, meaning that so long as you don’t accidentally spin up multiple screen sessions it will be enough to always get back to the session you want.\nUsing this knowledge you could, for example:\nSSH to an MCECS Linux server.\nStart up a new screen session.\nDo any work you need inside.\nDetach from screen.\nGo home and reattach to the same exact session.\nAll without any fear of losing your work from a system crash or forgetting to save.\nFrom the above sections you should have more than enough working knowledge to be able to start using screen effectively. However, there are some instances in which you might create multiple screen sessions and you will need to know how to manage those effectively.\nA very common mistake people make when first using screen is to accidentally type “screen” instead of “screen -r” when meaning to re-attach. This will create a second screen session and if you detach and attempt to reattach you’ll see the following:\nSolving this problem is very simple, you can type “screen -r ” to enter a screen session with the given number. In the above example, my screen sessions have PIDs of 14573, 14563, and 14556, as you can see. So you could simply type “screen -r 14573” and then from within screen you can use the command “ctrl-a -> \\” to delete your current screen.\n“Ctrl-a -> \\” is a new command that won’t just detach you from the screen and leave it running, it will remove it forever,\nso use it with caution\n. After deleting the screen you accidentally created, you should be able to “screen -r” back into the screen session you wanted.\nAnother way to find the screen session you want is to use “screen -ls” which will list all screen sessions you have running. If you’ve been creating new screens by just typing “screen” than the output of “screen -ls” will look something like this:\nWhile this does show you the date that each screen session was created, it’s kind of difficult to differentiate which screen is which. Thankfully, screen has a solution.\nOn creating a new screen window, instead of using “screen” use “screen -S ” to give your new session a name of your choosing. This aids in identifying which screen is which as you can see below:\nI have two screen sessions that I’ve named “school” and “work.” You can then reattach to a named screen using “screen -r ” to quickly get back to the workstation you want.\nPage load link\nGo to Top","attrs_markdown":"[Skip to content](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/persistent-screen\/#content)\n\n[YouTube](https:\/\/www.youtube.com\/user\/catpsu\/ \"YouTube\")\n\n503-725-5420 \\| FAB 82\\|[support@cat.pdx.edu](mailto:support@cat.pdx.edu)\n\n[![Computer Action Team Logo](https:\/\/cat.pdx.edu\/wp-content\/uploads\/2020\/09\/PSUthecat-logo-mcecs-2.png) ![Computer Action Team Logo](https:\/\/cat.pdx.edu\/wp-content\/uploads\/2017\/08\/psu-logomobile.png)](https:\/\/cat.pdx.edu\/)\n\n- [Home](https:\/\/cat.pdx.edu\/)\n- [Users](https:\/\/cat.pdx.edu\/users\/)\n  - [For New Users](https:\/\/cat.pdx.edu\/users\/getting-help\/)\n  - [Computer Accounts](https:\/\/cat.pdx.edu\/users\/computer-accounts\/)\n  - [Facilities](https:\/\/cat.pdx.edu\/users\/facilities\/)\n  - [Lab Reservation Calendars](https:\/\/cat.pdx.edu\/users\/facilities\/lab-reservation-calendars\/)\n  - [Guidelines](https:\/\/cat.pdx.edu\/users\/guidelines\/)\n  - [CS Tutors](https:\/\/cat.pdx.edu\/users\/cs-tutors\/)\n- [Platforms](https:\/\/cat.pdx.edu\/platforms\/)\n  - [Windows](https:\/\/cat.pdx.edu\/platforms\/windows\/)\n  - [Linux](https:\/\/cat.pdx.edu\/platforms\/linux\/)\n  - [Mac](https:\/\/cat.pdx.edu\/platforms\/mac\/)\n  - [Mobile](https:\/\/cat.pdx.edu\/platforms\/mobile\/)\n- [Services](https:\/\/cat.pdx.edu\/services\/)\n  - [Printing](https:\/\/cat.pdx.edu\/services\/printing\/)\n  - [Network](https:\/\/cat.pdx.edu\/services\/network\/)\n  - [Software](https:\/\/cat.pdx.edu\/services\/software\/)\n  - [Storage](https:\/\/cat.pdx.edu\/services\/storage\/)\n  - [Scanning Solutions](https:\/\/cat.pdx.edu\/services\/scanning\/)\n  - [Web Services](https:\/\/cat.pdx.edu\/services\/web\/)\n  - [Email Services in MCECS](https:\/\/cat.pdx.edu\/services\/mail\/)\n- [About](https:\/\/cat.pdx.edu\/about-the-cat\/)\n- [Contact](https:\/\/cat.pdx.edu\/contact-us\/)\n\n# Keeping your shell sessions persistent with Screen\n1. [Home](https:\/\/cat.pdx.edu\/)\n2. [Platforms](https:\/\/cat.pdx.edu\/platforms\/)\n3. [Linux](https:\/\/cat.pdx.edu\/platforms\/linux\/)\n4. [Remote Access to Linux Services](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/)\n5. Keeping your shell sessions persistent with Screen\n\nKeeping your shell sessions persistent with Screen[admin](https:\/\/cat.pdx.edu\/author\/admin\/ \"Posts by admin\")2020-12-29T17:14:01-08:00\n\n# **Persistent Shell Sessions with Screen**\n**Screen** is a program that facilitates the management of multiple shell sessions. When you run screen from a Linux command line, it will open a screen session *on top of* your current command line window, with a few important benefits:\n\n- Screen windows behave similarly to multiple tabs on a web browser, letting you switch to other “sessions” with a few keystrokes.\n- Screens give you the ability to “disconnect” your screen session, leaving your running programs intact and allowing you to reconnect at a later time to resume your work. You can imagine this like minimizing a window instead of closing it. This is invaluable if you have a long running process and wish to start it and return to check on its progress from time to time.\n- If your terminal session is closed (via ssh or through a Linux X Windows session), all work that you’re doing stays around. The screen session will become “detached” but is still active. This means that you can pick up right where you left off easily. This adds a layer of security for your important work, and also provides the ability to easily work on the same project from many different machines.\n\n![Image Showing a Diagram of Screen When Connecting Remotely](https:\/\/cat.pdx.edu\/wp-content\/uploads\/2018\/07\/screen_dia-300x279.png)\n\n## **How to use Screen**\n### Opening Screen\nTo open a screen session, type “screen” from the command line like you would for any other command. Once run, you will be placed inside a new screen session, which looks a lot like a normal terminal window.\n\nOnce within screen, the main command that you use to manage your shell window(s) is “ctrl-a” combined with any number of other keys. For example, “ctrl-a” followed by “?” will bring up the screen help menu. You will use “ctrl-a” followed by something for virtually everything within your screen session.\n\n### Creating & Switching Screen Windows\nFrom within a screen session, you can also open multiple windows and easily tab switch between them. New windows can be made with “ctrl-a” -\\> “c”; it’s important to understand that each screen “window” is actually an entirely new shell at the command line. When you create a new window you’ll see that all of your windows are listed at the bottom of the window, and the active window is highlighted in green. It should look something like this:\n\n![Image Showing the Linux Prompt on a CAT Server](https:\/\/cat.pdx.edu\/wp-content\/uploads\/2018\/07\/screen_1.png)\n\nIn order to switch through all of your active windows, you can use “ctrl-a” -\\> “n” to go to the next window and “ctrl-a” -\\> “p” to go to the previous window. Each window also has an associated number, as you can see on the bottom of the above screenshot. An alternative to switching windows is to use “ctrl-a” followed by the tab number to jump right to that window.\n\n### Disconnecting & Reconnecting to a Screen Session\nYou can also detach from a screen session manually with “ctrl-a” -\\> “d” and then reattach by typing “screen -r” at the command line when you log back into the system.\n\nImportantly, reconnecting with screen -r will open the screen session that you’ve most recently closed, meaning that so long as you don’t accidentally spin up multiple screen sessions it will be enough to always get back to the session you want.\n\nUsing this knowledge you could, for example:\n\n1. SSH to an MCECS Linux server.\n2. Start up a new screen session.\n3. Do any work you need inside.\n4. Detach from screen.\n5. Go home and reattach to the same exact session.\n\nAll without any fear of losing your work from a system crash or forgetting to save.\n\n## **Managing Multiple Screen Sessions**\nFrom the above sections you should have more than enough working knowledge to be able to start using screen effectively. However, there are some instances in which you might create multiple screen sessions and you will need to know how to manage those effectively.\n\n### Re-attaching to a Screen Session\nA very common mistake people make when first using screen is to accidentally type “screen” instead of “screen -r” when meaning to re-attach. This will create a second screen session and if you detach and attempt to reattach you’ll see the following:\n\n![Image Showing 3 Open Screen Sessions on a CAT Server](https:\/\/cat.pdx.edu\/wp-content\/uploads\/2018\/07\/screen_2.png)\n\nSolving this problem is very simple, you can type “screen -r ” to enter a screen session with the given number. In the above example, my screen sessions have PIDs of 14573, 14563, and 14556, as you can see. So you could simply type “screen -r 14573” and then from within screen you can use the command “ctrl-a -\\> \\\\” to delete your current screen.\n\n“Ctrl-a -\\> \\\\” is a new command that won’t just detach you from the screen and leave it running, it will remove it forever, **so use it with caution**. After deleting the screen you accidentally created, you should be able to “screen -r” back into the screen session you wanted.\n\n### Effectively Using Multiple Screen Sessions\nAnother way to find the screen session you want is to use “screen -ls” which will list all screen sessions you have running. If you’ve been creating new screens by just typing “screen” than the output of “screen -ls” will look something like this:\n\n![Image showing 3 Open Screen Sessions Running on a CAT Server](https:\/\/cat.pdx.edu\/wp-content\/uploads\/2018\/07\/screen_3.png)\n\nWhile this does show you the date that each screen session was created, it’s kind of difficult to differentiate which screen is which. Thankfully, screen has a solution.\n\nOn creating a new screen window, instead of using “screen” use “screen -S ” to give your new session a name of your choosing. This aids in identifying which screen is which as you can see below:\n\n![Image showing 2 Named Open Screen Sessions Running on a CAT Server](https:\/\/cat.pdx.edu\/wp-content\/uploads\/2018\/07\/screen_4.png)\n\nI have two screen sessions that I’ve named “school” and “work.” You can then reattach to a named screen using “screen -r ” to quickly get back to the workstation you want.\n\n- [Linux](https:\/\/cat.pdx.edu\/platforms\/linux\/)\n  - [Administrivia \\>](https:\/\/cat.pdx.edu\/platforms\/linux\/administrivia\/)\n  - [Linux User Environment \\>](https:\/\/cat.pdx.edu\/platforms\/linux\/user-environment\/)\n  - [Remote Access](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/)\n    - [Connecting to PSU SECURE (Wi-FI)](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/psu-secure-gnome\/)\n    - [Using OpenVPN on Linux](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/openvpn\/)\n    - [Using SSH for Remote Connections in MCECS](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/using-ssh-for-remote-connections-in-mcecs\/)\n    - [Using SSH from Linux](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/using-ssh-from-linux\/)\n    - [SSH Port Forwarding](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/ssh-portforward\/)\n    - [Dealing with SSH Host Key Changes](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/dealing-with-ssh-host-key-changes\/)\n    - [Using SFTP for Remote File Transfer from the Command Line](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/using-sftp-for-remote-file-transfer-from-command-line\/)\n    - [Copying Your CAT Linux Files Remotely](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/copying-your-cat-linux-files-remotely\/)\n    - [Keeping your shell sessions persistent with Screen](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/persistent-screen\/)\n    - [Mosh (Mobile Shell) for Intermittent Connectivity](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/mosh\/)\n    - [Connecting to your Stash from Linux](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/connect-stash\/)\n    - [VNC in MCECS](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/vnc-in-mcecs\/)\n    - [VNC from Linux to Linux](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/vnc\/)\n    - [Running X11 Applications Remotely](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/remote-x\/)\n    - [Using RDP to Connect to a Windows Computer from Linux](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/using-rdp-to-connect-to-a-windows-computer-from-linux\/)\n    - [Using RDP to connect to Linux systems](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/rdp-to-linux-xrdp\/)\n    - [File Sharing through RDP from Linux](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/file-sharing-rdp-from-linux\/)\n    - [Printing Over SSH Using LPR](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/ssh-printing\/)\n  - [Linux Reference \\>](https:\/\/cat.pdx.edu\/platforms\/linux\/reference\/)\n  - [Linux How To’s and FAQs \\>](https:\/\/cat.pdx.edu\/platforms\/linux\/how-to\/)\n\n#### CONTACT THE CAT\nFront Desk: FAB LL Suite 82  \n Open: 8am-6pm M-F, noon-5pm Sat  \n (based on availability)\n\nEmail: [support@cat.pdx.edu](mailto:support@cat.pdx.edu)  \n Phone: 503.725.5420 (voicemail monitored)\n\nWeb chat: <https:\/\/support.cat.pdx.edu\/>\n\n#### Account Help\n- [Forgot Password?](https:\/\/cram.cecs.pdx.edu\/)\n- [Activate MCECS Account](https:\/\/cram.cecs.pdx.edu\/)\n- [Change Password](https:\/\/intranet.cecs.pdx.edu\/password\/)\n\n#### Website Help\n- [Sitemap](https:\/\/cat.pdx.edu\/sitemap\/)\n\n#### Computer Labs\n- [Locations](https:\/\/cat.pdx.edu\/users\/facilities\/computer-labs\/)\n- [Lab Reservation Calendars](https:\/\/cat.pdx.edu\/users\/facilities\/lab-reservation-calendars\/)\n- [FAB\/EB Card Access](https:\/\/cat.pdx.edu\/users\/facilities\/fab-eb-card-access\/)\n- [Lab Status](https:\/\/cat.pdx.edu\/labstatus\/)\n- [Lab Use Policy](https:\/\/cat.pdx.edu\/users\/guidelines\/lab-rules\/)\n- [CAT Lost & Found](https:\/\/cat.pdx.edu\/users\/guidelines\/lost-and-found\/)\n\n#### Join The CAT\n- [Who are we?](http:\/\/braindump.cat.pdx.edu\/#whatiscat)\n- [How to join?](http:\/\/braindump.cat.pdx.edu\/)\n- [Learn about The Braindump](http:\/\/braindump.cat.pdx.edu\/#whatisbraindump)\n\nCopyright 1993-2026 \\| Computer Action Team \\| Portland State University\n\n[YouTube](https:\/\/www.youtube.com\/user\/catpsu\/ \"YouTube\")\n\n[Page load link](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/persistent-screen\/)\n\n[Go to Top](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/persistent-screen\/)","attrs_readable_markdown":"[Skip to content](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/persistent-screen\/#content)\n\n- [Home](https:\/\/cat.pdx.edu\/)\n- [Users](https:\/\/cat.pdx.edu\/users\/)\n  - [For New Users](https:\/\/cat.pdx.edu\/users\/getting-help\/)\n  - [Computer Accounts](https:\/\/cat.pdx.edu\/users\/computer-accounts\/)\n  - [Facilities](https:\/\/cat.pdx.edu\/users\/facilities\/)\n  - [Lab Reservation Calendars](https:\/\/cat.pdx.edu\/users\/facilities\/lab-reservation-calendars\/)\n  - [Guidelines](https:\/\/cat.pdx.edu\/users\/guidelines\/)\n  - [CS Tutors](https:\/\/cat.pdx.edu\/users\/cs-tutors\/)\n- [Platforms](https:\/\/cat.pdx.edu\/platforms\/)\n  - [Windows](https:\/\/cat.pdx.edu\/platforms\/windows\/)\n  - [Linux](https:\/\/cat.pdx.edu\/platforms\/linux\/)\n  - [Mac](https:\/\/cat.pdx.edu\/platforms\/mac\/)\n  - [Mobile](https:\/\/cat.pdx.edu\/platforms\/mobile\/)\n- [Services](https:\/\/cat.pdx.edu\/services\/)\n  - [Printing](https:\/\/cat.pdx.edu\/services\/printing\/)\n  - [Network](https:\/\/cat.pdx.edu\/services\/network\/)\n  - [Software](https:\/\/cat.pdx.edu\/services\/software\/)\n  - [Storage](https:\/\/cat.pdx.edu\/services\/storage\/)\n  - [Scanning Solutions](https:\/\/cat.pdx.edu\/services\/scanning\/)\n  - [Web Services](https:\/\/cat.pdx.edu\/services\/web\/)\n  - [Email Services in MCECS](https:\/\/cat.pdx.edu\/services\/mail\/)\n- [About](https:\/\/cat.pdx.edu\/about-the-cat\/)\n- [Contact](https:\/\/cat.pdx.edu\/contact-us\/)\n\n1. [Home](https:\/\/cat.pdx.edu\/)\n2. [Platforms](https:\/\/cat.pdx.edu\/platforms\/)\n3. [Linux](https:\/\/cat.pdx.edu\/platforms\/linux\/)\n4. [Remote Access to Linux Services](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/)\n5. Keeping your shell sessions persistent with Screen\n\nKeeping your shell sessions persistent with Screen[admin](https:\/\/cat.pdx.edu\/author\/admin\/ \"Posts by admin\")2020-12-29T17:14:01-08:00\n\n**Screen** is a program that facilitates the management of multiple shell sessions. When you run screen from a Linux command line, it will open a screen session *on top of* your current command line window, with a few important benefits:\n\n- Screen windows behave similarly to multiple tabs on a web browser, letting you switch to other “sessions” with a few keystrokes.\n- Screens give you the ability to “disconnect” your screen session, leaving your running programs intact and allowing you to reconnect at a later time to resume your work. You can imagine this like minimizing a window instead of closing it. This is invaluable if you have a long running process and wish to start it and return to check on its progress from time to time.\n- If your terminal session is closed (via ssh or through a Linux X Windows session), all work that you’re doing stays around. The screen session will become “detached” but is still active. This means that you can pick up right where you left off easily. This adds a layer of security for your important work, and also provides the ability to easily work on the same project from many different machines.\n\n![Image Showing a Diagram of Screen When Connecting Remotely](https:\/\/cat.pdx.edu\/wp-content\/uploads\/2018\/07\/screen_dia-300x279.png)\n\nTo open a screen session, type “screen” from the command line like you would for any other command. Once run, you will be placed inside a new screen session, which looks a lot like a normal terminal window.\n\nOnce within screen, the main command that you use to manage your shell window(s) is “ctrl-a” combined with any number of other keys. For example, “ctrl-a” followed by “?” will bring up the screen help menu. You will use “ctrl-a” followed by something for virtually everything within your screen session.\n\nFrom within a screen session, you can also open multiple windows and easily tab switch between them. New windows can be made with “ctrl-a” -\\> “c”; it’s important to understand that each screen “window” is actually an entirely new shell at the command line. When you create a new window you’ll see that all of your windows are listed at the bottom of the window, and the active window is highlighted in green. It should look something like this:\n\n![Image Showing the Linux Prompt on a CAT Server](https:\/\/cat.pdx.edu\/wp-content\/uploads\/2018\/07\/screen_1.png)\n\nIn order to switch through all of your active windows, you can use “ctrl-a” -\\> “n” to go to the next window and “ctrl-a” -\\> “p” to go to the previous window. Each window also has an associated number, as you can see on the bottom of the above screenshot. An alternative to switching windows is to use “ctrl-a” followed by the tab number to jump right to that window.\n\nYou can also detach from a screen session manually with “ctrl-a” -\\> “d” and then reattach by typing “screen -r” at the command line when you log back into the system.\n\nImportantly, reconnecting with screen -r will open the screen session that you’ve most recently closed, meaning that so long as you don’t accidentally spin up multiple screen sessions it will be enough to always get back to the session you want.\n\nUsing this knowledge you could, for example:\n\n1. SSH to an MCECS Linux server.\n2. Start up a new screen session.\n3. Do any work you need inside.\n4. Detach from screen.\n5. Go home and reattach to the same exact session.\n\nAll without any fear of losing your work from a system crash or forgetting to save.\n\nFrom the above sections you should have more than enough working knowledge to be able to start using screen effectively. However, there are some instances in which you might create multiple screen sessions and you will need to know how to manage those effectively.\n\nA very common mistake people make when first using screen is to accidentally type “screen” instead of “screen -r” when meaning to re-attach. This will create a second screen session and if you detach and attempt to reattach you’ll see the following:\n\n![Image Showing 3 Open Screen Sessions on a CAT Server](https:\/\/cat.pdx.edu\/wp-content\/uploads\/2018\/07\/screen_2.png)\n\nSolving this problem is very simple, you can type “screen -r ” to enter a screen session with the given number. In the above example, my screen sessions have PIDs of 14573, 14563, and 14556, as you can see. So you could simply type “screen -r 14573” and then from within screen you can use the command “ctrl-a -\\> \\\\” to delete your current screen.\n\n“Ctrl-a -\\> \\\\” is a new command that won’t just detach you from the screen and leave it running, it will remove it forever, **so use it with caution**. After deleting the screen you accidentally created, you should be able to “screen -r” back into the screen session you wanted.\n\nAnother way to find the screen session you want is to use “screen -ls” which will list all screen sessions you have running. If you’ve been creating new screens by just typing “screen” than the output of “screen -ls” will look something like this:\n\n![Image showing 3 Open Screen Sessions Running on a CAT Server](https:\/\/cat.pdx.edu\/wp-content\/uploads\/2018\/07\/screen_3.png)\n\nWhile this does show you the date that each screen session was created, it’s kind of difficult to differentiate which screen is which. Thankfully, screen has a solution.\n\nOn creating a new screen window, instead of using “screen” use “screen -S ” to give your new session a name of your choosing. This aids in identifying which screen is which as you can see below:\n\n![Image showing 2 Named Open Screen Sessions Running on a CAT Server](https:\/\/cat.pdx.edu\/wp-content\/uploads\/2018\/07\/screen_4.png)\n\nI have two screen sessions that I’ve named “school” and “work.” You can then reattach to a named screen using “screen -r ” to quickly get back to the workstation you want.\n\n[Page load link](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/persistent-screen\/)\n\n[Go to Top](https:\/\/cat.pdx.edu\/platforms\/linux\/remote-access\/persistent-screen\/)","meta_canonical":null}

3. Robots.txt Check

Query:

Response:

4. Spam/Ban Check

Query:

Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

📄

INDEXABLE

✅

CRAWLED

22 days ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	PASS	`download_stamp > now() - 6 MONTH`	0.7 months ago
History drop	PASS	`isNull(history_drop_reason)`	No drop reason
Spam/ban	PASS	`fh_dont_index != 1 AND ml_spam_score = 0`	ml_spam_score=0
Canonical	PASS	`meta_canonical IS NULL OR = '' OR = src_unparsed`	Not set

Page Details

Property	Value
URL	https://cat.pdx.edu/platforms/linux/remote-access/persistent-screen/
Last Crawled	2026-03-21 03:30:49 (22 days ago)
First Indexed	2019-06-28 15:17:53 (6 years ago)
HTTP Status Code	200
Meta Title	Keeping your shell sessions persistent with Screen – Computer Action Team
Meta Description	Persistent Shell Sessions with Screen Screen is a program that facilitates the management of multiple shell sessions. When you run screen from a Linux command line, it will open a screen session on top of your current command line window, with a few important benefits:
Meta Canonical	null
Boilerpipe Text	Skip to content Home Users For New Users Computer Accounts Facilities Lab Reservation Calendars Guidelines CS Tutors Platforms Windows Linux Mac Mobile Services Printing Network Software Storage Scanning Solutions Web Services Email Services in MCECS About Contact Home Platforms Linux Remote Access to Linux Services Keeping your shell sessions persistent with Screen Keeping your shell sessions persistent with Screen admin 2020-12-29T17:14:01-08:00 Screen is a program that facilitates the management of multiple shell sessions. When you run screen from a Linux command line, it will open a screen session on top of your current command line window, with a few important benefits: Screen windows behave similarly to multiple tabs on a web browser, letting you switch to other “sessions” with a few keystrokes. Screens give you the ability to “disconnect” your screen session, leaving your running programs intact and allowing you to reconnect at a later time to resume your work. You can imagine this like minimizing a window instead of closing it. This is invaluable if you have a long running process and wish to start it and return to check on its progress from time to time. If your terminal session is closed (via ssh or through a Linux X Windows session), all work that you’re doing stays around. The screen session will become “detached” but is still active. This means that you can pick up right where you left off easily. This adds a layer of security for your important work, and also provides the ability to easily work on the same project from many different machines. To open a screen session, type “screen” from the command line like you would for any other command. Once run, you will be placed inside a new screen session, which looks a lot like a normal terminal window. Once within screen, the main command that you use to manage your shell window(s) is “ctrl-a” combined with any number of other keys. For example, “ctrl-a” followed by “?” will bring up the screen help menu. You will use “ctrl-a” followed by something for virtually everything within your screen session. From within a screen session, you can also open multiple windows and easily tab switch between them. New windows can be made with “ctrl-a” -> “c”; it’s important to understand that each screen “window” is actually an entirely new shell at the command line. When you create a new window you’ll see that all of your windows are listed at the bottom of the window, and the active window is highlighted in green. It should look something like this: In order to switch through all of your active windows, you can use “ctrl-a” -> “n” to go to the next window and “ctrl-a” -> “p” to go to the previous window. Each window also has an associated number, as you can see on the bottom of the above screenshot. An alternative to switching windows is to use “ctrl-a” followed by the tab number to jump right to that window. You can also detach from a screen session manually with “ctrl-a” -> “d” and then reattach by typing “screen -r” at the command line when you log back into the system. Importantly, reconnecting with screen -r will open the screen session that you’ve most recently closed, meaning that so long as you don’t accidentally spin up multiple screen sessions it will be enough to always get back to the session you want. Using this knowledge you could, for example: SSH to an MCECS Linux server. Start up a new screen session. Do any work you need inside. Detach from screen. Go home and reattach to the same exact session. All without any fear of losing your work from a system crash or forgetting to save. From the above sections you should have more than enough working knowledge to be able to start using screen effectively. However, there are some instances in which you might create multiple screen sessions and you will need to know how to manage those effectively. A very common mistake people make when first using screen is to accidentally type “screen” instead of “screen -r” when meaning to re-attach. This will create a second screen session and if you detach and attempt to reattach you’ll see the following: Solving this problem is very simple, you can type “screen -r ” to enter a screen session with the given number. In the above example, my screen sessions have PIDs of 14573, 14563, and 14556, as you can see. So you could simply type “screen -r 14573” and then from within screen you can use the command “ctrl-a -> \” to delete your current screen. “Ctrl-a -> \” is a new command that won’t just detach you from the screen and leave it running, it will remove it forever, so use it with caution . After deleting the screen you accidentally created, you should be able to “screen -r” back into the screen session you wanted. Another way to find the screen session you want is to use “screen -ls” which will list all screen sessions you have running. If you’ve been creating new screens by just typing “screen” than the output of “screen -ls” will look something like this: While this does show you the date that each screen session was created, it’s kind of difficult to differentiate which screen is which. Thankfully, screen has a solution. On creating a new screen window, instead of using “screen” use “screen -S ” to give your new session a name of your choosing. This aids in identifying which screen is which as you can see below: I have two screen sessions that I’ve named “school” and “work.” You can then reattach to a named screen using “screen -r ” to quickly get back to the workstation you want. Page load link Go to Top
Markdown	[Skip to content](https://cat.pdx.edu/platforms/linux/remote-access/persistent-screen/#content) [YouTube](https://www.youtube.com/user/catpsu/ "YouTube") 503-725-5420 \\| FAB 82\\|[support@cat.pdx.edu](mailto:support@cat.pdx.edu) [![Computer Action Team Logo](https://cat.pdx.edu/wp-content/uploads/2020/09/PSUthecat-logo-mcecs-2.png) ![Computer Action Team Logo](https://cat.pdx.edu/wp-content/uploads/2017/08/psu-logomobile.png)](https://cat.pdx.edu/) - [Home](https://cat.pdx.edu/) - [Users](https://cat.pdx.edu/users/) - [For New Users](https://cat.pdx.edu/users/getting-help/) - [Computer Accounts](https://cat.pdx.edu/users/computer-accounts/) - [Facilities](https://cat.pdx.edu/users/facilities/) - [Lab Reservation Calendars](https://cat.pdx.edu/users/facilities/lab-reservation-calendars/) - [Guidelines](https://cat.pdx.edu/users/guidelines/) - [CS Tutors](https://cat.pdx.edu/users/cs-tutors/) - [Platforms](https://cat.pdx.edu/platforms/) - [Windows](https://cat.pdx.edu/platforms/windows/) - [Linux](https://cat.pdx.edu/platforms/linux/) - [Mac](https://cat.pdx.edu/platforms/mac/) - [Mobile](https://cat.pdx.edu/platforms/mobile/) - [Services](https://cat.pdx.edu/services/) - [Printing](https://cat.pdx.edu/services/printing/) - [Network](https://cat.pdx.edu/services/network/) - [Software](https://cat.pdx.edu/services/software/) - [Storage](https://cat.pdx.edu/services/storage/) - [Scanning Solutions](https://cat.pdx.edu/services/scanning/) - [Web Services](https://cat.pdx.edu/services/web/) - [Email Services in MCECS](https://cat.pdx.edu/services/mail/) - [About](https://cat.pdx.edu/about-the-cat/) - [Contact](https://cat.pdx.edu/contact-us/) # Keeping your shell sessions persistent with Screen 1. [Home](https://cat.pdx.edu/) 2. [Platforms](https://cat.pdx.edu/platforms/) 3. [Linux](https://cat.pdx.edu/platforms/linux/) 4. [Remote Access to Linux Services](https://cat.pdx.edu/platforms/linux/remote-access/) 5. Keeping your shell sessions persistent with Screen Keeping your shell sessions persistent with Screen[admin](https://cat.pdx.edu/author/admin/ "Posts by admin")2020-12-29T17:14:01-08:00 # Persistent Shell Sessions with Screen Screen is a program that facilitates the management of multiple shell sessions. When you run screen from a Linux command line, it will open a screen session on top of your current command line window, with a few important benefits: - Screen windows behave similarly to multiple tabs on a web browser, letting you switch to other “sessions” with a few keystrokes. - Screens give you the ability to “disconnect” your screen session, leaving your running programs intact and allowing you to reconnect at a later time to resume your work. You can imagine this like minimizing a window instead of closing it. This is invaluable if you have a long running process and wish to start it and return to check on its progress from time to time. - If your terminal session is closed (via ssh or through a Linux X Windows session), all work that you’re doing stays around. The screen session will become “detached” but is still active. This means that you can pick up right where you left off easily. This adds a layer of security for your important work, and also provides the ability to easily work on the same project from many different machines. ![Image Showing a Diagram of Screen When Connecting Remotely](https://cat.pdx.edu/wp-content/uploads/2018/07/screen_dia-300x279.png) ## How to use Screen ### Opening Screen To open a screen session, type “screen” from the command line like you would for any other command. Once run, you will be placed inside a new screen session, which looks a lot like a normal terminal window. Once within screen, the main command that you use to manage your shell window(s) is “ctrl-a” combined with any number of other keys. For example, “ctrl-a” followed by “?” will bring up the screen help menu. You will use “ctrl-a” followed by something for virtually everything within your screen session. ### Creating & Switching Screen Windows From within a screen session, you can also open multiple windows and easily tab switch between them. New windows can be made with “ctrl-a” -\> “c”; it’s important to understand that each screen “window” is actually an entirely new shell at the command line. When you create a new window you’ll see that all of your windows are listed at the bottom of the window, and the active window is highlighted in green. It should look something like this: ![Image Showing the Linux Prompt on a CAT Server](https://cat.pdx.edu/wp-content/uploads/2018/07/screen_1.png) In order to switch through all of your active windows, you can use “ctrl-a” -\> “n” to go to the next window and “ctrl-a” -\> “p” to go to the previous window. Each window also has an associated number, as you can see on the bottom of the above screenshot. An alternative to switching windows is to use “ctrl-a” followed by the tab number to jump right to that window. ### Disconnecting & Reconnecting to a Screen Session You can also detach from a screen session manually with “ctrl-a” -\> “d” and then reattach by typing “screen -r” at the command line when you log back into the system. Importantly, reconnecting with screen -r will open the screen session that you’ve most recently closed, meaning that so long as you don’t accidentally spin up multiple screen sessions it will be enough to always get back to the session you want. Using this knowledge you could, for example: 1. SSH to an MCECS Linux server. 2. Start up a new screen session. 3. Do any work you need inside. 4. Detach from screen. 5. Go home and reattach to the same exact session. All without any fear of losing your work from a system crash or forgetting to save. ## Managing Multiple Screen Sessions From the above sections you should have more than enough working knowledge to be able to start using screen effectively. However, there are some instances in which you might create multiple screen sessions and you will need to know how to manage those effectively. ### Re-attaching to a Screen Session A very common mistake people make when first using screen is to accidentally type “screen” instead of “screen -r” when meaning to re-attach. This will create a second screen session and if you detach and attempt to reattach you’ll see the following: ![Image Showing 3 Open Screen Sessions on a CAT Server](https://cat.pdx.edu/wp-content/uploads/2018/07/screen_2.png) Solving this problem is very simple, you can type “screen -r ” to enter a screen session with the given number. In the above example, my screen sessions have PIDs of 14573, 14563, and 14556, as you can see. So you could simply type “screen -r 14573” and then from within screen you can use the command “ctrl-a -\> \\” to delete your current screen. “Ctrl-a -\> \\” is a new command that won’t just detach you from the screen and leave it running, it will remove it forever, so use it with caution. After deleting the screen you accidentally created, you should be able to “screen -r” back into the screen session you wanted. ### Effectively Using Multiple Screen Sessions Another way to find the screen session you want is to use “screen -ls” which will list all screen sessions you have running. If you’ve been creating new screens by just typing “screen” than the output of “screen -ls” will look something like this: ![Image showing 3 Open Screen Sessions Running on a CAT Server](https://cat.pdx.edu/wp-content/uploads/2018/07/screen_3.png) While this does show you the date that each screen session was created, it’s kind of difficult to differentiate which screen is which. Thankfully, screen has a solution. On creating a new screen window, instead of using “screen” use “screen -S ” to give your new session a name of your choosing. This aids in identifying which screen is which as you can see below: ![Image showing 2 Named Open Screen Sessions Running on a CAT Server](https://cat.pdx.edu/wp-content/uploads/2018/07/screen_4.png) I have two screen sessions that I’ve named “school” and “work.” You can then reattach to a named screen using “screen -r ” to quickly get back to the workstation you want. - [Linux](https://cat.pdx.edu/platforms/linux/) - [Administrivia \>](https://cat.pdx.edu/platforms/linux/administrivia/) - [Linux User Environment \>](https://cat.pdx.edu/platforms/linux/user-environment/) - [Remote Access](https://cat.pdx.edu/platforms/linux/remote-access/) - [Connecting to PSU SECURE (Wi-FI)](https://cat.pdx.edu/platforms/linux/remote-access/psu-secure-gnome/) - [Using OpenVPN on Linux](https://cat.pdx.edu/platforms/linux/remote-access/openvpn/) - [Using SSH for Remote Connections in MCECS](https://cat.pdx.edu/platforms/linux/remote-access/using-ssh-for-remote-connections-in-mcecs/) - [Using SSH from Linux](https://cat.pdx.edu/platforms/linux/remote-access/using-ssh-from-linux/) - [SSH Port Forwarding](https://cat.pdx.edu/platforms/linux/remote-access/ssh-portforward/) - [Dealing with SSH Host Key Changes](https://cat.pdx.edu/platforms/linux/remote-access/dealing-with-ssh-host-key-changes/) - [Using SFTP for Remote File Transfer from the Command Line](https://cat.pdx.edu/platforms/linux/remote-access/using-sftp-for-remote-file-transfer-from-command-line/) - [Copying Your CAT Linux Files Remotely](https://cat.pdx.edu/platforms/linux/remote-access/copying-your-cat-linux-files-remotely/) - [Keeping your shell sessions persistent with Screen](https://cat.pdx.edu/platforms/linux/remote-access/persistent-screen/) - [Mosh (Mobile Shell) for Intermittent Connectivity](https://cat.pdx.edu/platforms/linux/remote-access/mosh/) - [Connecting to your Stash from Linux](https://cat.pdx.edu/platforms/linux/remote-access/connect-stash/) - [VNC in MCECS](https://cat.pdx.edu/platforms/linux/remote-access/vnc-in-mcecs/) - [VNC from Linux to Linux](https://cat.pdx.edu/platforms/linux/remote-access/vnc/) - [Running X11 Applications Remotely](https://cat.pdx.edu/platforms/linux/remote-access/remote-x/) - [Using RDP to Connect to a Windows Computer from Linux](https://cat.pdx.edu/platforms/linux/remote-access/using-rdp-to-connect-to-a-windows-computer-from-linux/) - [Using RDP to connect to Linux systems](https://cat.pdx.edu/platforms/linux/remote-access/rdp-to-linux-xrdp/) - [File Sharing through RDP from Linux](https://cat.pdx.edu/platforms/linux/remote-access/file-sharing-rdp-from-linux/) - [Printing Over SSH Using LPR](https://cat.pdx.edu/platforms/linux/remote-access/ssh-printing/) - [Linux Reference \>](https://cat.pdx.edu/platforms/linux/reference/) - [Linux How To’s and FAQs \>](https://cat.pdx.edu/platforms/linux/how-to/) #### CONTACT THE CAT Front Desk: FAB LL Suite 82 Open: 8am-6pm M-F, noon-5pm Sat (based on availability) Email: [support@cat.pdx.edu](mailto:support@cat.pdx.edu) Phone: 503.725.5420 (voicemail monitored) Web chat: <https://support.cat.pdx.edu/> #### Account Help - [Forgot Password?](https://cram.cecs.pdx.edu/) - [Activate MCECS Account](https://cram.cecs.pdx.edu/) - [Change Password](https://intranet.cecs.pdx.edu/password/) #### Website Help - [Sitemap](https://cat.pdx.edu/sitemap/) #### Computer Labs - [Locations](https://cat.pdx.edu/users/facilities/computer-labs/) - [Lab Reservation Calendars](https://cat.pdx.edu/users/facilities/lab-reservation-calendars/) - [FAB/EB Card Access](https://cat.pdx.edu/users/facilities/fab-eb-card-access/) - [Lab Status](https://cat.pdx.edu/labstatus/) - [Lab Use Policy](https://cat.pdx.edu/users/guidelines/lab-rules/) - [CAT Lost & Found](https://cat.pdx.edu/users/guidelines/lost-and-found/) #### Join The CAT - [Who are we?](http://braindump.cat.pdx.edu/#whatiscat) - [How to join?](http://braindump.cat.pdx.edu/) - [Learn about The Braindump](http://braindump.cat.pdx.edu/#whatisbraindump) Copyright 1993-2026 \\| Computer Action Team \\| Portland State University [YouTube](https://www.youtube.com/user/catpsu/ "YouTube") [Page load link](https://cat.pdx.edu/platforms/linux/remote-access/persistent-screen/) [Go to Top](https://cat.pdx.edu/platforms/linux/remote-access/persistent-screen/)
Readable Markdown	[Skip to content](https://cat.pdx.edu/platforms/linux/remote-access/persistent-screen/#content) - [Home](https://cat.pdx.edu/) - [Users](https://cat.pdx.edu/users/) - [For New Users](https://cat.pdx.edu/users/getting-help/) - [Computer Accounts](https://cat.pdx.edu/users/computer-accounts/) - [Facilities](https://cat.pdx.edu/users/facilities/) - [Lab Reservation Calendars](https://cat.pdx.edu/users/facilities/lab-reservation-calendars/) - [Guidelines](https://cat.pdx.edu/users/guidelines/) - [CS Tutors](https://cat.pdx.edu/users/cs-tutors/) - [Platforms](https://cat.pdx.edu/platforms/) - [Windows](https://cat.pdx.edu/platforms/windows/) - [Linux](https://cat.pdx.edu/platforms/linux/) - [Mac](https://cat.pdx.edu/platforms/mac/) - [Mobile](https://cat.pdx.edu/platforms/mobile/) - [Services](https://cat.pdx.edu/services/) - [Printing](https://cat.pdx.edu/services/printing/) - [Network](https://cat.pdx.edu/services/network/) - [Software](https://cat.pdx.edu/services/software/) - [Storage](https://cat.pdx.edu/services/storage/) - [Scanning Solutions](https://cat.pdx.edu/services/scanning/) - [Web Services](https://cat.pdx.edu/services/web/) - [Email Services in MCECS](https://cat.pdx.edu/services/mail/) - [About](https://cat.pdx.edu/about-the-cat/) - [Contact](https://cat.pdx.edu/contact-us/) 1. [Home](https://cat.pdx.edu/) 2. [Platforms](https://cat.pdx.edu/platforms/) 3. [Linux](https://cat.pdx.edu/platforms/linux/) 4. [Remote Access to Linux Services](https://cat.pdx.edu/platforms/linux/remote-access/) 5. Keeping your shell sessions persistent with Screen Keeping your shell sessions persistent with Screen[admin](https://cat.pdx.edu/author/admin/ "Posts by admin")2020-12-29T17:14:01-08:00 Screen is a program that facilitates the management of multiple shell sessions. When you run screen from a Linux command line, it will open a screen session on top of your current command line window, with a few important benefits: - Screen windows behave similarly to multiple tabs on a web browser, letting you switch to other “sessions” with a few keystrokes. - Screens give you the ability to “disconnect” your screen session, leaving your running programs intact and allowing you to reconnect at a later time to resume your work. You can imagine this like minimizing a window instead of closing it. This is invaluable if you have a long running process and wish to start it and return to check on its progress from time to time. - If your terminal session is closed (via ssh or through a Linux X Windows session), all work that you’re doing stays around. The screen session will become “detached” but is still active. This means that you can pick up right where you left off easily. This adds a layer of security for your important work, and also provides the ability to easily work on the same project from many different machines. ![Image Showing a Diagram of Screen When Connecting Remotely](https://cat.pdx.edu/wp-content/uploads/2018/07/screen_dia-300x279.png) To open a screen session, type “screen” from the command line like you would for any other command. Once run, you will be placed inside a new screen session, which looks a lot like a normal terminal window. Once within screen, the main command that you use to manage your shell window(s) is “ctrl-a” combined with any number of other keys. For example, “ctrl-a” followed by “?” will bring up the screen help menu. You will use “ctrl-a” followed by something for virtually everything within your screen session. From within a screen session, you can also open multiple windows and easily tab switch between them. New windows can be made with “ctrl-a” -\> “c”; it’s important to understand that each screen “window” is actually an entirely new shell at the command line. When you create a new window you’ll see that all of your windows are listed at the bottom of the window, and the active window is highlighted in green. It should look something like this: ![Image Showing the Linux Prompt on a CAT Server](https://cat.pdx.edu/wp-content/uploads/2018/07/screen_1.png) In order to switch through all of your active windows, you can use “ctrl-a” -\> “n” to go to the next window and “ctrl-a” -\> “p” to go to the previous window. Each window also has an associated number, as you can see on the bottom of the above screenshot. An alternative to switching windows is to use “ctrl-a” followed by the tab number to jump right to that window. You can also detach from a screen session manually with “ctrl-a” -\> “d” and then reattach by typing “screen -r” at the command line when you log back into the system. Importantly, reconnecting with screen -r will open the screen session that you’ve most recently closed, meaning that so long as you don’t accidentally spin up multiple screen sessions it will be enough to always get back to the session you want. Using this knowledge you could, for example: 1. SSH to an MCECS Linux server. 2. Start up a new screen session. 3. Do any work you need inside. 4. Detach from screen. 5. Go home and reattach to the same exact session. All without any fear of losing your work from a system crash or forgetting to save. From the above sections you should have more than enough working knowledge to be able to start using screen effectively. However, there are some instances in which you might create multiple screen sessions and you will need to know how to manage those effectively. A very common mistake people make when first using screen is to accidentally type “screen” instead of “screen -r” when meaning to re-attach. This will create a second screen session and if you detach and attempt to reattach you’ll see the following: ![Image Showing 3 Open Screen Sessions on a CAT Server](https://cat.pdx.edu/wp-content/uploads/2018/07/screen_2.png) Solving this problem is very simple, you can type “screen -r ” to enter a screen session with the given number. In the above example, my screen sessions have PIDs of 14573, 14563, and 14556, as you can see. So you could simply type “screen -r 14573” and then from within screen you can use the command “ctrl-a -\> \\” to delete your current screen. “Ctrl-a -\> \\” is a new command that won’t just detach you from the screen and leave it running, it will remove it forever, so use it with caution. After deleting the screen you accidentally created, you should be able to “screen -r” back into the screen session you wanted. Another way to find the screen session you want is to use “screen -ls” which will list all screen sessions you have running. If you’ve been creating new screens by just typing “screen” than the output of “screen -ls” will look something like this: ![Image showing 3 Open Screen Sessions Running on a CAT Server](https://cat.pdx.edu/wp-content/uploads/2018/07/screen_3.png) While this does show you the date that each screen session was created, it’s kind of difficult to differentiate which screen is which. Thankfully, screen has a solution. On creating a new screen window, instead of using “screen” use “screen -S ” to give your new session a name of your choosing. This aids in identifying which screen is which as you can see below: ![Image showing 2 Named Open Screen Sessions Running on a CAT Server](https://cat.pdx.edu/wp-content/uploads/2018/07/screen_4.png) I have two screen sessions that I’ve named “school” and “work.” You can then reattach to a named screen using “screen -r ” to quickly get back to the workstation you want. [Page load link](https://cat.pdx.edu/platforms/linux/remote-access/persistent-screen/) [Go to Top](https://cat.pdx.edu/platforms/linux/remote-access/persistent-screen/)
Shard	195 (laksa)
Root Hash	536666605424911595
Unparsed URL	edu,pdx!cat,/platforms/linux/remote-access/persistent-screen/ s443