|
This page describes how to configure the DFOS login
rc files in a standardised way. A script is provided which automatically
creates all the required files and fills them with the default content, and
prompts you to edit them with new content.
Although intended for use on "empty accounts", it could as well be
used to "standardise" existing accounts. Exisiting versions of files needing
to be created newly are renamed, not deleted.
The standardised DFOS login relies on bash, the VLTSW standard PECS
and then on .qcrc and .dfosrc files.
Installation of PECS provides a .bashrc file, a .profile file and a
.pecs directory filled with several further PECS files... Insure that no
.bash_profile exists otherwise this will be sourced and the .profile file
will NOT be sourced.
From the bash man page:
When bash is invoked as an interactive login shell, or as a non-inter-
active shell with the --login option, it first reads and executes com-
mands from the file /etc/profile, if that file exists. After reading
that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.pro-
file, in that order, and reads and executes commands from the first
one that exists and is readable. The --noprofile option may be used
when the shell is started to inhibit this behavior.
So once correctly set up, the following sequence of files are sourced:
- /etc/profile (if it exists)
- ${HOME}/.profile
- ${HOME}/.bashrc (sourced by ${HOME}/.profile)
- ${HOME}/.pecs/apps-all.env
- ${HOME}/.pecs/misc-all.env
- ${HOME}/.qcrc (sourced by misc-all.env)
- ${HOME}/.dfosrc (sourced by .qcrc)
- ${HOME}/.pecs/misc-all.ali
When Condor is used for pipeline processing, it does not do a full
login, but starts only at .qcrc, therefore only the definitions in .qcrc and
.dfosrc are available to Condor run processes, therefore the .pecs files
should be essentially empty unless there is stuff you want defined for
interactive sessions but not for Condor sessions.
Note though that processAB when called from Condor does source .bashrc,
which thus sources your .pecs files.
- setup.newQC.Account: Download, set executable
permissions (chmod u+rx setup.newQC.Account) and then execute.
|
