Hallo Torsten,
> Installing a EMI-2 WN with these variables in site-info.def
>
> [root@wn160 yaim_files]# grep ATLAS site-info.def
> ATLASSGM_Q_GROUP_ENABLE="atlas"
> ATLASPRD_Q_GROUP_ENABLE="atlas"
> ATLASANL_Q_GROUP_ENABLE="atlas"
> ATLASMPI_Q_GROUP_ENABLE="atlas"
> VO_ATLAS_VOMS_SERVERS="'vomss://voms.cern.ch:8443/voms/atlas?/atlas/'"
> VO_ATLAS_QUEUES="atlasprd.q atlasanl.q atlassgm.q atlasmpi.q"
> VO_ATLAS_SW_DIR=/cvmfs/atlas.cern.ch/repo/sw
> ATLAS_LOCAL_AREA=/gridsoft/atlas-cvmfs/local
> VO_ATLAS_DEFAULT_SE=$SE_HOST
>
> [...]
>
> But
>
> [atlasprd001@wn160 ~]$ printenv | grep VO_
> [atlasprd001@wn160 ~]$ printenv | grep LCG_
> LCG_LOCATION=/usr
>
>
> I assume VO_ATLAS_SW_DIR is still supported, but it's not set in the
> environment after installing. Or do we need to change to this vo.d structure?
You can still set all of that in site-info.def as before.
I hope you did _not_ run a specific function as the last step?
That can easily lead to an incomplete environment.
Only with the "-c" option YAIM is guaranteed to do a complete job.
(With the "-r" option one would always need to add "-f config_lcgenv"
at the end of the command line, i.e. as an extra function to be run.)
You can run yaim with debug arguments "-d N" with N ranging from 1 up to 7,
until you see what is going wrong...
|