Andreas Unterkircher wrote:
> Hello Jean-Michel,
>
> the problem with config_lcgenv is a bug in yaim introduced with the
> transition to glite 3.1 and only affecting the 3.0 tarball. To fix it for
> the 3.0 gliteUI_WN* tarball do the following:
>
> In the file $INSTALL_ROOT/glite/yaim/libexec/configure_node remove the
> lines
>
> # We are configuring a tarball
> unset GLITE_EXTERNAL_ROOT
> if ( echo ${node} | egrep -q 'TAR' ) ; then
> export GLITE_EXTERNAL_ROOT="${INSTALL_ROOT}/external"
> fi
>
> Let me know if it works.
> I will fix this for future releases of the 3.0 tarball.
Hello Andreas,
I tried. I still do not have a lcgenv.[sh|csh],
not in INSTALL_ROOT/etc/env.d, neither in INSTALL_ROOT/etc/profile.d.
The configuration procedure config_lcgenv is called and now tries to
write in /etc/profile.d which cannot be written by a the root account
that I use for installing the TAR_* distribs.
I check the YAIM mecanism and found that there are function with the
"_30" suffix to be used with gLite 3.0. For the TAR_UI, the
node-info.d/glite-tar_ui_30 file contains a call to function
config_lcgenv_30 while for TAR_WN, the file node-info.d/glite-tar_wn_30
calls config_lcgenv. I wonder if this could be the cause of the problem.
config_lcgenv uses LCG_ENV_LOC=${GLITE_EXTERNAL_ROOT:-}/etc/profile.d
and I believe GLITE_EXTERNAL_ROOT is not defined in 3.0
config_lcgenv_30 uses LCG_ENV_LOC=${INSTALL_ROOT}/etc/env.d which is
correct.
There may be other function that lack the _30 suffix in
node-info.d/glite-tar_wn_30
JM
--
------------------------------------------------------------------------
Jean-michel BARBET | Tel: +33 (0)2 51 85 84 86
Laboratoire SUBATECH Nantes France | Fax: +33 (0)2 51 85 84 79
CNRS-IN2P3/Ecole des Mines/Universite | E-Mail: [log in to unmask]
------------------------------------------------------------------------
|