3 This version of dxspider requires perl5 (it is written entirely in perl5 and
4 makes extensive use of perl objects). This program is known to work with
7 In addition to the standard perl5 distribution you will require to load the
8 the following modules:-
10 1) CPAN - this has a load of the standard extra stuff in it. To load it type:-
12 # perl -MCPAN -e shell
13 cpan> install Bundle::CPAN
16 Please sure there were no errors, be particularly careful when installing
17 libwww stuff, I would suggest 'no host lookups' and pressing <space> and
18 enter for each of the offered default hostnames.
20 2) Date::Parse, MLDBM, IO::Select
22 As you have so carefully loaded it, I suggest you use the CPAN system
25 # perl -MCPAN -e shell
26 cpan> install Date::Parse
32 cpan> install IO::Select
34 3) select a user to run the cluster as UNDER _NO_ CIRCUMSTANCES USE ROOT.
36 I say again DO NOT USE root.
38 Pick an existing user or create a new one. Don't care which. I don't know
39 your security requirements.
41 4) login as root (I shall use 'jim' for any examples).
44 # tar xvfz spider-x.x.tar.gz
45 # ln -s ~jim/spider /spider
46 # groupadd -g 251 spider (or another number)
47 # vi /etc/group (or your favorite editor)
48 add jim (or whatever) and root to the group spider
49 it should look something like:-
53 # chown -R jim.spider spider
54 # find . -type d -exec chmod 2775 {} \;
55 # find . -type f -exec chmod 775 {} \;
57 This last step allows various users of group spider to have write
58 access to all the directories. Not really needed for now but will
59 be useful when web interfaces start to appear.
61 6) if you have any users that require network logins, set them up as real
62 users with useradd -m <callsign>. Alter the default .bashrc so that it
63 contains just one line (assuming you use the default bash shell).
65 exec /spider/perl/client.pl <callsign>
67 Don't forget to give them a real password. This is really for network
70 7) for incoming AX25 connections you are expected to have got the AX25
71 utilities setup, tested and working. See the AX25-HOWTO for more info
72 on this - it really is outside the scope of this document. I would
73 recommend using ax25-utils-2.1.42a-5.i386.rpm or above as a starting
74 point. DXSpider uses ax25d for incoming connections. You need to have
79 default * * * * * * - djk /spider/perl/client.pl client.pl %u ax25
82 default * * * * * * - djk /spider/perl/client.pl client.pl %u ax25
84 where ether and bbs are appropriate KNOWN WORKING axport and nrport
87 Obviously you can use different names, callsigns or whatever for your
88 purposes, but it is up to you to get it to work.
90 Note I use BPQ over ethernet which why I have the port names I have.
92 8) login as jim (or whatever)
93 $ startx (much easier to use X)
97 $ cp perl/DXVars.pm local
101 now alter your cluster callsign, sysop callsign and other user info
102 as you wish. Note that this a perl file which will parsed and executed
103 as part of the cluster. If you get it wrong then perl will complain
104 when you start the cluster process.
106 PLEASE USE CAPITAL LETTERS FOR CALLSIGNS
108 DON'T alter the DXVars.pm (or any other file) in /spider/perl, they are
109 overwritten with every release. Any files or commands you place in
110 /spider/local or /spider/local_cmd will automagically be used in preference
111 to the ones in /spider/perl EVEN whilst the cluster is running!
117 DXSpider DX Cluster Version x.x
118 Copyright (c) 1998 Dirk Koopman G1TLH
120 loading band data ...
121 loading user file system ...
122 starting listener ...
123 reading existing message headers
125 orft we jolly well go ...
128 9) now log in again or start another rxvt or xterm
131 you should now see a normal cluster prompt.
133 at the cluster prompt:-
135 G1JIM de GB7JIM 10-Sep-98 1000Z> set/node GB7XXX
137 for every dxcluster you expect to connect to or from.
139 G1JIM de GB7JIM 10-Sep-98 1001Z> shutdown
141 The cluster and the client should both go back to prompts
145 The callsigns should be the sysop callsign and the cluster callsign
146 as per your modified DXVars.pm. You can check that the cluster
147 connections will work by:-
149 $ client.pl gb7xxx (doesn't have to be uppercase).
150 PC38^GB7JIM^~ <- the cluster thinks this is a cluster