Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
2- ./configure ¡Vwith-comm=shared --prefix=/usr/local
4- make install
in the 5th step error was
Errors while trying to run rsh 192.168.0.25 ¡Vn /bin/ls /usr/local/mpich/mpich-184.108.40.206/mpichfoo unexpected response from 192.168.0.25
ƒÞ > /bin/ls: /usr/local/mpich/mpich-220.127.116.11/mpichfoo:
ƒÞ no such file or directory
The ls test failed on some machines.
This usually means that u donot have a common filesystem on all of the machines in your machines list; MPICH requires this for mpirun (it is possible to handle this in a procgroup file; see the¡K¡K)
Other possible problems include:-
The remote shell command rsh doesnot allow you to run ls.
See the doc abt remote shell & rhosts
You have common filesystem, but with inconsistent names
See the doc on the automounter fix
1 error were encountered while testing the machines list for LINUX
only these machines seem to be available
now since this is only a two node cluster host1 is the server on to which MPICH is being installed. & 192.168.0.25 is the client¡K..
rsh on both nodes is logging freely¡K¡K.
On the server side the file ¡§ machines.LINUX ¡§ contains