HPC Getting Started: Logging on
Once your HPC account is set up, login to the supercomputer cluster using the Secure Shell (SSH) to connect to dlx.uky.edu and authenticate with your link blue userid and password. If you don't know how to do this, or don't have an SSH client, then see the Secure Shell (SSH) FAQ. After logging in the first time, you may want to set up an ssh key-pair to authenticate in the future. See How do I set up an ssh key pair? for details.
As usual, if you type your password incorrectly five times in a row, your link blue account will be locked for half an hour.
You must forward email from the HPC cluster to an email address that you read regularly, so the HPC support team can contact you in the event of problems with your jobs or account. To do this, create a file in your home directory named .forward (note the leading period). This file should contain a single line, which is the address to which your mail should be forwarded.
If you want to display graphics on your workstation, you'll probably want to run an X server. Add the '-Y' flag to the ssh command or setup X tunneling on your ssh client. See How do I set up an X server? for details.
Your Computing Environment
When you logon to the cluster, you will be in your $HOME directory. This is where you will find your dot files and folders, i.e., their names begins with a ".". The way you interact with the DLX computer can be controlled via certain startup scripts that run when you log in and at other times. You can customize some of these scripts, which are called "dot files," by setting environment variables and aliases in them.
There are several "standard" dot-files such as .bash_profile, .bashrc, .forward, .cshrc, .kshrc, .login, .profile, .tcshrc, or .zprofile. Which of those you modify depends on your choice of shell. The default shell is bash. to change shell type the name of the shell. The DLX supports bash, tsch, and, csh.
The table below contains examples of basic customizations. Note that when making changes such as these it's always a good idea to have two terminal sessions active on the machine so that you can back out changes if needed!
|export ENVAR=value||setenv ENVAR value|
|export PATH=$PATH:/new/path||set PATH = ( $PATH /new/path)|
|alias ll='ls -lrt’||alias ll “ls –lrt”|
To activate changes you have made in a dot file, type: source .name_of_dot_file