Differences

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

--- abstract:caviness:system_access:system_access [2018-11-29 15:25] – [Logging on to Caviness] ssunkara
+++ abstract:caviness:system_access:system_access [2021-10-26 15:28] (current) – [Secure shell program (SSH)] anita
@@ Line 20: / Line 20: @@
 files in the ''.ssh'' directory.
 </note>
+Please refer to Windows and Mac/Linux related sections for specific details using the command line on your local computer:
+  * [[:abstract:caviness:system_access:windows|Windows]]
+  * [[:abstract:caviness:system_access:linux|Mac/Linux]]
 ===== Logging on to Caviness =====
-You need a [[abstract:caviness:account:account|Caviness account]] to access the login node. For example,  using SSH to connect to the Caviness login node with account ''traine'', type:
+You need a [[abstract:caviness:account:account|Caviness account]] to access the login node and it is very important to review the information about [[abstract:caviness:account:account#cluster-accounts|cluster accounts]] and [[abstract:caviness:account:account#cluster-groups|cluster groups]] before connecting. For example, using SSH to connect to the Caviness login node with account ''traine'', type:
 <code bash>
     ssh traine@caviness.hpc.udel.edu
+</code>
+or if you need you use X-Windows requiring X11 forwarding, then use
+<code bash>
+    ssh -Y traine@caviness.hpc.udel.edu
 </code>
-Please refer to Windows and Mac/Linux related sections for specific details:
+You may set up direct SSH key authentication on Caviness once you are on the system by adding the desired public key to your authorized_keys file in the .ssh directory inside your home directory. Once you have a SSH key set up this way, you can access Caviness directly by running ''ssh caviness.hpc.udel.edu'' or ''ssh -Y caviness.hpc.udel.edu''.
-  * [[:abstract:caviness:system_access:windows|Windows]]
-  * [[:abstract:caviness:system_access:linux|Mac/Linux]]
-To learn about launching GUI applications on the Caviness, refer to [[abstract:caviness:runjobs:schedule_jobs#launching-gui-applications-x11-forwarding|Schedule Jobs]] page.
+Once you are logged into Caviness, your account is configured as a member of an investing-entity group name ([[abstract:caviness:app_dev:compute_env#using-workgroup-and-directories|workgroup]]) which determines access to your group's compute nodes, queues and storage resources on Caviness. Setting your workgroup environment is required in order to submit jobs to the Caviness 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 Caviness, 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 Caviness. Setting your workgroup environment is required in order to submit jobs to the Caviness 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 42: / Line 44: @@
 </code>
-You will need to know [[:training:linux:linux|Unix/Linux]] and [[:training:hpc:hpc|HPC]] concepts before using Caviness. Use the <html><span style="color:#ffffff;background-color:#2fa4e7;padding:3px 7px !important;border-radius:4px;">sidebar</span></html> to navigate documentation about Caviness, from accessing the cluster to running applications, using [[:software:software|software]] and available [[:training:training|training]].
+Please review all the information regarding your computing environment especially the [[abstract:caviness:app_dev:compute_env#startup-and-logout-scripts|startup and logout scripts]] and [[abstract:caviness:app_dev:compute_env#using-valet-and-your-unix-environment|using VALET]]. You will need to know [[:training:linux:linux|Unix/Linux]] and [[:training:hpc:hpc|HPC]] concepts before using Caviness. Use the <html><span style="color:#ffffff;background-color:#2fa4e7;padding:3px 7px !important;border-radius:4px;">sidebar</span></html> to navigate documentation about Caviness, from accessing the cluster to running applications, using [[:software:software|software]] and available [[:training:training|training]].
+To learn about launching GUI applications on Caviness from a Windows machine, refer to [[abstract:caviness:runjobs:schedule_jobs#launching-gui-applications-x11-forwarding|Schedule Jobs]] page.
+<note important>Please review the [[technical:generic:caviness-login-cpu-limit|document]] summarizing the current resource limits and the need for and implementation of additional limits on the Caviness cluster login nodes.</note>
 ===== 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 63: @@
 </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.