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.
Andreas
--
Andreas Unterkircher
IT Department
Grid Deployment Group
CERN
CH-1211 Geneva 23
On Wed, 22 Aug 2007, Jean-Michel Barbet wrote:
> Hello,
>
> I am looking at the last update of the relocatable distribution for
> glite 3.0 UI and WN (TAR_UI and TAR_WN).
>
> I noticed two problems :
>
> a) Function config_lcgenv faild with messages like :
>
> /usr/remote/public/GLITE-3_0_2-31/WN/glite/yaim/site/../bin/../libexec/configure
> _node: line 44:
> /usr/remote/public/GLITE-3_0_2-31/WN/external/etc/profile.d/lcgenv.sh: No such
> file or directory
>
> I had to create the directories external/ to make it work :
> mkdir -p $INSTALL_ROOT/external/etc/profile.d
>
> b) At the end of the yaim script, the function mktemp failed because
> the filename has only 4 X characters. On my system (SL3.0.2) this
> function works if I give 6 X characters.
> I patched the /opt/glite/yaim/bin/yaim script and it worked.
> diff ../bin/yaim.org ../bin/yaim
> 305c305
> < mytmpfile=`mktemp /tmp/yaimtmp.XXXX`; rm -f ${mytmpfile}
> ---
> > mytmpfile=`mktemp /tmp/yaimtmp.XXXXXX`; rm -f ${mytmpfile}
>
> JM
>
>
>
|