If its RSH problem
these solutions might help you
As root
vi /etc/host.deny
ALL : ALL # which will deny all intruders
vi /etc/host.allow
192.168.0. in.rlogind : 192.168.0. portmap : 192.168.0. sshd : 192.168.0.
ALLOWING RSH/RLOGIN without a password. In order to allow rsh/rlogin
without passwords, we must place the hostnames of all machines which
are to be allowed passwordless access in the
/etc/hosts.equiv
file on the machine(s)) which is allowing such access. If, for
example, we wish to allow unrestricted access between two machines, a
and b, through RSH, we would need to place appropriate
/etc/hosts.equiv files on each machine.
regards,
Adarsh
------------------------------------------------
http://www.adarshpatil.com
On Wed, 3 Nov 2004 15:49:51 -0500 (EST), zli_at_[hidden] <zli_at_[hidden]> wrote:
> Dear folks in lam-mpi society:
> I am Zhiyi Li, a research associate in Virginia Bioinformatics
> Institute in Virginia Tech. I work with staff in VBI and found
> our PBS Linux Cluster has the problem:
> Any one of cluster nodes can not rsh other cluster nodes.
>
> That is the key where lamboot command can not boot cluster nodes for
> lam-mpi runtime system.
>
> If you know the answer how to set up PBS Linux Cluster system
> to make it can rsh communicate between cluster nodes, please
> suggest me.
> Our system brief is like this: two servers: galadriel, lorien,
> 96 cluster nodes:lorien01, lorien02, .....lorien96, all work
> are submitted to PBS queue by PBS scripts. My directory is home/zli
> directory in server node:galadriel.
>
> Sincerely and Best regards
> Zhiyi Li
> Virginia Bioinformatics Institute
> Virginia Tech
> Blacksburg, VT 24060
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
