On Jan 4, 2006, at 5:28 PM, Sebastian wrote:
> I already have made the integration and it works finde, in a
> bash-environment, where only one LAM-Version runs, 7.0.6 with SGE.
>
> But this is just a test environment, we use the csh-Shell where
> alreay a
> LAM-Version is defined, 6.5.9.
>
> Because the old version is needed for some programs, we can change the
> global environment-variables LAMHOME.
>
> Now i thougt, i make a wrapper which sets the environment on each
> node to
> the right PATH and LAMHOME variable.
>
> For this i must know what happens after/when lamboot is submitted.
>
> Does lamboot start on each node a rsh-session and start then hboot?
Yes. Specifically (in the rsh case), lamboot invokes a command
something like:
rsh <otherhost> hboot ...and a bunch of parameters...
> Where should i put a wrapper that it works efficient and it is simple?
It might be easier just to change your path on all the nodes in
question. There are many ways to do this. For example, if you have
a networked filesystem with a common $HOME, you can add some logic to
your .cshrc, perhaps something like this:
if (-f $HOME/.which_lam_to_use) then
source $HOME/.which_lam_to_use
fi
And you can selectively write out the contents of
$HOME/.which_lam_to_use something like:
set path = (/path/to/desired/lam $path)
That way, you don't have to mess with LAMHOME at all (I would advise
leaving LAMHOME unset) and you don't have to muck around with the
internals of lamboot.
Would that work for you?
--
{+} Jeff Squyres
{+} The Open MPI Project
{+} http://www.open-mpi.org/
|
