In the spider tree will be a directory spider-web. This is a +neat little java web applet that can be run from a website. The applet +must run on the same machine as the cluster. The included README file is +shown below.
-In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename this to badmsg.pl and edit the file. -The original looks something like this .... +
I should comment here that the applet is precompiled, that is, ready to go. +It was compiled using JDK1.3.1. If your version is earlier than this then it +may not work. Should that be the case you need to recompile or update your +JDK. To recompile do the following ...
+cd /spider/spider-web
+rm *.class
+/usr/bin/javac spiderclient.java
+
+I have used /usr/bin/javac as an example, your path to javac may be different.
++
+Spider-WEB v0.6b -# The format of each line is as follows +Completely based on a clx web client written in Java by dl6dbh +(ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz) -# type source pattern -# P/B/F T/F/O/S regex +The webserver has to run on the same machine as your DxSpider software! -# type: P - private, B - bulletin (msg), F - file (ak1a bull) -# source: T - to field, F - from field, O - origin, S - subject -# pattern: a perl regex on the field requested +It is assumed that you have Java installed. You need JDK1.3.1 at least. -# Currently only type B and P msgs are affected by this code. -# -# The list is read from the top down, the first pattern that matches -# causes the action to be taken. +Installation instructions (Performed as root): -# The pattern can be undef or 0 in which case it will always be selected -# for the action specified +Put all the files in the spider-web directory into a newly created directory +under the DocumentRoot of your websever for instance 'client'. In my case +this is: /home/httpd/html/client/ although ymmv. For Suse the correct +path should be /usr/local/httpd/htdocs/client/ for example. +Move spider.cgi to the cgi-bin directory of your webserver, in my case that is +/home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be +/usr/local/httpd/cgi-bin/ for example. +Change the permissions of the files to ensure they are correct, obviously you +will need to use the correct path the the files according to your system: -package DXMsg; +chmod 755 /home/httpd/html/cgi-bin/spider.cgi +chmod -R 755 /home/httpd/html/client/ -@badmsg = ( -'B', 'T', 'SALE', -'B', 'T', 'WANTED', -'B', 'S', 'WANTED', -'B', 'S', 'SALE', -'B', 'S', 'WTB', -'B', 'S', 'WTS', -'B', 'T', 'FS', -); -- -
-
I think this is fairly self explanatory. It is simply a list of subject headers that we do not want to pass on to either -the users of the cluster or the other cluster nodes that we are linked to. This is usually because of rules and regulations -pertaining to items for sale etc in a particular country. -
-
In the same way as mail, there are some types of spot we do not wish to pass on to users or linked cluster nodes. In the -/spider/data directory you will find a file called baddx.pl.issue. Rename this to baddx.pl and edit the file. The original -looks like this .... -
-
-
+# Uncomment and set the hostname manually here if the above fails.
+# $HOSTNAME = "gb7mbc.spoo.org" ;
+$PORT = "8000" ;
-# the list of dx spot addresses that we don't store and don't pass on
+'HOSTNAME' is the hostname of your cluster.
+'PORT' is the portnumber that you use to connect to your DxSpider via
+telnet (see Listeners.pm)
-package DXProt;
+NOTE: If you can start the console but cannot connect to the cluster from it,
+then it is possible that the machine you are on cannot resolve the hostname of
+your cluster machine. If this is the case, you need to set your hostname
+manually as above.
-@baddx = qw
+You also need to set the $NODECALL variable. This prints the name of your
+choosing (probably your cluster callsign) on the html page.
- FROG
- SALE
- FORSALE
- WANTED
- P1RATE
- PIRATE
- TEST
- DXTEST
- NIL
- NOCALL
-);
+You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
--
Again, this is simply a list of names we do not want to see in the spotted field of a DX callout. -
-
-
Create a file in /spider/data called badwords. The format is quite -simple. Lines beginning with # are ignored so comments can be added. An -example file is below ... -
-
-
-# Below is a list of words we do not wish to see on the cluster
-grunge grunged grunging
-splodge splodger splodging
-grince
-fluffle
-
-Multiple words can be used on the same line as shown. Obviously these -are just examples :-) -
-
You can reload the file from the cluster prompt as sysop with load/badwords. -