The directions from USCMS are here: http://uscms.org/SoftwareComputing/UserComputing/ConnectUAF.html. However, you need to follow additional directions.
There are three programs you will want to run: kinit to get permission to login, klist to check those permissions, and ssh to actually connect. However, on the hep.wisc.edu computers, the default versions of kinit and ssh are not the ones that work, and the "klist" command doesn't exist. Therefore, wherever the webpage says "kinit", "klist", or "ssh", you need to insert the following commands:
kinit --> /usr/kerberos/bin/kinit klist --> klist-krb5 ssh --> ssh-krb5
In addition, due to something with the Scientific Linux 3.0.4
operating system that the hep.wisc.edu computers use, you can't actually log
into cmsuaf.fnal.gov or cmsuafng.fnal.gov as such; you will have to log into
one of the direct access nodes listed on the above USCMS webpage (the nodes
are cmswn0xx.fnal.gov where xx is 51 through 55). Now it is possible
to just login to cmslpc.fnal.gov.
$ /usr/kerberos/bin/kinit -A -f [fnal_username]Enter your FNAL kerberos password at the prompt.
$ klist-krb5 -a -fDepending on whether you've already tried logging in, there will be one or more entries in the list. Each should have a Flags: field and an Addresses: field.
$ ssh-krb5 cmslpc.fnal.gov
$ ssh-krb5 -l joeschmoe cmslpc.fnal.gov
$ ssh-krb5 joeschmoe@cmslpc.fnal.govThis will log you in. If after the welcome message you see a line like
/usr/X11R6/bin/xauth: timeout in locking authority file /afs/fnal/files/home/room2/jleonard/.Xauthoritythis means that you don't have the correct permissions, and you won't be able to write to your home directory. (See the USCMS FAQ page, http://www.uscms.org/SoftwareComputing/UserComputing/FAQ.html.)
This is the process that I have found to work. Let me know if you think
something's wrong. The USCMS page above (
http://uscms.org/SoftwareComputing/UserComputing/ConnectUAF.html) also
has a lot of information. A recent e-mail from the USCMS computing
people said they wanted to phase out the direct access nodes, but later I got
confirmation that they'd keep them around for the people like us who can't
log in any other way. We can now login using the head nodes.