<P>From 1.48 onwards it will become increasingly possible to control DXSpider's
operation with scripts of various kinds.
<P>
-<P>In the first instance, in 1.48, the sysop can create, with their favorite
-text editor, files in the directory <EM>/spider/scripts</EM> which contain
-any legal command for a callsign or class of connection which will be executed
-at logon.
+<P>The directory /spider/scripts is where it all happens and is used for several
+things. Firstly it contains a file called startup that can be used to call
+in any changes to the cluster from the default settings on startup. This
+script is executed immediately after all initialisation of the node is done
+but before any connections are possible. Examples of this include how many
+spots it is possible to get with the sh/dx command, whether you want
+registration/passwords to be permanently on etc. An example file is shown
+below and is included in the distribution as startup.issue.
<P>
-<P>
-The filename is the callsign of the connection that you want the script to
-operate on, eg: <EM>/spider/scripts/g1tlh</EM>. The filenames are always in
-lower case on those architectures where this makes a difference.
+<BLOCKQUOTE><CODE>
+<PRE>
+#
+# 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
+#
+</PRE>
+</CODE></BLOCKQUOTE>
<P>
-<P>In addition to the callsign specific scripts there are three others:-
+<P>As usual, any text behind a # is treated as a comment and not read.
+<P>Secondly, it is used to store the login scripts for users and nodes. Currently
+this can only be done by the sysop but it is envisaged that eventually users will
+be able to set their own. An example is included in the distibution but here is
+a further example.
<P>
<BLOCKQUOTE><CODE>
<PRE>
-startup
-user_default
-node_default
+#
+# G0FYD
+#
+blank +
+sh/wwv 3
+blank +
+sh/dx
+blank +
+t g0jhc You abt?
+blank +
</PRE>
</CODE></BLOCKQUOTE>
-<P>The <EM>startup</EM> script is executed immediately after all
-initialisation of the node is done, but before any connections are
-possible.
-<P>
-<P>The <EM>user_default</EM> script is executed for every user that does
-<B>NOT</B> already have a specific script.
+<P>The lines in between commands can simply insert a blank line or a character
+such as a + sign to make the output easier to read. Simply create this script
+with your favourite editor and save it with the callsign of the user as the
+filename. Filenames should always be in lower case.
<P>
-<P>The <EM>node_default</EM> script is executed for every node that doesn't
-have a specific script.
+<P>Commands can be inserted in the same way for nodes. A node may wish a series
+of commands to be issued on login, such as a merge command for example.
<P>
-<P>There are a couple of examples in the <EM>/spider/scripts</EM> directory.
+<P>Thirdly, there are 2 default scripts for users and nodes who do not have a
+specifically defined script. These are <EM>user_default</EM> and
+<EM>node_default</EM>
<P>
<HR>
<A HREF="adminmanual-5.html">Next</A>
the setup. Many thanks to Fred Lloyd, the proprieter of
<A HREF="http://www.qrz.com">qrz.com</A> for allowing this access.
<P>
-<H2><A NAME="ss6.9">6.9 Scripts</A>
-</H2>
-
-<P>The directory /spider/scripts is used for several things. Firstly it
-contains a file called startup that can be used to call in any changes
-to the cluster from the default settings on startup. Examples of this
-include how many spots it is possible to get with the sh/dx command,
-whether you want registration/passwords to be permanently on etc. An
-example file is shown below and is included in the distribution as
-startup.issue.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-#
-# 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
-#
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Secondly, it is used to store the login scripts for users. Currently
-this can only be done by the sysop but it is envisaged that eventually
-users will be able to set their own. An example is included in the
-distibution but here is a further example.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-#
-# G0FYD
-#
-blank +
-sh/wwv 3
-blank +
-sh/dx
-blank +
-t g0jhc You abt?
-blank +
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>The lines in between commands can simply insert a blank line or a character
-such as a + sign to make the output easier to read.
-<P>
<HR>
<A HREF="adminmanual-7.html">Next</A>
<A HREF="adminmanual-5.html">Previous</A>
<P>which will arrange for them to be forward candidates again.
<P>Order is not important.
<P>
-<H2><A NAME="ss9.16">9.16 clear/spots (0)</A>
+<H2><A NAME="ss9.16">9.16 clear/announce (8)</A>
+</H2>
+
+<P><CODE><B>clear/announce [input] <callsign> [0-9|all]</B> Clear an announce filter line</CODE>
+<P>
+<P>A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
+<P>
+<H2><A NAME="ss9.17">9.17 clear/route (8)</A>
+</H2>
+
+<P><CODE><B>clear/route [input] ^lt;callsign> [0-9|all]</B> Clear a route filter line</CODE>
+<P>
+<P>This command allows you to clear (remove) a line in a route filter or to
+remove the whole filter.
+<P>see CLEAR/SPOTS for a more detailed explanation.
+<P>A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
+<P>
+<H2><A NAME="ss9.18">9.18 clear/spots (0)</A>
</H2>
<P><CODE><B>clear/spots [1|all]</B> Clear a spot filter line</CODE>
</CODE></BLOCKQUOTE>
<P>the filter will be completely removed.
<P>
+<H2><A NAME="ss9.19">9.19 clear/spots (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>clear/spots [input] <callsign> [0-9|all]</B> Clear a spot filter line</CODE>
+<P>
+<P>A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
+<P>
+<H2><A NAME="ss9.20">9.20 clear/wcy (0)</A>
+</H2>
+
+<P><CODE><B>clear/wcy [1|all]</B> Clear a WCY filter line</CODE>
+<P>
+<P>This command allows you to clear (remove) a line in a WCY filter or to
+remove the whole filter.
+<P>see CLEAR/SPOTS for a more detailed explanation.
+<P>
+<H2><A NAME="ss9.21">9.21 clear/wcy (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>clear/wcy [input] <callsign> [0-9|all]</B> Clear a WCY filter line</CODE>
+<P>
+<P>A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
+<P>
+<H2><A NAME="ss9.22">9.22 clear/wwv (0)</A>
+</H2>
+
+<P><CODE><B>clear/wwv [1|all]</B> Clear a WWV filter line</CODE>
+<P>
+<P>This command allows you to clear (remove) a line in a WWV filter or to
+remove the whole filter.
+<P>see CLEAR/SPOTS for a more detailed explanation.
<P>
-<H2><A NAME="ss9.17">9.17 connect (5) </A>
+<H2><A NAME="ss9.23">9.23 clear/wwv (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>clear/wwv [input] <callsign> [0-9|all]</B> Clear a WWV filter line</CODE>
+<P>
+<P>A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
+<P>
+<H2><A NAME="ss9.24">9.24 connect (5) </A>
</H2>
<P><CODE><B>connect <callsign></B> Start a connection to another DX Cluster</CODE>
use the script in /spider/connect/<callsign> to effect the 'chat' exchange
necessary to traverse the network(s) to logon to the cluster <callsign>.
<P>
-<H2><A NAME="ss9.18">9.18 dbavail (0)</A>
+<H2><A NAME="ss9.25">9.25 dbavail (0)</A>
</H2>
<P><CODE><B>dbavail</B> Show a list of all the databases in the system</CODE>
<P>The title says it all really, this command lists all the databases defined
in the system. It is also aliased to SHOW/COMMAND.
<P>
-<H2><A NAME="ss9.19">9.19 dbcreate (9)</A>
+<H2><A NAME="ss9.26">9.26 dbcreate (9)</A>
</H2>
<P><CODE><B>dbcreate <name></B> Create a database entry<BR>
<P>See DBIMPORT for the importing of existing AK1A format data to databases.
See DBSHOW for generic database enquiry
<P>
-<H2><A NAME="ss9.20">9.20 dbimport (9)</A>
+<H2><A NAME="ss9.27">9.27 dbimport (9)</A>
</H2>
<P><CODE><B>dbimport <dbname></B> Import AK1A data into a database</CODE>
<P>will import the standard OBLAST database that comes with AK1A into the
oblast database held locally.
<P>
-<H2><A NAME="ss9.21">9.21 dbremove (9)</A>
+<H2><A NAME="ss9.28">9.28 dbremove (9)</A>
</H2>
<P><CODE><B>dbremove <dbname></B> Delete a database</CODE>
<P>There is no warning, no comeback, no safety net.
<P>You have been warned.
<P>
-<H2><A NAME="ss9.22">9.22 dbshow (0)</A>
+<H2><A NAME="ss9.29">9.29 dbshow (0)</A>
</H2>
<P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE>
</CODE></BLOCKQUOTE>
<P>
<P>
-<H2><A NAME="ss9.23">9.23 debug (9)</A>
+<H2><A NAME="ss9.30">9.30 debug (9)</A>
</H2>
<P><CODE><B>debug</B> Set the cluster program into debug mode</CODE>
</CODE></BLOCKQUOTE>
<P>It will interrupt the cluster just after the debug command has finished.
<P>
-<H2><A NAME="ss9.24">9.24 directory (0)</A>
+<H2><A NAME="ss9.31">9.31 delete/user (9)</A>
+</H2>
+
+<P><CODE><B>delete/user <callsign></B> Delete a user from the User Database</CODE>
+<P>
+<P>This command will completely remove a one or more users from the database.
+<P>There is NO SECOND CHANCE.
+<P>It goes without saying that you should use this command CAREFULLY!
+<P>
+<P>
+<H2><A NAME="ss9.32">9.32 directory (0)</A>
</H2>
<P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
</CODE></BLOCKQUOTE>
<P>
<P>
-<H2><A NAME="ss9.25">9.25 directory (extended for sysops) (5)</A>
+<H2><A NAME="ss9.33">9.33 directory (extended for sysops) (5)</A>
</H2>
<P>Works just like the user command except that sysops can see ALL messages.
<P>
-<H2><A NAME="ss9.26">9.26 disconnect (8)</A>
+<H2><A NAME="ss9.34">9.34 disconnect (8)</A>
</H2>
<P><CODE><B>disconnect <call> [<call> ...]</B> Disconnect a user or node</CODE>
<P>
<P>Disconnect any <call> connected locally
<P>
-<H2><A NAME="ss9.27">9.27 dx (0)</A>
+<H2><A NAME="ss9.35">9.35 dx (0)</A>
</H2>
<P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE>
<P>The <freq> is compared against the available bands set up in the
cluster. See SHOW/BANDS for more information.
<P>
-<H2><A NAME="ss9.28">9.28 export (9)</A>
+<H2><A NAME="ss9.36">9.36 export (9)</A>
</H2>
<P><CODE><B>export <msgno> <filename></B> Export a message to a file</CODE>
access. For example:-
<P>EXPORT 2345 /tmp/a
<P>
-<H2><A NAME="ss9.29">9.29 export_users (9)</A>
+<H2><A NAME="ss9.37">9.37 export_users (9)</A>
</H2>
<P><CODE><B>export_users [<filename>]</B> Export the users database to ascii</CODE>
<P>BE WARNED: this will write to any file you have write access to. No check is
made on the filename (if any) that you specify.
<P>
-<H2><A NAME="ss9.30">9.30 forward/latlong (8)</A>
+<H2><A NAME="ss9.38">9.38 filtering (0)</A>
+</H2>
+
+<P><CODE><B>filtering</B> Filtering things in DXSpider</CODE>
+<P>
+<P>There are a number of things you can filter in the DXSpider system. They
+all use the same general mechanism.
+<P>In general terms you can create a 'reject' or an 'accept' filter which
+can have up to 10 lines in it. You do this using, for example:-
+<P>accept/spots .....
+reject/spots .....
+<P>where ..... are the specific commands for that type of filter. There
+are filters for spots, wwv, announce, wcy and (for sysops)
+connects. See each different accept or reject command reference for
+more details.
+<P>There is also a command to clear out one or more lines in a filter and
+one to show you what you have set. They are:-
+<P>clear/spots 1
+clear/spots all
+<P>and
+<P>show/filter
+<P>There is clear/xxxx command for each type of filter.
+<P>For now we are going to use spots for the examples, but you can apply
+the principles to all types of filter.
+<P>There are two main types of filter 'accept' or 'reject'; which you use
+depends entirely on how you look at the world and what is least
+writing to achieve what you want. Each filter has 10 lines (of any
+length) which are tried in order. If a line matches then the action
+you have specified is taken (ie reject means ignore it and accept
+means gimme it).
+<P>The important thing to remember is that if you specify a 'reject'
+filter (all the lines in it say 'reject/spots' (for instance) then if
+a spot comes in that doesn't match any of the lines then you will get
+it BUT if you specify an 'accept' filter then any spots that don't
+match are dumped. For example if I have a one line accept filter:-
+<P>accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+<P>then automatically you will ONLY get VHF spots from or to CQ zones 14
+15 and 16. If you set a reject filter like:
+<P>reject/spots on hf/cw
+<P>Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
+and will work it even on CW then you could say:-
+<P>reject/spots on hf/cw and not info iota
+<P>But in that case you might only be interested in iota and say:-
+<P>accept/spots not on hf/cw or info iota
+<P>which is exactly the same. You should choose one or the other until
+you are confortable with the way it works. Yes, you can mix them
+(actually you can have an accept AND a reject on the same line) but
+don't try this at home until you can analyse the results that you get
+without ringing up the sysop for help.
+<P>You can arrange your filter lines into logical units, either for your
+own understanding or simply convenience. I have one set frequently:-
+<P>reject/spots 1 on hf/cw
+reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
+<P>What this does is to ignore all HF CW spots (being a class B I can't
+read any CW and couldn't possibly be interested in HF :-) and also
+rejects any spots on VHF which don't either originate or spot someone
+in Europe.
+<P>This is an exmaple where you would use the line number (1 and 2 in
+this case), if you leave the digit out, the system assumes '1'. Digits
+'0'-'9' are available.
+<P>You can leave the word 'and' out if you want, it is implied. You can
+use any number of brackets to make the 'expression' as you want
+it. There are things called precedence rules working here which mean
+that you will NEED brackets in a situation like line 2 because,
+without it, will assume:-
+<P>(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+<P>annoying, but that is the way it is. If you use OR - use
+brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
+just 'and by_zone'.
+<P>If you want to alter your filter you can just redefine one or more
+lines of it or clear out one line. For example:-
+<P>reject/spots 1 on hf/ssb
+<P>or
+<P>clear/spots 1
+<P>To remove the filter in its entirty:-
+<P>clear/spots all
+<P>There are similar CLEAR commands for the other filters:-
+<P>clear/announce
+clear/wcy
+clear/wwv
+<P>ADVANCED USERS:-
+<P>Once you are happy with the results you get, you may like to experiment.
+<P>my example that filters hf/cw spots and accepts vhf/uhf spots from EU
+can be written with a mixed filter, eg:
+<P>rej/spot on hf/cw
+acc/spot on 0/30000
+acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+<P>each filter slot actually has a 'reject' slot and an 'accept'
+slot. The reject slot is executed BEFORE the accept slot.
+<P>It was mentioned earlier that after a reject test that doesn't match,
+the default for following tests is 'accept', the reverse is true for
+'accept'. In the example what happens is that the reject is executed
+first, any non hf/cw spot is passed to the accept line, which lets
+thru everything else on HF.
+<P>The next filter line lets through just VHF/UHF spots from EU.
+<P>
+<H2><A NAME="ss9.39">9.39 forward/latlong (8)</A>
</H2>
<P><CODE><B>forward/latlong <node_call></B> Send latitude and longitude information to another cluster</CODE>
<EM>set/dxgrid</EM> enabled. This could be a LOT of information though, so
it is not recommended on slow links.
<P>
-<H2><A NAME="ss9.31">9.31 forward/opername (1)</A>
+<H2><A NAME="ss9.40">9.40 forward/opername (1)</A>
</H2>
<P><CODE><B>forward/opername <call></B> Send out information on this <call> to all clusters</CODE>
be broadcast in PC41 protocol packets. This information is Name, QTH, Location
and Homenode. PC41s are only sent for the information that is available.
<P>
-<H2><A NAME="ss9.32">9.32 help (0)</A>
+<H2><A NAME="ss9.41">9.41 help (0)</A>
</H2>
<P><CODE><B>help <cmd></B> Get help on a command</CODE>
for the <string> you specify and give you a list of likely commands
to look at with HELP.
<P>
-<H2><A NAME="ss9.33">9.33 init (5)</A>
+<H2><A NAME="ss9.42">9.42 init (5)</A>
</H2>
<P><CODE><B>init <node call></B> Re-initialise a link to an AK1A compatible node</CODE>
node>).
<P>Best of luck - you will need it.
<P>
-<H2><A NAME="ss9.34">9.34 kill (0)</A>
+<H2><A NAME="ss9.43">9.43 kill (0)</A>
</H2>
<P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE>
delete messages that you have originated or been sent (unless you are
the sysop).
<P>
-<H2><A NAME="ss9.35">9.35 kill (5)</A>
+<H2><A NAME="ss9.44">9.44 kill (5)</A>
</H2>
<P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system<BR>
this command. You can remove more than one message at a time.
<P>As a sysop you can kill any message on the system.
<P>
-<H2><A NAME="ss9.36">9.36 kill full (5)</A>
+<H2><A NAME="ss9.45">9.45 kill full (5)</A>
</H2>
<P><CODE><B>kill full <msgno> [<msgno>]</B> Delete a message from the whole cluster</CODE>
<P>This uses the subject field, so any messages that have exactly the same subject
will be deleted. Beware!
<P>
-<H2><A NAME="ss9.37">9.37 links (0)</A>
+<H2><A NAME="ss9.46">9.46 kill/expunge (6)</A>
+</H2>
+
+<P><CODE><B>kill/expunge <msgno> [<msgno>..]</B>Expunge a message</CODE>
+<P>
+<P>Deleting a message using the normal KILL commands only marks that message
+for deletion. The actual deletion only happens later (usually two days later).
+<P>The KILL EXPUNGE command causes the message to be truly deleted more or less
+immediately.
+<P>It otherwise is used in the same way as the KILL command.
+<P>
+<P>
+<H2><A NAME="ss9.47">9.47 links (0)</A>
</H2>
<P><CODE><B>links</B> Show which nodes are physically connected</CODE>
some information about them. See WHO for a list of all connections.
<P>
<P>
-<H2><A NAME="ss9.38">9.38 load/aliases (9)</A>
+<H2><A NAME="ss9.48">9.48 load/aliases (9)</A>
</H2>
<P><CODE><B>load/aliases</B> Reload the command alias table</CODE>
do this if you change this file whilst the cluster is running in order for the
changes to take effect.
<P>
-<H2><A NAME="ss9.39">9.39 load/badmsg (9)</A>
+<H2><A NAME="ss9.49">9.49 load/badmsg (9)</A>
</H2>
<P><CODE><B>load/badmsg</B> Reload the bad message table</CODE>
expressions which are searched for in the fields targetted of each message.
If any of them match then that message is immediately deleted on receipt.
<P>
-<H2><A NAME="ss9.40">9.40 load/bands (9)</A>
+<H2><A NAME="ss9.50">9.50 load/badwords (9)</A>
+</H2>
+
+<P><CODE><B>load/badwords</B> Reload the bad words table</CODE>
+<P>
+<P>Reload the /spider/data/badwords file if you have changed it manually whilst
+the cluster is running. This file contains a list of words which, if found
+on certain text portions of PC protocol, will cause those protocol frames
+to be rejected. It will all put out a message if any of these words are
+used on the announce, dx and talk commands. The words can be one or
+more on a line, lines starting with '#' are ignored.
+<P>
+<H2><A NAME="ss9.51">9.51 load/bands (9)</A>
</H2>
<P><CODE><B>load/bands</B> Reload the band limits table</CODE>
<P>Reload the /spider/data/bands.pl file if you have changed it manually whilst
the cluster is running.
<P>
-<H2><A NAME="ss9.41">9.41 load/cmd_cache (9)</A>
+<H2><A NAME="ss9.52">9.52 load/cmd_cache (9)</A>
</H2>
<P><CODE><B>load/cmd_cache</B> Reload the automatic command cache</CODE>
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.
<P>
-<H2><A NAME="ss9.42">9.42 load/forward (9)</A>
+<H2><A NAME="ss9.53">9.53 load/forward (9)</A>
</H2>
<P><CODE><B>load/forward</B> Reload the msg forwarding routing table</CODE>
<P>Reload the /spider/msg/forward.pl file if you have changed it
manually whilst the cluster is running.
<P>
-<H2><A NAME="ss9.43">9.43 load/messages (9)</A>
+<H2><A NAME="ss9.54">9.54 load/messages (9)</A>
</H2>
<P><CODE><B>load/messages</B> Reload the system messages file</CODE>
command. You need to do this if get something like :-
<P>unknown message 'xxxx' in lang 'en'
<P>
-<H2><A NAME="ss9.44">9.44 load/prefixes (9)</A>
+<H2><A NAME="ss9.55">9.55 load/prefixes (9)</A>
</H2>
<P><CODE><B>load/prefixes</B> Reload the prefix table</CODE>
<P>Reload the /spider/data/prefix_data.pl file if you have changed it manually
whilst the cluster is running.
<P>
-<H2><A NAME="ss9.45">9.45 merge (5)</A>
+<H2><A NAME="ss9.56">9.56 merge (5)</A>
</H2>
<P><CODE><B>merge <node> [<no spots>/<no wwv>]</B> Ask for the latest spots and WWV</CODE>
to your databases they will not duplicate any that have recently been added
(the last 2 days for spots and last month for WWV data).
<P>
-<H2><A NAME="ss9.46">9.46 msg (9)</A>
+<H2><A NAME="ss9.57">9.57 msg (9)</A>
</H2>
<P><CODE><B>msg <cmd> <msgno> [data ...]</B> Alter various message parameters</CODE>
<P>STAT/MSG <msgno>
<P>This will display more information on the message than DIR does.
<P>
-<H2><A NAME="ss9.47">9.47 pc (8)</A>
+<H2><A NAME="ss9.58">9.58 pc (8)</A>
</H2>
<P><CODE><B>pc <call> <text></B> Send text (eg PC Protocol) to <call></CODE>
without any processing, added of "from <blah> to <blah>" or whatever.
<P>pc G1TLH Try doing that properly!!!
<P>
-<H2><A NAME="ss9.48">9.48 ping (1)</A>
+<H2><A NAME="ss9.59">9.59 ping (1)</A>
</H2>
<P><CODE><B>ping <node></B> Check the link quality between nodes</CODE>
Any visible cluster node can be PINGed.
<P>
<P>
-<H2><A NAME="ss9.49">9.49 rcmd (1)</A>
+<H2><A NAME="ss9.60">9.60 rcmd (1)</A>
</H2>
<P><CODE><B>rcmd <node call> <cmd></B> Send a command to another DX cluster</CODE>
other system is allowing RCMDs from this node and c) whether you have
permission to send this command at all.
<P>
-<H2><A NAME="ss9.50">9.50 read (0)</A>
+<H2><A NAME="ss9.61">9.61 read (0)</A>
</H2>
<P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
message either sent by or sent to your callsign.
<P>
<P>
-<H2><A NAME="ss9.51">9.51 read (extended for sysops) (5) </A>
+<H2><A NAME="ss9.62">9.62 read (extended for sysops) (5) </A>
</H2>
<P><CODE><B>read <msgno></B> Read a message on the system</CODE>
<P>
<P>As a sysop you may read any message on the system
<P>
-<H2><A NAME="ss9.52">9.52 reject/announce</A>
+<H2><A NAME="ss9.63">9.63 reject/announce</A>
</H2>
<P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
</CODE></BLOCKQUOTE>
<P>but this probably for advanced users...
<P>
-<H2><A NAME="ss9.53">9.53 reject/announce (extended for sysops) (8)</A>
+<H2><A NAME="ss9.64">9.64 reject/announce (extended for sysops) (8)</A>
</H2>
<P><CODE><B>reject/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.54">9.54 reject/route (8)</A>
+<H2><A NAME="ss9.65">9.65 reject/route (8)</A>
</H2>
<P><CODE><B>reject/route <call> [0-9] <pattern></B> Set an 'reject' filter line for routing</CODE>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.55">9.55 reject/spots (0)</A>
+<H2><A NAME="ss9.66">9.66 reject/spots (0)</A>
</H2>
<P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE>
</CODE></BLOCKQUOTE>
<P>but this probably for advanced users...
<P>
-<H2><A NAME="ss9.56">9.56 reject/spots (extended for sysops) (8)</A>
+<H2><A NAME="ss9.67">9.67 reject/spots (extended for sysops) (8)</A>
</H2>
<P><CODE><B>reject/spots <call> [input] [0-9] <pattern></B>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.57">9.57 reject/wcy (0)</A>
+<H2><A NAME="ss9.68">9.68 reject/wcy (0)</A>
</H2>
<P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE>
<P>This command is really provided for future use.
<P>See HELP FILTER for information.
<P>
-<H2><A NAME="ss9.58">9.58 reject/wcy (extended for sysops) (8)</A>
+<H2><A NAME="ss9.69">9.69 reject/wcy (extended for sysops) (8)</A>
</H2>
<P><CODE><B>reject/wcy <call> [input] [0-9] <pattern></B>
default for nodes and users eg:-
<P>reject/wcy gb7djk all
<P>
-<H2><A NAME="ss9.59">9.59 reject/wwv (0)</A>
+<H2><A NAME="ss9.70">9.70 reject/wwv (0)</A>
</H2>
<P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE>
by stations in the US).
<P>See HELP FILTER for information.
<P>
-<H2><A NAME="ss9.60">9.60 reject/wwv (extended for sysops) (8)</A>
+<H2><A NAME="ss9.71">9.71 reject/wwv (extended for sysops) (8)</A>
</H2>
<P><CODE><B>reject/wwv <call> [input] [0-9] <pattern></B>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.61">9.61 reply (0)</A>
+<H2><A NAME="ss9.72">9.72 reply (0)</A>
</H2>
<P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
NOPRIVATE, B that you can use with the SEND command (see SEND
for further details)
<P>
-<H2><A NAME="ss9.62">9.62 send (0)</A>
+<H2><A NAME="ss9.73">9.73 send (0)</A>
</H2>
<P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
<P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
SP is an alias for SEND PRIVATE
<P>
-<H2><A NAME="ss9.63">9.63 set/address (0)</A>
+<H2><A NAME="ss9.74">9.74 set/address (0)</A>
</H2>
<P><CODE><B>set/address <your_address></B> Record your postal address</CODE>
<P>
<P>Literally, record your address details on the cluster.
<P>
-<H2><A NAME="ss9.64">9.64 set/announce (0)</A>
+<H2><A NAME="ss9.75">9.75 set/announce (0)</A>
</H2>
<P><CODE><B>set/announce</B> Allow announce messages</CODE>
<P>
<P>Allow announce messages to arrive at your terminal.
<P>
-<H2><A NAME="ss9.65">9.65 set/arcluster (5)</A>
+<H2><A NAME="ss9.76">9.76 set/arcluster (5)</A>
</H2>
<P><CODE><B>set/arcluster <node_call> [<node_call> ...]</B> Make
<P>
<P>Set the node_call as an AR-Cluster type node
<P>
-<H2><A NAME="ss9.66">9.66 set/baddx (8)</A>
+<H2><A NAME="ss9.77">9.77 set/baddx (8)</A>
</H2>
<P><CODE><B>set/baddx <call></B> Stop words we do not wish to see in the callsign field
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.67">9.67 set/badnode (6)</A>
+<H2><A NAME="ss9.78">9.78 set/badnode (6)</A>
</H2>
<P><CODE><B>set/badnode <node_call></B> Stop spots from this node_call
<P>will allow spots from him again.
<P>Use with extreme care. This command may well be superceded by FILTERing.
<P>
-<H2><A NAME="ss9.68">9.68 set/badspotter (8)</A>
+<H2><A NAME="ss9.79">9.79 set/badspotter (8)</A>
</H2>
<P><CODE><B>set/badspotter <call></B> Stop spots from this callsign being propagated</CODE>
<P>will allow spots from him again.
<P>Use with extreme care. This command may well be superceded by FILTERing.
<P>
-<H2><A NAME="ss9.69">9.69 set/beep (0)</A>
+<H2><A NAME="ss9.80">9.80 set/badword (8)</A>
+</H2>
+
+<P><CODE><B>set/badword <word></B> Stop things with this word being propogated</CODE>
+<P>
+<P>Setting a word as a 'badword' will prevent things like spots,
+announces or talks with this word in the the text part from going any
+further. They will not be displayed and they will not be sent onto
+other nodes.
+<P>The word must be written in full, no wild cards are allowed eg:-
+<P>set/badword annihilate annihilated annihilation
+<P>will stop anything with these words in the text.
+<P>unset/badword annihilated
+<P>will allow text with this word again.
+<P>
+<P>
+<H2><A NAME="ss9.81">9.81 set/beep (0)</A>
</H2>
<P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE>
<P>
<P>Add a beep to DX and other terminal messages.
<P>
-<H2><A NAME="ss9.70">9.70 set/bbs (5)</A>
+<H2><A NAME="ss9.82">9.82 set/bbs (5)</A>
</H2>
<P><CODE><B>set/bbs <call> [<call>..]</B>Make <call> a BBS</CODE>
<P>
-<H2><A NAME="ss9.71">9.71 set/clx (5)</A>
+<H2><A NAME="ss9.83">9.83 set/clx (5)</A>
</H2>
<P><CODE><B>set/clx <node_call> [<node_call> ...]</B> Make
<P>
<P>Set the node_call as a CLX type node
<P>
-<H2><A NAME="ss9.72">9.72 set/debug (9)</A>
+<H2><A NAME="ss9.84">9.84 set/debug (9)</A>
</H2>
<P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE>
command.
<P>You can remove a debug level with unset/debug <name>
<P>
-<H2><A NAME="ss9.73">9.73 set/dx (0)</A>
+<H2><A NAME="ss9.85">9.85 set/dx (0)</A>
</H2>
<P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE>
<P>
<P>You can stop DX messages with the <EM>unset/dx</EM> command
<P>
-<H2><A NAME="ss9.74">9.74 set/dxgrid (0)</A>
+<H2><A NAME="ss9.86">9.86 set/dxgrid (0)</A>
</H2>
<P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE>
the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
command to remove the grid squares.
<P>
-<H2><A NAME="ss9.75">9.75 set/dxnet (5)</A>
+<H2><A NAME="ss9.87">9.87 set/dxnet (5)</A>
</H2>
<P><CODE><B>set/dxnet <node_call> [<node_call> ...]</B> Make
<P>
<P>Set the node_call as a DXNet type node
<P>
-<H2><A NAME="ss9.76">9.76 set/echo (0)</A>
+<H2><A NAME="ss9.88">9.88 set/echo (0)</A>
</H2>
<P><CODE><B>set/echo</B> Make the cluster echo your input</CODE>
<P>The setting is stored in your user profile.
<P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
<P>
-<H2><A NAME="ss9.77">9.77 set/here (0)</A>
+<H2><A NAME="ss9.89">9.89 set/email (0)</A>
+</H2>
+
+<P><CODE><B>set/email <email_address></B> Set email address(es) and forward your personals</CODE>
+<P>
+<P>If any personal messages come in for your callsign then you can use
+these commands to control whether they are forwarded onto your email
+address. To enable the forwarding do something like:-
+<P>SET/EMAIL mike.tubby@somewhere.com
+<P>You can have more than one email address (each one separated by a space).
+Emails are forwarded to all the email addresses you specify.
+<P>You can disable forwarding by:-
+<P>UNSET/EMAIL
+<P>
+<H2><A NAME="ss9.90">9.90 set/here (0)</A>
</H2>
<P><CODE><B>set/here</B> Set the here flag</CODE>
command to let people know you are away. This simply puts brackets
around your callsign to indicate you are not available.
<P>
-<H2><A NAME="ss9.78">9.78 set/homenode (0)</A>
+<H2><A NAME="ss9.91">9.91 set/homenode (0)</A>
</H2>
<P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.79">9.79 set/hops (8)</A>
+<H2><A NAME="ss9.92">9.92 set/hops (8)</A>
</H2>
<P><CODE><B>set/hops <node_call> ann|spots|wwv|wcy <n></B>
<P>Set SHOW/HOPS for information on what is already set. This command
creates a filter and works in conjunction with the filter system.
<P>
-<H2><A NAME="ss9.80">9.80 set/isolate (9)</A>
+<H2><A NAME="ss9.93">9.93 set/isolate (9)</A>
</H2>
<P><CODE><B>set/isolate <node call></B> Isolate a node from the rest of the network</CODE>
<P>You can see which nodes are isolated with the show/isolate (1) command.
<P>You can remove the isolation with the command unset/isolate.
<P>
-<H2><A NAME="ss9.81">9.81 set/language (0)</A>
+<H2><A NAME="ss9.94">9.94 set/language (0)</A>
</H2>
<P><CODE><B>set/language <language></B> Set the language you wish to use</CODE>
<P>You can select the language that you want the cluster to use. Currently
the languages available are <EM>en</EM> (English) and <EM>nl</EM> (Dutch).
<P>
-<H2><A NAME="ss9.82">9.82 set/location (0)</A>
+<H2><A NAME="ss9.95">9.95 set/location (0)</A>
</H2>
<P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE>
</CODE></BLOCKQUOTE>
<P>
<P>
-<H2><A NAME="ss9.83">9.83 set/sys_location (9)</A>
+<H2><A NAME="ss9.96">9.96 set/sys_location (9)</A>
</H2>
<P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.84">9.84 set/logininfo (0)</A>
+<H2><A NAME="ss9.97">9.97 set/logininfo (0)</A>
</H2>
<P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE>
can stop these messages by using the <EM>unset/logininfo</EM> command.
<P>
<P>
-<H2><A NAME="ss9.85">9.85 set/lockout (9)</A>
+<H2><A NAME="ss9.98">9.98 set/lockout (9)</A>
</H2>
<P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE>
<P>You can show who is locked out with the <EM>show/lockout</EM> command.
To allow the user to connect again, use the <EM>unset/lockout</EM> command.
<P>
-<H2><A NAME="ss9.86">9.86 set/name (0)</A>
+<H2><A NAME="ss9.99">9.99 set/name (0)</A>
</H2>
<P><CODE><B>set/name <your_name></B> Set your name</CODE>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.87">9.87 set/node (9)</A>
+<H2><A NAME="ss9.100">9.100 set/node (9)</A>
</H2>
<P><CODE><B>set/node <call> [<call> ...]</B> Make the callsign an AK1A cluster</CODE>
</CODE></BLOCKQUOTE>
<P>To see what your nodes are set to, use the <EM>show/nodes</EM> command.
<P>
-<H2><A NAME="ss9.88">9.88 set/obscount (9)</A>
+<H2><A NAME="ss9.101">9.101 set/obscount (9)</A>
</H2>
<P><CODE><B>set/obscount <count> <node call></B> Set the 'pump-up' obsolescence counter</CODE>
default values, if a node has not responded to a ping within 15 minutes,
it is disconnected.
<P>
-<H2><A NAME="ss9.89">9.89 set/page (0)</A>
+<H2><A NAME="ss9.102">9.102 set/page (0)</A>
</H2>
<P><CODE><B>set/page <n></B> Set the number of lines per page</CODE>
</CODE></BLOCKQUOTE>
<P>The setting is stored in your user profile.
<P>
+<H2><A NAME="ss9.103">9.103 set/password (0)</A>
+</H2>
+
+<P><CODE><B>set/password</B> Set your own password</CODE>
+<P>
+<P>This command only works for a 'telnet' user (currently). It will
+only work if you have a password already set. This initial password
+can only be set by the sysop.
+<P>When you execute this command it will ask you for your old password,
+then ask you to type in your new password twice (to make sure you
+get it right). You may or may not see the data echoed on the screen
+as you type, depending on the type of telnet client you have.
<P>
-<H2><A NAME="ss9.90">9.90 set/password (9)</A>
+<H2><A NAME="ss9.104">9.104 set/password (9)</A>
</H2>
<P><CODE><B>set/password <callsign> <string></B> Set a users password</CODE>
<P>
<P>The password for a user can only be set by a full sysop. The string
-can contain any characters but any spaces are removed (you can type in
-spaces - but they won't appear in the password). You can see the
-result with STAT/USER. The password is the usual 30 character baycom
-type password.
-<P>
-<H2><A NAME="ss9.91">9.91 set/pinginterval (9)</A>
+can contain any characters.
+<P>The way this field is used depends on context. If it is being used in
+the SYSOP command context then you are offered 5 random numbers and you
+have to supply the corresponding letters. This is now mainly for ax25
+connections.
+<P>If it is being used on incoming telnet connections then, if a password
+is set or the:
+<P>set/var $main::passwdreq = 1
+<P>command is executed in the startup script, then a password prompt is
+given after the normal 'login: ' prompt.
+<P>The command "unset/password" is provided to allow a sysop to remove a
+users password completely in case a user forgets or loses their password.
+<P>
+<H2><A NAME="ss9.105">9.105 set/pinginterval (9)</A>
</H2>
<P><CODE><B>set/pinginterval <time> <node call></B> Set the ping time to neighbouring nodes</CODE>
(as certain cluster software doesn't always notice), see SET/OBSCOUNT
for more information.
<P>
-<H2><A NAME="ss9.92">9.92 set/privilege (9)</A>
+<H2><A NAME="ss9.106">9.106 set/privilege (9)</A>
</H2>
<P><CODE><B>set/privilege <n> <call> [<call> ...]</B> Set the privilege level on a call</CODE>
<P>If you are a sysop and you come in as a normal user on a remote connection
your privilege will automatically be set to 0.
<P>
-<H2><A NAME="ss9.93">9.93 set/spider (5)</A>
+<H2><A NAME="ss9.107">9.107 set/spider (5)</A>
</H2>
<P><CODE><B>set/spider <node_call> [<node_call> ...]</B> Make
<P>
<P>Set the node_call as a DXSpider type node
<P>
-<H2><A NAME="ss9.94">9.94 set/sys_qra (9)</A>
+<H2><A NAME="ss9.108">9.108 set/sys_qra (9)</A>
</H2>
<P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA locator</CODE>
<P>
-<H2><A NAME="ss9.95">9.95 set/qra (0)</A>
+<H2><A NAME="ss9.109">9.109 set/qra (0)</A>
</H2>
<P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.96">9.96 set/qth (0)</A>
+<H2><A NAME="ss9.110">9.110 set/qth (0)</A>
</H2>
<P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.97">9.97 set/talk (0)</A>
+<H2><A NAME="ss9.111">9.111 set/register (9)</A>
+</H2>
+
+<P><CODE><B>set/register <call></B> Mark a user as registered</CODE>
+<P>
+<P>Registration is a concept that you can switch on by executing the
+<P>set/var $main::regreq = 1
+<P>command (usually in your startup file)
+<P>If a user is NOT registered then, firstly, instead of the normal
+motd file (/spider/data/motd) being sent to the user at startup, the
+user is sent the motd_nor file instead. Secondly, the non registered
+user only has READ-ONLY access to the node. The non-registered user
+cannot use DX, ANN etc.
+<P>The only exception to this is that a non-registered user can TALK or
+SEND messages to the sysop.
+<P>To unset a user use the 'unset/register' command
+<P>
+<H2><A NAME="ss9.112">9.112 set/talk (0)</A>
</H2>
<P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE>
<P>Allow talk messages to arrive at your console. You can switch off
talks with the <EM>unset/talk</EM> command.
<P>
-<H2><A NAME="ss9.98">9.98 set/wcy (0)</A>
+<H2><A NAME="ss9.113">9.113 set/wcy (0)</A>
</H2>
<P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE>
<P>Allow WCY information to be seen at your console. You can switch off
WCY messages with the <EM>unset/wcy</EM> command.
<P>
-<H2><A NAME="ss9.99">9.99 set/wwv (0)</A>
+<H2><A NAME="ss9.114">9.114 set/wwv (0)</A>
</H2>
<P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE>
<P>Allow WWV information to be seen at your console. You can switch off
WWV messages with the <EM>unset/wwv</EM> command.
<P>
-<H2><A NAME="ss9.100">9.100 set/wx (0)</A>
+<H2><A NAME="ss9.115">9.115 set/wx (0)</A>
</H2>
<P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE>
<P>Allow WX information to be seen at your console. You can switch off
WX messages with the <EM>unset/wx</EM> command.
<P>
-<H2><A NAME="ss9.101">9.101 show/baddx (1)</A>
+<H2><A NAME="ss9.116">9.116 show/baddx (1)</A>
</H2>
<P><CODE><B>show/baddx</B>Show all the bad dx calls in the system</CODE>
<P>Display all the bad dx callsigns in the system, see SET/BADDX
for more information.
<P>
-<H2><A NAME="ss9.102">9.102 show/badnode (6)</A>
+<H2><A NAME="ss9.117">9.117 show/badnode (6)</A>
</H2>
<P><CODE><B>show/badnode</B> Show all the bad nodes in the system</CODE>
<P>Display all the bad node callsigns in the system, see SET/BADNODE
for more information.
<P>
-<H2><A NAME="ss9.103">9.103 show/badspotter (1)</A>
+<H2><A NAME="ss9.118">9.118 show/badspotter (1)</A>
</H2>
<P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE>
<P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
for more information.
<P>
-<H2><A NAME="ss9.104">9.104 show/configuration (0)</A>
+<H2><A NAME="ss9.119">9.119 show/badword (1)</A>
+</H2>
+
+<P><CODE><B>show/badword</B> Show all the bad words in the system</CODE>
+<P>
+<P>Display all the bad words in the system, see SET/BADWORD
+for more information.
+<P>
+<H2><A NAME="ss9.120">9.120 show/configuration (0)</A>
</H2>
<P><CODE><B>show/configuration [<node>]</B> Show all visible nodes and their users</CODE>
<P>This command is normally abbreviated to: sh/c
<P>BE WARNED: the list that is returned can be VERY long
<P>
-<H2><A NAME="ss9.105">9.105 show/configuration/node (0)</A>
+<H2><A NAME="ss9.121">9.121 show/configuration/node (0)</A>
</H2>
<P><CODE><B>show/configuration/node</B> Show all the nodes connected</CODE>
<P>
<P>Show all the nodes connected locally and the nodes they have connected.
<P>
-<H2><A NAME="ss9.106">9.106 show/connect (1)</A>
+<H2><A NAME="ss9.122">9.122 show/connect (1)</A>
</H2>
<P><CODE><B>show/connect</B> Show all the active connections</CODE>
<P>This command shows information on all the active connections known to
the node. This command gives slightly more information than WHO.
<P>
-<H2><A NAME="ss9.107">9.107 show/date (0)</A>
+<H2><A NAME="ss9.123">9.123 show/date (0)</A>
</H2>
<P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
then it will show UTC and UTC + the local offset (not including DST) at
the prefixes or callsigns that you specify.
<P>
-<H2><A NAME="ss9.108">9.108 show/debug (9)</A>
+<H2><A NAME="ss9.124">9.124 show/debug (9)</A>
</H2>
<P><CODE><B>show/debug</B> Show what levels of debug you are logging</CODE>
<P>
<P>The levels can be set with <EM>set/debug</EM>
<P>
-<H2><A NAME="ss9.109">9.109 show/dx (0)</A>
+<H2><A NAME="ss9.125">9.125 show/dx (0)</A>
</H2>
<P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.110">9.110 show/dxcc (0)</A>
+<H2><A NAME="ss9.126">9.126 show/dxcc (0)</A>
</H2>
<P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.111">9.111 show/files (0)</A>
+<H2><A NAME="ss9.127">9.127 sh/dxstats (0)</A>
+</H2>
+
+<P><CODE><B>sh/dxstats</B> Show the DX Statistics for last 31 days</CODE>
+<P>
+<P>Show the total DX spots for the last 31 days
+<P>
+<P>
+<H2><A NAME="ss9.128">9.128 show/files (0)</A>
</H2>
<P><CODE><B>show/files [<filearea> [<string>]]</B> List
</CODE></BLOCKQUOTE>
<P>See also TYPE - to see the contents of a file.
<P>
-<H2><A NAME="ss9.112">9.112 show/filter (0)</A>
+<H2><A NAME="ss9.129">9.129 show/filter (0)</A>
</H2>
<P><CODE><B>show/filter</B> Show the filters you have set</CODE>
<P>Show the contents of all the filters that are set by you. This command
displays all the filters set - for all the various categories.
<P>
-<H2><A NAME="ss9.113">9.113 show/filter (extended for sysops) (5)</A>
+<H2><A NAME="ss9.130">9.130 show/filter (extended for sysops) (5)</A>
</H2>
<P><CODE><B>show/filter <callsign></B> Show the filters set by <callsign></CODE>
<P>
<P>A sysop can look at any filters that have been set.
<P>
-<H2><A NAME="ss9.114">9.114 show/hops (8)</A>
+<H2><A NAME="ss9.131">9.131 show/hfstats (0)</A>
+</H2>
+
+<P><CODE><B>show/hfstats</B> Show the HF DX Statistics for last 31 days</CODE>
+<P>
+<P>Show the HF DX spots breakdown by band for the last 31 days
+<P>
+<H2><A NAME="ss9.132">9.132 show/hftable (0)</A>
+</H2>
+
+<P><CODE><B>show/hftable</B> Show the HF DX Spotter Table for your country</CODE>
+<P>
+<P>Show the HF DX Spotter table for your country for the last 31 days
+<P>
+<H2><A NAME="ss9.133">9.133 show/hops (8)</A>
</H2>
<P><CODE><B>show/hops <node_call> [ann|spots|wcy|wwv|]</B> Show the hop counts for a node</CODE>
which category you want to see. If you leave the category out then
all the categories will be listed.
<P>
-<H2><A NAME="ss9.115">9.115 show/isolate (1)</A>
+<H2><A NAME="ss9.134">9.134 show/isolate (1)</A>
</H2>
<P><CODE><B>show/isolate</B> Show a list of isolated nodes</CODE>
<P>
<P>Show which nodes are currently set to be isolated.
<P>
-<H2><A NAME="ss9.116">9.116 show/lockout (9)</A>
+<H2><A NAME="ss9.135">9.135 show/lockout (9)</A>
</H2>
<P><CODE><B>show/lockout</B> Show a list of excluded callsigns</CODE>
<P>Show a list of callsigns that have been excluded (locked out) of the
cluster locally with the <EM>set/lockout</EM> command
<P>
-<H2><A NAME="ss9.117">9.117 show/log (8)</A>
+<H2><A NAME="ss9.136">9.136 show/log (8)</A>
</H2>
<P><CODE><B>show/log [<callsign>]</B> Show excerpts from the system log</CODE>
it will output a general logfile. With the optional callsign it will
show output from the log associated with that callsign.
<P>
-<H2><A NAME="ss9.118">9.118 show/moon (0)</A>
+<H2><A NAME="ss9.137">9.137 show/moon (0)</A>
</H2>
<P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.119">9.119 show/muf (0)</A>
+<H2><A NAME="ss9.138">9.138 show/muf (0)</A>
</H2>
<P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
</CODE></BLOCKQUOTE>
<P>indicating that you will have weak, fading circuits on top band and
80m but usable signals on 40m (about S3).
-<P>inputing:-
+<P>inputting:-
<P>
<BLOCKQUOTE><CODE>
<PRE>
should be noted that the figures will probably not be very useful, nor
terrible accurate, but it is included for completeness.
<P>
-<H2><A NAME="ss9.120">9.120 show/node (1)</A>
+<H2><A NAME="ss9.139">9.139 show/newconfiguration (0)</A>
+</H2>
+
+<P><CODE><B>show/newconfiguration [<node>]</B> Show all the nodes and users visible</CODE>
+<P>
+<P>This command allows you to see all the users that can be seen
+and the nodes to which they are connected.
+<P>This command produces essentially the same information as
+SHOW/CONFIGURATION except that it shows all the duplication of
+any routes that might be present It also uses a different format
+which may not take up quite as much space if you don't have any
+loops.
+<P>BE WARNED: the list that is returned can be VERY long
+<P>
+<H2><A NAME="ss9.140">9.140 show/newconfiguration/node (0)</A>
+</H2>
+
+<P><CODE><B>show/newconfiguration/node</B> Show all the nodes connected locally</CODE>
+<P>
+<P>Show all the nodes connected to this node in the new format.
+<P>
+<H2><A NAME="ss9.141">9.141 show/node (1)</A>
</H2>
<P><CODE><B>show/node [<node_call> ...]</B> Show the type and version
command line. If no callsigns are specified then a sorted list of all
the non-user callsigns known to the system will be displayed.
<P>
-<H2><A NAME="ss9.121">9.121 show/prefix (0)</A>
+<H2><A NAME="ss9.142">9.142 show/prefix (0)</A>
</H2>
<P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE>
<P>See also SHOW/DXCC
<P>
<P>
-<H2><A NAME="ss9.122">9.122 show/program (5)</A>
+<H2><A NAME="ss9.143">9.143 show/program (5)</A>
</H2>
<P><CODE><B>show/program</B> Show the locations of all the included program modules</CODE>
<P>Show the name and location where every program module was load from. This
is useful for checking where you think you have loaded a .pm file from.
<P>
-<H2><A NAME="ss9.123">9.123 show/qra (0)</A>
+<H2><A NAME="ss9.144">9.144 show/qra (0)</A>
</H2>
<P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.124">9.124 show/qrz (0)</A>
+<H2><A NAME="ss9.145">9.145 show/qrz (0)</A>
</H2>
<P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE>
and returns any information available for that callsign. This service
is provided for users of this software by http://www.qrz.com
<P>
-<H2><A NAME="ss9.125">9.125 show/route (0)</A>
+<H2><A NAME="ss9.146">9.146 show/registered (9)</A>
+</H2>
+
+<P><CODE><B>show/registered [<prefix>[</B> Show the registered users</CODE>
+<P>
+<H2><A NAME="ss9.147">9.147 show/route (0)</A>
</H2>
<P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.126">9.126 show/satellite (0)</A>
+<H2><A NAME="ss9.148">9.148 show/satellite (0)</A>
</H2>
<P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.127">9.127 show/sun (0)</A>
+<H2><A NAME="ss9.149">9.149 show/sun (0)</A>
</H2>
<P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.128">9.128 show/time (0)</A>
+<H2><A NAME="ss9.150">9.150 show/time (0)</A>
</H2>
<P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
then it will show UTC and UTC + the local offset (not including DST) at
the prefixes or callsigns that you specify.
<P>
-<H2><A NAME="ss9.129">9.129 show/wcy (0)</A>
+<H2><A NAME="ss9.151">9.151 show/vhfstats (0)</A>
+</H2>
+
+<P><CODE><B>show/vhfstats</B> Show the VHF DX Statistics for last 31 days</CODE>
+<P>
+<P>Show the VHF DX spots breakdown by band for the last 31 days
+<P>
+<H2><A NAME="ss9.152">9.152 show/vhftable (0)</A>
+</H2>
+
+<P><CODE><B>show/vhftable</B> Show the VHF DX Spotter Table for your country</CODE>
+<P>
+<P>Show the VHF DX Spotter table for your country for the last 31 days
+<P>
+<H2><A NAME="ss9.153">9.153 show/wcy (0)</A>
</H2>
<P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
<P>
<P>Display the most recent WCY information that has been received by the system
<P>
-<H2><A NAME="ss9.130">9.130 show/wwv (0)</A>
+<H2><A NAME="ss9.154">9.154 show/wwv (0)</A>
</H2>
<P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
<P>Display the most recent WWV information that has been received by the system
<P>
<P>
-<H2><A NAME="ss9.131">9.131 shutdown (5)</A>
+<H2><A NAME="ss9.155">9.155 shutdown (5)</A>
</H2>
<P><CODE><B>shutdown</B> Shutdown the cluster</CODE>
<P>Shutdown the cluster and disconnect all the users. If you have Spider
set to respawn in /etc/inittab it will of course restart.
<P>
-<H2><A NAME="ss9.132">9.132 spoof (9)</A>
+<H2><A NAME="ss9.156">9.156 spoof (9)</A>
</H2>
<P><CODE><B>spoof <callsign> <command></B> Run commands as another user</CODE>
kind of things that users seem to always get wrong.. like home_node for
example.
<P>
-<H2><A NAME="ss9.133">9.133 stat/db (5)</A>
+<H2><A NAME="ss9.157">9.157 stat/db (5)</A>
</H2>
<P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE>
<P>Depending on your privilege level you will see more or less information.
This command is unlikely to be of much use to anyone other than a sysop.
<P>
-<H2><A NAME="ss9.134">9.134 stat/channel (5)</A>
+<H2><A NAME="ss9.158">9.158 stat/channel (5)</A>
</H2>
<P><CODE><B>stat/channel <callsign></B> Show the status of a channel on the cluster</CODE>
you are on or else for the callsign that you asked for.
<P>Only the fields that are defined (in perl term) will be displayed.
<P>
-<H2><A NAME="ss9.135">9.135 stat/msg (5)</A>
+<H2><A NAME="ss9.159">9.159 stat/msg (5)</A>
</H2>
<P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE>
<P>If no message number is given then the status of the message system is
displayed.
<P>
-<H2><A NAME="ss9.136">9.136 stat/route_node (5)</A>
+<H2><A NAME="ss9.160">9.160 stat/route_node (5)</A>
</H2>
<P><CODE><B>stat/route_node <callsign></B> Show the data in a Route::Node object</CODE>
<P>
-<H2><A NAME="ss9.137">9.137 stat/route_user (5)</A>
+<H2><A NAME="ss9.161">9.161 stat/route_user (5)</A>
</H2>
<P><CODE><B>stat/route_user <callsign></B> Show the data in a Route::User object</CODE>
<P>
-<H2><A NAME="ss9.138">9.138 stat/user (5)</A>
+<H2><A NAME="ss9.162">9.162 stat/user (5)</A>
</H2>
<P><CODE><B>stat/user <callsign></B> Show the full status of a user</CODE>
and stuff.
<P>Only the fields that are defined (in perl term) will be displayed.
<P>
-<H2><A NAME="ss9.139">9.139 sysop (0)</A>
+<H2><A NAME="ss9.163">9.163 sysop (0)</A>
</H2>
<P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE>
numbers but nothing will happen when you input a string. Any match is
case sensitive.
<P>
-<H2><A NAME="ss9.140">9.140 talk (0)</A>
+<H2><A NAME="ss9.164">9.164 talk (0)</A>
</H2>
<P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss9.141">9.141 type (0)</A>
+<H2><A NAME="ss9.165">9.165 type (0)</A>
</H2>
<P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE>
<P>See also SHOW/FILES to see what fileareas are available and a
list of content.
<P>
-<H2><A NAME="ss9.142">9.142 who (0)</A>
+<H2><A NAME="ss9.166">9.166 who (0)</A>
</H2>
<P><CODE><B>who</B> Show who is physically connected locally</CODE>
<P>This is a quick listing that shows which callsigns are connected and
what sort of connection they have
<P>
-<H2><A NAME="ss9.143">9.143 wx (0)</A>
+<H2><A NAME="ss9.167">9.167 wx (0)</A>
</H2>
<P><CODE><B>wx <text></B> Send a weather message to local users<BR>
<P>Weather messages can sometimes be useful if you are experiencing an extreme
that may indicate enhanced conditions
<P>
-<H2><A NAME="ss9.144">9.144 wx (enhanced for sysops) (5)</A>
+<H2><A NAME="ss9.168">9.168 wx (enhanced for sysops) (5)</A>
</H2>
<P><CODE><B>wx sysop <text></B> Send a weather message to other clusters only</CODE>
<HR>
<H1>The DXSpider Administration Manual v1.48</H1>
-<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.49 November 2001 revision 1.0
+<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.49 November 2001 revision 1.1
<P><HR>
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
<HR>
<LI><A HREF="adminmanual-6.html#ss6.6">6.6 Console.pl</A>
<LI><A HREF="adminmanual-6.html#ss6.7">6.7 Updating kepler data</A>
<LI><A HREF="adminmanual-6.html#ss6.8">6.8 The QRZ callbook</A>
-<LI><A HREF="adminmanual-6.html#ss6.9">6.9 Scripts</A>
</UL>
<P>
<H2><A NAME="toc7">7.</A> <A HREF="adminmanual-7.html">Security</A></H2>
<LI><A HREF="adminmanual-9.html#ss9.13">9.13 apropos (0)</A>
<LI><A HREF="adminmanual-9.html#ss9.14">9.14 bye (0)</A>
<LI><A HREF="adminmanual-9.html#ss9.15">9.15 catchup (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.16">9.16 clear/spots (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.17">9.17 connect (5) </A>
-<LI><A HREF="adminmanual-9.html#ss9.18">9.18 dbavail (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.19">9.19 dbcreate (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.20">9.20 dbimport (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.21">9.21 dbremove (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.22">9.22 dbshow (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.23">9.23 debug (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.24">9.24 directory (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.25">9.25 directory (extended for sysops) (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.26">9.26 disconnect (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.27">9.27 dx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.28">9.28 export (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.29">9.29 export_users (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.30">9.30 forward/latlong (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.31">9.31 forward/opername (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.32">9.32 help (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.33">9.33 init (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.34">9.34 kill (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.35">9.35 kill (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.36">9.36 kill full (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.37">9.37 links (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.38">9.38 load/aliases (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.39">9.39 load/badmsg (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.40">9.40 load/bands (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.41">9.41 load/cmd_cache (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.42">9.42 load/forward (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.43">9.43 load/messages (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.44">9.44 load/prefixes (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.45">9.45 merge (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.46">9.46 msg (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.47">9.47 pc (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.48">9.48 ping (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.49">9.49 rcmd (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.50">9.50 read (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.51">9.51 read (extended for sysops) (5) </A>
-<LI><A HREF="adminmanual-9.html#ss9.52">9.52 reject/announce</A>
-<LI><A HREF="adminmanual-9.html#ss9.53">9.53 reject/announce (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.54">9.54 reject/route (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.55">9.55 reject/spots (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.56">9.56 reject/spots (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.57">9.57 reject/wcy (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.58">9.58 reject/wcy (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.59">9.59 reject/wwv (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.60">9.60 reject/wwv (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.61">9.61 reply (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.62">9.62 send (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.63">9.63 set/address (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.64">9.64 set/announce (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.65">9.65 set/arcluster (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.66">9.66 set/baddx (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.67">9.67 set/badnode (6)</A>
-<LI><A HREF="adminmanual-9.html#ss9.68">9.68 set/badspotter (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.69">9.69 set/beep (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.70">9.70 set/bbs (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.71">9.71 set/clx (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.72">9.72 set/debug (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.73">9.73 set/dx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.74">9.74 set/dxgrid (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.75">9.75 set/dxnet (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.76">9.76 set/echo (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.77">9.77 set/here (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.78">9.78 set/homenode (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.79">9.79 set/hops (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.80">9.80 set/isolate (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.81">9.81 set/language (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.82">9.82 set/location (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.83">9.83 set/sys_location (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.84">9.84 set/logininfo (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.85">9.85 set/lockout (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.86">9.86 set/name (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.87">9.87 set/node (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.88">9.88 set/obscount (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.89">9.89 set/page (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.90">9.90 set/password (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.91">9.91 set/pinginterval (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.92">9.92 set/privilege (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.93">9.93 set/spider (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.94">9.94 set/sys_qra (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.95">9.95 set/qra (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.96">9.96 set/qth (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.97">9.97 set/talk (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.98">9.98 set/wcy (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.99">9.99 set/wwv (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.100">9.100 set/wx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.101">9.101 show/baddx (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.102">9.102 show/badnode (6)</A>
-<LI><A HREF="adminmanual-9.html#ss9.103">9.103 show/badspotter (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.104">9.104 show/configuration (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.105">9.105 show/configuration/node (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.106">9.106 show/connect (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.107">9.107 show/date (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.108">9.108 show/debug (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.109">9.109 show/dx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.110">9.110 show/dxcc (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.111">9.111 show/files (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.112">9.112 show/filter (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.113">9.113 show/filter (extended for sysops) (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.114">9.114 show/hops (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.115">9.115 show/isolate (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.116">9.116 show/lockout (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.117">9.117 show/log (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.118">9.118 show/moon (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.119">9.119 show/muf (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.120">9.120 show/node (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.121">9.121 show/prefix (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.122">9.122 show/program (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.123">9.123 show/qra (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.124">9.124 show/qrz (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.125">9.125 show/route (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.126">9.126 show/satellite (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.127">9.127 show/sun (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.128">9.128 show/time (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.129">9.129 show/wcy (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.130">9.130 show/wwv (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.131">9.131 shutdown (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.132">9.132 spoof (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.133">9.133 stat/db (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.134">9.134 stat/channel (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.135">9.135 stat/msg (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.136">9.136 stat/route_node (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.137">9.137 stat/route_user (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.138">9.138 stat/user (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.139">9.139 sysop (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.140">9.140 talk (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.141">9.141 type (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.142">9.142 who (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.143">9.143 wx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.144">9.144 wx (enhanced for sysops) (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.16">9.16 clear/announce (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.17">9.17 clear/route (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.18">9.18 clear/spots (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.19">9.19 clear/spots (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.20">9.20 clear/wcy (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.21">9.21 clear/wcy (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.22">9.22 clear/wwv (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.23">9.23 clear/wwv (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.24">9.24 connect (5) </A>
+<LI><A HREF="adminmanual-9.html#ss9.25">9.25 dbavail (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.26">9.26 dbcreate (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.27">9.27 dbimport (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.28">9.28 dbremove (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.29">9.29 dbshow (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.30">9.30 debug (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.31">9.31 delete/user (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.32">9.32 directory (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.33">9.33 directory (extended for sysops) (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.34">9.34 disconnect (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.35">9.35 dx (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.36">9.36 export (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.37">9.37 export_users (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.38">9.38 filtering (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.39">9.39 forward/latlong (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.40">9.40 forward/opername (1)</A>
+<LI><A HREF="adminmanual-9.html#ss9.41">9.41 help (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.42">9.42 init (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.43">9.43 kill (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.44">9.44 kill (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.45">9.45 kill full (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.46">9.46 kill/expunge (6)</A>
+<LI><A HREF="adminmanual-9.html#ss9.47">9.47 links (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.48">9.48 load/aliases (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.49">9.49 load/badmsg (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.50">9.50 load/badwords (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.51">9.51 load/bands (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.52">9.52 load/cmd_cache (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.53">9.53 load/forward (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.54">9.54 load/messages (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.55">9.55 load/prefixes (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.56">9.56 merge (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.57">9.57 msg (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.58">9.58 pc (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.59">9.59 ping (1)</A>
+<LI><A HREF="adminmanual-9.html#ss9.60">9.60 rcmd (1)</A>
+<LI><A HREF="adminmanual-9.html#ss9.61">9.61 read (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.62">9.62 read (extended for sysops) (5) </A>
+<LI><A HREF="adminmanual-9.html#ss9.63">9.63 reject/announce</A>
+<LI><A HREF="adminmanual-9.html#ss9.64">9.64 reject/announce (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.65">9.65 reject/route (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.66">9.66 reject/spots (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.67">9.67 reject/spots (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.68">9.68 reject/wcy (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.69">9.69 reject/wcy (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.70">9.70 reject/wwv (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.71">9.71 reject/wwv (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.72">9.72 reply (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.73">9.73 send (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.74">9.74 set/address (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.75">9.75 set/announce (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.76">9.76 set/arcluster (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.77">9.77 set/baddx (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.78">9.78 set/badnode (6)</A>
+<LI><A HREF="adminmanual-9.html#ss9.79">9.79 set/badspotter (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.80">9.80 set/badword (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.81">9.81 set/beep (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.82">9.82 set/bbs (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.83">9.83 set/clx (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.84">9.84 set/debug (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.85">9.85 set/dx (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.86">9.86 set/dxgrid (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.87">9.87 set/dxnet (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.88">9.88 set/echo (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.89">9.89 set/email (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.90">9.90 set/here (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.91">9.91 set/homenode (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.92">9.92 set/hops (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.93">9.93 set/isolate (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.94">9.94 set/language (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.95">9.95 set/location (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.96">9.96 set/sys_location (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.97">9.97 set/logininfo (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.98">9.98 set/lockout (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.99">9.99 set/name (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.100">9.100 set/node (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.101">9.101 set/obscount (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.102">9.102 set/page (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.103">9.103 set/password (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.104">9.104 set/password (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.105">9.105 set/pinginterval (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.106">9.106 set/privilege (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.107">9.107 set/spider (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.108">9.108 set/sys_qra (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.109">9.109 set/qra (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.110">9.110 set/qth (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.111">9.111 set/register (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.112">9.112 set/talk (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.113">9.113 set/wcy (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.114">9.114 set/wwv (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.115">9.115 set/wx (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.116">9.116 show/baddx (1)</A>
+<LI><A HREF="adminmanual-9.html#ss9.117">9.117 show/badnode (6)</A>
+<LI><A HREF="adminmanual-9.html#ss9.118">9.118 show/badspotter (1)</A>
+<LI><A HREF="adminmanual-9.html#ss9.119">9.119 show/badword (1)</A>
+<LI><A HREF="adminmanual-9.html#ss9.120">9.120 show/configuration (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.121">9.121 show/configuration/node (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.122">9.122 show/connect (1)</A>
+<LI><A HREF="adminmanual-9.html#ss9.123">9.123 show/date (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.124">9.124 show/debug (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.125">9.125 show/dx (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.126">9.126 show/dxcc (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.127">9.127 sh/dxstats (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.128">9.128 show/files (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.129">9.129 show/filter (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.130">9.130 show/filter (extended for sysops) (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.131">9.131 show/hfstats (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.132">9.132 show/hftable (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.133">9.133 show/hops (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.134">9.134 show/isolate (1)</A>
+<LI><A HREF="adminmanual-9.html#ss9.135">9.135 show/lockout (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.136">9.136 show/log (8)</A>
+<LI><A HREF="adminmanual-9.html#ss9.137">9.137 show/moon (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.138">9.138 show/muf (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.139">9.139 show/newconfiguration (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.140">9.140 show/newconfiguration/node (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.141">9.141 show/node (1)</A>
+<LI><A HREF="adminmanual-9.html#ss9.142">9.142 show/prefix (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.143">9.143 show/program (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.144">9.144 show/qra (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.145">9.145 show/qrz (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.146">9.146 show/registered (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.147">9.147 show/route (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.148">9.148 show/satellite (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.149">9.149 show/sun (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.150">9.150 show/time (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.151">9.151 show/vhfstats (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.152">9.152 show/vhftable (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.153">9.153 show/wcy (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.154">9.154 show/wwv (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.155">9.155 shutdown (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.156">9.156 spoof (9)</A>
+<LI><A HREF="adminmanual-9.html#ss9.157">9.157 stat/db (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.158">9.158 stat/channel (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.159">9.159 stat/msg (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.160">9.160 stat/route_node (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.161">9.161 stat/route_user (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.162">9.162 stat/user (5)</A>
+<LI><A HREF="adminmanual-9.html#ss9.163">9.163 sysop (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.164">9.164 talk (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.165">9.165 type (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.166">9.166 who (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.167">9.167 wx (0)</A>
+<LI><A HREF="adminmanual-9.html#ss9.168">9.168 wx (enhanced for sysops) (5)</A>
</UL>
<HR>
<A HREF="adminmanual-1.html">Next</A>
<title>The DXSpider Administration Manual v1.48</title>
<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)</author>
-<date>Version 1.49 November 2001 revision 1.0</date>
+<date>Version 1.49 November 2001 revision 1.1</date>
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
From 1.48 onwards it will become increasingly possible to control DXSpider's
operation with scripts of various kinds.
-<p>
-In the first instance, in 1.48, the sysop can create, with their favorite
-text editor, files in the directory <em>/spider/scripts</em> which contain
-any legal command for a callsign or class of connection which will be executed
-at logon.
+<P>
+The directory /spider/scripts is where it all happens and is used for several
+things. Firstly it contains a file called startup that can be used to call
+in any changes to the cluster from the default settings on startup. This
+script is executed immediately after all initialisation of the node is done
+but before any connections are possible. Examples of this include how many
+spots it is possible to get with the sh/dx command, whether you want
+registration/passwords to be permanently on etc. An example file is shown
+below and is included in the distribution as startup.issue.
-<p>
-The filename is the callsign of the connection that you want the script to
-operate on, eg: <em>/spider/scripts/g1tlh</em>. The filenames are always in
-lower case on those architectures where this makes a difference.
+<tscreen><verb>
+#
+# 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
+#
+</verb></tscreen>
-<p>
-In addition to the callsign specific scripts there are three others:-
+<P>
+As usual, any text behind a # is treated as a comment and not read.
+
+Secondly, it is used to store the login scripts for users and nodes. Currently
+this can only be done by the sysop but it is envisaged that eventually users will
+be able to set their own. An example is included in the distibution but here is
+a further example.
<tscreen><verb>
-startup
-user_default
-node_default
+#
+# G0FYD
+#
+blank +
+sh/wwv 3
+blank +
+sh/dx
+blank +
+t g0jhc You abt?
+blank +
</verb></tscreen>
-
-The <em>startup</em> script is executed immediately after all
-initialisation of the node is done, but before any connections are
-possible.
-<p>
-The <em>user_default</em> script is executed for every user that does
-<bf>NOT</bf> already have a specific script.
+The lines in between commands can simply insert a blank line or a character
+such as a + sign to make the output easier to read. Simply create this script
+with your favourite editor and save it with the callsign of the user as the
+filename. Filenames should always be in lower case.
-<p>
-The <em>node_default</em> script is executed for every node that doesn't
-have a specific script.
+<P>
+Commands can be inserted in the same way for nodes. A node may wish a series
+of commands to be issued on login, such as a merge command for example.
-<p>
-There are a couple of examples in the <em>/spider/scripts</em> directory.
+<P>
+Thirdly, there are 2 default scripts for users and nodes who do not have a
+specifically defined script. These are <em>user_default</em> and
+<em>node_default</em>
<sect>Databases
the setup. Many thanks to Fred Lloyd, the proprieter of
<htmlurl url="http://www.qrz.com" name="qrz.com"> for allowing this access.
-<sect1>Scripts
-
-<P>
-The directory /spider/scripts is used for several things. Firstly it
-contains a file called startup that can be used to call in any changes
-to the cluster from the default settings on startup. Examples of this
-include how many spots it is possible to get with the sh/dx command,
-whether you want registration/passwords to be permanently on etc. An
-example file is shown below and is included in the distribution as
-startup.issue.
-
-<tscreen><verb>
-#
-# 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
-#
-</verb></tscreen>
-
-Secondly, it is used to store the login scripts for users. Currently
-this can only be done by the sysop but it is envisaged that eventually
-users will be able to set their own. An example is included in the
-distibution but here is a further example.
-
-<tscreen><verb>
-#
-# G0FYD
-#
-blank +
-sh/wwv 3
-blank +
-sh/dx
-blank +
-t g0jhc You abt?
-blank +
-</verb></tscreen>
-
-The lines in between commands can simply insert a blank line or a character
-such as a + sign to make the output easier to read.
-
<sect>Security
<P>
Order is not important.
+<sect1>clear/announce (8)
+
+<P>
+<tt>
+<bf>clear/announce [input] <callsign> [0-9|all]</bf> Clear an announce filter line
+</tt>
+
+<P>
+A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
+
+<sect1>clear/route (8)
+
+<P>
+<tt>
+<bf>clear/route [input] ^lt;callsign> [0-9|all]</bf> Clear a route filter line
+</tt>
+
+<P>
+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.
+
<sect1>clear/spots (0)
<P>
the filter will be completely removed.
+<sect1>clear/spots (extended for sysops) (8)
+
+<P>
+<tt>
+<bf>clear/spots [input] <callsign> [0-9|all]</bf> Clear a spot filter line
+</tt>
+
+<P>
+A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
+
+<sect1>clear/wcy (0)
+
+<P>
+<tt>
+<bf>clear/wcy [1|all]</bf> Clear a WCY filter line
+</tt>
+
+<P>
+This command allows you to clear (remove) a line in a WCY filter or to
+remove the whole filter.
+
+see CLEAR/SPOTS for a more detailed explanation.
+
+<sect1>clear/wcy (extended for sysops) (8)
+
+<P>
+<tt>
+<bf>clear/wcy [input] <callsign> [0-9|all]</bf> Clear a WCY filter line
+</tt>
+
+<P>
+A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
+
+<sect1>clear/wwv (0)
+
+<P>
+<tt>
+<bf>clear/wwv [1|all]</bf> Clear a WWV filter line
+</tt>
+
+<P>
+This command allows you to clear (remove) a line in a WWV filter or to
+remove the whole filter.
+
+see CLEAR/SPOTS for a more detailed explanation.
+
+<sect1>clear/wwv (extended for sysops) (8)
+
+<P>
+<tt>
+<bf>clear/wwv [input] <callsign> [0-9|all]</bf> Clear a WWV filter line
+</tt>
+
+<P>
+A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
<sect1>connect (5)
It will interrupt the cluster just after the debug command has finished.
+<sect1>delete/user (9)
+
+<P>
+<tt>
+<bf>delete/user <callsign></bf> Delete a user from the User Database
+</tt>
+
+<P>
+This command will completely remove a one or more users from the database.
+
+There is NO SECOND CHANCE.
+
+It goes without saying that you should use this command CAREFULLY!
+
+
<sect1>directory (0)
<P>
BE WARNED: this will write to any file you have write access to. No check is
made on the filename (if any) that you specify.
+<sect1>filtering (0)
+
+<P>
+<tt>
+<bf>filtering</bf> Filtering things in DXSpider
+</tt>
+
+<P>
+There are a number of things you can filter in the DXSpider system. They
+all use the same general mechanism.
+
+In general terms you can create a 'reject' or an 'accept' filter which
+can have up to 10 lines in it. You do this using, for example:-
+
+ accept/spots .....
+ reject/spots .....
+
+where ..... are the specific commands for that type of filter. There
+are filters for spots, wwv, announce, wcy and (for sysops)
+connects. See each different accept or reject command reference for
+more details.
+
+There is also a command to clear out one or more lines in a filter and
+one to show you what you have set. They are:-
+
+ clear/spots 1
+ clear/spots all
+
+and
+
+ show/filter
+
+There is clear/xxxx command for each type of filter.
+
+For now we are going to use spots for the examples, but you can apply
+the principles to all types of filter.
+
+There are two main types of filter 'accept' or 'reject'; which you use
+depends entirely on how you look at the world and what is least
+writing to achieve what you want. Each filter has 10 lines (of any
+length) which are tried in order. If a line matches then the action
+you have specified is taken (ie reject means ignore it and accept
+means gimme it).
+
+The important thing to remember is that if you specify a 'reject'
+filter (all the lines in it say 'reject/spots' (for instance) then if
+a spot comes in that doesn't match any of the lines then you will get
+it BUT if you specify an 'accept' filter then any spots that don't
+match are dumped. For example if I have a one line accept filter:-
+
+ accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+then automatically you will ONLY get VHF spots from or to CQ zones 14
+15 and 16. If you set a reject filter like:
+
+ reject/spots on hf/cw
+
+Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
+and will work it even on CW then you could say:-
+
+ reject/spots on hf/cw and not info iota
+
+But in that case you might only be interested in iota and say:-
+
+ accept/spots not on hf/cw or info iota
+
+which is exactly the same. You should choose one or the other until
+you are confortable with the way it works. Yes, you can mix them
+(actually you can have an accept AND a reject on the same line) but
+don't try this at home until you can analyse the results that you get
+without ringing up the sysop for help.
+
+You can arrange your filter lines into logical units, either for your
+own understanding or simply convenience. I have one set frequently:-
+
+ reject/spots 1 on hf/cw
+ reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
+
+What this does is to ignore all HF CW spots (being a class B I can't
+read any CW and couldn't possibly be interested in HF :-) and also
+rejects any spots on VHF which don't either originate or spot someone
+in Europe.
+
+This is an exmaple where you would use the line number (1 and 2 in
+this case), if you leave the digit out, the system assumes '1'. Digits
+'0'-'9' are available.
+
+You can leave the word 'and' out if you want, it is implied. You can
+use any number of brackets to make the 'expression' as you want
+it. There are things called precedence rules working here which mean
+that you will NEED brackets in a situation like line 2 because,
+without it, will assume:-
+
+ (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+
+annoying, but that is the way it is. If you use OR - use
+brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
+just 'and by_zone'.
+
+If you want to alter your filter you can just redefine one or more
+lines of it or clear out one line. For example:-
+
+ reject/spots 1 on hf/ssb
+
+or
+
+ clear/spots 1
+
+To remove the filter in its entirty:-
+
+ clear/spots all
+
+There are similar CLEAR commands for the other filters:-
+
+ clear/announce
+ clear/wcy
+ clear/wwv
+
+ADVANCED USERS:-
+
+Once you are happy with the results you get, you may like to experiment.
+
+my example that filters hf/cw spots and accepts vhf/uhf spots from EU
+can be written with a mixed filter, eg:
+
+ rej/spot on hf/cw
+ acc/spot on 0/30000
+ acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+
+each filter slot actually has a 'reject' slot and an 'accept'
+slot. The reject slot is executed BEFORE the accept slot.
+
+It was mentioned earlier that after a reject test that doesn't match,
+the default for following tests is 'accept', the reverse is true for
+'accept'. In the example what happens is that the reject is executed
+first, any non hf/cw spot is passed to the accept line, which lets
+thru everything else on HF.
+
+The next filter line lets through just VHF/UHF spots from EU.
+
<sect1>forward/latlong (8)
<P>
This uses the subject field, so any messages that have exactly the same subject
will be deleted. Beware!
+<sect1>kill/expunge (6)
+
+<P>
+<tt>
+<bf>kill/expunge <msgno> [<msgno>..]</bf>Expunge a message
+</tt>
+
+<P>
+Deleting a message using the normal KILL commands only marks that message
+for deletion. The actual deletion only happens later (usually two days later).
+
+The KILL EXPUNGE command causes the message to be truly deleted more or less
+immediately.
+
+It otherwise is used in the same way as the KILL command.
+
+
<sect1>links (0)
<P>
expressions which are searched for in the fields targetted of each message.
If any of them match then that message is immediately deleted on receipt.
+<sect1>load/badwords (9)
+
+<P>
+<tt>
+<bf>load/badwords</bf> Reload the bad words table
+</tt>
+
+<P>
+Reload the /spider/data/badwords file if you have changed it manually whilst
+the cluster is running. This file contains a list of words which, if found
+on certain text portions of PC protocol, will cause those protocol frames
+to be rejected. It will all put out a message if any of these words are
+used on the announce, dx and talk commands. The words can be one or
+more on a line, lines starting with '#' are ignored.
+
<sect1>load/bands (9)
<P>
Use with extreme care. This command may well be superceded by FILTERing.
+<sect1>set/badword (8)
+
+<P>
+<tt>
+<bf>set/badword <word></bf> Stop things with this word being propogated
+</tt>
+
+<P>
+Setting a word as a 'badword' will prevent things like spots,
+announces or talks with this word in the the text part from going any
+further. They will not be displayed and they will not be sent onto
+other nodes.
+
+The word must be written in full, no wild cards are allowed eg:-
+
+ set/badword annihilate annihilated annihilation
+
+will stop anything with these words in the text.
+
+ unset/badword annihilated
+
+will allow text with this word again.
+
+
<sect1>set/beep (0)
<P>
YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
+<sect1>set/email (0)
+
+<P>
+<tt>
+<bf>set/email <email_address></bf> Set email address(es) and forward your personals
+</tt>
+
+<P>
+If any personal messages come in for your callsign then you can use
+these commands to control whether they are forwarded onto your email
+address. To enable the forwarding do something like:-
+
+ SET/EMAIL mike.tubby@somewhere.com
+
+You can have more than one email address (each one separated by a space).
+Emails are forwarded to all the email addresses you specify.
+
+You can disable forwarding by:-
+
+ UNSET/EMAIL
+
<sect1>set/here (0)
<P>
The setting is stored in your user profile.
+<sect1>set/password (0)
+
+<P>
+<tt>
+<bf>set/password</bf> Set your own password
+</tt>
+
+<P>
+This command only works for a 'telnet' user (currently). It will
+only work if you have a password already set. This initial password
+can only be set by the sysop.
+
+When you execute this command it will ask you for your old password,
+then ask you to type in your new password twice (to make sure you
+get it right). You may or may not see the data echoed on the screen
+as you type, depending on the type of telnet client you have.
<sect1>set/password (9)
<P>
The password for a user can only be set by a full sysop. The string
-can contain any characters but any spaces are removed (you can type in
-spaces - but they won't appear in the password). You can see the
-result with STAT/USER. The password is the usual 30 character baycom
-type password.
+can contain any characters.
+
+The way this field is used depends on context. If it is being used in
+the SYSOP command context then you are offered 5 random numbers and you
+have to supply the corresponding letters. This is now mainly for ax25
+connections.
+
+If it is being used on incoming telnet connections then, if a password
+is set or the:
+
+ set/var $main::passwdreq = 1
+
+command is executed in the startup script, then a password prompt is
+given after the normal 'login: ' prompt.
+
+The command "unset/password" is provided to allow a sysop to remove a
+users password completely in case a user forgets or loses their password.
<sect1>set/pinginterval (9)
<P>
-<tt>
-<bf>set/pinginterval <time> <node call></bf> Set the ping time
+<tt><bf>set/pinginterval <time> <node call></bf> Set the ping time
to neighbouring nodes
</tt>
set/qth East Dereham, Norfolk
</verb></tscreen>
+<sect1>set/register (9)
+
+<P>
+<tt>
+<bf>set/register <call></bf> Mark a user as registered
+</tt>
+
+<P>
+Registration is a concept that you can switch on by executing the
+
+ set/var $main::regreq = 1
+
+command (usually in your startup file)
+
+If a user is NOT registered then, firstly, instead of the normal
+motd file (/spider/data/motd) being sent to the user at startup, the
+user is sent the motd_nor file instead. Secondly, the non registered
+user only has READ-ONLY access to the node. The non-registered user
+cannot use DX, ANN etc.
+
+The only exception to this is that a non-registered user can TALK or
+SEND messages to the sysop.
+
+To unset a user use the 'unset/register' command
+
<sect1>set/talk (0)
<P>
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
for more information.
+<sect1>show/badword (1)
+
+<P>
+<tt>
+<bf>show/badword</bf> Show all the bad words in the system
+</tt>
+
+<P>
+Display all the bad words in the system, see SET/BADWORD
+for more information.
+
<sect1>show/configuration (0)
<P>
SH/DXCC W on 20m info iota
</verb></tscreen>
+<sect1>sh/dxstats (0)
+
+<P>
+<tt>
+<bf>sh/dxstats</bf> Show the DX Statistics for last 31 days
+</tt>
+
+<P>
+Show the total DX spots for the last 31 days
+
+
<sect1>show/files (0)
<P>
<P>
A sysop can look at any filters that have been set.
+<sect1>show/hfstats (0)
+
+<P>
+<tt>
+<bf>show/hfstats</bf> Show the HF DX Statistics for last 31 days
+</tt>
+
+<P>
+Show the HF DX spots breakdown by band for the last 31 days
+
+<sect1>show/hftable (0)
+
+<P>
+<tt>
+<bf>show/hftable</bf> Show the HF DX Spotter Table for your country
+</tt>
+
+<P>
+Show the HF DX Spotter table for your country for the last 31 days
+
<sect1>show/hops (8)
<P>
indicating that you will have weak, fading circuits on top band and
80m but usable signals on 40m (about S3).
-inputing:-
+inputting:-
<tscreen><verb>
SH/MUF W 24
should be noted that the figures will probably not be very useful, nor
terrible accurate, but it is included for completeness.
+<sect1>show/newconfiguration (0)
+
+<P>
+<tt>
+<bf>show/newconfiguration [<node>]</bf> Show all the nodes and users visible
+</tt>
+
+<P>
+This command allows you to see all the users that can be seen
+and the nodes to which they are connected.
+
+This command produces essentially the same information as
+SHOW/CONFIGURATION except that it shows all the duplication of
+any routes that might be present It also uses a different format
+which may not take up quite as much space if you don't have any
+loops.
+
+BE WARNED: the list that is returned can be VERY long
+
+<sect1>show/newconfiguration/node (0)
+
+<P>
+<tt>
+<bf>show/newconfiguration/node</bf> Show all the nodes connected locally
+</tt>
+
+<P>
+Show all the nodes connected to this node in the new format.
+
<sect1>show/node (1)
<P>
and returns any information available for that callsign. This service
is provided for users of this software by http://www.qrz.com
+<sect1>show/registered (9)
+
+<P>
+<tt>
+<bf>show/registered [<prefix>[</bf> Show the registered users
+</tt>
+
<sect1>show/route (0)
<P>
then it will show UTC and UTC + the local offset (not including DST) at
the prefixes or callsigns that you specify.
+<sect1>show/vhfstats (0)
+
+<P>
+<tt>
+<bf>show/vhfstats</bf> Show the VHF DX Statistics for last 31 days
+</tt>
+
+<P>
+Show the VHF DX spots breakdown by band for the last 31 days
+
+<sect1>show/vhftable (0)
+
+<P>
+<tt>
+<bf>show/vhftable</bf> Show the VHF DX Spotter Table for your country
+</tt>
+
+<P>
+Show the VHF DX Spotter table for your country for the last 31 days
+
<sect1>show/wcy (0)
<P>
The DXSpider Administration Manual v1.48
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.49 November 2001 revision 1.0
+ Version 1.49 November 2001 revision 1.1
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
6.6 Console.pl
6.7 Updating kepler data
6.8 The QRZ callbook
- 6.9 Scripts
7. Security
9.13 apropos (0)
9.14 bye (0)
9.15 catchup (5)
- 9.16 clear/spots (0)
- 9.17 connect (5)
- 9.18 dbavail (0)
- 9.19 dbcreate (9)
- 9.20 dbimport (9)
- 9.21 dbremove (9)
- 9.22 dbshow (0)
- 9.23 debug (9)
- 9.24 directory (0)
- 9.25 directory (extended for sysops) (5)
- 9.26 disconnect (8)
- 9.27 dx (0)
- 9.28 export (9)
- 9.29 export_users (9)
- 9.30 forward/latlong (8)
- 9.31 forward/opername (1)
- 9.32 help (0)
- 9.33 init (5)
- 9.34 kill (0)
- 9.35 kill (5)
- 9.36 kill full (5)
- 9.37 links (0)
- 9.38 load/aliases (9)
- 9.39 load/badmsg (9)
- 9.40 load/bands (9)
- 9.41 load/cmd_cache (9)
- 9.42 load/forward (9)
- 9.43 load/messages (9)
- 9.44 load/prefixes (9)
- 9.45 merge (5)
- 9.46 msg (9)
- 9.47 pc (8)
- 9.48 ping (1)
- 9.49 rcmd (1)
- 9.50 read (0)
- 9.51 read (extended for sysops) (5)
- 9.52 reject/announce
- 9.53 reject/announce (extended for sysops) (8)
- 9.54 reject/route (8)
- 9.55 reject/spots (0)
- 9.56 reject/spots (extended for sysops) (8)
- 9.57 reject/wcy (0)
- 9.58 reject/wcy (extended for sysops) (8)
- 9.59 reject/wwv (0)
- 9.60 reject/wwv (extended for sysops) (8)
- 9.61 reply (0)
- 9.62 send (0)
- 9.63 set/address (0)
- 9.64 set/announce (0)
- 9.65 set/arcluster (5)
- 9.66 set/baddx (8)
- 9.67 set/badnode (6)
- 9.68 set/badspotter (8)
- 9.69 set/beep (0)
- 9.70 set/bbs (5)
- 9.71 set/clx (5)
- 9.72 set/debug (9)
- 9.73 set/dx (0)
- 9.74 set/dxgrid (0)
- 9.75 set/dxnet (5)
- 9.76 set/echo (0)
- 9.77 set/here (0)
- 9.78 set/homenode (0)
- 9.79 set/hops (8)
- 9.80 set/isolate (9)
- 9.81 set/language (0)
- 9.82 set/location (0)
- 9.83 set/sys_location (9)
- 9.84 set/logininfo (0)
- 9.85 set/lockout (9)
- 9.86 set/name (0)
- 9.87 set/node (9)
- 9.88 set/obscount (9)
- 9.89 set/page (0)
- 9.90 set/password (9)
- 9.91 set/pinginterval (9)
- 9.92 set/privilege (9)
- 9.93 set/spider (5)
- 9.94 set/sys_qra (9)
- 9.95 set/qra (0)
- 9.96 set/qth (0)
- 9.97 set/talk (0)
- 9.98 set/wcy (0)
- 9.99 set/wwv (0)
- 9.100 set/wx (0)
- 9.101 show/baddx (1)
- 9.102 show/badnode (6)
- 9.103 show/badspotter (1)
- 9.104 show/configuration (0)
- 9.105 show/configuration/node (0)
- 9.106 show/connect (1)
- 9.107 show/date (0)
- 9.108 show/debug (9)
- 9.109 show/dx (0)
- 9.110 show/dxcc (0)
- 9.111 show/files (0)
- 9.112 show/filter (0)
- 9.113 show/filter (extended for sysops) (5)
- 9.114 show/hops (8)
- 9.115 show/isolate (1)
- 9.116 show/lockout (9)
- 9.117 show/log (8)
- 9.118 show/moon (0)
- 9.119 show/muf (0)
- 9.120 show/node (1)
- 9.121 show/prefix (0)
- 9.122 show/program (5)
- 9.123 show/qra (0)
- 9.124 show/qrz (0)
- 9.125 show/route (0)
- 9.126 show/satellite (0)
- 9.127 show/sun (0)
- 9.128 show/time (0)
- 9.129 show/wcy (0)
- 9.130 show/wwv (0)
- 9.131 shutdown (5)
- 9.132 spoof (9)
- 9.133 stat/db (5)
- 9.134 stat/channel (5)
- 9.135 stat/msg (5)
- 9.136 stat/route_node (5)
- 9.137 stat/route_user (5)
- 9.138 stat/user (5)
- 9.139 sysop (0)
- 9.140 talk (0)
- 9.141 type (0)
- 9.142 who (0)
- 9.143 wx (0)
- 9.144 wx (enhanced for sysops) (5)
+ 9.16 clear/announce (8)
+ 9.17 clear/route (8)
+ 9.18 clear/spots (0)
+ 9.19 clear/spots (extended for sysops) (8)
+ 9.20 clear/wcy (0)
+ 9.21 clear/wcy (extended for sysops) (8)
+ 9.22 clear/wwv (0)
+ 9.23 clear/wwv (extended for sysops) (8)
+ 9.24 connect (5)
+ 9.25 dbavail (0)
+ 9.26 dbcreate (9)
+ 9.27 dbimport (9)
+ 9.28 dbremove (9)
+ 9.29 dbshow (0)
+ 9.30 debug (9)
+ 9.31 delete/user (9)
+ 9.32 directory (0)
+ 9.33 directory (extended for sysops) (5)
+ 9.34 disconnect (8)
+ 9.35 dx (0)
+ 9.36 export (9)
+ 9.37 export_users (9)
+ 9.38 filtering (0)
+ 9.39 forward/latlong (8)
+ 9.40 forward/opername (1)
+ 9.41 help (0)
+ 9.42 init (5)
+ 9.43 kill (0)
+ 9.44 kill (5)
+ 9.45 kill full (5)
+ 9.46 kill/expunge (6)
+ 9.47 links (0)
+ 9.48 load/aliases (9)
+ 9.49 load/badmsg (9)
+ 9.50 load/badwords (9)
+ 9.51 load/bands (9)
+ 9.52 load/cmd_cache (9)
+ 9.53 load/forward (9)
+ 9.54 load/messages (9)
+ 9.55 load/prefixes (9)
+ 9.56 merge (5)
+ 9.57 msg (9)
+ 9.58 pc (8)
+ 9.59 ping (1)
+ 9.60 rcmd (1)
+ 9.61 read (0)
+ 9.62 read (extended for sysops) (5)
+ 9.63 reject/announce
+ 9.64 reject/announce (extended for sysops) (8)
+ 9.65 reject/route (8)
+ 9.66 reject/spots (0)
+ 9.67 reject/spots (extended for sysops) (8)
+ 9.68 reject/wcy (0)
+ 9.69 reject/wcy (extended for sysops) (8)
+ 9.70 reject/wwv (0)
+ 9.71 reject/wwv (extended for sysops) (8)
+ 9.72 reply (0)
+ 9.73 send (0)
+ 9.74 set/address (0)
+ 9.75 set/announce (0)
+ 9.76 set/arcluster (5)
+ 9.77 set/baddx (8)
+ 9.78 set/badnode (6)
+ 9.79 set/badspotter (8)
+ 9.80 set/badword (8)
+ 9.81 set/beep (0)
+ 9.82 set/bbs (5)
+ 9.83 set/clx (5)
+ 9.84 set/debug (9)
+ 9.85 set/dx (0)
+ 9.86 set/dxgrid (0)
+ 9.87 set/dxnet (5)
+ 9.88 set/echo (0)
+ 9.89 set/email (0)
+ 9.90 set/here (0)
+ 9.91 set/homenode (0)
+ 9.92 set/hops (8)
+ 9.93 set/isolate (9)
+ 9.94 set/language (0)
+ 9.95 set/location (0)
+ 9.96 set/sys_location (9)
+ 9.97 set/logininfo (0)
+ 9.98 set/lockout (9)
+ 9.99 set/name (0)
+ 9.100 set/node (9)
+ 9.101 set/obscount (9)
+ 9.102 set/page (0)
+ 9.103 set/password (0)
+ 9.104 set/password (9)
+ 9.105 set/pinginterval (9)
+ 9.106 set/privilege (9)
+ 9.107 set/spider (5)
+ 9.108 set/sys_qra (9)
+ 9.109 set/qra (0)
+ 9.110 set/qth (0)
+ 9.111 set/register (9)
+ 9.112 set/talk (0)
+ 9.113 set/wcy (0)
+ 9.114 set/wwv (0)
+ 9.115 set/wx (0)
+ 9.116 show/baddx (1)
+ 9.117 show/badnode (6)
+ 9.118 show/badspotter (1)
+ 9.119 show/badword (1)
+ 9.120 show/configuration (0)
+ 9.121 show/configuration/node (0)
+ 9.122 show/connect (1)
+ 9.123 show/date (0)
+ 9.124 show/debug (9)
+ 9.125 show/dx (0)
+ 9.126 show/dxcc (0)
+ 9.127 sh/dxstats (0)
+ 9.128 show/files (0)
+ 9.129 show/filter (0)
+ 9.130 show/filter (extended for sysops) (5)
+ 9.131 show/hfstats (0)
+ 9.132 show/hftable (0)
+ 9.133 show/hops (8)
+ 9.134 show/isolate (1)
+ 9.135 show/lockout (9)
+ 9.136 show/log (8)
+ 9.137 show/moon (0)
+ 9.138 show/muf (0)
+ 9.139 show/newconfiguration (0)
+ 9.140 show/newconfiguration/node (0)
+ 9.141 show/node (1)
+ 9.142 show/prefix (0)
+ 9.143 show/program (5)
+ 9.144 show/qra (0)
+ 9.145 show/qrz (0)
+ 9.146 show/registered (9)
+ 9.147 show/route (0)
+ 9.148 show/satellite (0)
+ 9.149 show/sun (0)
+ 9.150 show/time (0)
+ 9.151 show/vhfstats (0)
+ 9.152 show/vhftable (0)
+ 9.153 show/wcy (0)
+ 9.154 show/wwv (0)
+ 9.155 shutdown (5)
+ 9.156 spoof (9)
+ 9.157 stat/db (5)
+ 9.158 stat/channel (5)
+ 9.159 stat/msg (5)
+ 9.160 stat/route_node (5)
+ 9.161 stat/route_user (5)
+ 9.162 stat/user (5)
+ 9.163 sysop (0)
+ 9.164 talk (0)
+ 9.165 type (0)
+ 9.166 who (0)
+ 9.167 wx (0)
+ 9.168 wx (enhanced for sysops) (5)
______________________________________________________________________
network, then you do not need to do route filtering and you will feel
a lot better for not getting involved. If you are successfully using
isolation then you also probably don't need to use route filtering.
+
+
To put it simply, you should not mix Isolation and Route Filtering.
It will work, of sorts, but you will not get the expected results. If
you are using Isolation sucessfully at the moment, do not get involved
The generic commands are:-
-
-
reject/route node_default <filter_option>
or
channel_zone <numbers>
+
+
Please be careful if you alter this setting, it will affect ALL your
links! Remember, this is a default filter for node connections, not a
per link default.
+
1.4. General route filtering
Exactly the same rules apply for general route filtering. You would
+
What this does is to ignore all HF CW spots and also rejects any spots
on VHF which don't either originate or spot someone in Europe.
reject/spots 1 on hf/ssb
-
-
-
would redefine our earlier example, or
You can filter in several different ways. The options are listed in
the various helpfiles for accept, reject and filter.
+
1.8. Default filters
Sometimes all that is needed is a general rule for node connects.
acc/spot on 0/30000
acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
Note that the first filter has not been specified with a number. This
will automatically be assumed to be number 1. In this case, we have
said reject all HF spots in the CW section of the bands but accept all
- #
- # hop table construction
- #
- package DXProt;
- # default hopcount to use
- $def_hopcount = 5;
- # some variable hop counts based on message type
- %hopcount =
- (
- 11 => 10,
- 16 => 10,
- 17 => 10,
- 19 => 10,
- 21 => 10,
- );
- # the per node hop control thingy
- %nodehops =
- GB7ADX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- GB7UDX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- GB7BAA => {
- 11 => 5,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- };
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ #
+ # hop table construction
+ #
+
+ package DXProt;
+
+ # default hopcount to use
+ $def_hopcount = 5;
+
+ # some variable hop counts based on message type
+ %hopcount =
+ (
+ 11 => 10,
+ 16 => 10,
+ 17 => 10,
+ 19 => 10,
+ 21 => 10,
+ );
+
+
+ # the per node hop control thingy
+
+
+ %nodehops =
+
+ GB7ADX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+
+ GB7UDX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ GB7BAA => {
+ 11 => 5,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ };
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)
DXSpider's operation with scripts of various kinds.
- 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.
+ The directory /spider/scripts is where it all happens and is used for
+ several things. Firstly it contains a file called startup that can be
+ used to call in any changes to the cluster from the default settings
+ on startup. This script is executed immediately after all
+ initialisation of the node is done but before any connections are
+ possible. Examples of this include how many spots it is possible to
+ get with the sh/dx command, whether you want registration/passwords to
+ be permanently on etc. An example file is shown below and is included
+ in the distribution as startup.issue.
- 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 addition to the callsign specific scripts there are three others:-
- startup
- user_default
- node_default
+ #
+ # 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
+ #
+
- The startup script is executed immediately after all initialisation of
- the node is done, but before any connections are possible.
+ As usual, any text behind a # is treated as a comment and not read.
+
+ Secondly, it is used to store the login scripts for users and nodes.
+ Currently this can only be done by the sysop but it is envisaged that
+ eventually users will be able to set their own. An example is
+ included in the distibution but here is a further example.
+
+
+
+ #
+ # G0FYD
+ #
+ blank +
+ sh/wwv 3
+ blank +
+ sh/dx
+ blank +
+ t g0jhc You abt?
+ blank +
+
+
- The user_default script is executed for every user that does NOT
- already have a specific script.
+ The lines in between commands can simply insert a blank line or a
+ character such as a + sign to make the output easier to read. Simply
+ create this script with your favourite editor and save it with the
+ callsign of the user as the filename. Filenames should always be in
+ lower case.
- The node_default script is executed for every node that doesn't have a
- specific script.
+ Commands can be inserted in the same way for nodes. A node may wish a
+ series of commands to be issued on login, such as a merge command for
+ example.
- There are a couple of examples in the /spider/scripts directory.
+ Thirdly, there are 2 default scripts for users and nodes who do not
+ have a specifically defined script. These are user_default and
+ node_default
5. Databases
+
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...
-
This will update the existing local oblast database or create it if it
does not exist.
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
actually running.
-
-
-
6.4. Other text messages
You can set other text messages to be read by the user if they input
-
- type news
+ type 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) >
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
#!/usr/bin/perl
# provide some standard aliases for commands for terminally
proprieter of qrz.com for allowing this access.
- 6.9. Scripts
-
- The directory /spider/scripts is used for several things. Firstly it
- contains a file called startup that can be used to call in any changes
- to the cluster from the default settings on startup. Examples of this
- include how many spots it is possible to get with the sh/dx command,
- whether you want registration/passwords to be permanently on etc. An
- example file is shown below and is included in the distribution as
- startup.issue.
-
-
-
- #
- # 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
- #
-
-
-
-
- Secondly, it is used to store the login scripts for users. Currently
- this can only be done by the sysop but it is envisaged that eventually
- users will be able to set their own. An example is included in the
- distibution but here is a further example.
-
-
-
- #
- # G0FYD
- #
- blank +
- sh/wwv 3
- blank +
- sh/dx
- blank +
- t g0jhc You abt?
- blank +
-
-
-
-
- The lines in between commands can simply insert a blank line or a
- character such as a + sign to make the output easier to read.
-
-
-
-
7. Security
From version 1.49 DXSpider has some additional security features.
set/var $main::passwdreq = 1
+
+
+
at the cluster prompt. This can also be added to the
/spider/scripts/startup file as above to make the change permanent.
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
+
and your files will be updated. As above, remember to recompile the
"C" client if it has been updated (CVS will tell you) and restart if
any of the perl scripts have been altered or added, again, CVS will
some examples:-
-
-
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)
-
- acc/ann by G,M,2
+ acc/ann by G,M,2
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>
origin_zone <numbers>
+
+
+
some examples:-
-
-
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 -
thus: hf/ssb. You can also just have a simple range like: 0/30000 -
-
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
- 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
accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
-
This version allows a sysop to set a filter for a callsign as well as
the default for nodes and users eg:-
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.
Order is not important.
- 9.16. clear/spots (0)
+ 9.16. clear/announce (8)
+
+ clear/announce [input] <callsign> [0-9|all] Clear an announce filter
+ line
+
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
+
+
+ 9.17. clear/route (8)
+
+ clear/route [input] ^lt;callsign> [0-9|all] Clear a route filter line
+
+
+ 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.18. clear/spots (0)
clear/spots [1|all] Clear a spot filter line
the filter will be completely removed.
+ 9.19. clear/spots (extended for sysops) (8)
+
+ clear/spots [input] <callsign> [0-9|all] Clear a spot filter line
+
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
+
- 9.17. connect (5)
+
+
+
+ 9.20. clear/wcy (0)
+
+ clear/wcy [1|all] Clear a WCY filter line
+
+
+ This command allows you to clear (remove) a line in a WCY filter or to
+ remove the whole filter.
+
+ see CLEAR/SPOTS for a more detailed explanation.
+
+
+ 9.21. clear/wcy (extended for sysops) (8)
+
+ clear/wcy [input] <callsign> [0-9|all] Clear a WCY filter line
+
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
+
+
+ 9.22. clear/wwv (0)
+
+ clear/wwv [1|all] Clear a WWV filter line
+
+
+ This command allows you to clear (remove) a line in a WWV filter or to
+ remove the whole filter.
+
+ see CLEAR/SPOTS for a more detailed explanation.
+
+
+ 9.23. clear/wwv (extended for sysops) (8)
+
+ clear/wwv [input] <callsign> [0-9|all] Clear a WWV filter line
+
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
+
+
+ 9.24. connect (5)
connect <callsign> Start a connection to another DX Cluster
cluster <callsign>.
- 9.18. dbavail (0)
+ 9.25. dbavail (0)
dbavail Show a list of all the databases in the system
defined in the system. It is also aliased to SHOW/COMMAND.
- 9.19. dbcreate (9)
+ 9.26. dbcreate (9)
dbcreate <name> Create a database entry
dbcreate <name> chain <name> [<name>..] Create a chained database
Databases can exist offsite. To define a database that lives on
another node do:
-
DBCREATE buckmaster remote gb7dxc
Remote databases cannot be chained; however, the last database in a a
databases. See DBSHOW for generic database enquiry
- 9.20. dbimport (9)
+
+
+ 9.27. dbimport (9)
dbimport <dbname> Import AK1A data into a database
oblast database held locally.
- 9.21. dbremove (9)
+ 9.28. dbremove (9)
dbremove <dbname> Delete a database
For example:
-
DBREMOVE oblast
will remove the oblast database from the system and it will also
You have been warned.
- 9.22. dbshow (0)
+ 9.29. dbshow (0)
dbshow <dbname> <key> Display an entry, if it exists, in a database
-
-
- 9.23. debug (9)
+ 9.30. debug (9)
debug Set the cluster program into debug mode
finished.
- 9.24. directory (0)
+ 9.31. delete/user (9)
- directory List messages
+ delete/user <callsign> Delete a user from the User Database
+
+
+ This command will completely remove a one or more users from the
+ database.
+
+ There is NO SECOND CHANCE.
+
+ It goes without saying that you should use this command CAREFULLY!
+
+
+
+ 9.32. directory (0)
+
+ directory List messages
directory own List your own messages
directory new List all new messages
directory to <call> List all messages to <call>
You can abbreviate all the commands to one letter and use ak1a
syntax:-
-
-
-
DIR/T G1* 10
DIR/S QSL 10-100 5
- 9.25. directory (extended for sysops) (5)
+ 9.33. directory (extended for sysops) (5)
Works just like the user command except that sysops can see ALL
messages.
- 9.26. disconnect (8)
+ 9.34. disconnect (8)
disconnect <call> [<call> ...] Disconnect a user or node
Disconnect any <call> connected locally
- 9.27. dx (0)
+ 9.35. dx (0)
dx [by <call>] <freq> <call> <remarks> Send a DX spot
DX 144.600 FR0G
DX 144600 FR0G
+
+
+
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.
cluster. See SHOW/BANDS for more information.
- 9.28. export (9)
+ 9.36. export (9)
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
EXPORT 2345 /tmp/a
- 9.29. export_users (9)
+ 9.37. export_users (9)
export_users [<filename>] Export the users database to ascii
check is made on the filename (if any) that you specify.
- 9.30. forward/latlong (8)
+ 9.38. filtering (0)
+
+ filtering Filtering things in DXSpider
+
+
+ There are a number of things you can filter in the DXSpider system.
+ They all use the same general mechanism.
+
+ In general terms you can create a 'reject' or an 'accept' filter which
+ can have up to 10 lines in it. You do this using, for example:-
+
+ accept/spots ..... reject/spots .....
+
+ where ..... are the specific commands for that type of filter. There
+ are filters for spots, wwv, announce, wcy and (for sysops) connects.
+ See each different accept or reject command reference for more
+ details.
+
+ There is also a command to clear out one or more lines in a filter and
+ one to show you what you have set. They are:-
+
+ clear/spots 1 clear/spots all
+
+ and
+
+ show/filter
+
+ There is clear/xxxx command for each type of filter.
+
+ For now we are going to use spots for the examples, but you can apply
+ the principles to all types of filter.
+
+ There are two main types of filter 'accept' or 'reject'; which you use
+ depends entirely on how you look at the world and what is least
+ writing to achieve what you want. Each filter has 10 lines (of any
+ length) which are tried in order. If a line matches then the action
+ you have specified is taken (ie reject means ignore it and accept
+ means gimme it).
+
+ The important thing to remember is that if you specify a 'reject'
+ filter (all the lines in it say 'reject/spots' (for instance) then if
+ a spot comes in that doesn't match any of the lines then you will get
+ it BUT if you specify an 'accept' filter then any spots that don't
+ match are dumped. For example if I have a one line accept filter:-
+
+ accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+ then automatically you will ONLY get VHF spots from or to CQ zones 14
+ 15 and 16. If you set a reject filter like:
+
+ reject/spots on hf/cw
+
+ Then you will get everything EXCEPT HF CW spots, If you am interested
+ in IOTA and will work it even on CW then you could say:-
+
+ reject/spots on hf/cw and not info iota
+
+ But in that case you might only be interested in iota and say:-
+
+ accept/spots not on hf/cw or info iota
+
+ which is exactly the same. You should choose one or the other until
+ you are confortable with the way it works. Yes, you can mix them
+ (actually you can have an accept AND a reject on the same line) but
+ don't try this at home until you can analyse the results that you get
+ without ringing up the sysop for help.
+
+ You can arrange your filter lines into logical units, either for your
+ own understanding or simply convenience. I have one set frequently:-
+
+ reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone
+ 14,15,16 or call_zone 14,15,16)
+
+ What this does is to ignore all HF CW spots (being a class B I can't
+ read any CW and couldn't possibly be interested in HF :-) and also
+ rejects any spots on VHF which don't either originate or spot someone
+ in Europe.
+
+ This is an exmaple where you would use the line number (1 and 2 in
+ this case), if you leave the digit out, the system assumes '1'. Digits
+
+ You can leave the word 'and' out if you want, it is implied. You can
+ use any number of brackets to make the 'expression' as you want it.
+ There are things called precedence rules working here which mean that
+ you will NEED brackets in a situation like line 2 because, without it,
+ will assume:-
+
+ (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+
+ annoying, but that is the way it is. If you use OR - use brackets.
+ Whilst we are here CASE is not important. 'And BY_Zone' is just 'and
+ by_zone'.
+
+ If you want to alter your filter you can just redefine one or more
+ lines of it or clear out one line. For example:-
+
+ reject/spots 1 on hf/ssb
+
+ or
+
+ clear/spots 1
+
+
+ To remove the filter in its entirty:-
+
+ clear/spots all
+
+ There are similar CLEAR commands for the other filters:-
+
+ clear/announce clear/wcy clear/wwv
+
+ ADVANCED USERS:-
+
+ Once you are happy with the results you get, you may like to
+ experiment.
+
+ my example that filters hf/cw spots and accepts vhf/uhf spots from EU
+ can be written with a mixed filter, eg:
+
+ rej/spot on hf/cw acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and
+ (by_zone 14,15,16 or call_zone 14,15,16)
+
+ each filter slot actually has a 'reject' slot and an 'accept' slot.
+ The reject slot is executed BEFORE the accept slot.
+
+ It was mentioned earlier that after a reject test that doesn't match,
+ the default for following tests is 'accept', the reverse is true for
+ first, any non hf/cw spot is passed to the accept line, which lets
+ thru everything else on HF.
+
+ The next filter line lets through just VHF/UHF spots from EU.
+
+
+ 9.39. forward/latlong (8)
forward/latlong <node_call> Send latitude and longitude information to
another cluster
so it is not recommended on slow links.
- 9.31. forward/opername (1)
+ 9.40. forward/opername (1)
forward/opername <call> Send out information on this <call> to all
clusters
available.
- 9.32. help (0)
+ 9.41. help (0)
help <cmd> Get help on a command
commands to look at with HELP.
- 9.33. init (5)
+ 9.42. init (5)
init <node call> Re-initialise a link to an AK1A compatible node
Best of luck - you will need it.
- 9.34. kill (0)
+ 9.43. kill (0)
kill <msgno> [<msgno> ..] Delete a message from the local system
the sysop).
- 9.35. kill (5)
+ 9.44. kill (5)
kill <msgno> [<msgno> ...] Remove or erase a message from the system
kill from <call> Remove all messages from a callsign
As a sysop you can kill any message on the system.
- 9.36. kill full (5)
+
+ 9.45. kill full (5)
kill full <msgno> [<msgno>] Delete a message from the whole cluster
same subject will be deleted. Beware!
- 9.37. links (0)
+ 9.46. kill/expunge (6)
+
+ kill/expunge <msgno> [<msgno>..]Expunge a message
+
+
+ Deleting a message using the normal KILL commands only marks that
+ message for deletion. The actual deletion only happens later (usually
+ two days later).
+
+ The KILL EXPUNGE command causes the message to be truly deleted more
+ or less immediately.
+
+ It otherwise is used in the same way as the KILL command.
+
+
+ 9.47. links (0)
links Show which nodes are physically connected
- 9.38. load/aliases (9)
+ 9.48. load/aliases (9)
load/aliases Reload the command alias table
running in order for the changes to take effect.
- 9.39. load/badmsg (9)
+ 9.49. load/badmsg (9)
load/badmsg Reload the bad message table
deleted on receipt.
- 9.40. load/bands (9)
+ 9.50. load/badwords (9)
+
+ load/badwords Reload the bad words table
+
+
+ Reload the /spider/data/badwords file if you have changed it manually
+ whilst the cluster is running. This file contains a list of words
+ which, if found on certain text portions of PC protocol, will cause
+ those protocol frames to be rejected. It will all put out a message if
+ any of these words are used on the announce, dx and talk commands. The
+ words can be one or more on a line, lines starting with '#' are
+ ignored.
+
+
+ 9.51. load/bands (9)
load/bands Reload the band limits table
whilst the cluster is running.
- 9.41. load/cmd_cache (9)
+ 9.52. load/cmd_cache (9)
load/cmd_cache Reload the automatic command cache
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.42. load/forward (9)
+ 9.53. load/forward (9)
load/forward Reload the msg forwarding routing table
whilst the cluster is running.
- 9.43. load/messages (9)
+ 9.54. load/messages (9)
load/messages Reload the system messages file
unknown message 'xxxx' in lang 'en'
- 9.44. load/prefixes (9)
+ 9.55. load/prefixes (9)
load/prefixes Reload the prefix table
manually whilst the cluster is running.
- 9.45. merge (5)
+ 9.56. merge (5)
merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
data).
- 9.46. msg (9)
+ 9.57. msg (9)
msg <cmd> <msgno> [data ...] Alter various message parameters
This will display more information on the message than DIR does.
- 9.47. pc (8)
+ 9.58. pc (8)
pc <call> <text> Send text (eg PC Protocol) to <call>
pc G1TLH Try doing that properly!!!
- 9.48. ping (1)
+ 9.59. ping (1)
ping <node> Check the link quality between nodes
- 9.49. rcmd (1)
+ 9.60. rcmd (1)
rcmd <node call> <cmd> Send a command to another DX cluster
whether you have permission to send this command at all.
- 9.50. read (0)
+ 9.61. read (0)
read Read the next unread personal message addressed to you
read <msgno> Read the specified message
- 9.51. read (extended for sysops) (5)
+ 9.62. read (extended for sysops) (5)
read <msgno> Read a message on the system
As a sysop you may read any message on the system
- 9.52. reject/announce
+ 9.63. reject/announce
reject/announce [0-9] <pattern> Set a reject filter for announce
but this probably for advanced users...
- 9.53. reject/announce (extended for sysops) (8)
+ 9.64. reject/announce (extended for sysops) (8)
reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
version
- 9.54. reject/route (8)
+ 9.65. reject/route (8)
reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
routing
- 9.55. reject/spots (0)
+ 9.66. reject/spots (0)
reject/spots [0-9] <pattern> Set a reject filter line for spots
but this probably for advanced users...
- 9.56. reject/spots (extended for sysops) (8)
+ 9.67. reject/spots (extended for sysops) (8)
reject/spots <call> [input] [0-9] <pattern> Reject spot filter sysop
version
- 9.57. reject/wcy (0)
+ 9.68. reject/wcy (0)
reject/wcy [0-9] <pattern> Set a reject WCY filter
- 9.58. reject/wcy (extended for sysops) (8)
+ 9.69. reject/wcy (extended for sysops) (8)
reject/wcy <call> [input] [0-9] <pattern> WCY reject filter sysop
version
reject/wcy gb7djk all
- 9.59. reject/wwv (0)
+ 9.70. reject/wwv (0)
reject/wwv [0-9] <pattern> Set a reject WWV filter
See HELP FILTER for information.
- 9.60. reject/wwv (extended for sysops) (8)
+ 9.71. reject/wwv (extended for sysops) (8)
reject/wwv <call> [input] [0-9] <pattern> WWV reject filter sysop
version
reject/wwv user_default by W
- 9.61. reply (0)
+ 9.72. reply (0)
reply Reply (privately) to the last message that you have read
reply <msgno> Reply (privately) to the specified message
further details)
- 9.62. send (0)
+ 9.73. send (0)
send <call> [<call> ...] Send a message to one or more callsigns
send RR <call> Send a message and ask for a read receipt
is an alias for SEND PRIVATE
- 9.63. set/address (0)
+ 9.74. set/address (0)
set/address <your_address> Record your postal address
Literally, record your address details on the cluster.
- 9.64. set/announce (0)
+ 9.75. set/announce (0)
set/announce Allow announce messages
Allow announce messages to arrive at your terminal.
- 9.65. set/arcluster (5)
+ 9.76. set/arcluster (5)
set/arcluster <node_call> [<node_call> ...] Make the node_call an AR-
Cluster type node
Set the node_call as an AR-Cluster type node
- 9.66. set/baddx (8)
+ 9.77. set/baddx (8)
set/baddx <call> Stop words we do not wish to see in the callsign
field of a dx spot being propagated
- 9.67. set/badnode (6)
+ 9.78. set/badnode (6)
set/badnode <node_call> Stop spots from this node_call being
propagated
FILTERing.
- 9.68. set/badspotter (8)
+ 9.79. set/badspotter (8)
set/badspotter <call> Stop spots from this callsign being propagated
FILTERing.
- 9.69. set/beep (0)
+ 9.80. set/badword (8)
- set/beep Add beeps to terminal messages
+ set/badword <word> Stop things with this word being propogated
+
+
+ Setting a word as a 'badword' will prevent things like spots,
+ announces or talks with this word in the the text part from going any
+ further. They will not be displayed and they will not be sent onto
+ other nodes.
+ The word must be written in full, no wild cards are allowed eg:-
+
+ set/badword annihilate annihilated annihilation
+
+ will stop anything with these words in the text.
+
+ unset/badword annihilated
+
+ will allow text with this word again.
+
+
+
+ 9.81. set/beep (0)
+
+ set/beep Add beeps to terminal messages
Add a beep to DX and other terminal messages.
- 9.70. set/bbs (5)
+ 9.82. set/bbs (5)
set/bbs <call> [<call>..]Make <call> a BBS
- 9.71. set/clx (5)
+ 9.83. set/clx (5)
set/clx <node_call> [<node_call> ...] Make the node_call a CLX type
node
Set the node_call as a CLX type node
- 9.72. set/debug (9)
+ 9.84. set/debug (9)
set/debug <name> Add a debug level to the debug set
+
You can choose to log several different levels. The levels are
chan state msg cron connect
You can remove a debug level with unset/debug <name>
- 9.73. set/dx (0)
+ 9.85. set/dx (0)
set/dxAllow DX messages to arrive at your terminal
You can stop DX messages with the unset/dx command
- 9.74. set/dxgrid (0)
+ 9.86. set/dxgrid (0)
set/dxgridAllow grid squares on the end of DX messages
to remove the grid squares.
- 9.75. set/dxnet (5)
+ 9.87. set/dxnet (5)
set/dxnet <node_call> [<node_call> ...] Make the node_call a DXNet
type node
Set the node_call as a DXNet type node
- 9.76. set/echo (0)
+ 9.88. set/echo (0)
set/echo Make the cluster echo your input
YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
- 9.77. set/here (0)
+ 9.89. set/email (0)
+
+ set/email <email_address> Set email address(es) and forward your
+ personals
+
+
+ If any personal messages come in for your callsign then you can use
+ these commands to control whether they are forwarded onto your email
+ address. To enable the forwarding do something like:-
+
+ SET/EMAIL mike.tubby@somewhere.com
+
+ You can have more than one email address (each one separated by a
+ space). Emails are forwarded to all the email addresses you specify.
+
+ You can disable forwarding by:-
+
+ UNSET/EMAIL
+
+
+ 9.90. set/here (0)
set/here Set the here flag
brackets around your callsign to indicate you are not available.
-
-
- 9.78. set/homenode (0)
+ 9.91. set/homenode (0)
set/homenode <node_call> Set your home cluster
- 9.79. set/hops (8)
+ 9.92. set/hops (8)
set/hops <node_call> ann|spots|wwv|wcy <n> Set hop count
This command allows you to set up special hop counts for a node for
currently: announce, spots, wwv and wcy broadcasts.
-
-
-
eg:
set/hops gb7djk ann 10
set/hops gb7mbc spots 20
creates a filter and works in conjunction with the filter system.
- 9.80. set/isolate (9)
+ 9.93. set/isolate (9)
set/isolate <node call> Isolate a node from the rest of the network
You can remove the isolation with the command unset/isolate.
- 9.81. set/language (0)
+ 9.94. set/language (0)
set/language <language> Set the language you wish to use
You can select the language that you want the cluster to use.
Currently the languages available are en (English) and nl (Dutch).
- 9.82. set/location (0)
+
+ 9.95. set/location (0)
set/location <lat and long> Set your latitude and longitude
- 9.83. set/sys_location (9)
+ 9.96. set/sys_location (9)
set/sys_location <lat & long> Set your cluster latitude and longitude
example:-
-
SET/LOCATION 52 22 N 0 57 E
- 9.84. set/logininfo (0)
+ 9.97. set/logininfo (0)
set/logininfo Show logins and logouts of nodes and users
- 9.85. set/lockout (9)
+ 9.98. set/lockout (9)
set/lockout <call> Stop a callsign connecting to the cluster
allow the user to connect again, use the unset/lockout command.
- 9.86. set/name (0)
+ 9.99. set/name (0)
set/name <your_name> Set your name
set/name Dirk
- 9.87. set/node (9)
+
+
+
+ 9.100. set/node (9)
set/node <call> [<call> ...] Make the callsign an AK1A cluster
To see what your nodes are set to, use the show/nodes command.
- 9.88. set/obscount (9)
+
+
+
+ 9.101. set/obscount (9)
set/obscount <count> <node call> Set the 'pump-up' obsolescence
counter
minutes, it is disconnected.
- 9.89. set/page (0)
+ 9.102. set/page (0)
set/page <n> Set the number of lines per page
The setting is stored in your user profile.
+ 9.103. set/password (0)
+
+ set/password Set your own password
+
+ This command only works for a 'telnet' user (currently). It will only
+ work if you have a password already set. This initial password can
+ only be set by the sysop.
- 9.90. set/password (9)
+ When you execute this command it will ask you for your old password,
+ then ask you to type in your new password twice (to make sure you get
+ it right). You may or may not see the data echoed on the screen as you
+ type, depending on the type of telnet client you have.
+
+
+ 9.104. set/password (9)
set/password <callsign> <string> Set a users password
The password for a user can only be set by a full sysop. The string
- can contain any characters but any spaces are removed (you can type in
- spaces - but they won't appear in the password). You can see the
- result with STAT/USER. The password is the usual 30 character baycom
- type password.
+ can contain any characters.
+
+ The way this field is used depends on context. If it is being used in
+ the SYSOP command context then you are offered 5 random numbers and
+ you have to supply the corresponding letters. This is now mainly for
+ ax25 connections.
+
+ If it is being used on incoming telnet connections then, if a password
+ is set or the:
+ set/var $main::passwdreq = 1
- 9.91. set/pinginterval (9)
+ command is executed in the startup script, then a password prompt is
+ given after the normal 'login: ' prompt.
+
+ The command "unset/password" is provided to allow a sysop to remove a
+ users password completely in case a user forgets or loses their
+ password.
+
+
+ 9.105. set/pinginterval (9)
set/pinginterval <time> <node call> Set the ping time to neighbouring
nodes
for more information.
- 9.92. set/privilege (9)
+ 9.106. set/privilege (9)
set/privilege <n> <call> [<call> ...] Set the privilege level on a
call
connection your privilege will automatically be set to 0.
- 9.93. set/spider (5)
+
+
+
+ 9.107. set/spider (5)
set/spider <node_call> [<node_call> ...] Make the node_call a DXSpider
type node
-
Set the node_call as a DXSpider type node
- 9.94. set/sys_qra (9)
+ 9.108. set/sys_qra (9)
set/sys_qra <locator> Set your cluster QRA locator
- 9.95. set/qra (0)
+ 9.109. set/qra (0)
set/qra <locator> Set your QRA locator
- 9.96. set/qth (0)
+ 9.110. set/qth (0)
set/qth <your QTH> Set your QTH
- 9.97. set/talk (0)
+ 9.111. set/register (9)
+
+ set/register <call> Mark a user as registered
+
+
+ Registration is a concept that you can switch on by executing the
+
+ set/var $main::regreq = 1
+
+ command (usually in your startup file)
+
+ If a user is NOT registered then, firstly, instead of the normal motd
+ file (/spider/data/motd) being sent to the user at startup, the user
+ is sent the motd_nor file instead. Secondly, the non registered user
+ only has READ-ONLY access to the node. The non-registered user cannot
+ use DX, ANN etc.
+
+ The only exception to this is that a non-registered user can TALK or
+ SEND messages to the sysop.
+
+ To unset a user use the 'unset/register' command
+
+
+ 9.112. set/talk (0)
set/talk Allow talk messages to be seen at your console
talks with the unset/talk command.
- 9.98. set/wcy (0)
+ 9.113. set/wcy (0)
set/wcy Allow WCY messages to be seen at your console
WCY messages with the unset/wcy command.
- 9.99. set/wwv (0)
+ 9.114. set/wwv (0)
set/wwv Allow WWV messages to be seen at your console
Allow WWV information to be seen at your console. You can switch off
WWV messages with the unset/wwv command.
- 9.100. set/wx (0)
+
+ 9.115. set/wx (0)
set/wx Allow WX messages to be seen at your console
WX messages with the unset/wx command.
- 9.101. show/baddx (1)
+ 9.116. show/baddx (1)
show/baddxShow all the bad dx calls in the system
information.
- 9.102. show/badnode (6)
+ 9.117. show/badnode (6)
show/badnode Show all the bad nodes in the system
more information.
- 9.103. show/badspotter (1)
+ 9.118. show/badspotter (1)
show/badspotter Show all the bad spotters in the system
SET/BADSPOTTER for more information.
- 9.104. show/configuration (0)
+ 9.119. show/badword (1)
+
+ show/badword Show all the bad words in the system
+
+
+ Display all the bad words in the system, see SET/BADWORD for more
+ information.
+
+
+ 9.120. show/configuration (0)
show/configuration [<node>] Show all visible nodes and their users
BE WARNED: the list that is returned can be VERY long
- 9.105. show/configuration/node (0)
+ 9.121. show/configuration/node (0)
show/configuration/node Show all the nodes connected
connected.
- 9.106. show/connect (1)
+ 9.122. show/connect (1)
show/connect Show all the active connections
This command shows information on all the active connections known to
the node. This command gives slightly more information than WHO.
- 9.107. show/date (0)
+
+
+ 9.123. show/date (0)
show/date [<prefix>|<callsign>] Show the local time
including DST) at the prefixes or callsigns that you specify.
- 9.108. show/debug (9)
+ 9.124. show/debug (9)
show/debug Show what levels of debug you are logging
The levels can be set with set/debug
- 9.109. show/dx (0)
+
+
+
+ 9.125. show/dx (0)
show/dx [options] interrogate the spot database
qra [<locator>] - this will look for the specific locator if
you specify one or else anything that looks like a locator.
+
+
+
e.g.
- 9.110. show/dxcc (0)
+
+
+ 9.126. show/dxcc (0)
show/dxcc <prefix> Interrogate the spot database by country
- 9.111. show/files (0)
+ 9.127. sh/dxstats (0)
+
+ sh/dxstats Show the DX Statistics for last 31 days
+
+
+ Show the total DX spots for the last 31 days
+
+
+
+ 9.128. show/files (0)
show/files [<filearea> [<string>]] List the contents of a filearea
+
See also TYPE - to see the contents of a file.
- 9.112. show/filter (0)
+ 9.129. show/filter (0)
show/filter Show the filters you have set
-
Show the contents of all the filters that are set by you. This command
displays all the filters set - for all the various categories.
- 9.113. show/filter (extended for sysops) (5)
+ 9.130. show/filter (extended for sysops) (5)
show/filter <callsign> Show the filters set by <callsign>
A sysop can look at any filters that have been set.
- 9.114. show/hops (8)
+ 9.131. show/hfstats (0)
+
+ show/hfstats Show the HF DX Statistics for last 31 days
+
+
+ Show the HF DX spots breakdown by band for the last 31 days
+
+
+ 9.132. show/hftable (0)
+
+ show/hftable Show the HF DX Spotter Table for your country
+
+
+ Show the HF DX Spotter table for your country for the last 31 days
+
+
+ 9.133. show/hops (8)
show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a
node
the categories will be listed.
- 9.115. show/isolate (1)
+ 9.134. show/isolate (1)
show/isolate Show a list of isolated nodes
Show which nodes are currently set to be isolated.
- 9.116. show/lockout (9)
+ 9.135. show/lockout (9)
show/lockout Show a list of excluded callsigns
cluster locally with the set/lockout command
- 9.117. show/log (8)
+ 9.136. show/log (8)
show/log [<callsign>] Show excerpts from the system log
show output from the log associated with that callsign.
- 9.118. show/moon (0)
+ 9.137. show/moon (0)
show/moon [<prefix>|<callsign>] Show moon rise and set times
Show the Moon rise and set times for a (list of) prefixes or
callsigns, together with the azimuth and elevation of the sun
currently at those locations.
+
If you don't specify any prefixes or callsigns, it will show the times
for your QTH (assuming you have set it with either SET/LOCATION or
SET/QRA), together with the current azimuth and elevation.
- 9.119. show/muf (0)
+ 9.138. show/muf (0)
show/muf <prefix> [<hours>][long] Show the likely propagation to
<prefix>
- SH/MUF W
+ SH/MUF W
indicating that you will have weak, fading circuits on top band and
80m but usable signals on 40m (about S3).
- inputing:-
+ inputting:-
terrible accurate, but it is included for completeness.
- 9.120. show/node (1)
+ 9.139. show/newconfiguration (0)
+
+ show/newconfiguration [<node>] Show all the nodes and users visible
+
+
+ This command allows you to see all the users that can be seen and the
+ nodes to which they are connected.
+
+ This command produces essentially the same information as
+ SHOW/CONFIGURATION except that it shows all the duplication of any
+ routes that might be present It also uses a different format which may
+ not take up quite as much space if you don't have any loops.
+
+ BE WARNED: the list that is returned can be VERY long
+
+
+ 9.140. show/newconfiguration/node (0)
+
+ show/newconfiguration/node Show all the nodes connected locally
+
+
+ Show all the nodes connected to this node in the new format.
+
+
+ 9.141. show/node (1)
show/node [<node_call> ...] Show the type and version number of nodes
the non-user callsigns known to the system will be displayed.
- 9.121. show/prefix (0)
+ 9.142. show/prefix (0)
show/prefix <callsign> Interrogate the prefix database
- 9.122. show/program (5)
+ 9.143. show/program (5)
show/program Show the locations of all the included program modules
from.
- 9.123. show/qra (0)
+ 9.144. show/qra (0)
show/qra <locator> [<locator>] Show the distance between locators
show/qra <lat> <long> Convert latitude and longitude to a locator
SH/QRA IO92QL
SH/QRA JN06 IN73
-
-
-
The first example will show the distance and bearing to the locator
from yourself, the second example will calculate the distance and
bearing from the first locator to the second. You can use 4 or 6
- 9.124. show/qrz (0)
+ 9.145. show/qrz (0)
show/qrz <callsign> Show any callbook details on a callsign
provided for users of this software by http://www.qrz.com
+ 9.146. show/registered (9)
+ show/registered [<prefix>[ Show the registered users
- 9.125. show/route (0)
+ 9.147. show/route (0)
show/route <callsign> Show the route to <callsign>
- 9.126. show/satellite (0)
+ 9.148. show/satellite (0)
show/satellite <name> [<hours> <interval>] Show satellite tracking
data
give information for the next three hours for every five minute
period.
+
You can alter the number of hours and the step size, within certain
limits.
- 9.127. show/sun (0)
+ 9.149. show/sun (0)
show/sun [<prefix>|<callsign>] Show sun rise and set times
If all else fails it will show the sunrise and set times for the node
that you are connected to.
-
For example:-
- 9.128. show/time (0)
+ 9.150. show/time (0)
show/time [<prefix>|<callsign>] Show the local time
including DST) at the prefixes or callsigns that you specify.
- 9.129. show/wcy (0)
+ 9.151. show/vhfstats (0)
+
+ show/vhfstats Show the VHF DX Statistics for last 31 days
+
+
+ Show the VHF DX spots breakdown by band for the last 31 days
+
+
+ 9.152. show/vhftable (0)
+
+ show/vhftable Show the VHF DX Spotter Table for your country
+
+ Show the VHF DX Spotter table for your country for the last 31 days
+
+
+ 9.153. show/wcy (0)
show/wcy Show the last 10 WCY broadcasts
show/wcy <n> Show the last <n> WCY broadcasts
system
- 9.130. show/wwv (0)
+ 9.154. show/wwv (0)
show/wwv Show the last 10 WWV broadcasts
show/wwv <n> Show the last <n> WWV broadcasts
- 9.131. shutdown (5)
+ 9.155. shutdown (5)
shutdown Shutdown the cluster
set to respawn in /etc/inittab it will of course restart.
- 9.132. spoof (9)
+ 9.156. spoof (9)
spoof <callsign> <command> Run commands as another user
like home_node for example.
-
-
-
- 9.133. stat/db (5)
+ 9.157. stat/db (5)
stat/db <dbname> Show the status of a database
other than a sysop.
- 9.134. stat/channel (5)
+ 9.158. stat/channel (5)
stat/channel <callsign> Show the status of a channel on the cluster
Only the fields that are defined (in perl term) will be displayed.
-
- 9.135. stat/msg (5)
+ 9.159. stat/msg (5)
stat/msg <msgno> Show the status of a message
displayed.
- 9.136. stat/route_node (5)
+ 9.160. stat/route_node (5)
stat/route_node <callsign> Show the data in a Route::Node object
- 9.137. stat/route_user (5)
+ 9.161. stat/route_user (5)
stat/route_user <callsign> Show the data in a Route::User object
- 9.138. stat/user (5)
+ 9.162. stat/user (5)
stat/user <callsign> Show the full status of a user
Only the fields that are defined (in perl term) will be displayed.
- 9.139. sysop (0)
+ 9.163. sysop (0)
sysop Regain your privileges if you login remotely
- aa2bbbb0ccc5ddd7xxx3n
- or 2 0 5 7 3
- or 20573
+
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
case sensitive.
- 9.140. talk (0)
+ 9.164. talk (0)
talk <callsign> Enter talk mode with <callsign>
talk <callsign> <text> Send a text message to <callsign>
If you want to do something (such as send a spot) you precede the
normal command with a '/' character, eg:-
+
+
+
/DX 14001 G1TLH What's a B class licensee doing on 20m CW?
/HELP talk
- 9.141. type (0)
+
+
+
+ 9.165. type (0)
type <filearea>/<name> Look at a file in one of the fileareas
content.
- 9.142. who (0)
+ 9.166. who (0)
who Show who is physically connected locally
what sort of connection they have
- 9.143. wx (0)
+ 9.167. wx (0)
wx <text> Send a weather message to local users
wx full <text> Send a weather message to all cluster users
extreme that may indicate enhanced conditions
- 9.144. wx (enhanced for sysops) (5)
+ 9.168. wx (enhanced for sysops) (5)
wx sysop <text> Send a weather message to other clusters only
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
projects / spider.git / commitdiff