Bernie,
There are problems with trying to run on a system with multiple versions
of LAM installed. The key seems to be to define the PATH environment
variable dynamically and differently for the different runtime
environments. I've observed the following behavior. After executing:
cd /usr/local/lam7.1/bin
./lamboot
I found that the 7.0 version of lamd was actually booted because the
directory containing the 7.0 version of lam appeared in the PATH and
that's where hboot came from when the 7.1 version of lam called hboot.
Use of modules is one strategy to configure the environment so that the
PATH !!!!ONLY!!!! points to the version of LAM that you want to use.
Otherwise, it gets real tricky...
John Bussoletti
-----Original Message-----
From: Borenstein, Bernard S
Sent: Monday, February 28, 2005 4:37 PM
To: lam_at_[hidden]
Subject: LAM: linux cluster with both 32 and 64 bit nodes
We have an unusual situation with our updated cluster. We have both 32
bit and 64 bit nodes. But here is what we want to do :
1) Run old 32 bit programs on our new 64 bit nodes (Suse linux 9.1)
2) Run old 32 bit program on our old 32 bit nodes
3) Run recompiled 64 bit programs on our new 64 bit nodes.
We use OpenPBS and our admin has defined an os64 queue for the 64 bit
nodes. The problem we're having is how to define in the users
.bashrc or .cshrc the correct LAM path. We have tried setting the
LAMHOME environment variable in the PBS submit script, but the .bashrc
or
.cshrc don't seem to see the value (its blank). We need to add the
correct LAM to the path so lamboot can find all required routines (like
hboot) and
if we are running 32 bit executables on the 64 bit nodes, we need to add
the 32 bit lam to the path, not the 64 bit lam.
I'm hoping someone here has run into this and can give me some ideas
about how to solve this.
Thanx,
Bernie Borenstein
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|
