- The DXSpider Installation Manual v1.47
+ The DXSpider Installation Manual v1.49
Iain Philipps, G0RDI (g0rdi@77hz.com) and Ian Maude, G0VGS,
(ianmaude@btinternet.com)
- Version 1.47, April 2001 revision 1.0
+ November 2001 revision 1.0
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
1.2 Preparation
1.3 Installing the software
1.4 Setting callsigns etc
- 1.5 Starting up for the first time
- 1.6 The Client program
+ 1.5 The client program
+ 1.6 Starting up for the first time
2. Linux quick installation guide
- o Data-Dumper-2.101.tar.gz
+ o Data-Dumper-2.10.tar.gz
o TimeDate-1.10.tar.gz
o Net-Telnet-3.02.tar.gz
- o Curses-1.05.tar.gz
+ o Curses-1.06.tar.gz
o Time-HiRes-01.20.tar.gz
- Do get the latest versions of these packages and install them but use
- the above list as the earliest versions usable.
+ 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: -
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ # tar xvfz /usr/local/packages/Data-Dumper-2.10.tar.gz
+ # cd Data-Dumper-2.10
+ # perl Makefile.PL
+ # make test
+ # make install
+ # cd ..
+ #
+ # tar xvfz /usr/local/packages/TimeDate-1.10.tar.gz
+ # cd TimeDate-1.10
+ # perl Makefile.PL
+ # make test
+ # make install
+ # cd ..
+ #
+ # tar xvfz /usr/local/packages/IO-1.20.tar.gz
+ # cd IO-1.20
+ # perl Makefile.PL
+ # make test
+ # make install UNINST=1
+ # cd ..
+ #
+ # tar xvfz /usr/local/packages/Net-Telnet-3.02.tar.gz
+ # cd Net-Telnet-3.02
+ # perl Makefile.PL
+ # make test
+ # make install
+ # cd ..
+ #
+ # tar xvfz /usr/local/packages/Curses-1.06.tar.gz
+ # cd Curses-1.06
+ # perl Makefile.PL
+ # make test
+ # make install
+ # cd ..
+ #
+ # tar xvfz /usr/local/packages/Time-HiRes-01.20.tar.gz
+ # cd Time-HiRes-01.20
+ # perl Makefile.PL
+ # make test
+ # make install
+ # cd ..
+
+
+
+
+ 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.
+
1.2. Preparation
your own choice.
+ # adduser -m sysop
- # adduser -m sysop
+ For SUSE distributions, the command would be ..
- Now set a password for the user ...
+ # useradd -m sysop
- # passwd sysop
- # New UNIX password:
- # Retype new UNIX password:
- passwd: all authentication tokens updated successfully
+ Now set a password for the user ...
+
+
+
+ # passwd sysop
+ # New UNIX password:
+ # Retype new UNIX password:
+ passwd: all authentication tokens updated successfully
- # chown -R sysop.spider spider
- # find . -type d -exec chmod 2775 {} \;
- # find . -type f -exec chmod 775 {} \;
+ # chown -R sysop.spider spider
+ # find . -type d -exec chmod 2775 {} \;
+ # find . -type f -exec chmod 775 {} \;
-
- # chown root ax25_call netrom_call
- # chmod 4775 ax25_call netrom_call
+ # chown root ax25_call netrom_call
+ # chmod 4775 ax25_call netrom_call
+ $ ./create_sysop.pl
+
- $ ./create_sysop.pl
+ 1.5. 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.
+
- 1.5. Starting up for the first time
+ 1.6. Starting up for the first time
We can now bring spider up for the first time and see if all is well
or not! It should look something like this ...
$ ./client
-
-
-
This should log you into the cluster as the sysop under the alias
callsign we set earlier. In this case the callsign is G0VGS. The
cluster callsign is set in the DXVars.pm file in /spider/local. In
and both the cluster and the client should return to Linux prompts.
- 1.6. 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.
-
2. Linux quick installation guide
o cp perl/DXVars.pm.issue local/DXVars.pm (sysop)
+
o cd to /spider/local and edit DXVars to set your details (sysop)
o cd ../perl (sysop)
..
-
default * * * * * * - sysop /spider/src/client client %s ax25
+
+
3.2. Allowing telnet connects from users
./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
- @listen = (
- ["gb7baa.dxcluster.net", 8000],
- ["44.131.16.2", 6300],
- );
+
+
+
+
+ @listen = (
+ ["gb7baa.dxcluster.net", 8000],
+ ["44.131.16.2", 6300],
+ );
- set/node (AK1A type)
- set/spider
- set/dxnet
- set/clx
+ set/node (AK1A type)
+ set/spider
+ set/dxnet
+ set/clx
- set/node gb7baa
+ set/node gb7baa
unset/node gb7baa
-
-
-
3.6. Connection scripts
Because DXSpider operates under Linux, connections can be made using
# All lines starting with a # are ignored, as are completely blank
lines.
+
timeout
timeout followed by a number is the number of seconds to wait
for a command to complete. If there is no timeout specified in
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.
-
-
-
timeout 60
abort (Busy|Sorry|Fail)
# don't forget to chmod 4775 netrom_call!
-
- timeout 60
- abort (Busy|Sorry|Fail)
- # this does exactly the same as the previous example
- # the '1' is the AGW port number to connect thru for g1tlh
- connect agw 1 g1tlh
- # you can leave this out if you call the script 'gb7dxm'
- client gb7dxm ax25
+ timeout 60
+ abort (Busy|Sorry|Fail)
+ # this does exactly the same as the previous example
+ # the '1' is the AGW port number to connect thru for g1tlh
+ connect agw 1 g1tlh
+ # you can leave this out if you call the script 'gb7dxm'
+ client gb7dxm ax25
-
-
-
-
-
-
-
-
-
-
-
-
-
-
<- D G1TLH connect gb7djk-1
-> D G1TLH connection to GB7DJK-1 started
-> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
# 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')
projects / spider.git / blobdiff