X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Finstallation.sgml;h=4fbf7fbd34cb97ed59aba119e1c74f7ef7320277;hb=8e862ce4b386889bc91c34ec788df0bd1a062c6c;hp=280f4cdd977c0e23e47b11034f83b26bfadd407a;hpb=6624dcdf07d628e8d6a16fc6549edf40be25b7b2;p=spider.git diff --git a/sgml/installation.sgml b/sgml/installation.sgml index 280f4cdd..4fbf7fbd 100644 --- a/sgml/installation.sgml +++ b/sgml/installation.sgml @@ -4,10 +4,10 @@ -The DXSpider Installation Manual v1.48 +The DXSpider Installation Manual v1.49 Iain Philipps, G0RDI (g0rdi@77hz.com) and Ian Maude, G0VGS, (ianmaude@btinternet.com) -Version 1.48, July 2001 revision 1.1 +December 2001 revision 1.1 A reference for SysOps of the DXSpider DXCluster program. @@ -41,8 +41,12 @@ Spider required perl 5.004, however it is now STRONGLY recommended that you use at least version 5.005_03 as this is the version being used in the development of Spider. -

In addition to the standard Red Hat distribution you will require the -following modules from ... +

+In addition to the standard Red Hat distribution you will require the +following modules from , please note however that with later versions of perl, some of these +modules may be included with the distribution. Get the modules anyway and try +to install as below. If they complain, they are probably already a part of your +perl distribution.

@@ -50,12 +54,14 @@ following modules from - +

-Copy the CPAN modules listed above to a convenient place on your computer. One good place would be /usr/local/packages, and the instructions which follow will assume that that's where you have put them. +Copy the CPAN modules listed above to a convenient place on your computer. One good +place would be /usr/local/packages, and the instructions which follow will assume that +that's where you have put them.

Log in as 'root', and make sure you're at '/root' before you continue. Here are exactly the commands you must issue next: - @@ -89,8 +95,8 @@ Log in as 'root', and make sure you're at '/root' before you continue. Here are # make install # cd .. # -# tar xvfz /usr/local/packages/Curses-1.05.tar.gz -# cd Curses-1.05 +# tar xvfz /usr/local/packages/Curses-1.06.tar.gz +# cd Curses-1.06 # perl Makefile.PL # make test # make install @@ -105,7 +111,8 @@ Log in as 'root', and make sure you're at '/root' before you continue. Here are

-Do not fall into the trap of thinking they're all the same, just because they nearly are! Pay particular attention to the instructions of IO, above. +Do not fall into the trap of thinking they're all the same, just because they +nearly are! Pay particular attention to the instructions of IO, above. Preparation @@ -122,11 +129,17 @@ the name sysop. You can call it anything you wish. Depending on your security requirements you may wish to use an existing user, however this is your own choice. -

# adduser -m sysop +

+For SUSE distributions, the command would be .. + + +# useradd -m sysop + +

Now set a password for the user ... @@ -150,6 +163,7 @@ permissions. Copy the tarball to /home/sysop and do the following. # groupadd -g 251 spider (or another number) +

If you do not have the command groupadd available to you simply add a line in /etc/group by hand. @@ -157,6 +171,7 @@ add a line in /etc/group by hand. # vi /etc/group (or your favorite editor) +

You also need to add some others to the group, including your own callsign (this will be used as an alias) and root. The finished line in /etc/group should look something like this @@ -206,11 +221,31 @@ $ vi DXVars.pm (or your favourite editor)

Using the distributed DXVars.pm as a a template, set your cluster callsign, -sysop callsign and other user info to suit your own environment. Note that -this a perl file which will be parsed and executed as part of the cluster. If -you get it wrong then perl will complain when you start the cluster process. -It is important only to alter the text of any section. Some of the lines look -a little odd. Take this line for example .... +sysop callsign and other user info to suit your own environment. + + +$mycall = "GB7DJK"; + + +

+This is the call sign of your cluster. If you use an SSID then include it here +also. + + +$myalias = "G1TLH"; + + +

+This is the sysop user callsign, normally your own. + +

+PLEASE USE CAPITAL LETTERS FOR CALLSIGNS + +

+Note that this a perl file which will be parsed and executed as part of the +cluster. If you get it wrong then perl will complain when you start the cluster +process. It is important only to alter the text of any section. Some of the +lines look a little odd. Take this line for example .... $myemail = "ianmaude\@btinternet.com"; @@ -220,8 +255,6 @@ $myemail = "ianmaude\@btinternet.com"; There appears to be an extra slash in there. However this has to be there for the file to work so leave it in. -

PLEASE USE CAPITAL LETTERS FOR CALLSIGNS -

DON'T alter any file in /spider/perl, they are overwritten with every release. Any files or commands you place in /spider/local or /spider/local_cmd @@ -243,6 +276,18 @@ the sysop. $ ./create_sysop.pl +The client program + +

+In earlier versions of Spider, all the processes were Perl scripts. This +was fine but with a lot of users your computer memory would soon be used up. +To combat this a new client was written in "C". This client only works for +incoming connects at the moment. Before you can use it though it +has to be "made". CD to /spider/src and type make. You +should see the output on your screen and hopefully now have a small C program +called client. Leave it in this directory. + + Starting up for the first time

@@ -280,6 +325,7 @@ was set as GB7MBC. You should therefore see this when you login .... G0VGS de GB7MBC 19-Nov-1999 2150Z > +

If you do, congratulations! If not, look over the instructions again, you have probably missed something out. You can shut spider down again with the command .... @@ -291,17 +337,6 @@ shutdown

and both the cluster and the client should return to Linux prompts. -The Client program - -

-In earlier versions of Spider, all the processes were Perl scripts. This -was fine but with a lot of users your computer memory would soon be used up. -To combat this a new client was written in "C". This client only works for -incoming connects at the moment. Before you can use it though it -has to be "made". CD to /spider/src and type make. You -should see the output on your screen and hopefully now have a small C program -called client. Leave it in this directory. - Linux quick installation guide @@ -332,6 +367,7 @@ is the user that should be doing that process. ./cluster.pl (sysop) +

Spider should now be running and you should be able to login using the client program. @@ -343,6 +379,7 @@ client program. killall -HUP inetd (root) +

Spider should now be able to accept logins via telnet, netrom and ax25. @@ -371,12 +408,14 @@ each interface that you wish to allow connections on, use the following format . default * * * * * * - sysop /spider/src/client client %u ax25 +

or, if you wish your users to be able to use SSID's on their callsigns .. default * * * * * * - sysop /spider/src/client client %s ax25 +

For most purposes this is not desirable. The only time you probably will need this is when you need to allow other cluster nodes that are using SSID's in. In this case it would probably be better to use the first example and @@ -402,6 +441,7 @@ in /etc/services to allow connections to a port number, like this .... spdlogin 8000/tcp # spider anonymous login port +

Then add a line in /etc/inetd.conf like this .... @@ -415,14 +455,15 @@ Once this is done, you need to restart inetd like this .... killall -HUP inetd - -

Now login as sysop and cd spider/src. You can test that spider +

+Now login as sysop and cd spider/src. You can test that spider is accepting telnet logins by issuing the following command .... ./client login telnet +

You should get a login prompt and on issuing a callsign, you will be given access to the cluster. Note, you will not get a password login. There seems no good reason for a password prompt to be given so it is not asked for. @@ -636,7 +677,7 @@ or symbols:- connects to GB7DJK-1 [instead of a script called gb7djk-1]). - +

There are many possible ways to configure the script but here are three examples, one for a NETRom/AX25 connect, one for AGW engines and one for tcp/ip. @@ -695,6 +736,7 @@ connection to GB7DJK-1 started G0VGS de GB7MBC 13-Dec-1998 2043Z > +

This will start a connection using the script called gb7djk-1. You can follow the connection by watching the term or console from where you started cluster.pl. From version 1.47 onwards, you will need to set/debug connect first. @@ -787,6 +829,7 @@ connect telnet mary.lancs.ac.uk 'connect' '' +

So, the first connection is made by Spider. This is fine as Spider uses the Net_Telnet script from within perl. This actually uses TCP rather than TELNET so no negotiation will be done on the first connection. Once connected to @@ -826,7 +869,7 @@ This line works fine for RedHat distributions. It is also fine for SuSE up to DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 - +

The line required for Slackware distributions is slightly different. My thanks to Aurelio, PA3EZL for this information. @@ -1229,7 +1272,7 @@ a comment) # check every 10 minutes to see if gb7xxx is connected and if not # start a connect job going -0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx') +0,10,20,30,40,50 * * * * start_connect('gb7xxx') unless connected('gb7xxx')