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 .... +
CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held +at +Sourceforge. This means +that it is possible to update your DXSpider installation to the latest +sources by using a few simple commands. +
+
THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST +INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!! +THIS MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!! +YOU HAVE BEEN WARNED!!! +
+
DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE +CONSEQUENCES!!! +
+
I am of course assuming that you have a machine with both DXSpider and +Internet access running. +
+
BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR +ENTIRE SPIDER TREE!! +
+
Assuming you are connected to the Internet, you need to login to the +CVS repository and then update your Spider source. There are several +steps which are listed below ... +
+
First login as the user sysop. Next you need to connect to the CVS +repository. You do this with the command below ...
-
-
-# the list of regexes for messages that we won't store having
-# received them (bear in mind that we must receive them fully before
-# we can bin them)
-
-
-# The format of each line is as follows
-
-# type source pattern
-# P/B/F T/F/O/S regex
-
-# 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
-
-# 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.
-
-# The pattern can be undef or 0 in which case it will always be selected
-# for the action specified
-
-
-
-package DXMsg;
-
-@badmsg = (
-'B', 'T', 'SALE',
-'B', 'T', 'WANTED',
-'B', 'S', 'WANTED',
-'B', 'S', 'SALE',
-'B', 'S', 'WTB',
-'B', 'S', 'WTS',
-'B', 'T', 'FS',
-);
+cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
-You will get a password prompt. Simply hit return here and your machine should +return to a normal linux prompt.
-
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. +
What happens next depends on whether you have an existing installation that +you want to update with the latest and greatest or whether you just want +to see what is there and/or run it on a new machine for testing. +
If you are installing Spider from CVS then change directory to /home/sysop +
If you are wanting to update Spider then cd to /tmp
-
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 .... +
The next step will create a brand new 'spider' directory in your current +directory. +
+
+cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider ++
This command is all on one line. +
+
Hopefully your screen should show you downloading files. The -z3 simply compresses +the download to improve speed. +When this has finished, you will have exactly the same as if you had untarred a full +tarball PLUS some extra directories and files that CVS needs to do the magic that +it does. +
+
Now if you are doing a new installation, that's it. Carry on as if you have +just downloaded and untarred the lastest tarball. +
+
If you want to upgrade your current installation then do this ...
-
-# the list of dx spot addresses that we don't store and don't pass on
-
-
-package DXProt;
-
-@baddx = qw
-
- FROG
- SALE
- FORSALE
- WANTED
- P1RATE
- PIRATE
- TEST
- DXTEST
- NIL
- NOCALL
-);
+tar cvfz /tmp/s.tgz spider
+cd /
+tar xvfzp /tmp/s.tgz
This is assuming you downloaded to the /tmp directory of course.
-
Again, this is simply a list of names we do not want to see in the spotted field of a DX callout. +
NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions +correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU????? +
Remember to recompile the C client (cd /spider/src; make)
+
At this point the files have been upgraded. You can (usually) restart the cluster +in your own time. However, if you attempt to use any new commands or features +expect it to be fatal! At least your cluster will have been restarted then so it +will be too late to worry about it!
-
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 ... +
Now the magic part! From now on when you want to update, simply connect to the +Internet and then, as the user sysop ...
-# Below is a list of words we do not wish to see on the cluster
-grunge grunged grunging
-splodge splodger splodging
-grince
-fluffle
+cd /spider
+cvs -z3 update -d
Multiple words can be used on the same line as shown. Obviously these -are just examples :-) +
and your files will be updated. As above, remember to recompile the "C" client +if it has been updated (CVS will tell you) and restart if any of the perl scripts +have been altered or added, again, CVS will tell you.
-
You can reload the file from the cluster prompt as sysop with load/badwords. +
You will find any changes documented in the /spider/Changes file.