Our scripts insert the line
export PATH=/path/to/64/bins:$PATH
before we do anything else. If the node finds a 64-bit bin, then it runs
it, if not then it uses the 32-bit bins. Our PHP front end creates the
scripts that are submitted to SLURM so we updated our scripts when we
updated our cluster. The thing to watch out for is if you have a mix
then this fails (don't know why you would do this). Our master node is
running 32-bit, all the worker nodes are 64-bit, but the master never
runs jobs.
Robert LeBlanc
On Mon, 2005-02-28 at 17:45 -0700, Borenstein, Bernard S wrote:
> 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/
>
>
--
Robert LeBlanc
BioAg Computer Support
Brigham Young University
|
