Newsgroups: comp.parallel.mpi
From: rdaoud@magnus.acs.ohio-state.edu (Raja B Daoud)
Subject: Re: Problems with LAM
Organization: Ohio Supercomputer Center
Date: 15 May 1995 09:00:15 GMT
Message-ID: <3p756v$52q@charm.magnus.acs.ohio-state.edu>

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

If it doesn't work, the error message will give a good hint about the problem.
The typical problems are:

- you're asked for a password  -> setup a .rhosts file
- can't find "tkill"           -> add the LAM binaries path to shell paths
- "stty" TCGETS error          -> move terminal setting commands to .login

From here we can take this off-line.  Email the LAM team at: lam@tbag.osc.edu

>Also, how do I apply the lam52-patch files?  It's found together with the
>LAM52 source code, but I can't find any patch executable to patch them in.

You can get the "patch" tool from your nearest GNU ftp site.
Once you have it, cd to the LAM main (root) directory and type:

% cat lam52-patch* | patch -p
% make

Regards,

--Raja

-=-
Raja Daoud				raja@tbag.osc.edu
Ohio Supercomputer Center		http://www.osc.edu/lam.html

