|
Frequently
Encountered Problems and Solutions to Them
P:
When I log into cmsuaf.fnal.gov or cmslpc.fnal.gov I cannot write to the files in my afs area.
A: Afs authentication at login has been turned off because home directories are no longer on afs. You need to run aklog in order to get your afs tokens before you try to write in your afshome area.
P:
When I log into cmslpc.fnal.gov running "scramv1 project" produces error about missing modules.
A: The default .cshrc and .bashrc sets up UPS. This causes the wrong version of perl to appear in the path. To fix this remove or comment out the following UPS setup section of your .cshrc or .bashrc
if ( -f "/afs/fnal.gov/ups/etc/setups.csh" ) then
source "/afs/fnal.gov/ups/etc/setups.csh"
endif
if ( { ups exist shrc } ) then
setup shrc
endif
P:
When I run kinit on the UAF my password appears on the screen!!!
A: The default login scripts on UAF cause /usr/java/jdk1.5.0_06/bin to appear before /usr/krb5/bin in the path. The kinit in the java package echos the characters as you type your password. To fix this put this in your login script:
alias kinit "/usr/krb5/bin/kinit"
P:
Every now and then commands like ls and less respond very slowly after setting the environment with eval `scram runtime -csh`.
A: When you setup CMS software runtime enviornment with scram, the
LD_LIBRARY_PATH is increased and performance is adversely affected.
A temporary solution for this issue is:
For sh-like syntax:
export LD_LIBRARY_PATH=/lib:/usr/lib:${LD_LIBRARY_PATH:-}
For csh-like syntax: (most UAF users want this)
if ((${?LD_LIBRARY_PATH})) then
setenv LD_LIBRARY_PATH /lib:/usr/lib:${LD_LIBRARY_PATH}
else
setenv LD_LIBRARY_PATH /lib:/usr/lib
endif
P:
Every now and then my terminal gets screwed up and it is impossible
to work on it.
A:
Probably the window was resized. Try issuing the :
eval resize or just resize command.
P:
When I try to execute xterm to create an additional terminal
the screen
pops up but dies right away, what's
going on?
A:
The problem is that by default xterm tries to run through
the login procedure on the woker node that you
are at. Since
we disabled
direct logins this will fail. To prevent this specify the
shell you want to execute e.g. xterm
-e /bin/tcsh then
the xterm
should start correctly provided your display settings etc.
are set correctly.
We plan to set an alias for the xterm command so in the future
one can just type xterm.
|
