The DXSpider Installation Manual v1.50
Iain Philipps, G0RDI (g0rdi@77hz.com) and Ian Maude, G0VGS,
(g0vgs@gb7mbc.net)
- July 2002 revision 0.2
+ July 2002 revision 0.3
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
In addition to the standard Red Hat distribution you will require the
- following modules from http://www.cpan.org/modules/bymodule/ , please
+ following modules from http://www.cpan.org/modules/by-module/ , 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
- For SUSE distributions, the command would be ..
+ For SuSE distributions, the command would be ..
This line works fine for RedHat distributions. It is also fine for
- SuSE up to 7.0. From Suse 7.1 you need to add runlevels 2 and 5 like
+ SuSE up to 7.0. From SuSE 7.1 you need to add runlevels 2 and 5 like
this ...
restart it should it crash for any reason.
+ NB: It should be noted that /dev/tty7 is only an example. Some SuSE
+ systems will only accept upto tty6. It really does not matter which
+ tty you run it on.
+
+
As root type the command telinit q. DXSpider should start up
immediately. You will see the output on tty7 and if you login as
sysop you should find everything running nicely.
- D:\ppm>ppm install Data-Dumper.ppd
- Installing package 'Data-Dumper.ppd'
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib
- Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html
- Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm
- Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist
- D:\ppm>
+
+
+
+
+
+ D:\ppm>ppm install Data-Dumper.ppd
+ Installing package 'Data-Dumper.ppd'
+ Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs
+ Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll
+ Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp
+ Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib
+ Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html
+ Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm
+ Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist
+ D:\ppm>
+
+
+
+
I'm not going to bother you with exhaustive details of the rest of
them, but suffice it to say you need to:
local disk. If you got the TGZ file, unpack it to somewhere
convenient. The following examples assume that you put it on drive
"C:\", for convenience.
-
-
You will need winzip to manipulate the TGZ files (they are bit like
ZIP files) if you are not using CVS.
go to "C:\spider\" and create them. If "C:\spider" is missing, go back
and figure out why, because it shouldn't be.
-
Now create your own local copy of the DXVars.pm file by:-
you must write them as "\@" or "\$".
-
6.1. Incoming telnets
If you want to enable inbound "TELNET" connections (or you are running
-
-
- copy \spider\perl\Listeners.pm \spider\local
- cd \spider\local
- notepad listeners.pm
+ copy \spider\perl\Listeners.pm \spider\local
+ cd \spider\local
+ notepad listeners.pm
- notepad AGWConnect.pm
+
+ notepad AGWConnect.pm
- DXSpider DX Cluster Version 1.47
- Copyright (c) 1998-2001 Dirk Koopman G1TLH
- loading prefixes ...
- loading band data ...
- loading user file system ...
- starting listeners ...
- Internal port: localhost 27754
- load badwords: Ok
- reading in duplicate spot and WWV info ...
- reading existing message headers ...
- load badmsg: Ok
- load forward: Ok
- load swop: Ok
- @msg = 0 before delete
- @msg = 0 after delete
- reading cron jobs ...v cron: reading /spider/cmd/crontab
- cron: adding 1 0 * * 0
- DXUser::export("$main::data/user_asc")
- reading database descriptors ...
- doing local initialisation ...
- orft we jolly well go ...
- queue msg (0)
+
+
+
+
+
+
+
+
+
+
+
+
+
+ DXSpider DX Cluster Version 1.47
+ Copyright (c) 1998-2001 Dirk Koopman G1TLH
+ loading prefixes ...
+ loading band data ...
+ loading user file system ...
+ starting listeners ...
+ Internal port: localhost 27754
+ load badwords: Ok
+ reading in duplicate spot and WWV info ...
+ reading existing message headers ...
+ load badmsg: Ok
+ load forward: Ok
+ load swop: Ok
+ @msg = 0 before delete
+ @msg = 0 after delete
+ reading cron jobs ...v cron: reading /spider/cmd/crontab
+ cron: adding 1 0 * * 0
+ DXUser::export("$main::data/user_asc")
+ reading database descriptors ...
+ doing local initialisation ...
+ orft we jolly well go ...
+ queue msg (0)
+
+
+
+
Now, if that's what you've got, you are very nearly home and dry (in
as far as these particular experiments are concerned, anyhow)
like:-
-
Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.47
Cluster: 1 nodes, 1 local / 1 total users Max users 2 Uptime 0 00:00
M0ADI de GB7SJP 4-Mar-2001 1511Z >
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
projects / spider.git / blobdiff