<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>
projects / spider.git / blobdiff