mirror of https://github.com/tLDP/LDP
*** empty log message ***
This commit is contained in:
parent
7865741427
commit
2498b12b7a
|
@ -193,7 +193,8 @@
|
|||
to communicate between nodes. Here is a rule: If the manual tells you to
|
||||
do something, DO IT! The lam manual also tells you to run as a non-root
|
||||
user. Make the same user for every box. Build every box on the cluster
|
||||
with the same user “wolf” with the same password.</para>
|
||||
with that same user and password. I named that non root user "wolf".
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Hosts</title>
|
||||
|
@ -286,20 +287,14 @@ cat >> exports
|
|||
<para>Make sure that services we want are up:</para>
|
||||
|
||||
<screen>chkconfig -add sshd
|
||||
chkconfig -add telnet
|
||||
chkconfig -add nfs
|
||||
chkconfig -add rexec
|
||||
chkconfig -add rlogin
|
||||
chkconfig -level 3 rsh on
|
||||
chkconfig -level 3 telnet on
|
||||
chkconfig -level 3 nfs on
|
||||
chkconfig -level 3 rexec on
|
||||
chkconfig -level 3 rlogin on</screen>
|
||||
|
||||
<para>Telnet? I added this just as a convenience. It is not needed but
|
||||
it is nice to have while debugging nfs. How are you going to log into a
|
||||
box if you can’t ssh to the box?</para>
|
||||
|
||||
<para>…And, during startup, I saw some services that I know I don’t
|
||||
want, and in my opinion, could be removed. You may add or remove others
|
||||
that suit your needs; just include the ones shown above.</para>
|
||||
|
@ -380,7 +375,7 @@ ssh-agent sh -c ‘ssh-add && bash’</screen>
|
|||
describe that; I just got the source and followed the directions, and in
|
||||
another experiment I installed their rpm. Both of them worked fine.
|
||||
Remember the whole reason we are doing this is to learn; go forth and
|
||||
learn. </para>
|
||||
learn.</para>
|
||||
|
||||
<para>You may also read more documentation regarding LAM and other
|
||||
message passing interface software <ulink
|
||||
|
@ -392,7 +387,7 @@ ssh-agent sh -c ‘ssh-add && bash’</screen>
|
|||
<title>Set Up Slave Nodes</title>
|
||||
|
||||
<para>Get your network cables out. Install Linux on the first non-head
|
||||
node.</para>
|
||||
node. Follow these steps for each non-head node.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Base Linux Install</title>
|
||||
|
@ -574,15 +569,16 @@ Added linux * </screen>
|
|||
<para>All done! You are almost ready to start wolfing.</para>
|
||||
|
||||
<para>Reboot your boxes. Did they all come up? Can you ping the head node
|
||||
from each box? Can you ping each node from the head node? Can you telnet?
|
||||
Can you ssh? Don’t worry about doing ssh as root; only as wolf.</para>
|
||||
from each box? Can you ping each node from the head node? Can you ssh?
|
||||
Don’t worry about doing ssh as root; only as wolf. Also only worry about
|
||||
ssh from the head to the slave, not the other way around.</para>
|
||||
|
||||
<para>If you are logged in as wolf, and ssh to a box, does it go
|
||||
automatically, without prompting for password?</para>
|
||||
|
||||
<para>After the node boots up, log in as wolf, and say “mount”. Does it
|
||||
show wolf00:/mnt/wolf mounted? On the head node, copy a file into
|
||||
/mnt/wolf. Can you read and write that file from the node box?</para>
|
||||
/mnt/wolf. Can you read and write that file from the slave node?</para>
|
||||
|
||||
<para>This is really not required; it is merely convenient to have a
|
||||
common directory reside on the head node. With a common shared directory,
|
||||
|
|
Loading…
Reference in New Issue