Setting up a BRAHMS account on RCF

Depending on your login shell, you should follow one of the links below. To figure out what your login shell is, do

        prompt%  echo $SHELL

If it says /bin/bash, /bin/sh or similar you're using a SH family shell. If it says /bin/csh, /bin/tcsh you're using a CSH family shell.

CSH family shells
SH family shells

General issues

Here, a few general issues are listed.

Do not put . in your PATH environment variable. You're leaving yourself wide open for all kinds of attacks.
Do not put relative paths in your PATH environment variable. You're leaving yourself wide open for all kinds of attacks.
When modifing environment variables like LD_LIBRARY_PATH, MANPATH and the like, always check if it's defined before modifying it.
Always put braces '{', '}' around variables names.

CSH family shells

Your ~/.cshrc and ~/.tcshrc files should be completly empty. Those files are read by any shell, and mistakes in those shells are rather fatal, and any setting there will override your normal settings, sometimes leading to very odd results.

Your ~/.login file should look like:

        #
        # Login shell reconfiguration file 
	# 
	# setenv BRAHMS_NEW 1 
	if  ( -f /brahms/u/brahmlib/etc/brahms.login ) then 
	   source /brahms/u/brahmlib/etc/brahms.login
	endif 

	# 
	# Personal configuration follows here. 
	#

If you want to use the new software tree, uncomment the definition of BRAHMS_NEW above.

In the personal section, you should put setup code that enables your software, aliases, and the like. Note, that a lot of aliases have been defined for you.

Suppose you want your own BRAT and similar installed on your account. Then I highly recommend you create a architecture specific tree, so that Red Hat 7.2 stuff is installed in ~/i386_linux24, Red Hat 6.2 in ~/i386_linux22, and Solaris stuff in ~/sun4x_58. The in your ~/.login file, put

       setenv SYSNAME `fs sysname | sed "s,.*'\(.*\).*',\1,"`
       setenv MY_SOFTWARE 1
       if ($?MY_SOFTWARE) then 
          if ( -d ${HOME}/${SYSNAME}/bin ) then 
            echo "Using my software"   
            setenv PATH /brahms/u/cholm/${SYSNAME}/bin:${PATH}
            setenv PATH /brahms/u/cholm/${SYSNAME}/sbin:${PATH}
         endif
       endif

An alternative is to create your personal directory in /afs/rhic/brahms/user/${USER}, with the subdirectories

       prompt% mkdir /afs/rhic/brahms/user/${USER}
       prompt% cd /afs/rhic/brahms/user/${USER}
       prompt% mkdir .i386_linux24
       prompt% mkdir .i386_linux24/bin
       prompt% mkdir .i386_linux24/lib
       prompt% mkdir .i386_linux22
       prompt% mkdir .i386_linux22/bin
       prompt% mkdir .i386_linux22/lib
       prompt% mkdir .sun4x_58
       prompt% mkdir .sun4x_58/bin
       prompt% mkdir .sun4x_58/lib
       prompt% mkdir etc
       prompt% mkdir include
       prompt% mkdir share
       prompt% mkdir var

and then make the symbolic links

         prompt% ln -s @sys/bin bin 
	 prompt% ln -s @sys/lib lib

And put in your ~/.login file

       if ( -d /afs/rhic/brahms/user/${USER}/bin ) then 
          setenv PATH /afs/rhic/brahms/user/${USER}/bin:${PATH}
       endif

This has the advantage that AFS takes care of all the arcitecture dependent stuff, and you only have one installation of the archicture inpdentent stuff. The down side is that you're using AFS.

Please do not reset the PATH in you're ~/.login script. Always append.

SH family shells

Your ~/.bashrc and ~/.shrc files should be completly empty. Those files are read by any shell, and mistakes in those shells are rather fatal, and any setting there will override your normal settings, sometimes leading to very odd results.

Your ~/.profile file should look like:

        #
        # Login shell reconfiguration file 
	# 
	# excport BRAHMS_NEW=1 
	if  test -f /brahms/u/brahmlib/etc/brahms.profile ; then 
	   . /brahms/u/brahmlib/etc/brahms.profile
	fi 

	# 
	# Personal configuration follows here. 
	#

If you want to use the new software tree, uncomment the definition of BRAHMS_NEW above.

In the personal section, you should put setup code that enables your software, aliases, and the like. Note, that a lot of aliases have been defined for you.

       export SYSNAME=`fs sysname | sed "s,.*'\(.*\).*',\1,"`
       export MY_SOFTWARE=1
       if test ! "x$MY_SOFTWARE" = "x" ; then 
          if test -d ${HOME}/${SYSNAME}/bin ; then 
            echo "Using my software"   
            export PATH=/brahms/u/cholm/${SYSNAME}/bin:${PATH}
            export PATH=/brahms/u/cholm/${SYSNAME}/sbin:${PATH}
         fi
       fi

An alternative is to create your personal directory in /afs/rhic/brahms/user/${USER}, with the subdirectories

       prompt% mkdir /afs/rhic/brahms/user/${USER}
       prompt% cd /afs/rhic/brahms/user/${USER}
       prompt% mkdir .i386_linux24
       prompt% mkdir .i386_linux24/bin
       prompt% mkdir .i386_linux24/lib
       prompt% mkdir .i386_linux22
       prompt% mkdir .i386_linux22/bin
       prompt% mkdir .i386_linux22/lib
       prompt% mkdir .sun4x_58
       prompt% mkdir .sun4x_58/bin
       prompt% mkdir .sun4x_58/lib
       prompt% mkdir etc
       prompt% mkdir include
       prompt% mkdir share
       prompt% mkdir var

and then make the symbolic links

         prompt% ln -s @sys/bin bin 
	 prompt% ln -s @sys/lib lib

And put in your ~/.profile file

       if test -d /afs/rhic/brahms/user/${USER}/bin ; then 
          export PATH=/afs/rhic/brahms/user/${USER}/bin:${PATH}
       fi

This has the advantage that AFS takes care of all the arcitecture dependent stuff, and you only have one installation of the archicture inpdentent stuff. The down side is that you're using AFS.

Please do not reset the PATH in you're ~/.profile script. Always append.

to the BRAHMS Private Page