Fedor Ratnikov,
12/10/02 4:43 PM
HEXCAF at Rutgers is a clone of CDF CAF at Fermilab and the most information of how to use Fermilab CAF is valid for HEXCAF as well. This document assumes reader is familiar with basic CAF documentation http://cdfcaf.fnal.gov/doc/UserGuide/UserGuide.html. HEXCAF specific is described below.
Access is granted by HEXCAF administrator (Pieter or Fedor at the moment). All members of HEX/CDF are granted already.
Jobs are submitted to CAF by means of a Graphical User Interface (GUI), which is run from the user's desktop. The CAF GUI package is stored in the CDF CVS repository. To use multi CAF version of GUI - CafGui_dcaf user should create configuration file .cafrc which describes a variety of CAFs. The file describing HEXFARM can be copied from here. The .cafrc file must be in current or in the home directory when starting CafGui_dcaf. A good idea is putting .cafrc into home directory once forever
To use the CAF GUI, type:
> source ~cdfsoft/cdf2.cshrc
> setup cdfsoft2 development
> CafGui_dcaf &
CafGui requires Kerberos dynamic libraries. If it complains because of Kerberos libraries, add libraries to the corresponding path:
> setenv LD_LIBRARY_PATH /usr/krb5/lib:$LD_LIBRARY_PATH
Note extra menu Analisys Farm on the top. Destination CAF may be selected there.
In order for the output tar file to be copied to your desktop you must have the file .k5login in your home directory:
your_user_name@FNAL.GOV
caf3/cdf/your_user_name@FNAL.GOV
Note caf3 that is a notation for HEXCAF in FNAL.GOV realm. caf/cdf/your_user_name@FNAL.GOV can also be added to accept output from Fermilab CAF as well.
Destination host must accept incoming kerberized RCP connections. Most Fermilab hosts satisfy this requirement. hexcaf.rutgers.edu is the only RUTGERS host that shares users home areas and can be used to put output to HEXFARM data disks.
Communication with central CAF is hardcoded there. A HEXCAF destination should be defined via environment: setenv CAF_CURRENT rutgers.
Commands cafjobs and cafkill then work like described in primary CAF manual.
Commands caflog and caftail does not work because they need kerberized remote access to worker nodes.
HEXCAF has no internal FTP server. All output must be either written to the HEXFARM data disks that all are mounted on HEXCAF. Alternative way is to write into current directory of the job - all files will be grabbed, tarred and copied to the destination specified in CafGui.
No ICAF service on HEXCAF
Standard FBSNG monitoring is installed: http://hexcaf.rutgers.edu:8080/fbswww
Note, that CAF job is running as ‘cafuser’ user and has (or has not) corresponding privileges. Particularly it cannot write into your directories unless write access is granted.
Enjoy your HEXCAF!