Another, perhaps better way is to do the following
setenv GLOBUS_LOCATION \
/afs/slac.stanford.edu/package/globustools/vdtclient/curr/globus
source $GLOBUS_LOCATION/etc/globus-user-env.csh
This will only give you gloubs, which might be enough for now. Let me
know if this work for you.
(Are we abusing this PLANNING list? should this thread be move to
Hypernews?)
Wei Yang | [log in to unmask] | 650-926-3338(O)
Stephen J. Gowdy wrote:
> Hmm, after I add this to the ATLAS login the environemtn variable
> LD_LIBRARY_PATH gets too long. If I add "set verbose=1" to my .cshrc I see
> the last thing done is;
>
> if ( $?PATH ) then
> setenv PATH
> /afs/slac.stanford.edu/package/globustools/vdtclient/v1.3.9/netlogger/bin:${PATH}
> else
> if ( $?LD_LIBRARY_PATH ) then
> setenv LD_LIBRARY_PATH
> /afs/slac.stanford.edu/package/globustools/vdtclient/v1.3.9/netlogger/lib:${LD_LIBRARY_PATH}
> Word too long.
> [yakut06] ~ >
>
> and LD_LIBRARY_PATH is almost 4k;
>
> [yakut06] ~ > echo $LD_LIBRARY_PATH | wc
> echo $LD_LIBRARY_PATH | wc
> 1 1 4082
>
> A lot of this is ATLAS-added stuff as they seem to do the same thing with
> adding a bazillion directories to the PATH-type environemtn variables.
>
> I'm not sure if it will be possible to have ATLAS somehow fix that but I
> will ask. Is there a way for the globus setup to use fewer directories?
> (BaBar creates symlinks in a specific directory to get around this type of
> problem).
