X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=html%2Fadminmanual-2.html;h=584af331ec41076f8f7e07269f13dae18bac1bb9;hb=7bc3b4bda7b8f4faed9c90e671d82dbcc66a65d7;hp=d606eb79060174a66f986027139004f1267c3a4c;hpb=4fa8a0251b64361c908d056393b46abece6d38be;p=spider.git diff --git a/html/adminmanual-2.html b/html/adminmanual-2.html index d606eb79..584af331 100644 --- a/html/adminmanual-2.html +++ b/html/adminmanual-2.html @@ -2,19 +2,129 @@
-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. +
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 .... +
+
+
+
+# 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',
+);
+
+
++
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. +
+
From version 1.47, this method is replaced by the command set/baddx +
+
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 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
+);
+
+
++
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.