Newsgroups: comp.parallel.mpi
From: Nick Nevin <nevin@osc.edu>
Subject: Re: Problems running LAM on AIX 4.1 cluster
Organization: Ohio Supercomputer Center
Date: 24 Jun 1996 08:47:22 -0400
Message-ID: <vn2spblxtb9.fsf@alex.osc.edu>


     > The documentation of LAM says, LAM requires its binaries to be
     > in the PATH when using rsh (since LAM usese rsh to start processes
     > on other machine like ihfibm2 in the given example). So i tried to
     > verify the PATH when using rsh by typing

     > ihfibm7> rsh ihfibm2 echo \$PATH
 
     > machine ihfibm2 responds with

     >   :/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/bin

     > Ok, you might say: "That's the problem, just add your LAM binary
     > path and it will work". That's what i'm thinking, too.
     > But, how can I change the above PATH? rsh invokes my ksh shell
     > without using the PATHS in /etc/environment, /etc/profile,
     > ~/.profile or ~/.kshrc. And i even could'nt find the location
     > where the shown PATH is set.

Since your remote shell is ksh you should set the PATH in ~/.profile.
On booting LAM detects which shell you are using as your remote shell
and acts appropriately. In the case of ksh it sources ~/.profile
remotely. In the case of csh it does nothing special since the remote
shell sources ~/.cshrc itself.

Regards, Nick.

-=-
Nick Nevin				nevin@osc.edu
Ohio Supercomputer Center		http://www.osc.edu/lam.html

