<title>The DXSpider Installation and Administration Manual
<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
-<date>Version 1.28 January 2001
+<date>Version 1.32 February 2001
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
</abstract>
<sect>Installation (Original version by Iain Phillips, G0RDI)
-<P>
-Last modified: 03 January 2001 by Ian Maude, G0VGS
-
<sect1>Introduction
<P>
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.
-<sect1>Filtering DX callouts
+<sect1>Filtering DX callouts (Depricated)
+
+<P>
+<bf><it>From version 1.47, this method is replaced by the command set/baddx</it></bf>
<P>
In the same way as mail, there are some types of spot we do not wish to pass on
<P>
You can reload the file from the cluster prompt as sysop with load/badwords.
+<sect>Mail
+
+<P>
+DXSpider deals seamlessly with standard AK1A type mail. It supports both
+personal and bulletin mail and the sysop has additional commands to ensure
+that mail gets to where it is meant. DXSpider will send mail almost
+immediately, assuming that the target is on line. However, only one
+mail message is dealt with at any one time. If a mail message is already
+being sent or recieved, then the new message will be queued until it has
+finished.
+
+The cluster mail is automatically deleted after 30 days unless the sysop
+sets the "keep" flag using the <em>msg</em> command.
+
+<sect1>Personal mail
+
+<P>
+Personal mail is sent using the <em>sp</em> command. This is actually the
+default method of sending mail and so a simple <em>s</em> for send will do.
+A full list of the send commands and options is in the <em>command set</em>
+section, so I will not duplicate them here.
+
+<sect1>Bulletin mail
+
+<P>
+Bulletin mail is sent by using the <em>sb</em> command. This is one of the
+most common mistakes users make when sending mail. They send a bulletin
+mail with <em>s</em> or <em>sp</em> instead of <em>sb</em> and of course
+the message never leaves the cluster. This can be rectified by the sysop
+by using the <em>msg</em> command.
+
+<P>Bulletin addresses can be set using the Forward.pl file.
+
+<sect1>Forward.pl
+
+<P>
+DXSpider receives all and any mail sent to it without any alterations needed
+in files. Because personal and bulletin mail are treated differently, there
+is no need for a list of accepted bulletin addresses. It is necessary, however,
+to tell the program which links accept which bulletins. For example, it is
+pointless sending bulletins addresses to "UK" to any links other than UK
+ones. The file that does this is called forward.pl and lives in /spider/msg.
+At default, like other spider files it is named forward.pl.issue. Rename it
+to forward.pl and edit the file to match your requirements.
+The format is below ...
+
+<tscreen><verb>
+#
+# 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 = (
+'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ],
+'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ],
+'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ],
+'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+);
+</verb></tscreen>
+
+Simply insert a bulletin address and state in the brackets where you wish
+that mail to go. For example, you can see here that mail sent to "UK" will
+only be sent to the UK links and not to PA4AB-14.
+
+<P>
+To force the cluster to reread the file use load/forward
+
+
+<sect1>The msg command
+
+<P>
+The <em>msg</em> command is a very powerful and flexible tool for the
+sysop. It allows the sysop to alter to and from fields and make other
+changes to manage the cluster mail.
+
+Here is a full list of the various options ...
+
+<tscreen><verb>
+ 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
+</verb></tscreen>
+
+These commands are simply typed from within the cluster as the sysop user.
+
+<sect1>Message status
+
+<P>
+You can check on a message from within the cluster by using the command
+<em>stat/msg</em>. This will give you additional information on the
+message number including which nodes have received it, which node it
+was received from and when etc. Here is an example of the output of
+the command ...
+
+<tscreen><verb>
+G0VGS de GB7MBC 28-Jan-2001 1308Z >
+stat/msg 6869
+ From: GB7DJK
+ Msg Time: 26-Jan-2001 1302Z
+ Msgno: 6869
+ Origin: GB7DJK
+ Size: 8012
+ Subject: AMSAT 2line KEPS 01025.AMSAT
+ To: UK
+Got it Nodes: GB7BAA, GB7ADX
+ Private: 0
+Read Confirm: 0
+ Times read: 0
+G0VGS de GB7MBC 28-Jan-2001 1308Z >
+</verb></tscreen>
+
+<sect1>Filtering mail
+
+<P>
+This is described in the section on <em>Other filters</em> so I will not
+duplicate it here.
+
+<sect1>Distribution lists
+
+<P>
+Distribution lists are simply a list of users to send certain types of
+mail to. An example of this is mail you only wish to send to other
+sysops. In /spider/msg there is a directory called <em>distro</em>. You
+put any distibution lists in here. For example, here is a file called
+SYSOP.pl that caters for the UK sysops.
+
+<tscreen><verb>
+qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
+ GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
+ GB7DXK GB7DXI GB7DXS)
+</verb></tscreen>
+
+Any mail sent to "sysop" would only be sent to the callsigns in this list.
+
+<sect1>BBS interface
+
+<P>
+Spider provides a simple BBS interface. No input is required from the sysop
+of the cluster at all. The BBS simply sets the cluster as a BBS and pushes
+any required mail to the cluster. No mail can flow from Spider to the BBS,
+the interface is one-way.
+
+<P>
+Please be careful not to flood the cluster network with unnecessary mail.
+Make sure you only send mail to the clusters that want it by using the
+Forward.pl file very carefully.
+
+<sect>Databases
+
+<P>
+Spider allows the creation of local or remote databases. It supports
+chained databases, allowing several different databases to be scanned
+with one simple command. Importing of databases is limited at present
+to the standard AK1A databases such as OBLAST and the DB0SDX QSL
+database but will expand with time.
+
+<sect1>Creating databases
+
+<P>
+Creating a database could not be more simple. All the commands are
+sent from the cluster prompt as the <em>sysop</em> user.
+
+To create a database you use the command <em>dbcreate</em>. It can
+be used in 3 different ways like so ..
+
+<tscreen><verb>
+dbcreate <name>
+</verb></tscreen>
+
+To simply create a database locally, you just tell the command the
+name of the database. This does not create the actual database, it
+simply defines it to say that it exists.
+
+<tscreen><verb>
+dbcreate <name> chain <name> [<name>...]
+</verb></tscreen>
+
+This creates a chained database entry. The first database will be
+scanned, then the second, the third etc...
+
+<tscreen><verb>
+dbcreate <name> remote <name>
+</verb></tscreen>
+
+This creates a remote entry. the first name field is the database
+name at the remote node, then the remote switch, then the actual
+node_call of the remote node, for example...
+
+<tscreen><verb>
+dbcreate buckmaster remote gb7dxc
+</verb></tscreen>
+
+Remote databases cannot be chained, however, the last database in a
+chain can be a remote database.
+
+<sect1>Importing databases
+
+<P>
+The only databases that Spider can currently import are the standard
+AK1A databases such as OBLAST or the DB0SDX qsl and address database.
+This will be added to with time.
+
+To import such a database, first put the file somewhere useful like /tmp
+and then issue the following command ...
+
+<tscreen><verb>
+dbimport oblast /tmp/OBLAST.FUL
+</verb></tscreen>
+
+This will update the existing local oblast database or create it if
+it does not exist.
+
+<sect1>Checking available databases
+
+<P>
+Once a database is created, you will want to check that it has been
+added. To do this use the <em>dbavail</em> command. This will
+output the available databases. For example ...
+
+<tscreen><verb>
+dbavail
+DB Name Location Chain
+qsl Local
+buck GB7ADX
+hftest GB7DXM
+G0VGS de GB7MBC 3-Feb-2001 1925Z >
+</verb></tscreen>
+
+<sect1>Looking up databases
+
+<P>
+To look for information in a defined database, simply use the <em>dbshow</em>
+command, for example ...
+
+<tscreen><verb>
+dbshow buckmaster G0YLM
+</verb></tscreen>
+
+will show the information for the callsign G0YLM from the buckmaster
+database if it exists. To make things more standard for the users
+you can add an entry in the Aliases file so that it looks like a standard
+<em>show</em> command like this ...
+
+<tscreen><verb>
+'^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
+</verb></tscreen>
+
+Now you can simply use show/buckmaster or an abreviation.
+
+<sect1>Removing databases
+
+<P>
+To delete an existing database you use the <em>dbremove</em> command.
+For example ...
+
+<tscreen><verb>
+dbremove oblast
+</verb></tscreen>
+
+would remove the oblast database and its associated datafile from the
+system. There are no warnings or recovery possible from this command.
+If you remove a database it ceases to exist and would have to be created
+from scratch if you still required it.
+
<sect>Information, files and useful programs
<sect1>MOTD
always turn out as you think. Care is needed and you need to test the
results once you have set an alias.
-<sect1>Forward.pl
+<sect1>Console.pl
<P>
-DXSpider receives all and any mail sent to it without any alterations needed
-in files. Because personal and bulletin mail are treated differently, there
-is no need for a list of accepted bulletin addresses. It is necessary, however,
-to tell the program which links accept which bulletins. For example, it is
-pointless sending bulletins addresses to "UK" to any links other than UK
-ones. The file that does this is called forward.pl and lives in /spider/msg.
-At default, like other spider files it is named forward.pl.issue. Rename it
-to forward.pl and edit the file to match your requirements.
-The format is below ...
+In later versions of Spider a simple console program is provided for the sysop.
+This has a type ahead buffer with line editing facilities and colour for spots,
+announces etc. To use this program, simply use console.pl instead of client.pl.
-<tscreen><verb>
-#
-# 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)
-#
+<P>
+To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
+file with your favourite editor.
-package DXMsg;
+<sect1>Updating kepler data
-@forward = (
-'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ],
-'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ],
-'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ],
-'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-);
+<P>
+Spider has a powerful and flexible show/satellite command. In order for
+this to be accurate, the kepler data has to be updated regularly. In
+general, this data is available as an email or via cluster mail.
+Updating it is simple. First you need to export the mail message as a
+file. You do this with the <em>export</em> command from the cluster prompt
+as the sysop. For example ...
+
+<tscreen><verb>
+export 5467 /spider/perl/keps.in
</verb></tscreen>
-Simply insert a bulletin address and state in the brackets where you wish
-that mail to go. For example, you can see here that mail sent to "UK" will
-only be sent to the UK links and not to PA4AB-14.
+would export message number 5467 as a file called keps.in in the
+/spider/perl directory.
-<P>
-To force the cluster to reread the file use load/forward
+Now login to a VT as sysop and cd /spider/perl. There is a command in
+the perl directory called <em>convkeps.pl</em>. All we need to do now is
+convert the file like so ...
-<sect1>Distribution lists
+<tscreen><verb>
+./convkeps.pl keps.in
+</verb></tscreen>
-<P>
-Distribution lists are simply a list of users to send certain types of
-mail to. An example of this is mail you only wish to send to other
-sysops. In /spider/msg there is a directory called <em>distro</em>. You
-put any distibution lists in here. For example, here is a file called
-SYSOP.pl that caters for the UK sysops.
+Now go back to the cluster and issue the command ...
<tscreen><verb>
-qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
- GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
- GB7DXK GB7DXI GB7DXS)
+load/keps
</verb></tscreen>
-Any mail sent to "sysop" would only be sent to the callsigns in this list.
-
-<sect1>Console.pl
-
-<P>
-In later versions of Spider a simple console program is provided for the sysop.
-This has a type ahead buffer with line editing facilities and colour for spots,
-announces etc. To use this program, simply use console.pl instead of client.pl.
+That is it! the kepler data has been updated.
-<P>
-To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
-file with your favourite editor.
<sect>CVS
repository. You do this with the command below ...
<verb>
-cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/DXSpider login
+cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
</verb>
You will get a password prompt. Simply hit return here and your machine should
directory.
<verb>
-cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/DXSpider co spider
+cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
</verb>
This command is all on one line.
You can use any of the following things in this line:-
-<verb>
+<tscreen><verb>
info <string> eg: iota or qsl
by <prefixes> eg: G,M,2
origin <prefixes>
channel <prefixes>
wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX (distros)
-</verb>
+</verb></tscreen>
some examples:-
-<verb>
+<tscreen><verb>
acc/ann dest 6MUK
acc/ann 2 by_zone 14,15,16
(this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
-</verb>
+</verb></tscreen>
or
-<verb>
+<tscreen><verb>
acc/ann by G,M,2
-</verb>
+</verb></tscreen>
This filter would only allow announces that were posted buy UK stations.
You can use the tag 'all' to accept everything eg:
-<verb>
+<tscreen><verb>
acc/ann all
-</verb>
+</verb></tscreen>
but this probably for advanced users...
This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
accept/ann by G,M,2
accept/ann input node_default by G,M,2
accept/ann user_default by G,M,2
-</verb>
+</verb></tscreen>
<sect1>accept/spots (0)
You can use any of the following things in this line:-
-<verb>
+<tscreen><verb>
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
by_zone <numbers>
origin <prefixes>
channel <prefixes>
-</verb>
+</verb></tscreen>
<P>
For frequencies, you can use any of the band names defined in
some examples:-
-<verb>
+<tscreen><verb>
acc/spot 1 on hf/cw
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</verb>
+</verb></tscreen>
You can use the tag 'all' to accept everything, eg:
-<verb>
+<tscreen><verb>
acc/spot 3 all
-</verb>
+</verb></tscreen>
but this probably for advanced users...
This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
accept/spot db0sue-7 1 by_zone 14,15,16
accept/spot node_default all
set/hops node_default 10
accept/spot user_default by G,M,2
-</verb>
+</verb></tscreen>
<sect1>accept/wcy (0)
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
-<verb>
+<tscreen><verb>
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
by_itu <numbers>
by_zone <numbers>
channel <prefixes>
-</verb>
+</verb></tscreen>
<P>
There are no examples because WCY Broadcasts only come from one place and
This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
accept/wcy node_default all
set/hops node_default 10
-</verb>
+</verb></tscreen>
<sect1>accept/wwv (0)
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
-<verb>
+<tscreen><verb>
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
by_itu <numbers>
by_zone <numbers>
channel <prefixes>
-</verb>
+</verb></tscreen>
for example
-<verb>
+<tscreen><verb>
accept/wwv by_zone 4
-</verb>
+</verb></tscreen>
is probably the only useful thing to do (which will only show WWV broadcasts
by stations in the US).
This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
accept/wwv db0sue-7 1 by_zone 4
accept/wwv node_default all
set/hops node_default 10
accept/wwv user_default by W,K
-</verb>
+</verb></tscreen>
<sect1>announce (0)
be ALL the non-private messages. You can prevent this by using these
commmands:-
-<verb>
+<tscreen><verb>
catchup GB7DJK all
catchup GB7DJK 300 301 302 303 500-510
-</verb>
+</verb></tscreen>
and to undo what you have just done:-
-<verb>
+<tscreen><verb>
uncatchup GB7DJK all
uncatchup GB7DJK 300 301 302 303 500-510
-</verb>
+</verb></tscreen>
which will arrange for them to be forward candidates again.
If you have a filter:-
-<verb>
+<tscreen><verb>
acc/spot 1 on hf/cw
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</verb>
+</verb></tscreen>
and you say:-
-<verb>
+<tscreen><verb>
clear/spot 1
-</verb>
+</verb></tscreen>
you will be left with:-
-<verb>
+<tscreen><verb>
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</verb>
+</verb></tscreen>
If you do:
-<verb>
+<tscreen><verb>
clear/spot all
-</verb>
+</verb></tscreen>
the filter will be completely removed.
It is expected that the sysop will add an entry to the local Aliases file
so that users can use the more familiar AK1A style of enquiry such as:
-<verb>
+<tscreen><verb>
SH/BUCK G1TLH
-</verb>
+</verb></tscreen>
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:
-<verb>
+<tscreen><verb>
DBSHOW buck G1TLH
-</verb>
+</verb></tscreen>
<sect1>debug (9)
You can combine some of the various directory commands together eg:-
-<verb>
+<tscreen><verb>
DIR TO G1TLH 5
or
DIR SUBJECT IOTA 200-250
-</verb>
+</verb></tscreen>
You can abbreviate all the commands to one letter and use ak1a syntax:-
-<verb>
+<tscreen><verb>
DIR/T G1* 10
DIR/S QSL 10-100 5
-</verb>
+</verb></tscreen>
<sect1>directory (extended for sysops) (5)
This is how you send a DX Spot to other users. You can, in fact, now
enter the <freq> and the <call> either way round.
-<verb>
+<tscreen><verb>
DX FR0G 144.600
DX 144.600 FR0G
DX 144600 FR0G
-</verb>
+</verb></tscreen>
will all give the same result. You can add some remarks to the end
of the command and they will be added to the spot.
-<verb>
+<tscreen><verb>
DX FR0G 144600 this is a test
-</verb>
+</verb></tscreen>
You can credit someone else by saying:-
-<verb>
+<tscreen><verb>
DX by G1TLH FR0G 144.600 he isn't on the cluster
-</verb>
+</verb></tscreen>
The <freq> is compared against the available bands set up in the
cluster. See SHOW/BANDS for more information.
<sect1>kill full (5)
+<P>
<tt>
<bf>kill full <msgno> [<msgno>]</bf> Delete a message from the
whole cluster
<sect1>load/baddx (9)
+
+<P>
<tt>
<bf>load/baddx</bf> Reload the bad DX table
</tt>
You can use any of the following things in this line:-
-<verb>
+<tscreen><verb>
info <string> eg: iota or qsl
by <prefixes> eg: G,M,2
origin <prefixes>
channel <prefixes>
wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX (distros)
-</verb>
+</verb></tscreen>
some examples:-
-<verb>
+<tscreen><verb>
rej/ann by_zone 14,15,16 and not by G,M,2
-</verb>
+</verb></tscreen>
You can use the tag 'all' to reject everything eg:
-<verb>
+<tscreen><verb>
rej/ann all
-</verb>
+</verb></tscreen>
but this probably for advanced users...
This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
reject/ann by G,M,2
reject/ann input node_default by G,M,2
reject/ann user_default by G,M,2
-</verb>
+</verb></tscreen>
<sect1>reject/spots (0)
</tt>
<P>
-Create an 'reject this spot' line for a filter.
+Create a 'reject this spot' line for a filter.
-An reject filter line means that if the spot matches this filter it is
+A reject filter line means that if the spot matches this filter it is
dumped (not passed on). See HELP FILTERS for 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:-
-<verb>
+<tscreen><verb>
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
by_zone <numbers>
origin <prefixes>
channel <prefixes>
-</verb>
+</verb></tscreen>
For frequencies, you can use any of the band names defined in
SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
some examples:-
-<verb>
+<tscreen><verb>
rej/spot 1 on hf
rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
-</verb>
+</verb></tscreen>
You can use the tag 'all' to reject everything eg:
-<verb>
+<tscreen><verb>
rej/spot 3 all
-</verb>
+</verb></tscreen>
but this probably for advanced users...
This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
reject/spot db0sue-7 1 by_zone 14,15,16
reject/spot node_default all
set/hops node_default 10
reject/spot user_default by G,M,2
-</verb>
+</verb></tscreen>
<sect1>reject/wcy (0)
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
-<verb>
+<tscreen><verb>
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
by_itu <numbers>
by_zone <numbers>
channel <prefixes>
-</verb>
+</verb></tscreen>
There are no examples because WCY Broadcasts only come from one place and
you either want them or not (see UNSET/WCY if you don't want them).
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
-<verb>
+<tscreen><verb>
by <prefixes> eg: G,M,2
origin <prefixes>
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
by_itu <numbers>
by_zone <numbers>
channel <prefixes>
-</verb>
+</verb></tscreen>
for example
-<verb>
+<tscreen><verb>
reject/wwv by_zone 14,15,16
-</verb>
+</verb></tscreen>
is probably the only useful thing to do (which will only show WWV broadcasts
by stations in the US).
<P>This version allows a sysop to set a filter for a callsign as well as the
default for nodes and users eg:-
-<verb>
+<tscreen><verb>
reject/wwv db0sue-7 1 by_zone 4
reject/wwv node_default all
reject/wwv user_default by W
-</verb>
+</verb></tscreen>
<sect1>reply (0)
You can have multiple qualifiers so that you can have for example:-
-<verb>
+<tscreen><verb>
SEND RR COPY 123 PRIVATE G1TLH G0RDI
-</verb>
+</verb></tscreen>
which should send a copy of message 123 to G1TLH and G0RDI and you will
receive a read receipt when they have read the message.
<P>
Set the node_call as an AR-Cluster type node
+<sect1>set/baddx (8)
+
+<P>
+<tt>
+<bf>set/baddx <call></bf> Stop words we do not wish to see in the callsign field
+of a dx spot being propagated
+</tt>
+
+<P>
+Setting a word as 'baddx' will prevent spots with that word in the callsign
+field of a DX spot from going any further. They will not be displayed and they
+will not be sent onto other nodes.
+
+The word must be wriiten in full, no wild cards are allowed eg:-
+
+<tscreen><verb>
+ set/baddx FORSALE VIDEO FR0G
+</verb></tscreen>
+
+To allow a word again, use the following command ...
+
+<tscreen><verb>
+ unset/baddx VIDEO
+</verb></tscreen>
+
<sect1>set/badnode (6)
<P>
The call can be a full or partial call (or a prefix), eg:-
-<verb>
+<tscreen><verb>
set/badnode K1TTT
-</verb>
+</verb></tscreen>
will stop anything from K1TTT (including any SSID's)
-<verb>
+<tscreen><verb>
unset/badnode K1TTT
-</verb>
+</verb></tscreen>
+
+will allow spots from him again.
+
+Use with extreme care. This command may well be superceded by FILTERing.
+
+<sect1>set/badspotter (8)
+
+<P>
+<tt>
+<bf>set/badspotter <call></bf> Stop spots from this callsign being propagated
+</tt>
+
+<P>
+Setting a callsign as a 'badspotter' will prevent spots from this callsign
+going any further. They will not be displayed and they will not be
+sent onto other nodes.
+
+The call must be written in full, no wild cards are allowed eg:-
+
+<tscreen><verb>
+ set/badspotter VE2STN
+</verb></tscreen>
+
+will stop anything from VE2STN. If you want SSIDs as well then you must
+enter them specifically.
+
+<tscreen><verb>
+ unset/badspotter VE2STN
+</verb></tscreen>
will allow spots from him again.
to you will normally find their way there should you not be connected.
eg:-
-<verb>
+<tscreen><verb>
SET/HOMENODE gb7djk
-</verb>
+</verb></tscreen>
<sect1>set/hops (8)
This command allows you to set up special hop counts for a node
for currently: announce, spots, wwv and wcy broadcasts.
-<verb>
+<tscreen><verb>
eg:
set/hops gb7djk ann 10
set/hops gb7mbc spots 20
-</verb>
+</verb></tscreen>
Set SHOW/HOPS for information on what is already set. This command
creates a filter and works in conjunction with the filter system.
You can set your latitude and longitude manually or alternatively use the
<em>set/qra</em> command which will do the conversion for you.
-<verb>
+<tscreen><verb>
set/location 54 04 N 2 02 E
-</verb>
+</verb></tscreen>
<sect1>set/sys_location (9)
what your latitude and longitude is. If you have not yet done a SET/QRA
then this command will set your QRA locator for you. For example:-
-<verb>
+<tscreen><verb>
SET/LOCATION 52 22 N 0 57 E
-</verb>
+</verb></tscreen>
<sect1>set/logininfo (0)
<P>
Tell the cluster what your name is, eg:-
-<verb>
+<tscreen><verb>
set/name Dirk
-</verb>
+</verb></tscreen>
<sect1>set/node (9)
From version 1.41 you can also set the following types of cluster
-<verb>
+<tscreen><verb>
set/spider
set/dxnet
set/clx
set/arcluster
-</verb>
+</verb></tscreen>
To see what your nodes are set to, use the <em>show/nodes</em> command.
of output from a command is more than this. The default is 20. Setting it
explicitly to 0 will disable paging.
-<verb>
+<tscreen><verb>
SET/PAGE 30
SET/PAGE 0
-</verb>
+</verb></tscreen>
The setting is stored in your user profile.
done a SET/LOCATION then your latitude and longitude will be set roughly
correctly (assuming your locator is correct ;-). For example:-
-<verb>
+<tscreen><verb>
SET/QRA JO02LQ
-</verb>
+</verb></tscreen>
<sect1>set/qth (0)
<P>
Tell the system where your are. For example:-
-<verb>
+<tscreen><verb>
set/qth East Dereham, Norfolk
-</verb>
+</verb></tscreen>
<sect1>set/talk (0)
Allow WX information to be seen at your console. You can switch off
WX messages with the <em>unset/wx</em> command.
+<sect1>show/baddx (1)
+
+<P>
+<tt>
+<bf>show/baddx</bf>Show all the bad dx calls in the system
+</tt>
+
+<P>
+Display all the bad dx callsigns in the system, see SET/BADDX
+for more information.
+
<sect1>show/badnode (6)
<P>
Display all the bad node callsigns in the system, see SET/BADNODE
for more information.
+<sect1>show/badspotter (1)
+
+<P>
+<tt>
+<bf>show/badspotter</bf>Show all the bad spotters in the system
+</tt>
+
+<P>
+Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
+for more information.
+
<sect1>show/date (0)
<P>
In addition you can add any number of these options in very nearly
any order to the basic SHOW/DX command, they are:-
-<verb>
+<tscreen><verb>
on <band> - eg 160m 20m 2m 23cm 6mm
on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
qra [<locator>] - this will look for the specific locator if
you specify one or else anything that looks like a locator.
-</verb>
+</verb></tscreen>
e.g.
-<verb>
+<tscreen><verb>
SH/DX 9m0
SH/DX on 20m info iota
SH/DX 9a on vhf day 30
SH/DX iota
SH/DX iota eu-064
SH/DX qra jn86
-</verb>
+</verb></tscreen>
<sect1>show/dxcc (0)
The options for SHOW/DX also apply to this command.
e.g.
-<verb>
+<tscreen><verb>
SH/DXCC G
SH/DXCC W on 20m info iota
-</verb>
+</verb></tscreen>
<sect1>show/files (0)
available on the system. To see the contents of a particular file
area type:-
-<verb>
+<tscreen><verb>
SH/FILES <filearea>
-</verb>
+</verb></tscreen>
where <filearea> is the name of the filearea you want to see the
contents of.
You can also use shell globbing characters like '*' and '?' in a
string to see a selection of files in a filearea eg:-
-<verb>
+<tscreen><verb>
SH/FILES bulletins arld*
-</verb>
+</verb></tscreen>
See also TYPE - to see the contents of a file.
Show a list of callsigns that have been excluded (locked out) of the
cluster locally with the <em>set/lockout</em> command
+<sect1>show/log (8)
+
+<P>
+<tt>
+<bf>show/log [<callsign>]</bf> Show excerpts from the system log
+</tt>
+
+<P>
+This command outputs a short section of the system log. On its own
+it will output a general logfile. With the optional callsign it will
+show output from the log associated with that callsign.
+
<sect1>show/moon (0)
<P>
For example:-
-<verb>
+<tscreen><verb>
SH/MOON
SH/MOON G1TLH W5UN
-</verb>
+</verb></tscreen>
<sect1>show/muf (0)
can specify anything up to 24 hours worth of data by appending the no of
hours required after the prefix. For example:-
-<verb>
+<tscreen><verb>
SH/MUF W
-</verb>
+</verb></tscreen>
produces:
-<verb>
+<tscreen><verb>
RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
Location Lat / Long Azim
UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
18 23 11.5 -35 mS0+ mS2 S3
19 0 11.2 -41 mS0+ mS2 S3
-</verb>
+</verb></tscreen>
indicating that you will have weak, fading circuits on top band and
80m but usable signals on 40m (about S3).
inputing:-
-<verb>
+<tscreen><verb>
SH/MUF W 24
-</verb>
+</verb></tscreen>
will get you the above display, but with the next 24 hours worth of
propagation data.
-<verb>
+<tscreen><verb>
SH/MUF W L 24
SH/MUF W 24 Long
-</verb>
+</verb></tscreen>
Gives you an estimate of the long path propagation characterics. It
should be noted that the figures will probably not be very useful, nor
given on the command line) the distance and beraing from your station
to the locator. For example:-
-<verb>
+<tscreen><verb>
SH/QRA IO92QL
SH/QRA JN06 IN73
-</verb>
+</verb></tscreen>
The first example will show the distance and bearing to the locator from
yourself, the second example will calculate the distance and bearing from
using this command with a latitude and longitude as an argument, for
example:-
-<verb>
+<tscreen><verb>
SH/QRA 52 41 N 0 58 E
-</verb>
+</verb></tscreen>
<sect1>show/qrz (0)
This command allows you to see to which node the callsigns specified are
connected. It is a sort of inverse sh/config.
-<verb>
+<tscreen><verb>
sh/route n2tly
-</verb>
+</verb></tscreen>
<sect1>show/satellite (0)
So for example:-
-<verb>
+<tscreen><verb>
SH/SAT AO-10
SH/SAT FENGYUN1 12 2
-</verb>
+</verb></tscreen>
<sect1>show/sun (0)
For example:-
-<verb>
+<tscreen><verb>
SH/SUN
SH/SUN G1TLH K9CW ZS
-</verb>
+</verb></tscreen>
<sect1>show/time (0)
with others to obscure your reply for any watchers. For example (and
these values are for explanation :-):
-<verb>
+<tscreen><verb>
password = 012345678901234567890123456789
> sysop
22 10 15 17 3
-</verb>
+</verb></tscreen>
you type:-
-<verb>
+<tscreen><verb>
aa2bbbb0ccc5ddd7xxx3n
or 2 0 5 7 3
or 20573
-</verb>
+</verb></tscreen>
They will all match. If there is no password you will still be offered
numbers but nothing will happen when you input a string. Any match is
If you want to do something (such as send a spot) you precede the normal
command with a '/' character, eg:-
-<verb>
+<tscreen><verb>
/DX 14001 G1TLH What's a B class licensee doing on 20m CW?
/HELP talk
-</verb>
+</verb></tscreen>
To leave talk mode type:
-<verb>
+<tscreen><verb>
/EX
-</verb>
+</verb></tscreen>
<sect1>type (0)
filearea 'bulletins' you want to look at file 'arld051' you would
enter:-
-<verb>
+<tscreen><verb>
TYPE bulletins/arld051
-</verb>
+</verb></tscreen>
See also SHOW/FILES to see what fileareas are available and a
list of content.
projects / spider.git / blobdiff