hi,
i am using mandrke10.0 + KDE.

i have linux cluster programing now.

i am using lam/mpi packages.

i have one doubt.

i had one hostfile


10.255.240.101
10.255.240.103
~
~



when i run a command like this (below) see the error ..!!

due to permission denied now how to set a anonymous login to remote host??







[staff@localhost staff]$ lamboot -v hostfile

LAM 7.0.6/MPI 2 C++/ROMIO - Indiana University

n-1<7147> ssi:boot:base:linear: booting n0 (10.255.240.101)
n-1<7147> ssi:boot:base:linear: booting n1 (10.255.240.103)
-----------------------------------------------------------------------------
LAM failed to execute a process on the remote node "10.255.240.103".
LAM was not trying to invoke any LAM-specific commands yet -- we were
simply trying to determine what shell was being used on the remote
host.

LAM tried to use the remote agent command "rsh"
to invoke "echo $SHELL" on the remote node.

This usually indicates an authentication problem with the remote
agent, or some other configuration type of error in your .cshrc or
.profile file. The following is a list of items that you may wish to
check on the remote node:

- You have an account and can login to the remote machine
- Incorrect permissions on your home directory (should
probably be 0755)
- Incorrect permissions on your $HOME/.rhosts file (if you are
using rsh -- they should probably be 0644)
- You have an entry in the remote $HOME/.rhosts file (if you
are using rsh) for the machine and username that you are
running from
- Your .cshrc/.profile must not print anything out to the
standard error
- Your .cshrc/.profile should set a correct TERM type
- Your .cshrc/.profile should set the SHELL environment
variable to your default shell

Try invoking the following command at the unix command line:

rsh 10.255.240.103 -n echo $SHELL

You will need to configure your local setup such that you will *not*
be prompted for a password to invoke this command on the remote node.
No output should be printed from the remote node before the output of
the command is displayed.

When you can get this command to execute successfully by hand, LAM
will probably be able to function properly.
-----------------------------------------------------------------------------
n-1<7147> ssi:boot:base:linear: Failed to boot n1 (10.255.240.103)
n-1<7147> ssi:boot:base:linear: aborted!
-----------------------------------------------------------------------------
lamboot encountered some error (see above) during the boot process,
and will now attempt to kill all nodes that it was previously able to
boot (if any).

Please wait for LAM to finish; if you interrupt this process, you may
have LAM daemons still running on remote nodes.
-----------------------------------------------------------------------------
n-1<7152> ssi:boot:base:linear: booting n0 (10.255.240.101)
n-1<7152> ssi:boot:base:linear: booting n1 (10.255.240.103)
-----------------------------------------------------------------------------
LAM failed to execute a process on the remote node "10.255.240.103".
LAM was not trying to invoke any LAM-specific commands yet -- we were
simply trying to determine what shell was being used on the remote
host.

LAM tried to use the remote agent command "rsh"
to invoke "echo $SHELL" on the remote node.

This usually indicates an authentication problem with the remote
agent, or some other configuration type of error in your .cshrc or
.profile file. The following is a list of items that you may wish to
check on the remote node:

- You have an account and can login to the remote machine
- Incorrect permissions on your home directory (should
probably be 0755)
- Incorrect permissions on your $HOME/.rhosts file (if you are
using rsh -- they should probably be 0644)
- You have an entry in the remote $HOME/.rhosts file (if you
are using rsh) for the machine and username that you are
running from
- Your .cshrc/.profile must not print anything out to the
standard error
- Your .cshrc/.profile should set a correct TERM type
- Your .cshrc/.profile should set the SHELL environment
variable to your default shell

Try invoking the following command at the unix command line:

rsh 10.255.240.103 -n echo $SHELL

You will need to configure your local setup such that you will *not*
be prompted for a password to invoke this command on the remote node.
No output should be printed from the remote node before the output of
the command is displayed.

When you can get this command to execute successfully by hand, LAM
will probably be able to function properly.
-----------------------------------------------------------------------------
n-1<7152> ssi:boot:base:linear: Failed to boot n1 (10.255.240.103)
n-1<7152> ssi:boot:base:linear: aborted!
lamboot did NOT complete successfully
[staff@localhost staff]$



can i have more help?

You'll need to set up passwordless RSH (via a hosts.equiv file) or SSH (via shared keys, see the ssh-keygen man page for more details) to allow paswordless login across your cluster. If you're going to use SSH instead of RSH, you'll probably need to set something in your configuration/environment to tell LAM about it, since it uses RSH by default.

Would be nice if told how to use hosts.equiv to get passwordless rsh