LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2005-12-09 18:37:54


On Dec 9, 2005, at 9:33 AM, Sebastian wrote:

> our cluster is running with the very old LAM-Version 6.5.9. Because we
> implement the Sun Grid Engine as Batch Queuing System, we will
> update our
> LAM-Version to 7.0.6.
>
> Because the jobs must run all the time, the Version 6.5.9 must
> actually run
> beside the Version 7.0.6, because we will make some tests bevor
> moving all
> nodes to this version and the SGE.

That should be no problem -- as long as they are installed in
different directories, you should be fine. For example:

/opt/lam-6.5.9
/opt/lam-7.0.6

Then, I think as you noticed, you set your PATH in your .bashrc (or
whatever shell startup file you need) to point to the one that you
want to use.

Also note that LAM 7.1.2b29 has the necessary machinery in it so that
you don't need to patch for SGE (they previously had you patch hboot.c).

> Now i have some problems with the SGE and LAM. I just made a
> local .bashrc
> file for the two nodes where we test the new version and rewrite
> all to the LAM 7.0.6 version.
>
> Now my questin is, which variables beside $PATH i have to set that
> only the LAM-Version 7.0.6 is taken.

PATH should be sufficient.

> I think actually i have some problems with different versions used
> when
> booting or something like that, are there any really important
> variables to set or other things to be done?

Nope -- PATH should be fine. You could try something simplistic like
the following. In your .bashrc, have a line like this:

-----
if test -f $HOME/.current-lam -a "`cat $HOME/.current-lam`" =
"6.5.9"; then
   LAM_PATH=/opt/lam-6.5.9/bin
else
   LAM_PATH=/opt/lam-7.0.6/bin
fi
export PATH=${LAM_PATH}:$PATH
-----

Then have a .current-lam text file in your $HOME that either contains
"6.5.9" or "7.0.6". Then, when you login, the right PATH should be
set and you should be good to go.

This is one trivial example -- an infinite number of variations are
possible on this theme.

Be sure that other entities are not putting LAM in your PATH
somewhere for you -- and if they are, ensure that you are the last
one to prefix your path with the version of LAM that you want. That
is: all that matter is where "lamboot" (and friends) are found. So
if LAM is in your PATH multiple times, while that is certainly not
optimal, what really matters is the left-most entry for LAM in your
PATH (because that's where lamboot and friends will be found).

Does that help?

--
{+} Jeff Squyres
{+} The Open MPI Project
{+} http://www.open-mpi.org/