Differences

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

--- abstract:farber:system_access:system_access [2018-03-21 16:23] – [Logging on the cluster] sraskar
+++ abstract:farber:system_access:system_access [2021-10-13 09:59] (current) – [Screen sessions] anita
@@ Line 1: / Line 1: @@
-====== Accessing a cluster =====
+====== Connecting to Farber =====
-//This section uses the wiki's [[:#documentation-conventions|documentation conventions]].//
 ===== Secure shell program (SSH) =====
@@ Line 21: / Line 21: @@
 </note>
-==== Logging on the cluster ====
-To initiate an SSH connection from a Mac/UNIX/Linux system to the cluster's login (head) node, use
-the generic command
-''ssh''<<//options//>> <<//HPC_username//>>@<<//HPC_hostname//>>
+===== Logging on to Farber =====
+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:
-For example,
 <code bash>
-    ssh -Y traine@farber.hpc.udel.edu
+    ssh traine@farber.hpc.udel.edu
 </code>
-This **ssh** command is on your local system.  This example assumes you have a local command line interface, and have an X11 server running, for example, Mac/UNIX/Linux or cygwin/X (with the openssh client)
+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]]
-<note tip>**Windows with PuTTY/Xming**: When using the recommended [[http://udeploy.udel.edu/software/putty-with-xming|PuTTY/Xming on Windows]] installation instructions, you create a saved session with the options to want to use every time you logon.  You can create as many saved sessions as needed with various options.
-</note>
-<note tip>**Mac/UNIX/Lunix with command line SSH**:
+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:
-When using the recommended setup for [[general/connect/ssh-command-line|command line SSH]], you can add a service that bundles options you want to use every time you logon or copy files. You can add as many services as needed with various options.
-</note>
+<code bash>
+    workgroup -g it_css
+</code>
+You will need to know [[:training:linux:linux|Unix/Linux]] and [[:training:hpc:hpc|HPC]] concepts before using Farber. Use the <html><span style="color:#ffffff;background-color:#2fa4e7;padding:3px 7px !important;border-radius:4px;">sidebar</span></html> to navigate documentation about Farber, from accessing the cluster to running applications, using [[:software:software|software]] and available [[:training:training|training]].
 ===== 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 60: / 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.