X-Git-Url: http://scm.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-4.html;h=a54fa8ceb29de474306fad4952140af5aedcee30;hb=75abae88c65a19102d4a633a273a71750aa97728;hp=48e5702a0d5f5567ffe489adbbb9908391a59be7;hpb=b8ff94755eecda16276c449274c6a76c4f14a8d1;p=spider.git diff --git a/html/adminmanual-4.html b/html/adminmanual-4.html index 48e5702a..a54fa8ce 100644 --- a/html/adminmanual-4.html +++ b/html/adminmanual-4.html @@ -2,7 +2,7 @@
-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',
-);
-
-
+From 1.48 onwards it will become increasingly possible to control DXSpider's +operation with scripts of various kinds.
-
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 first instance, in 1.48, the sysop can create, with their favorite +text editor, files in the directory /spider/scripts which contain +any legal command for a callsign or class of connection which will be executed +at logon.
-
From version 1.47, this method is replaced by the command set/baddx +
+The filename is the callsign of the connection that you want the script to +operate on, eg: /spider/scripts/g1tlh. The filenames are always in +lower case on those architectures where this makes a difference.
-
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 .... +
In addition to the callsign specific scripts there are three others:-
-
-# 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
-);
+startup
+user_default
+node_default
+The startup script is executed immediately after all +initialisation of the node is done, but before any connections are +possible.
-
Again, this is simply a list of names we do not want to see in the spotted -field of a DX callout. +
The user_default script is executed for every user that does +NOT already have a specific script.
+
The node_default script is executed for every node that doesn't +have a specific script.
-
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. +
There are a couple of examples in the /spider/scripts directory.