The message below is of general interest to anyone who takes shifts, maybe not in the details but as an orientation on what to expect for the operator account. ----- Original Message ----- From: Konstantin Olchanski <olchansk@ux1.phy.bnl.gov> To: <brahms-dev-l@bnl.gov> Sent: Tuesday, July 18, 2000 9:38 PM Subject: operator account setup changed! > > > Folks, the operator account setup was changed. The purpose of > the changes is to make the environment as self sufficient as > possible. > > Here is the description of the operator account setup: > > 1) only the "tcsh" shell is supported. All bash related setup files > (.bashrc and the ilk) have been removed. > > 2) .login is an empty file to avoid "login shell vs non-login shell" > unix nonsense. > > 3) all setup is done in .cshrc > > 4) brahms_login.csh is no longer used and has been deleted. Since the > operator account cannot use the standard login file, it is best > to keep everything in one place, so all BRAHMS-specific setups > were moved to .cshrc. > > 5) the BRAHMS setup in .cshrc is as follows: > > - ROOTSYS is set to a local copy of ROOT: $HOME/root. This > is a copy of /opt/brahms/root/pro/linux, with some cleanup > (see my other email). > - BRATSYS and BRATHOME (are these two redundant?) > are set to $HOME/brat, a local checkout copy of BRAT. > - BRAHMS_ARCH is set to: linux > - CVSROOT is set to it's normal place in CVS. > > 6) PATH and LD_LIBRARY_PATH are setup to the "right" places > in ROOTSYS and BRATSYS, plus the additional entries > for ntuple and VertexNtuple. > > These settings make the operator account environment and BRAT/ROOT > applications built in this environment (i.e. BRAHVO) immune to > at least AFS outages. Some more work still needs to be done to make > it immune from pii3 outages. > > > -- > Konstantin Olchanski > Physics Department, Brookhaven National Laboratory, Long Island, New York > olchansk@bnl.gov >
This archive was generated by hypermail 2b29 : Wed Jul 19 2000 - 10:22:07 EDT