Differences

This shows you the differences between two versions of the page.

--- abstract:farber:system_access:system_access [2018-05-22 14:09] – [Accessing Farber] anita
+++ abstract:farber:system_access:system_access [2021-10-13 09:59] (current) – [Screen sessions] anita
@@ Line 21: / Line 21: @@
 </note>
-==== Logging on the cluster ====
-Please refer to Windows, Linux & Mac related sections for specific details -
-  * [[:abstract:farber:system_access:windows|Windows]]
-  * [[:abstract:farber:system_access:linux|Linux]]
-  * [[:abstract:farber:system_access:mac|Mac]]
 ===== Logging on to Farber =====
-You need a [[abstract:farber:account:account|Farber account]] to access the login node. For example,  [[[:abstract:farber:system_access:system_access| using SSH to connect]] to the Farber login node with account ''traine'', type:
+You need a [[abstract:farber:account:account|Farber account]] to access the login node. For example,  using SSH to connect to the Farber login node with account ''traine'', type:
 <code bash>
@@ Line 35: / Line 29: @@
 </code>
-===== Using Farber =====
+Please refer to Windows and Mac/Linux related sections for specific details:
+  * [[:abstract:farber:system_access:windows|Windows]]
+  * [[:abstract:farber:system_access:linux|Mac/Linux]]
-Your account is configured as a member of an investing-entity group name (workgroup) which determines access to your group's compute nodes, queues and storage resources on Farber. Setting your workgroup environment is required in order to submit jobs to the Farber cluster. For example, the ''traine'' account is a member of the ''it_css'' workgroup. To start a shell in the ''it_css'' workgroup, type:
+Once you are logged into Farber, your account is configured as a member of an investing-entity group name (workgroup) which determines access to your group's compute nodes, queues and storage resources on Farber. Setting your workgroup environment is required in order to submit jobs to the Farber cluster. For example, the ''traine'' account is a member of the ''it_css'' workgroup. To start a shell in the ''it_css'' workgroup, type:
 <code bash>
@@ Line 47: / Line 44: @@
 ===== Screen sessions =====
-When an ssh session is ended intentionally or by a loss of connectivity, you cannot generally
+When an SSH session is ended intentionally or by a loss of connectivity, you cannot generally restart it and resume your work. The UNIX **screen** command provides a useful solution. This
-restart it and resume your work. The UNIX **screen** command provides a useful solution. This
+command creates a virtual terminal window session that continues to run after you are logged off. It allows you to reattach the same virtual terminal window session and resume working.
-command creates a virtual terminal window session that continues to run after you are logged off. It
-allows you to reattach the same virtual terminal window session and resume working.
-See the **man** page for **screen** for details.
 <note tip>
-Suppose you have a significant amount of interactive work to be done on the cluster, but you have a interruption coming up shortly, such as lunch.
+Suppose you have a significant amount of interactive work to be done on the cluster, but you have an interruption coming up shortly, such as lunch.
 You can start a screen session and work until lunchtime.  Log out and when you come back from lunch, reattach the screen session and continue your work. Even output from jobs will be displayed, as if you never left.
 </note>
@@ Line 62: / Line 56: @@
 </note>
+See the **man** page for **screen** for details or review a short video [[https://www.youtube.com/watch?v=_ZJiEX4rmN4|How to Use the Screen Command on Linux]] to get started.