Newsgroups: comp.parallel.mpi
From: rdab100@hermes.cam.ac.uk
Subject: Re: LAM MPI & Linux Install problem - Please help.
Organization: University of Cambridge, England
Date: Mon, 27 Jul 1998 09:23:31 +0100
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <35BC3902.8FE7C8DF@hermes.cam.ac.uk>

Raja Daoud wrote:

> Dominic Baines  <rdab100@NOSPAM.hermes.cam.ac.uk> wrote:
> >export PATH=$PATH:/data/LAM/lam61/bin
> >this exists in the users .bash_profile
>
> >recon: testing n1 (kirk.domscluster)
> >bash: tkill: command not found
>
> I don't know bash, you probably need to put the PATH setting above in
> the .bashrc file.  Check the bash manpage for which of these startup
> files is auto-executed in non-interactive logins (e.g  rsh).  You need
> to be able to do "rsh kirk tkill -h" (or other LAM commands) and see
> the help menu printed.

I've put it in both .bash_profile and .bashrc but I err'd on the syntax in
.bashrcand forgot the $ !!! oops. Now it works.... yippeeeeee .......

> BTW, out of safety, you may want to use an account other than root,
> either your own account, or create another for MPI applications.
> Regards,

> --Raja
>
> -=-
> Raja Daoud                              Hewlett-Packard Co.
> raja@rsn.hp.com                         http://www.hp.com/go/mpi

  I wasn't thinking too straight when I started doing this but realised
that LAMhas to run as rdab100 accross the cluster after setting up nfs and
rsh. Thanks for
the advice. Would it make any difference if I chmod and chgrp,chown all
LAM's file to rdab100/users ? They are currently all root/root 755 (or
644)

Don't suppose there is an X windows monitor that you know of that I could
run to
keep track of how all the CPU's are doing under MPI would you ?

Thanks for the help.

Dominic