Ewan MacMahon wrote:
>> -----Original Message-----
>> From: Testbed Support for GridPP member institutes [mailto:TB-
>> [log in to unmask]] On Behalf Of Alastair Dewhurst
> <massive snip>
>> Hope this helps, thanks for the responses so far.
> It does, rather a lot I think. So, just to pin down some
> details, for a current/new type cvmfs setup one needs:
> - to set VO_ATLAS_SW_DIR to /cvmfs/atlas.cern.ch,
> - set a new variable ATLAS_LOCAL_AREA to point to a directory
> that contains a (preferably atlassgm writeable) file called
> setup.sh and also a setup.sh.local (both of while can presumably
> be copied from the current software area),
> - add:
> to the setup.sh.local
1) to set VO_ATLAS_SW_DIR to /cvmfs/atlas.cern.ch. This is /cvmfs/atlas.cern.ch/repo/sw in the new setup
2) ATLAS_POOLCOND_PATH is setup by atlas not by the site it might have
been different in earlier releases but once you source the setup.sh from
cvmfs it will set it up pointing to it. At this point Alessandro had to
do some magic when I installed cvmfs in Manchester.
3)ATLAS_LOCAL_AREA "preferably atlassgm writeable". It has to be
writable by atlas SGM as it put in there libraries and a minimal local
I'd suggest you to wait for the new version to come out and be settled.
At the moment there is a mixture of suggestions from people who have
different setups and things are going to change again. I have the most
recent setup but few things I had to do by hand (delete few files and
links) are now done by the rpm and the machines at cern will change name
and path in few weeks which means change the configuration on all WNs.