Newsgroups: comp.parallel.mpi
From: Martin Rysanek <rysanek@dcse.fee.vutbr.cz>
Subject: Re: Problems with LAM
Organization: FEECS, TU Brno, Czech Rep.
Date: Fri, 19 May 1995 12:31:39 +0200
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-ID: <Pine.SV4.3.91.950519122321.19918A-100000@kazi.dcse.fee.vutbr.cz>

On 15 May 1995, Raja B Daoud wrote:

> Cheshire Cat <koonmeng@nsrc.nus.sg> wrote:
> >I have 2 hosts in my lamhosts file, and when I type 'recon -v lamhosts', it
> >always fails to start up anything else but n0 (node0).
>
> LAM uses rsh to start up lamd on remote nodes.  The "recon" tool is there
> to check that the account(s), shell startup file (.cshrc or .profile),
> shell search paths, and the LAM installation are properly setup before
> running "lamboot".
>
> Check the recon(1) man page for the required conditions.  In addition,
> you can do a quick test by typing, from "host1":
>
> % rsh host2 tkill -N
>

The guys of Lam assume that your .profile simply defines PATH for
your executable files and LAM Shell variables. They execute .profile
during remote shell command. I had almost the same problem, so I changed
inetexec.c file and now, it works fine.

Check line in the file "inetexec.c" with ".profile" string and change
it to ".pathdef" file. Create in your home directory ".pathdef" file
and put in definition of shell variable PATH and TROLLIUSHOME. Recompile
LAM and I belive that your problem will be solved.

Regards

Martin Rysanek

-----------------------------------------------------------------------------
Martin Rysanek                               E-mail:rysanek@dcse.fee.vutbr.cz
Technical University of Brno, FEI VUT Brno      Tel:    (+42-5)      7275-280
Dept. of Computing Science and Engineering              (+42-5)      7275-111
Bozetechova 2, Brno 612 66, Czech Republic      Fax:    (+42-5)   41 21 11 41
-----------------------------------------------------------------------------


