On Tue, 9 Dec 2003, YoungHui Amend wrote:
> I see that lam/mpi is released as a standard library on these machines
> (default setup).
Err, this heavily depends on the Linux distribution that you use...
> When I update my .profile to put my path in front of /usr/bin/, it works
> fine. How else can I get the child processes to find the lam code in my
> path instead of /usr/bin?
You can make the setting system-wide (=for every user) by modifying PATH
in the system-wide profile. For example, if you're using Red Hat or
something similar, you can create /etc/profile.d/lam.sh which contains:
PATH="/the/path/to/your/new/lammpi:${PATH}"
export PATH
Then make sure that /etc/bashrc contains the bit that walks over all
/etc/profile.d content outside of the "if" for interactive sessions,
otherwise you'll get the right PATH when you log with rlogin, but will not
get it when you run something like 'rsh nodexxx uptime'.
Don't forget to create an /etc/profile.d/lam.csh with similar setting for
(t)csh users.
You have to do this on all nodes where the 2 versions coexist.
--
Bogdan Costescu
IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
E-mail: Bogdan.Costescu_at_[hidden]
|
