SLAC PEP-II
BABAR
SLAC<->RAL
Babar logo
HEPIC E,S & H Databases PDG HEP preprints
Organization Detector Computing Physics Documentation
Personnel Glossary Sitemap Search Hypernews
Unwrap page!
Comp. Search
Who's who?
Meetings
FAQ Homepage
Archive
Environment
Administration
New User Info.
Web Info/Tools
Monitoring
Training
Tools & Utils
Programming
C++ Standard
SRT, AFS, CVS
QA and QC
Remedy
Histogramming
Operations
PromptReco
Simulation Production
Online SW
Dataflow
Detector Control
Evt Processing
Run Control
Calibration
Databases
Offline
Workbook
Coding Standards
Simulation
Reconstruction
Prompt Reco.
BaBar Grid
Data Distribution
Beta & BetaTools
Kanga & Root
Analysis Tools
RooFit Toolkit
Data Management
Data Quality
Event display
Event Browser
Code releases
Databases
Check this page for HTML 4.01 Transitional compliance with the
W3C Validator
(More checks...)

FAQ Answerpage


QUESTION:
Setting up your PATH

ANSWER:

Setting up your PATH

The PATH environment variable controls where commands are found by the Unix shell. Its important that it be set to use SoftRelTools commands that are consistent with the test release you are working in.

The original way to do this was to use the BFCURRENT environment variable and/or a ~/BFCURRENT file, which the SRTstartup.csh script would use to manipulate the PATH variable. This still works, but is somewhat unwieldy:

  • Make sure the BFCURRENT environment variable is set to the name of the production release you are using (e.g. "current" or "2.4.1")
  • Use the command:

    source ~/SRTstartup.csh

    assuming you have copied SRTstartup.csh to your home directory so it can be found easily. You may also be able to locate it at $BFDIST/releases/current/SoftRelTools/Srtstartup.csh

Many, but not all sites, have an srtpath alias defined to do this. If your site is one of them,to set your PATH, you can use the command:

srtpath 2.4.1 $BFARCH

(NOTE: The $BFARCH is there because srtpath can also set the architecture in use, for example if you want to specify if you're using the native compiler instead of g++).

Its important that either SRTstartup.csh or srtpath be used to configure the PATH every time you start to use a test release. Relying on SRTstartup.csh setting the path to the "current" release is not a reliable solution.

(Last updated 10/8/98)


[ SLAC Homepage]  [Search] [FAQ Homepage]
If you have a FAQ (with or WITHOUT an answer), use our prototype submission form.
If you have comments or suggestions, email me at sison@slac.stanford.edu