- The DXSpider Administration Manual v1.48
+ The DXSpider Administration Manual v1.49
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.49 November 2001 revision 1.1
+ December 2001 revision 1.2
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
how the file works.
+ SHould any of the nodecalls include an ssid, it is important to wrap
+ the whole call in single quotes, like this ...
+
+
+
+
+ 'DB0FHF-15' => {
+ 11 => 5,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+
+
+
+
+ If you do not do this, you will get errors and the file will not work
+ as expected.
+
+
You can alter this file at any time, including whilst the cluster is
running. If you alter the file during runtime, the command load/hops
will bring your changes into effect.
-
1.11. Hop Control on Specific Nodes
You can set a callsign specific hop count for any of the standard
+ # 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
- # 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
+ # 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.
+ # 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
+ # The pattern can be undef or 0 in which case it will always be selected
+ # for the action specified
- package DXMsg;
+ package DXMsg;
- @badmsg = (
- );
+ @badmsg = (
+ );
of show/baddx, show/badspotter and show/badnode.
+
+
+
3. Mail
DXSpider deals seamlessly with standard AK1A type mail. It supports
default method of sending mail and so a simple s for send will do. A
full list of the send commands and options is in the command set
section, so I will not duplicate them here.
+
+
3.2. Bulletin mail
Bulletin mail is sent by using the sb command. This is one of the
- #
- # this is an example message forwarding file for the system
- #
- # The format of each line is as follows
- #
- # type to/from/at pattern action destinations
- # P/B/F T/F/A regex I/F [ call [, call ...] ]
- #
- # type: P - private, B - bulletin (msg), F - file (ak1a bull)
- # to/from/at: T - to field, F - from field, A - home bbs, O - origin
- # pattern: a perl regex on the field requested
- # action: I - ignore, F - forward
- # destinations: a reference to an array containing node callsigns
- #
- # if it is non-private and isn't in here then it won't get forwarded
- #
- # Currently only type B 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
- #
- # If the BBS list is undef or 0 and the action is 'F' (and it matches the
- # pattern) then it will always be forwarded to every node that doesn't have
- # it (I strongly recommend you don't use this unless you REALLY mean it, if
- # you allow a new link with this on EVERY bull will be forwarded immediately
- # on first connection)
- #
- package DXMsg;
- @forward = (
- );
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ #
+ # this is an example message forwarding file for the system
+ #
+ # The format of each line is as follows
+ #
+ # type to/from/at pattern action destinations
+ # P/B/F T/F/A regex I/F [ call [, call ...] ]
+ #
+ # type: P - private, B - bulletin (msg), F - file (ak1a bull)
+ # to/from/at: T - to field, F - from field, A - home bbs, O - origin
+ # pattern: a perl regex on the field requested
+ # action: I - ignore, F - forward
+ # destinations: a reference to an array containing node callsigns
+ #
+ # if it is non-private and isn't in here then it won't get forwarded
+ #
+ # Currently only type B 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
+ #
+ # If the BBS list is undef or 0 and the action is 'F' (and it matches the
+ # pattern) then it will always be forwarded to every node that doesn't have
+ # it (I strongly recommend you don't use this unless you REALLY mean it, if
+ # you allow a new link with this on EVERY bull will be forwarded immediately
+ # on first connection)
+ #
+
+ package DXMsg;
+
+ @forward = (
+ );
- MSG TO <msgno> <call> - change TO callsign to <call>
- MSG FRom <msgno> <call> - change FROM callsign to <call>
- MSG PRrivate <msgno> - set private flag
- MSG NOPRrivate <msgno> - unset private flag
- MSG RR <msgno> - set RR flag
- MSG NORR <msgno> - unset RR flag
- MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
- MSG NOKEep <msgno> - unset the keep flag
- MSG SUbject <msgno> <new> - change the subject to <new>
- MSG WAittime <msgno> - remove any waiting time for this message
- MSG NOREad <msgno> - mark message as unread
- MSG REad <msgno> - mark message as read
- MSG QUeue - queue any outstanding bulletins
- MSG QUeue 1 - queue any outstanding private messages
+
+
+
+
+
+
+
+
+ MSG TO <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - remove any waiting time for this message
+ MSG NOREad <msgno> - mark message as unread
+ MSG REad <msgno> - mark message as read
+ MSG QUeue - queue any outstanding bulletins
+ MSG QUeue 1 - queue any outstanding private messages
Times read: 0
G0VGS de GB7MBC 28-Jan-2001 1308Z >
+
+
+
+
3.6. Filtering mail
This is described in the section on Other filters so I will not
SYSOP.pl that caters for the UK sysops.
-
qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
GB7DXK GB7DXI GB7DXS)
-
-
-
-
-
-
-
-
- #
- # startup script example
- #
- # set maximum no of spots allowed to 100
- # set/var $Spot::maxspots = 1
- #
- # Set registration on
- # set/var $main::reqreg = 1
- #
- # Set passwords on
- # set/var $main::passwdreq = 1
- #
+ #
+ # startup script example
+ #
+ # set maximum no of spots allowed to 100
+ # set/var $Spot::maxspots = 1
+ #
+ # Set registration on
+ # set/var $main::reqreg = 1
+ #
+ # Set passwords on
+ # set/var $main::passwdreq = 1
+ #
eventually users will be able to set their own. An example is
included in the distibution but here is a further example.
-
-
#
# G0FYD
#
+
This will update the existing local oblast database or create it if it
does not exist.
+
+
5.4. Looking up databases
To look for information in a defined database, simply use the dbshow
If you remove a database it ceases to exist and would have to be
created from scratch if you still required it.
+
6. Information, files and useful programs
6.1. MOTD
registered they will receive the same message as any other user.
+
+
6.3. Downtime message
If for any reason the cluster is down, maybe for upgrade or
-
You can see that in the files area (basically the packclus directory)
there is a file called news and a directory called bulletin. You can
also see that dates they were created. In the case of the file news,
-
-
-
- type bulletin/opdx391
- Ohio/Penn DX Bulletin No. 391
- The Ohio/Penn Dx PacketCluster
- DX Bulletin No. 391
- BID: $OPDX.391
- January 11, 1999
- Editor Tedd Mirgliotta, KB8NW
- Provided by BARF-80 BBS Cleveland, Ohio
- Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
- Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
- Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
- & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
- Press Enter to continue, A to abort (508 lines) >
+ type bulletin/opdx391
+ Ohio/Penn DX Bulletin No. 391
+ The Ohio/Penn Dx PacketCluster
+ DX Bulletin No. 391
+ BID: $OPDX.391
+ January 11, 1999
+ Editor Tedd Mirgliotta, KB8NW
+ Provided by BARF-80 BBS Cleveland, Ohio
+ Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
+ Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
+ Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
+ & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
+ Press Enter to continue, A to abort (508 lines) >
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
You can create aliases for commands at will. Beware though, these may
not always turn out as you think. Care is needed and you need to test
the results once you have set an alias.
+
would export message number 5467 as a file called keps.in in the
/spider/perl directory.
+
Now login to a VT as sysop and cd /spider/perl. There is a command in
the perl directory called convkeps.pl. All we need to do now is
convert the file like so ...
+
Now go back to the cluster and issue the command ...
- That is it! the kepler data has been updated.
-
+ That is it! the kepler data has been updated.
6.8. The QRZ callbook
registered users, use the command show/register.
+
7.2. Passwords
At the moment, passwords only affect users who login to a DXSpider
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 ...
+
cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
dest <prefixes> eg: 6MUK,WDX (distros)
+ some examples:-
- some examples:-
acc/ann dest 6MUK
acc/ann 2 by_zone 14,15,16
more info. Please read this to understand how filters work - it will
save a lot of grief later on.
-
You can use any of the following things in this line:-
+
call <prefixes> the callsign of the thingy
call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <numbers>
9.4. accept/spots (0)
- accept/
announce [0-9] <pattern> Set an accept filter line for spots
+ accept/
spots [0-9] <pattern> Set an accept filter line for spots
Create an 'accept this spot' line for a filter.
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
- on <range> same as 'freq'
- call <prefixes> eg: G,PA,HB9
- info <string> eg: iota or qsl
- by <prefixes>
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- origin <prefixes>
- channel <prefixes>
+
+
+
+
+
+
+
+
+
+
+
+
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
+
+
-
-
-
-
-
-
-
-
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
+
+
+
+
+
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
for example
+
accept/wwv by_zone 4
This command will send your announcement across the whole cluster
network.
-
-
-
9.12. announce sysop (5)
announce sysop <text>
apropos <string> Search the help database
-
Search the help database for <string> (it isn't case sensitive), and
print the names of all the commands that may be relevant.
This command allows you to clear (remove) a line in a route filter or
to remove the whole filter.
-
see CLEAR/SPOTS for a more detailed explanation.
A sysop can clear an input or normal output filter for a user or the
node_default or user_default.
-
-
-
9.20. clear/wcy (0)
clear/wcy [1|all] Clear a WCY filter line
to allow
+
SH/BUCK g1tlh
to work as they may be used to.
databases. See DBSHOW for generic database enquiry
-
-
9.27. dbimport (9)
dbimport <dbname> Import AK1A data into a database
but if he hasn't and the database really does exist (use DBAVAIL or
SHOW/COMMAND to find out) you can do the same thing with:
+ DBSHOW buck G1TLH
- DBSHOW buck G1TLH
-
- DIR TO G1TLH 5
- or
- DIR SUBJECT IOTA 200-250
+
+
+ DIR TO G1TLH 5
+ or
+ DIR SUBJECT IOTA 200-250
You can abbreviate all the commands to one letter and use ak1a
syntax:-
+
+
+
DIR/T G1* 10
DIR/S QSL 10-100 5
- DX by G1TLH FR0G 144.600 he isn't on the cluster
+
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
export <msgno> <filename> Export a message to a file
+
Export a message to a file. This command can only be executed on a
local console with a fully privileged user. The file produced will be
in a form ready to be imported back into the cluster by placing it in
clear/spots 1
-
To remove the filter in its entirty:-
clear/spots all
same subject will be deleted. Beware!
+
+
9.46. kill/expunge (6)
kill/expunge <msgno> [<msgno>..]Expunge a message
It otherwise is used in the same way as the KILL command.
+
9.47. links (0)
links Show which nodes are physically connected
load/bands Reload the band limits table
-
Reload the /spider/data/bands.pl file if you have changed it manually
whilst the cluster is running.
delete a command in the local_cmd tree and want to use the normal one
again. Execute this command to reset everything back to the state it
was just after a cluster restart.
+
+
9.53. load/forward (9)
load/forward Reload the msg forwarding routing table
msg <cmd> <msgno> [data ...] Alter various message parameters
-
Alter message parameters like To, From, Subject, whether private or
bulletin or return receipt (RR) is required or whether to keep this
message from timing out.
-
-
-
-
-
-
-
-
-
-
- MSG TO <msgno> <call> - change TO callsign to <call>
- MSG FRom <msgno> <call> - change FROM callsign to <call>
- MSG PRrivate <msgno> - set private flag
- MSG NOPRrivate <msgno> - unset private flag
- MSG RR <msgno> - set RR flag
- MSG NORR <msgno> - unset RR flag
- MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
- MSG NOKEep <msgno> - unset the keep flag
- MSG SUbject <msgno> <new> - change the subject to <new>
- MSG WAittime <msgno> - remove any waitting time for this message
- MSG NOREad <msgno> - mark message as unread
- MSG REad <msgno> - mark message as read
- MSG QUeue - queue any outstanding bulletins
- MSG QUeue 1 - queue any outstanding private messages
+ MSG TO <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - remove any waitting time for this message
+ MSG NOREad <msgno> - mark message as unread
+ MSG REad <msgno> - mark message as read
+ MSG QUeue - queue any outstanding bulletins
+ MSG QUeue 1 - queue any outstanding private messages
+
+
+
9.60. rcmd (1)
rcmd <node call> <cmd> Send a command to another DX cluster
This command allows you to send nearly any command to another DX
Cluster node that is connected to the system.
-
Whether you get any output is dependant on a) whether the other system
knows that the node callsign of this cluster is in fact a node b)
whether the other system is allowing RCMDs from this node and c)
+
some examples:-
origin_itu <numbers>
origin_zone <numbers>
-
-
-
-
some examples:-
-
- rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
+ rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
rej/spot 1 on hf
rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
-
You can use the tag 'all' to reject everything eg:
projects / spider.git / blobdiff