On Tue, 13 Apr 2004, Bernard Li wrote:
> There is a flag for compiling LAM to use ssh instead of rsh - but if you
> do not want to re-compile at all, exporting the following variable will
> make LAM use ssh instead of rsh:
>
> LAMRSH=ssh
Sorry for the late reply.
Bernard is exactly right. The OSCAR-ized LAM RPM's used a configure
switch to tell LAM to default to SSH (since OSCAR does not, by default,
install rsh services on the cluster -- which is why you're having
problems). You can configure LAM 6.5.x the same way (it's been quite a
while, but I think the flag in the 6.5 series was "--with-rsh=ssh"; use
"./configure --help" to look up the specific name).
Alternatively, you can set the environment variable LAMRSH to "ssh" (as
Bernard suggests) before you run lamboot, and LAM will use "ssh" instead.
If you go this route, you might want to add "setenv LAMRSH ssh" in your
LAM 6.5.4 switcher module so that that environment variable will
automatically be set if someone selects to use that particular version of
LAM.
Either approach is fine -- they're actually just about equivalent.
Hope this helps.
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Oscar-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-users
