X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-2.html;h=b28822c1fb083c59afb49ff45cf8c04a13c0cef4;hb=d755df6b0d8636240520f66680972e9e70f98860;hp=b5f2402a13d203d79ccd6abc13158527d9055c75;hpb=439f25ba04e8c4ddbd6806f31da58c0939e2c868;p=spider.git diff --git a/html/adminmanual-2.html b/html/adminmanual-2.html index b5f2402a..b28822c1 100644 --- a/html/adminmanual-2.html +++ b/html/adminmanual-2.html @@ -2,25 +2,129 @@ - The DXSpider Installation and Administration Manual : The Client program + The DXSpider Administration Manual v1.48: Other filters + Next Previous Contents
-

2. The Client program

- -

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. +

2. Other filters

+ +

2.1 Filtering Mail +

+ +

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. +

+

2.2 Filtering DX callouts (Depricated) +

+ +

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. +

+

+

2.3 Filtering words from text fields in Announce, Talk and DX spots +

+ +

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.


Next