<P><CODE><B>dbavail</B> Show a list of all the Databases in the system</CODE></P>
<P>Title says it all really, this command lists all the databases definedin the system. It is also aliased to SHOW/COMMAND.</P>
-<H2><A NAME="ss11.30">11.30</A> <A HREF="adminmanual_en.html#toc11.30">dbshow <dbname> <key> (0)</A>
+<H2><A NAME="ss11.30">11.30</A> <A HREF="adminmanual_en.html#toc11.30">dbcreate <name> (9)</A>
+</H2>
+
+<P><CODE><B>dbcreate <name></B> Create a database entry</CODE></P>
+
+<H2><A NAME="ss11.31">11.31</A> <A HREF="adminmanual_en.html#toc11.31">dbcreate <name> chain <name> [<name>..] (9)</A>
+</H2>
+
+<P><CODE><B>dbcreate <name> chain <name> [<name>..]</B> Create a chained database entry</CODE></P>
+
+<H2><A NAME="ss11.32">11.32</A> <A HREF="adminmanual_en.html#toc11.32">dbcreate <name> cmd <dxspider command> (9)</A>
+</H2>
+
+<P><CODE><B>dbcreate <name> cmd <dxspider command></B> make a local command available as a DB</CODE></P>
+<P>DBCREATE allows you to define a database in the system. It doesn't actuallycreate anything, just defines it.The databases that are created are simple DB_File hash databases, they are therefore already 'indexed'.You can define a local database with the first form of the command eg:
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBCREATE oblast
+</PRE>
+</CODE></BLOCKQUOTE>
+You can also chain databases with the addition of the 'chain' keyword. This will search each database one after the other. A typical example is:
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBCREATE sdx_qsl chain sql_ad
+</PRE>
+</CODE></BLOCKQUOTE>
+No checking is done to see if the any of the chained databases exist, infact it is usually better to do the above staement first then do each ofthe chained databases.Databases can exist offsite. To define a database that lives on another node do:
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBCREATE buckmaster remote gb7dxc
+</PRE>
+</CODE></BLOCKQUOTE>
+Remote databases cannot be chained; however, the last database in a a chain can be a remote database eg:
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBCREATE qsl chain gb7dxc
+</PRE>
+</CODE></BLOCKQUOTE>
+To see what databases have been defined do:
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBAVAIL (or it will have been aliased to SHOW/COMMAND)
+</PRE>
+</CODE></BLOCKQUOTE>
+It would be normal for you to add an entry into your local Aliases fileto allow people to use the 'SHOW/<dbname>' style syntax. So you wouldneed to add a line like:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ 's' => [ .. .. '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', .. .. ],
+</PRE>
+</CODE></BLOCKQUOTE>
+to allow
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/BUCK g1tlh
+</PRE>
+</CODE></BLOCKQUOTE>
+to work as they may be used to.You can also make local commands available as 'pseudo' databases. Youcan therefore make spider special commands available as a database. Iimagine that this will be primarily useful for remote access from legacy nodes. For example:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBCREATE dxqsl cmd show/dxqsl
+</PRE>
+</CODE></BLOCKQUOTE>
+You also use one of these databases in a chain. This may be useful locally. See DBIMPORT for the importing of existing AK1A format data to databases.See DBSHOW for generic database enquiry</P>
+<H2><A NAME="ss11.33">11.33</A> <A HREF="adminmanual_en.html#toc11.33">dbcreate <name> remote <node> (9)</A>
+</H2>
+
+<P><CODE><B>dbcreate <name> remote <node></B> Create a remote database entry</CODE></P>
+
+<H2><A NAME="ss11.34">11.34</A> <A HREF="adminmanual_en.html#toc11.34">dbimport <dbname> <filename> (9)</A>
+</H2>
+
+<P><CODE><B>dbimport <dbname> <filename></B> Import AK1A data into a database</CODE></P>
+<P>If you want to import or update data in bulk to a database you can usethis command. It will either create or update entries into an existingdatabase. For example:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBIMPORT oblast /tmp/OBLAST.FUL
+</PRE>
+</CODE></BLOCKQUOTE>
+will import the standard OBLAST database that comes with AK1A into theoblast database held locally.</P>
+<H2><A NAME="ss11.35">11.35</A> <A HREF="adminmanual_en.html#toc11.35">dbremove <dbname> (9)</A>
+</H2>
+
+<P><CODE><B>dbremove <dbname></B> Delete a database</CODE></P>
+<P>DBREMOVE will completely remove a database entry and also delete any datafile that is associated with it. There is no warning, no comeback, no safety net. For example:
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBREMOVE oblast
+</PRE>
+</CODE></BLOCKQUOTE>
+will remove the oblast database from the system and it will also removethe associated datafile.I repeat:There is no warning, no comeback, no safety net.You have been warned.</P>
+<H2><A NAME="ss11.36">11.36</A> <A HREF="adminmanual_en.html#toc11.36">dbshow <dbname> <key> (0)</A>
</H2>
<P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.31">11.31</A> <A HREF="adminmanual_en.html#toc11.31">directory (0)</A>
+<H2><A NAME="ss11.37">11.37</A> <A HREF="adminmanual_en.html#toc11.37">debug (9)</A>
+</H2>
+
+<P><CODE><B>debug</B> Set the cluster program into debug mode</CODE></P>
+<P>Executing this command will only have an effect if you are running the clusterin debug mode i.e.
+<BLOCKQUOTE><CODE>
+<PRE>
+ perl -d cluster.pl
+</PRE>
+</CODE></BLOCKQUOTE>
+It will interrupt the cluster just after the debug command has finished.</P>
+<H2><A NAME="ss11.38">11.38</A> <A HREF="adminmanual_en.html#toc11.38">delete/usdb <callsign> ... (9)</A>
+</H2>
+
+<P><CODE><B>delete/usdb <callsign> ...</B> Delete this user from the US State Database</CODE></P>
+<P>This command will completely remove a one or more callsignsfrom the US States database.There is NO SECOND CHANCE.It goes without saying that you should use this command CAREFULLY!Note that these callsign may be re-instated by any weekly updates from the FCC.</P>
+<H2><A NAME="ss11.39">11.39</A> <A HREF="adminmanual_en.html#toc11.39">delete/user <callsign> ... (9)</A>
+</H2>
+
+<P><CODE><B>delete/user <callsign> ...</B> Delete this user from the User Database</CODE></P>
+<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!</P>
+<H2><A NAME="ss11.40">11.40</A> <A HREF="adminmanual_en.html#toc11.40">demonstrate <call> <command> (9)</A>
+</H2>
+
+<P><CODE><B>demonstrate <call> <command></B> Demonstrate a command to another user</CODE></P>
+<P>This command is provided so that sysops can demonstrate commands to other users. It runs a command as though that user had typed it in andthen sends the output to that user, together with the command that caused it.
+<BLOCKQUOTE><CODE>
+<PRE>
+ DEMO g7brn sh/dx iota oc209 DEMO g1tlh set/here
+</PRE>
+</CODE></BLOCKQUOTE>
+Note that this command is similar to SPOOF and will have the same sideeffects. Commands are run at the privilege of the user which is beingdemonstrated to. </P>
+<H2><A NAME="ss11.41">11.41</A> <A HREF="adminmanual_en.html#toc11.41">directory (0)</A>
</H2>
<P><CODE><B>directory</B> List messages </CODE></P>
-<H2><A NAME="ss11.32">11.32</A> <A HREF="adminmanual_en.html#toc11.32">directory <from>-<to> (0)</A>
+<H2><A NAME="ss11.42">11.42</A> <A HREF="adminmanual_en.html#toc11.42">directory <from>-<to> (0)</A>
</H2>
<P><CODE><B>directory <from>-<to></B> List messages <from> message <to> message </CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.33">11.33</A> <A HREF="adminmanual_en.html#toc11.33">directory <nn> (0)</A>
+<H2><A NAME="ss11.43">11.43</A> <A HREF="adminmanual_en.html#toc11.43">directory <nn> (0)</A>
</H2>
<P><CODE><B>directory <nn></B> List last <nn> messages</CODE></P>
-<H2><A NAME="ss11.34">11.34</A> <A HREF="adminmanual_en.html#toc11.34">directory all (0)</A>
+<H2><A NAME="ss11.44">11.44</A> <A HREF="adminmanual_en.html#toc11.44">directory all (0)</A>
</H2>
<P><CODE><B>directory all</B> List all messages</CODE></P>
-<H2><A NAME="ss11.35">11.35</A> <A HREF="adminmanual_en.html#toc11.35">directory from <call> (0)</A>
+<H2><A NAME="ss11.45">11.45</A> <A HREF="adminmanual_en.html#toc11.45">directory from <call> (0)</A>
</H2>
<P><CODE><B>directory from <call></B> List all messages from <call></CODE></P>
-<H2><A NAME="ss11.36">11.36</A> <A HREF="adminmanual_en.html#toc11.36">directory new (0)</A>
+<H2><A NAME="ss11.46">11.46</A> <A HREF="adminmanual_en.html#toc11.46">directory new (0)</A>
</H2>
<P><CODE><B>directory new</B> List all new messages</CODE></P>
-<H2><A NAME="ss11.37">11.37</A> <A HREF="adminmanual_en.html#toc11.37">directory own (0)</A>
+<H2><A NAME="ss11.47">11.47</A> <A HREF="adminmanual_en.html#toc11.47">directory own (0)</A>
</H2>
<P><CODE><B>directory own</B> List your own messages</CODE></P>
-<H2><A NAME="ss11.38">11.38</A> <A HREF="adminmanual_en.html#toc11.38">directory subject <string> (0)</A>
+<H2><A NAME="ss11.48">11.48</A> <A HREF="adminmanual_en.html#toc11.48">directory subject <string> (0)</A>
</H2>
<P><CODE><B>directory subject <string></B> List all messages with <string> in subject</CODE></P>
-<H2><A NAME="ss11.39">11.39</A> <A HREF="adminmanual_en.html#toc11.39">directory to <call> (0)</A>
+<H2><A NAME="ss11.49">11.49</A> <A HREF="adminmanual_en.html#toc11.49">directory to <call> (0)</A>
</H2>
<P><CODE><B>directory to <call></B> List all messages to <call></CODE></P>
-<H2><A NAME="ss11.40">11.40</A> <A HREF="adminmanual_en.html#toc11.40">directory- (5)</A>
+<H2><A NAME="ss11.50">11.50</A> <A HREF="adminmanual_en.html#toc11.50">directory- (5)</A>
</H2>
<P><CODE><B>directory-</B> </CODE></P>
<P>Sysops can see all users' messages.</P>
-<H2><A NAME="ss11.41">11.41</A> <A HREF="adminmanual_en.html#toc11.41">disconnect <call> [<call> ...] (8)</A>
+<H2><A NAME="ss11.51">11.51</A> <A HREF="adminmanual_en.html#toc11.51">disconnect <call> [<call> ...] (8)</A>
</H2>
<P><CODE><B>disconnect <call> [<call> ...]</B> Disconnect a user or cluster</CODE></P>
<P>Disconnect any <call> connected locally</P>
-<H2><A NAME="ss11.42">11.42</A> <A HREF="adminmanual_en.html#toc11.42">dx [by <call>] <freq> <call> <remarks> (0)</A>
+<H2><A NAME="ss11.52">11.52</A> <A HREF="adminmanual_en.html#toc11.52">dx [by <call>] <freq> <call> <remarks> (0)</A>
</H2>
<P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
The <freq> is compared against the available bands set up in the cluster. See SHOW/BANDS for more information.</P>
-<H2><A NAME="ss11.43">11.43</A> <A HREF="adminmanual_en.html#toc11.43">echo <line> (0)</A>
+<H2><A NAME="ss11.53">11.53</A> <A HREF="adminmanual_en.html#toc11.53">echo <line> (0)</A>
</H2>
<P><CODE><B>echo <line></B> Echo the line to the output</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
on the output.</P>
-<H2><A NAME="ss11.44">11.44</A> <A HREF="adminmanual_en.html#toc11.44">filtering... (0)</A>
+<H2><A NAME="ss11.54">11.54</A> <A HREF="adminmanual_en.html#toc11.54">export <msgno> <filename> (9)</A>
+</H2>
+
+<P><CODE><B>export <msgno> <filename></B> Export a message to a file</CODE></P>
+<P>Export a message to a file. This command can only be executed on a localconsole with a fully privileged user. The file produced will be in a formready to be imported back into the cluster by placing it in the import directory (/spider/msg/import).This command cannot overwrite an existing file. This is to provide some measure of security. Any files written will owned by the same user as the main cluster, otherwise you can put the new files anywhere the cluster canaccess. For example:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ EXPORT 2345 /tmp/a
+</PRE>
+</CODE></BLOCKQUOTE>
+</P>
+<H2><A NAME="ss11.55">11.55</A> <A HREF="adminmanual_en.html#toc11.55">export_users [<filename>] (9)</A>
+</H2>
+
+<P><CODE><B>export_users [<filename>]</B> Export the users database to ascii</CODE></P>
+<P>Export the users database to a file in ascii format. If no filenameis given then it will export the file to /spider/data/user_asc.If the file already exists it will be renamed to <filename>.o. In factup to 5 generations of the file can be kept each one with an extra 'o' on thesuffix. BE WARNED: this will write to any file you have write access to. No check ismade on the filename (if any) that you specify.</P>
+<H2><A NAME="ss11.56">11.56</A> <A HREF="adminmanual_en.html#toc11.56">filtering... (0)</A>
</H2>
<P><CODE><B>filtering...</B> Filtering things in DXSpider</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
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 executedfirst, any non hf/cw spot is passed to the accept line, which letsthru everything else on HF.The next filter line lets through just VHF/UHF spots from EU.</P>
-<H2><A NAME="ss11.45">11.45</A> <A HREF="adminmanual_en.html#toc11.45">forward/latlong <node_call> (8)</A>
+<H2><A NAME="ss11.57">11.57</A> <A HREF="adminmanual_en.html#toc11.57">forward/latlong <node_call> (8)</A>
</H2>
<P><CODE><B>forward/latlong <node_call></B> Send latitude and longitude information to another cluster</CODE></P>
<P>This command sends all the latitude and longitude information that yourcluster is holding against callsigns. One advantage of recieving thisinformation is that more locator information is held by you. Thismeans that more locators are given on the DX line assuming you haveSET/DXGRID enabled. This could be a LOT of information though, soit is not recommended on slow links.</P>
-<H2><A NAME="ss11.46">11.46</A> <A HREF="adminmanual_en.html#toc11.46">forward/opernam <call> (1)</A>
+<H2><A NAME="ss11.58">11.58</A> <A HREF="adminmanual_en.html#toc11.58">forward/opernam <call> (1)</A>
</H2>
<P><CODE><B>forward/opernam <call></B> Send out information on this <call> to all clusters</CODE></P>
<P>This command sends out any information held in the user file which can be broadcast in PC41 protocol packets. This information is Name, QTH, Locationand Homenode. PC41s are only sent for the information that is available.</P>
-<H2><A NAME="ss11.47">11.47</A> <A HREF="adminmanual_en.html#toc11.47">help (0)</A>
+<H2><A NAME="ss11.59">11.59</A> <A HREF="adminmanual_en.html#toc11.59">help (0)</A>
</H2>
<P><CODE><B>help</B> The HELP Command</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
Where <cmd> is the name of the command you want help on.All commands can be abbreviated, so SHOW/DX can be abbreviatedto SH/DX, ANNOUNCE can be shortened to AN and so on.Look at the APROPOS <string> command which will search the help databasefor the <string> you specify and give you a list of likely commandsto look at with HELP.</P>
-<H2><A NAME="ss11.48">11.48</A> <A HREF="adminmanual_en.html#toc11.48">init <node> (5)</A>
+<H2><A NAME="ss11.60">11.60</A> <A HREF="adminmanual_en.html#toc11.60">init <node> (5)</A>
</H2>
<P><CODE><B>init <node></B> Re-initialise a link to an AK1A compatible node</CODE></P>
<P>This command attempts to re-initialise a link to a (usually) AK1A nodethat has got confused, usually by a protocol loop of some kind. It maywork - but you usually will be better off simply disconnecting it (orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F <yournode>).Best of luck - you will need it.</P>
-<H2><A NAME="ss11.49">11.49</A> <A HREF="adminmanual_en.html#toc11.49">kill (5)</A>
+<H2><A NAME="ss11.61">11.61</A> <A HREF="adminmanual_en.html#toc11.61">kill (5)</A>
</H2>
<P><CODE><B>kill</B> </CODE></P>
<P>As a sysop you can kill any message on the system.</P>
-<H2><A NAME="ss11.50">11.50</A> <A HREF="adminmanual_en.html#toc11.50">kill <from msgno>-<to msgno> (0)</A>
+<H2><A NAME="ss11.62">11.62</A> <A HREF="adminmanual_en.html#toc11.62">kill <from msgno>-<to msgno> (0)</A>
</H2>
<P><CODE><B>kill <from msgno>-<to msgno></B> Delete a range of messages</CODE></P>
-<H2><A NAME="ss11.51">11.51</A> <A HREF="adminmanual_en.html#toc11.51">kill <from>-<to> (5)</A>
+<H2><A NAME="ss11.63">11.63</A> <A HREF="adminmanual_en.html#toc11.63">kill <from>-<to> (5)</A>
</H2>
<P><CODE><B>kill <from>-<to></B> Remove a range of messages from the system</CODE></P>
-<H2><A NAME="ss11.52">11.52</A> <A HREF="adminmanual_en.html#toc11.52">kill <msgno> [<msgno..] (0)</A>
+<H2><A NAME="ss11.64">11.64</A> <A HREF="adminmanual_en.html#toc11.64">kill <msgno> [<msgno..] (0)</A>
</H2>
<P><CODE><B>kill <msgno> [<msgno..]</B> Delete a message from the local system</CODE></P>
-<H2><A NAME="ss11.53">11.53</A> <A HREF="adminmanual_en.html#toc11.53">kill <msgno> [<msgno> ...] (0)</A>
+<H2><A NAME="ss11.65">11.65</A> <A HREF="adminmanual_en.html#toc11.65">kill <msgno> [<msgno> ...] (0)</A>
</H2>
<P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system</CODE></P>
<P>You can get rid of any message to or originating from your callsign using this command. You can remove more than one message at a time.</P>
-<H2><A NAME="ss11.54">11.54</A> <A HREF="adminmanual_en.html#toc11.54">kill expunge <msgno> [<msgno..] (6)</A>
+<H2><A NAME="ss11.66">11.66</A> <A HREF="adminmanual_en.html#toc11.66">kill expunge <msgno> [<msgno..] (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 messagefor deletion. The actual deletion only happens later (usually two days later).The KILL EXPUNGE command causes the message to be truly deleted more or lessimmediately.It otherwise is used in the same way as the KILL command.</P>
-<H2><A NAME="ss11.55">11.55</A> <A HREF="adminmanual_en.html#toc11.55">kill from <call> (5)</A>
+<H2><A NAME="ss11.67">11.67</A> <A HREF="adminmanual_en.html#toc11.67">kill from <call> (5)</A>
</H2>
<P><CODE><B>kill from <call></B> Remove all messages from a callsign</CODE></P>
-<H2><A NAME="ss11.56">11.56</A> <A HREF="adminmanual_en.html#toc11.56">kill full <msgno> [<msgno..] (5)</A>
+<H2><A NAME="ss11.68">11.68</A> <A HREF="adminmanual_en.html#toc11.68">kill full <msgno> [<msgno..] (5)</A>
</H2>
<P><CODE><B>kill full <msgno> [<msgno..]</B> Delete a message from the whole cluster</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
will delete a message (usually a 'bulletin') from the whole cluster system. This uses the subject field, so any messages that have exactly thesame subject will be deleted. Beware!</P>
-<H2><A NAME="ss11.57">11.57</A> <A HREF="adminmanual_en.html#toc11.57">kill full <msgno> [<msgno] (5)</A>
+<H2><A NAME="ss11.69">11.69</A> <A HREF="adminmanual_en.html#toc11.69">kill full <msgno> [<msgno] (5)</A>
</H2>
<P><CODE><B>kill full <msgno> [<msgno]</B> Remove a message from the entire cluster</CODE></P>
<P>Remove this message from the entire cluster system as well as your node.</P>
-<H2><A NAME="ss11.58">11.58</A> <A HREF="adminmanual_en.html#toc11.58">kill to <call> (5)</A>
+<H2><A NAME="ss11.70">11.70</A> <A HREF="adminmanual_en.html#toc11.70">kill to <call> (5)</A>
</H2>
<P><CODE><B>kill to <call></B> Remove all messages to a callsign</CODE></P>
-<H2><A NAME="ss11.59">11.59</A> <A HREF="adminmanual_en.html#toc11.59">kill from <regex> (0)</A>
+<H2><A NAME="ss11.71">11.71</A> <A HREF="adminmanual_en.html#toc11.71">kill from <regex> (0)</A>
</H2>
<P><CODE><B>kill from <regex></B> Delete messages FROM a callsign or pattern</CODE></P>
-<H2><A NAME="ss11.60">11.60</A> <A HREF="adminmanual_en.html#toc11.60">kill to <regex> (0)</A>
+<H2><A NAME="ss11.72">11.72</A> <A HREF="adminmanual_en.html#toc11.72">kill to <regex> (0)</A>
</H2>
<P><CODE><B>kill to <regex></B> Delete messages TO a callsign or pattern</CODE></P>
-<H2><A NAME="ss11.61">11.61</A> <A HREF="adminmanual_en.html#toc11.61">links (0)</A>
+<H2><A NAME="ss11.73">11.73</A> <A HREF="adminmanual_en.html#toc11.73">links (0)</A>
</H2>
<P><CODE><B>links</B> Show which nodes is physically connected</CODE></P>
<P>This is a quick listing that shows which links are connected andsome information about them. See WHO for a list of all connections.</P>
-<H2><A NAME="ss11.62">11.62</A> <A HREF="adminmanual_en.html#toc11.62">load/keps (5)</A>
+<H2><A NAME="ss11.74">11.74</A> <A HREF="adminmanual_en.html#toc11.74">load/aliases (9)</A>
+</H2>
+
+<P><CODE><B>load/aliases</B> Reload the command alias table</CODE></P>
+<P>Reload the /spider/cmd/Aliases file after you have editted it. Youwill need to do this if you change this file whilst the cluster isrunning in order for the changes to take effect.</P>
+<H2><A NAME="ss11.75">11.75</A> <A HREF="adminmanual_en.html#toc11.75">load/badmsg (9)</A>
+</H2>
+
+<P><CODE><B>load/badmsg</B> Reload the bad msg table</CODE></P>
+<P>Reload the /spider/msg/badmsg.pl file if you have changed it manually whilstthe cluster is running. This table contains a number of perl regular 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="ss11.76">11.76</A> <A HREF="adminmanual_en.html#toc11.76">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 whilstthe cluster is running. This file contains a list of words which, if foundon certain text portions of PC protocol, will cause those protocol framesto be rejected. It will all put out a message if any of these words areused 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="ss11.77">11.77</A> <A HREF="adminmanual_en.html#toc11.77">load/bands (9)</A>
+</H2>
+
+<P><CODE><B>load/bands</B> Reload the band limits table</CODE></P>
+<P>Reload the /spider/data/bands.pl file if you have changed it manually whilstthe cluster is running. </P>
+<H2><A NAME="ss11.78">11.78</A> <A HREF="adminmanual_en.html#toc11.78">load/cmd_cache (9)</A>
+</H2>
+
+<P><CODE><B>load/cmd_cache</B> Reload the automatic command cache</CODE></P>
+<P>Normally, if you change a command file in the cmd or local_cmd tree itwill automatially be picked up by the cluster program. Sometimes itcan get confused if you are doing a lot of moving commands about ordelete a command in the local_cmd tree and want to use the normal oneagain. Execute this command to reset everything back to the state itwas just after a cluster restart.</P>
+<H2><A NAME="ss11.79">11.79</A> <A HREF="adminmanual_en.html#toc11.79">load/forward (9)</A>
+</H2>
+
+<P><CODE><B>load/forward</B> Reload the msg forwarding routing table</CODE></P>
+<P>Reload the /spider/msg/forward.pl file if you have changed itmanually whilst the cluster is running.</P>
+<H2><A NAME="ss11.80">11.80</A> <A HREF="adminmanual_en.html#toc11.80">load/keps (5)</A>
</H2>
<P><CODE><B>load/keps</B> Load new keps data</CODE></P>
-<H2><A NAME="ss11.63">11.63</A> <A HREF="adminmanual_en.html#toc11.63">load/keps [nn] (5)</A>
+<H2><A NAME="ss11.81">11.81</A> <A HREF="adminmanual_en.html#toc11.81">load/keps [nn] (5)</A>
</H2>
<P><CODE><B>load/keps [nn]</B> Load new keps data from message</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
on a file containing NASA 2 line keps as a message issued by AMSAT. If there is a message number, then it will take the message, runconvkeps.pl on it and then load the data, all in one step.These messages are sent to ALL by GB7DJK (and others) from time to time. </P>
-<H2><A NAME="ss11.64">11.64</A> <A HREF="adminmanual_en.html#toc11.64">merge <node> [<no spots>/<no wwv>] (5)</A>
+<H2><A NAME="ss11.82">11.82</A> <A HREF="adminmanual_en.html#toc11.82">load/messages (9)</A>
+</H2>
+
+<P><CODE><B>load/messages</B> Reload the system messages file</CODE></P>
+<P>If you change the /spider/perl/Messages file (usually whilstfiddling/writing new commands) you can have them take effect during acluster session by executing this command. You need to do this if getsomething like :-unknown message 'xxxx' in lang 'en'</P>
+<H2><A NAME="ss11.83">11.83</A> <A HREF="adminmanual_en.html#toc11.83">load/prefixes (9)</A>
+</H2>
+
+<P><CODE><B>load/prefixes</B> Reload the prefix table</CODE></P>
+<P>Reload the /spider/data/prefix_data.pl file if you have changed itmanually whilst the cluster is running.</P>
+<H2><A NAME="ss11.84">11.84</A> <A HREF="adminmanual_en.html#toc11.84">merge <node> [<no spots>/<no wwv>] (5)</A>
</H2>
<P><CODE><B>merge <node> [<no spots>/<no wwv>]</B> Ask for the latest spots and WWV </CODE></P>
<P>MERGE allows you to bring your spot and wwv database up to date. By defaultit will request the last 10 spots and 5 WWVs from the node you select. The node must be connected locally.You can request any number of spots or wwv and although they will be appendedto 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="ss11.65">11.65</A> <A HREF="adminmanual_en.html#toc11.65">pc <call> <text> (8)</A>
+<H2><A NAME="ss11.85">11.85</A> <A HREF="adminmanual_en.html#toc11.85">msg <cmd> <msgno> [data ... ] (9)</A>
+</H2>
+
+<P><CODE><B>msg <cmd> <msgno> [data ... ]</B> Alter various message parameters</CODE></P>
+<P>Alter message parameters like To, From, Subject, whether private or bulletinor return receipt (RR) is required or whether to keep this message from timingout.
+<BLOCKQUOTE><CODE>
+<PRE>
+ MSG TO <msgno> <call> - change TO callsign to <call> MSG FRom <msgno> <call> - change FROM callsign to <call> MSG PRrivate <msgno> - set private flag MSG NOPRrivate <msgno> - unset private flag MSG RR <msgno> - set RR flag MSG NORR <msgno> - unset RR flag MSG KEep <msgno> - set the keep flag (message won't be deleted ever) MSG NOKEep <msgno> - unset the keep flag MSG SUbject <msgno> <new> - change the subject to <new> MSG WAittime <msgno> - remove any waitting time for this message MSG NOREad <msgno> - mark message as unread MSG REad <msgno> - mark message as read MSG QUeue - queue any outstanding bulletins MSG QUeue 1 - queue any outstanding private messages
+</PRE>
+</CODE></BLOCKQUOTE>
+You can look at the status of a message by using:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ STAT/MSG <msgno>
+</PRE>
+</CODE></BLOCKQUOTE>
+This will display more information on the message than DIR does.</P>
+<H2><A NAME="ss11.86">11.86</A> <A HREF="adminmanual_en.html#toc11.86">pc <call> <text> (8)</A>
</H2>
<P><CODE><B>pc <call> <text></B> Send arbitrary text to a connected callsign</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
Send any text you like to the callsign requested. This is used mainly to sendPC protocol to connected nodes either for testing or to unstick things. You can also use in the same way as a talk command to a connected user butwithout any processing, added of "from <blah> to <blah" or whatever.</P>
-<H2><A NAME="ss11.66">11.66</A> <A HREF="adminmanual_en.html#toc11.66">ping <node call> (1)</A>
+<H2><A NAME="ss11.87">11.87</A> <A HREF="adminmanual_en.html#toc11.87">ping <node call> (1)</A>
</H2>
<P><CODE><B>ping <node call></B> Check the link quality between nodes</CODE></P>
<P>This command allows you to send a frame to another cluster node onthe network and get a return frame. The time it takes to do thisis a good indication of the quality of the link. The actual timeit takes is output to the console in seconds.Any visible cluster node can be PINGed.</P>
-<H2><A NAME="ss11.67">11.67</A> <A HREF="adminmanual_en.html#toc11.67">rcmd <node call> <cmd> (1)</A>
+<H2><A NAME="ss11.88">11.88</A> <A HREF="adminmanual_en.html#toc11.88">rcmd <node call> <cmd> (1)</A>
</H2>
<P><CODE><B>rcmd <node call> <cmd></B> Send a command to another DX Cluster</CODE></P>
<P>This command allows you to send nearly any command to another DX Clusternode that is connected to the system. Whether you get any output is dependant on a) whether the other system knowsthat the node callsign of this cluster is in fact a node b) whether theother system is allowing RCMDs from this node and c) whether you havepermission to send this command at all.</P>
-<H2><A NAME="ss11.68">11.68</A> <A HREF="adminmanual_en.html#toc11.68">read (0)</A>
+<H2><A NAME="ss11.89">11.89</A> <A HREF="adminmanual_en.html#toc11.89">read (0)</A>
</H2>
<P><CODE><B>read</B> Read the next unread personal message addressed to you</CODE></P>
-<H2><A NAME="ss11.69">11.69</A> <A HREF="adminmanual_en.html#toc11.69">read <msgno> (0)</A>
+<H2><A NAME="ss11.90">11.90</A> <A HREF="adminmanual_en.html#toc11.90">read <msgno> (0)</A>
</H2>
<P><CODE><B>read <msgno></B> Read the specified message</CODE></P>
<P>You can read any messages that are sent as 'non-personal' and also anymessage either sent by or sent to your callsign.</P>
-<H2><A NAME="ss11.70">11.70</A> <A HREF="adminmanual_en.html#toc11.70">read- (5)</A>
+<H2><A NAME="ss11.91">11.91</A> <A HREF="adminmanual_en.html#toc11.91">read- (5)</A>
</H2>
<P><CODE><B>read-</B> </CODE></P>
<P>As a sysop you may read any message on the system</P>
-<H2><A NAME="ss11.71">11.71</A> <A HREF="adminmanual_en.html#toc11.71">reject (0)</A>
+<H2><A NAME="ss11.92">11.92</A> <A HREF="adminmanual_en.html#toc11.92">reject (0)</A>
</H2>
<P><CODE><B>reject</B> Set a filter to reject something</CODE></P>
<P>Create a filter to reject somethingThere are 2 types of filter, accept and reject. See HELP FILTERING for moreinfo.</P>
-<H2><A NAME="ss11.72">11.72</A> <A HREF="adminmanual_en.html#toc11.72">reject/announce <call> [input] [0-9] <pattern> (8)</A>
+<H2><A NAME="ss11.93">11.93</A> <A HREF="adminmanual_en.html#toc11.93">reject/announce <call> [input] [0-9] <pattern> (8)</A>
</H2>
<P><CODE><B>reject/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.73">11.73</A> <A HREF="adminmanual_en.html#toc11.73">reject/announce [0-9] <pattern> (0)</A>
+<H2><A NAME="ss11.94">11.94</A> <A HREF="adminmanual_en.html#toc11.94">reject/announce [0-9] <pattern> (0)</A>
</H2>
<P><CODE><B>reject/announce [0-9] <pattern></B> Set a 'reject' filter line for announce</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
but this probably for advanced users...</P>
-<H2><A NAME="ss11.74">11.74</A> <A HREF="adminmanual_en.html#toc11.74">reject/route <call> [0-9] <pattern> (8)</A>
+<H2><A NAME="ss11.95">11.95</A> <A HREF="adminmanual_en.html#toc11.95">reject/route <call> [0-9] <pattern> (8)</A>
</H2>
<P><CODE><B>reject/route <call> [0-9] <pattern></B> Set an 'reject' filter line for routing</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.</P>
-<H2><A NAME="ss11.75">11.75</A> <A HREF="adminmanual_en.html#toc11.75">reject/spots <call> [input] [0-9] <pattern> (8)</A>
+<H2><A NAME="ss11.96">11.96</A> <A HREF="adminmanual_en.html#toc11.96">reject/spots <call> [input] [0-9] <pattern> (8)</A>
</H2>
<P><CODE><B>reject/spots <call> [input] [0-9] <pattern></B> Spot filter sysop version</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.76">11.76</A> <A HREF="adminmanual_en.html#toc11.76">reject/spots [0-9] <pattern> (0)</A>
+<H2><A NAME="ss11.97">11.97</A> <A HREF="adminmanual_en.html#toc11.97">reject/spots [0-9] <pattern> (0)</A>
</H2>
<P><CODE><B>reject/spots [0-9] <pattern></B> Set a 'reject' filter line for spots</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
but this probably for advanced users...</P>
-<H2><A NAME="ss11.77">11.77</A> <A HREF="adminmanual_en.html#toc11.77">reject/wcy <call> [input] [0-9] <pattern> (8)</A>
+<H2><A NAME="ss11.98">11.98</A> <A HREF="adminmanual_en.html#toc11.98">reject/wcy <call> [input] [0-9] <pattern> (8)</A>
</H2>
<P><CODE><B>reject/wcy <call> [input] [0-9] <pattern></B> WCY filter sysop version</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.78">11.78</A> <A HREF="adminmanual_en.html#toc11.78">reject/wcy [0-9] <pattern> (0)</A>
+<H2><A NAME="ss11.99">11.99</A> <A HREF="adminmanual_en.html#toc11.99">reject/wcy [0-9] <pattern> (0)</A>
</H2>
<P><CODE><B>reject/wcy [0-9] <pattern></B> set a 'reject' WCY filter</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
There are no examples because WCY Broadcasts only come from one place andyou either want them or not (see UNSET/WCY if you don't want them).This command is really provided for future use.See HELP FILTER for information.</P>
-<H2><A NAME="ss11.79">11.79</A> <A HREF="adminmanual_en.html#toc11.79">reject/wwv <call> [input] [0-9] <pattern> (8)</A>
+<H2><A NAME="ss11.100">11.100</A> <A HREF="adminmanual_en.html#toc11.100">reject/wwv <call> [input] [0-9] <pattern> (8)</A>
</H2>
<P><CODE><B>reject/wwv <call> [input] [0-9] <pattern></B> WWV filter sysop version</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.80">11.80</A> <A HREF="adminmanual_en.html#toc11.80">reject/wwv [0-9] <pattern> (0)</A>
+<H2><A NAME="ss11.101">11.101</A> <A HREF="adminmanual_en.html#toc11.101">reject/wwv [0-9] <pattern> (0)</A>
</H2>
<P><CODE><B>reject/wwv [0-9] <pattern></B> set a 'reject' WWV filter</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
is probably the only useful thing to do (which will only show WWV broadcastsby stations in the US).See HELP FILTER for information.</P>
-<H2><A NAME="ss11.81">11.81</A> <A HREF="adminmanual_en.html#toc11.81">reply (0)</A>
+<H2><A NAME="ss11.102">11.102</A> <A HREF="adminmanual_en.html#toc11.102">reply (0)</A>
</H2>
<P><CODE><B>reply</B> Reply (privately) to the last message that you have read</CODE></P>
-<H2><A NAME="ss11.82">11.82</A> <A HREF="adminmanual_en.html#toc11.82">reply <msgno> (0)</A>
+<H2><A NAME="ss11.103">11.103</A> <A HREF="adminmanual_en.html#toc11.103">reply <msgno> (0)</A>
</H2>
<P><CODE><B>reply <msgno></B> Reply (privately) to the specified message</CODE></P>
-<H2><A NAME="ss11.83">11.83</A> <A HREF="adminmanual_en.html#toc11.83">reply b <msgno> (0)</A>
+<H2><A NAME="ss11.104">11.104</A> <A HREF="adminmanual_en.html#toc11.104">reply b <msgno> (0)</A>
</H2>
<P><CODE><B>reply b <msgno></B> Reply as a Bulletin to the specified message</CODE></P>
-<H2><A NAME="ss11.84">11.84</A> <A HREF="adminmanual_en.html#toc11.84">reply noprivate <msgno> (0)</A>
+<H2><A NAME="ss11.105">11.105</A> <A HREF="adminmanual_en.html#toc11.105">reply noprivate <msgno> (0)</A>
</H2>
<P><CODE><B>reply noprivate <msgno></B> Reply as a Bulletin to the specified message</CODE></P>
-<H2><A NAME="ss11.85">11.85</A> <A HREF="adminmanual_en.html#toc11.85">reply rr <msgno> (0)</A>
+<H2><A NAME="ss11.106">11.106</A> <A HREF="adminmanual_en.html#toc11.106">reply rr <msgno> (0)</A>
</H2>
<P><CODE><B>reply rr <msgno></B> Reply to the specified message with read receipt</CODE></P>
<P>You can reply to a message and the subject will automatically have"Re:" inserted in front of it, if it isn't already present.You can also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B that you can use with the SEND command (see SENDfor further details)</P>
-<H2><A NAME="ss11.86">11.86</A> <A HREF="adminmanual_en.html#toc11.86">send <call> [<call> ...] (0)</A>
+<H2><A NAME="ss11.107">11.107</A> <A HREF="adminmanual_en.html#toc11.107">save [-d -t -a] <filename> "<cmd>" [...] (9)</A>
+</H2>
+
+<P><CODE><B>save [-d -t -a] <filename> "<cmd>" [...]</B> Save command output to a file</CODE></P>
+<P>This sysop only cammand allows you to save the output of one or morecommands to a file. For example:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ save /spider/packclus/dxstats show/dxstat
+</PRE>
+</CODE></BLOCKQUOTE>
+will save the output of the normal command "show/dxstat" to the file"dxstats" in the files area.You can have some extra flags to the save which will either date stamp or time stamp or both the filename so:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002 save -t /tmp/a <cmd> creates /tmp/a_2301Z save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
+</PRE>
+</CODE></BLOCKQUOTE>
+The -a flag means append to the file instead of overwriting it.You can have more than one command on the line, to do this you MUSTenclose each command in double quotes (") eg:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
+</PRE>
+</CODE></BLOCKQUOTE>
+or
+<BLOCKQUOTE><CODE>
+<PRE>
+ save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
+</PRE>
+</CODE></BLOCKQUOTE>
+You can only write into places that the cluster has permission for (whichis that of the "sysop" user [which had BETTER NOT BE "root"]), you will need to create any directories you want to put stuff in beforehand as well.It is likely that you will want to run these commands in a crontab type situation. You would do that something like:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
+</PRE>
+</CODE></BLOCKQUOTE>
+Note that you still enclose each command with (") characters but you mustenclose the entire save command in (') characters. Now in fact, this can be varied if you know what you are doing. See theadmin manual for more details.</P>
+<H2><A NAME="ss11.108">11.108</A> <A HREF="adminmanual_en.html#toc11.108">send <call> [<call> ...] (0)</A>
</H2>
<P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns</CODE></P>
-<H2><A NAME="ss11.87">11.87</A> <A HREF="adminmanual_en.html#toc11.87">send copy <msgno> <call> (0)</A>
+<H2><A NAME="ss11.109">11.109</A> <A HREF="adminmanual_en.html#toc11.109">send copy <msgno> <call> (0)</A>
</H2>
<P><CODE><B>send copy <msgno> <call></B> Send a copy of a message to someone</CODE></P>
-<H2><A NAME="ss11.88">11.88</A> <A HREF="adminmanual_en.html#toc11.88">send noprivate <call> (0)</A>
+<H2><A NAME="ss11.110">11.110</A> <A HREF="adminmanual_en.html#toc11.110">send noprivate <call> (0)</A>
</H2>
<P><CODE><B>send noprivate <call></B> Send a message to all stations</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
This will show YOU the output from SH/VHFTABLE and also store it in themessage. You can carry on with the message until you are ready to send it. </P>
-<H2><A NAME="ss11.89">11.89</A> <A HREF="adminmanual_en.html#toc11.89">send private <call> (0)</A>
+<H2><A NAME="ss11.111">11.111</A> <A HREF="adminmanual_en.html#toc11.111">send private <call> (0)</A>
</H2>
<P><CODE><B>send private <call></B> Send a personal message</CODE></P>
-<H2><A NAME="ss11.90">11.90</A> <A HREF="adminmanual_en.html#toc11.90">send rr <call> (0)</A>
+<H2><A NAME="ss11.112">11.112</A> <A HREF="adminmanual_en.html#toc11.112">send rr <call> (0)</A>
</H2>
<P><CODE><B>send rr <call></B> Send a message and ask for a read receipt</CODE></P>
-<H2><A NAME="ss11.91">11.91</A> <A HREF="adminmanual_en.html#toc11.91">set/address <your address> (0)</A>
+<H2><A NAME="ss11.113">11.113</A> <A HREF="adminmanual_en.html#toc11.113">set/address <your address> (0)</A>
</H2>
<P><CODE><B>set/address <your address></B> Record your postal address</CODE></P>
-<H2><A NAME="ss11.92">11.92</A> <A HREF="adminmanual_en.html#toc11.92">set/announce (0)</A>
+<H2><A NAME="ss11.114">11.114</A> <A HREF="adminmanual_en.html#toc11.114">set/announce (0)</A>
</H2>
<P><CODE><B>set/announce</B> Allow announce messages to come out on your terminal</CODE></P>
-<H2><A NAME="ss11.93">11.93</A> <A HREF="adminmanual_en.html#toc11.93">set/anntalk (0)</A>
+<H2><A NAME="ss11.115">11.115</A> <A HREF="adminmanual_en.html#toc11.115">set/anntalk (0)</A>
</H2>
<P><CODE><B>set/anntalk</B> Allow talk like announce messages on your terminal</CODE></P>
-<H2><A NAME="ss11.94">11.94</A> <A HREF="adminmanual_en.html#toc11.94">set/arcluster <call> [<call>..] (5)</A>
+<H2><A NAME="ss11.116">11.116</A> <A HREF="adminmanual_en.html#toc11.116">set/arcluster <call> [<call>..] (5)</A>
</H2>
<P><CODE><B>set/arcluster <call> [<call>..]</B> Make the callsign an AR-Cluster node</CODE></P>
-<H2><A NAME="ss11.95">11.95</A> <A HREF="adminmanual_en.html#toc11.95">set/baddx <call>.. (8)</A>
+<H2><A NAME="ss11.117">11.117</A> <A HREF="adminmanual_en.html#toc11.117">set/baddx <call>.. (8)</A>
</H2>
<P><CODE><B>set/baddx <call>..</B> Stop callsigns in a dx spot being propagated</CODE></P>
-<H2><A NAME="ss11.96">11.96</A> <A HREF="adminmanual_en.html#toc11.96">set/badnode <call>.. (8)</A>
+<H2><A NAME="ss11.118">11.118</A> <A HREF="adminmanual_en.html#toc11.118">set/badnode <call>.. (8)</A>
</H2>
<P><CODE><B>set/badnode <call>..</B> Stop spots from this node being propagated</CODE></P>
-<H2><A NAME="ss11.97">11.97</A> <A HREF="adminmanual_en.html#toc11.97">set/badspotter <call>.. (8)</A>
+<H2><A NAME="ss11.119">11.119</A> <A HREF="adminmanual_en.html#toc11.119">set/badspotter <call>.. (8)</A>
</H2>
<P><CODE><B>set/badspotter <call>..</B> Stop spots from this callsign being propagated</CODE></P>
-<H2><A NAME="ss11.98">11.98</A> <A HREF="adminmanual_en.html#toc11.98">set/badword <word>.. (8)</A>
+<H2><A NAME="ss11.120">11.120</A> <A HREF="adminmanual_en.html#toc11.120">set/badword <word>.. (8)</A>
</H2>
<P><CODE><B>set/badword <word>..</B> Stop things with this word being propagated</CODE></P>
-<H2><A NAME="ss11.99">11.99</A> <A HREF="adminmanual_en.html#toc11.99">set/bbs <call> [<call>..] (5)</A>
+<H2><A NAME="ss11.121">11.121</A> <A HREF="adminmanual_en.html#toc11.121">set/bbs <call> [<call>..] (5)</A>
</H2>
<P><CODE><B>set/bbs <call> [<call>..]</B> Make the callsign a BBS</CODE></P>
-<H2><A NAME="ss11.100">11.100</A> <A HREF="adminmanual_en.html#toc11.100">set/beep (0)</A>
+<H2><A NAME="ss11.122">11.122</A> <A HREF="adminmanual_en.html#toc11.122">set/beep (0)</A>
</H2>
<P><CODE><B>set/beep</B> Add a beep to DX and other messages on your terminal</CODE></P>
-<H2><A NAME="ss11.101">11.101</A> <A HREF="adminmanual_en.html#toc11.101">set/clx <call> [<call>..] (5)</A>
+<H2><A NAME="ss11.123">11.123</A> <A HREF="adminmanual_en.html#toc11.123">set/clx <call> [<call>..] (5)</A>
</H2>
<P><CODE><B>set/clx <call> [<call>..]</B> Make the callsign an CLX node</CODE></P>
-<H2><A NAME="ss11.102">11.102</A> <A HREF="adminmanual_en.html#toc11.102">set/dx (0)</A>
+<H2><A NAME="ss11.124">11.124</A> <A HREF="adminmanual_en.html#toc11.124">set/debug <name> (9)</A>
+</H2>
+
+<P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE></P>
+
+<H2><A NAME="ss11.125">11.125</A> <A HREF="adminmanual_en.html#toc11.125">set/dx (0)</A>
</H2>
<P><CODE><B>set/dx</B> Allow DX messages to come out on your terminal</CODE></P>
-<H2><A NAME="ss11.103">11.103</A> <A HREF="adminmanual_en.html#toc11.103">set/dxcq (0)</A>
+<H2><A NAME="ss11.126">11.126</A> <A HREF="adminmanual_en.html#toc11.126">set/dxcq (0)</A>
</H2>
<P><CODE><B>set/dxcq</B> Show CQ Zones on the end of DX announcements</CODE></P>
-<H2><A NAME="ss11.104">11.104</A> <A HREF="adminmanual_en.html#toc11.104">set/dxgrid (0)</A>
+<H2><A NAME="ss11.127">11.127</A> <A HREF="adminmanual_en.html#toc11.127">set/dxgrid (0)</A>
</H2>
<P><CODE><B>set/dxgrid</B> Allow QRA Grid Squares on the end of DX announcements</CODE></P>
-<H2><A NAME="ss11.105">11.105</A> <A HREF="adminmanual_en.html#toc11.105">set/dxitu (0)</A>
+<H2><A NAME="ss11.128">11.128</A> <A HREF="adminmanual_en.html#toc11.128">set/dxitu (0)</A>
</H2>
<P><CODE><B>set/dxitu</B> Show ITU Zones on the end of DX announcements</CODE></P>
-<H2><A NAME="ss11.106">11.106</A> <A HREF="adminmanual_en.html#toc11.106">set/dxnet <call> [<call>..] (5)</A>
+<H2><A NAME="ss11.129">11.129</A> <A HREF="adminmanual_en.html#toc11.129">set/dxnet <call> [<call>..] (5)</A>
</H2>
<P><CODE><B>set/dxnet <call> [<call>..]</B> Make the callsign an DXNet node</CODE></P>
-<H2><A NAME="ss11.107">11.107</A> <A HREF="adminmanual_en.html#toc11.107">set/echo (0)</A>
+<H2><A NAME="ss11.130">11.130</A> <A HREF="adminmanual_en.html#toc11.130">set/echo (0)</A>
</H2>
<P><CODE><B>set/echo</B> Make the cluster echo your input</CODE></P>
-<H2><A NAME="ss11.108">11.108</A> <A HREF="adminmanual_en.html#toc11.108">set/email <email> ... (0)</A>
+<H2><A NAME="ss11.131">11.131</A> <A HREF="adminmanual_en.html#toc11.131">set/email <email> ... (0)</A>
</H2>
<P><CODE><B>set/email <email> ...</B> Set email address(es) and forward your personals</CODE></P>
-<H2><A NAME="ss11.109">11.109</A> <A HREF="adminmanual_en.html#toc11.109">set/here (0)</A>
+<H2><A NAME="ss11.132">11.132</A> <A HREF="adminmanual_en.html#toc11.132">set/here (0)</A>
</H2>
<P><CODE><B>set/here</B> Tell the system you are present at your terminal</CODE></P>
-<H2><A NAME="ss11.110">11.110</A> <A HREF="adminmanual_en.html#toc11.110">set/homenode <node> (0)</A>
+<H2><A NAME="ss11.133">11.133</A> <A HREF="adminmanual_en.html#toc11.133">set/homenode <node> (0)</A>
</H2>
<P><CODE><B>set/homenode <node> </B> Set your normal cluster callsign</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.111">11.111</A> <A HREF="adminmanual_en.html#toc11.111">set/hops <call> ann|spots|route|wwv|wcy <n> (8)</A>
+<H2><A NAME="ss11.134">11.134</A> <A HREF="adminmanual_en.html#toc11.134">set/hops <call> ann|spots|route|wwv|wcy <n> (8)</A>
</H2>
<P><CODE><B>set/hops <call> ann|spots|route|wwv|wcy <n></B> Set hop count </CODE></P>
-<H2><A NAME="ss11.112">11.112</A> <A HREF="adminmanual_en.html#toc11.112">set/language <lang> (0)</A>
+<H2><A NAME="ss11.135">11.135</A> <A HREF="adminmanual_en.html#toc11.135">set/isolate (9)</A>
+</H2>
+
+<P><CODE><B>set/isolate</B> Isolate a node from the rest of the network</CODE></P>
+<P>Connect a node to your system in such a way that you are a full protocolmember of its network and can see all spots on it, but nothing either leaksout from it nor goes back into from the rest of the nodes connected to you.You can potentially connect several nodes in this way.</P>
+<H2><A NAME="ss11.136">11.136</A> <A HREF="adminmanual_en.html#toc11.136">set/language <lang> (0)</A>
</H2>
<P><CODE><B>set/language <lang></B> Set the language you want to use</CODE></P>
<P>You can select the language that you want the cluster to use. Currentlythe languages available are en (English), de (German), es (Spanish) and nl (Dutch).</P>
-<H2><A NAME="ss11.113">11.113</A> <A HREF="adminmanual_en.html#toc11.113">set/location <lat & long> (0)</A>
+<H2><A NAME="ss11.137">11.137</A> <A HREF="adminmanual_en.html#toc11.137">set/location <lat & long> (0)</A>
</H2>
<P><CODE><B>set/location <lat & long></B> Set your latitude and longitude</CODE></P>
-<H2><A NAME="ss11.114">11.114</A> <A HREF="adminmanual_en.html#toc11.114">set/logininfo (0)</A>
+<H2><A NAME="ss11.138">11.138</A> <A HREF="adminmanual_en.html#toc11.138">set/lockout <call> (9)</A>
+</H2>
+
+<P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE></P>
+
+<H2><A NAME="ss11.139">11.139</A> <A HREF="adminmanual_en.html#toc11.139">set/logininfo (0)</A>
</H2>
<P><CODE><B>set/logininfo</B> Inform when a station logs in locally</CODE></P>
-<H2><A NAME="ss11.115">11.115</A> <A HREF="adminmanual_en.html#toc11.115">set/name <your name> (0)</A>
+<H2><A NAME="ss11.140">11.140</A> <A HREF="adminmanual_en.html#toc11.140">set/name <your name> (0)</A>
</H2>
<P><CODE><B>set/name <your name></B> Set your name</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.116">11.116</A> <A HREF="adminmanual_en.html#toc11.116">set/node <call> [<call>..] (5)</A>
+<H2><A NAME="ss11.141">11.141</A> <A HREF="adminmanual_en.html#toc11.141">set/node <call> [<call>..] (5)</A>
</H2>
<P><CODE><B>set/node <call> [<call>..]</B> Make the callsign an AK1A cluster</CODE></P>
<P>Tell the system that the call(s) are to be treated as AK1A cluster andfed PC Protocol rather normal user commands.</P>
-<H2><A NAME="ss11.117">11.117</A> <A HREF="adminmanual_en.html#toc11.117">set/obscount <count> <call> (8)</A>
+<H2><A NAME="ss11.142">11.142</A> <A HREF="adminmanual_en.html#toc11.142">set/obscount <count> <call> (8)</A>
</H2>
<P><CODE><B>set/obscount <count> <call></B> Set the 'pump-up' obscelence PING counter </CODE></P>
<P>From 1.35 onwards neighbouring nodes are pinged at regular intervals (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'counter which is decremented on every outgoing ping and then reset tothe 'obscount' value on every incoming ping. The default value of thisparameter is 2. What this means is that a neighbouring node will be pinged twice at (default) 300 second intervals and if no reply has been heard just beforewhat would be the third attempt, that node is disconnected.If a ping is heard then the obscount is reset to the full value. Usingdefault values, if a node has not responded to a ping within 15 minutes,it is disconnected.You can set this parameter between 1 and 9.It is STRONGLY recommended that you don't change the default.</P>
-<H2><A NAME="ss11.118">11.118</A> <A HREF="adminmanual_en.html#toc11.118">set/page <lines per page> (0)</A>
+<H2><A NAME="ss11.143">11.143</A> <A HREF="adminmanual_en.html#toc11.143">set/page <lines per page> (0)</A>
</H2>
<P><CODE><B>set/page <lines per page></B> Set the lines per page</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
The setting is stored in your user profile.</P>
-<H2><A NAME="ss11.119">11.119</A> <A HREF="adminmanual_en.html#toc11.119">set/password (0)</A>
+<H2><A NAME="ss11.144">11.144</A> <A HREF="adminmanual_en.html#toc11.144">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 willonly work if you have a password already set. This initial passwordcan 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 youget it right). You may or may not see the data echoed on the screenas you type, depending on the type of telnet client you have.</P>
-<H2><A NAME="ss11.120">11.120</A> <A HREF="adminmanual_en.html#toc11.120">set/prompt <string> (0)</A>
+<H2><A NAME="ss11.145">11.145</A> <A HREF="adminmanual_en.html#toc11.145">set/password <callsign> <string> (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 stringcan contain any characters. The way this field is used depends on context. If it is being used inthe SYSOP command context then you are offered 5 random numbers and youhave to supply the corresponding letters. This is now mainly for ax25connections.If it is being used on incoming telnet connections then, if a passwordis set or the:
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/var $main::passwdreq = 1
+</PRE>
+</CODE></BLOCKQUOTE>
+command is executed in the startup script, then a password prompt isgiven after the normal 'login: ' prompt. </P>
+<H2><A NAME="ss11.146">11.146</A> <A HREF="adminmanual_en.html#toc11.146">set/pinginterval <time> <nodecall> (9)</A>
+</H2>
+
+<P><CODE><B>set/pinginterval <time> <nodecall></B> Set ping time to neighbouring nodes </CODE></P>
+<P>As from release 1.35 all neighbouring nodes are pinged at regular intervalsin order to determine the rolling quality of the link and, in future, toaffect routing decisions. The default interval is 300 secs or 5 minutes.You can use this command to set a different interval. Please don't. But if you do the value you enter is treated as minutes up 30 and secondsfor numbers greater than that.This is used also to help determine when a link is down at the far end(as certain cluster software doesn't always notice), see SET/OBSCOUNTfor more information.If you must change it (and it may be useful for internet connected nodeson dynamic IP addresses that go away after a set time of usage) the timecan be specified as:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ 5 which if less than 30 is converted to minutes otherwise is taken as the no of seconds between pings. 120s 120 seconds 5m 5 minutes 1h 1 hour
+</PRE>
+</CODE></BLOCKQUOTE>
+Please be aware that this causes traffic to occur on the link, setting this value too low may annoy your neighbours beyond the point of endurance!You can switch this off by setting it to 0.</P>
+<H2><A NAME="ss11.147">11.147</A> <A HREF="adminmanual_en.html#toc11.147">set/privilege <n> <call> [<call..] (9)</A>
+</H2>
+
+<P><CODE><B>set/privilege <n> <call> [<call..]</B> Set privilege level on a call</CODE></P>
+<P>Set the privilege level on a callsign. The privilege levels that pertainto commands are as default:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ 0 - normal user 1 - allow remote nodes normal user RCMDs 5 - various privileged commands (including shutdown, but not disc- connect), the normal level for another node. 8 - more privileged commands (including disconnect) 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS LEVEL.
+</PRE>
+</CODE></BLOCKQUOTE>
+If you are a sysop and you come in as a normal user on a remote connectionyour privilege will automatically be set to 0.</P>
+<H2><A NAME="ss11.148">11.148</A> <A HREF="adminmanual_en.html#toc11.148">set/prompt <string> (0)</A>
</H2>
<P><CODE><B>set/prompt <string></B> Set your prompt to <string></CODE></P>
-<H2><A NAME="ss11.121">11.121</A> <A HREF="adminmanual_en.html#toc11.121">set/qra <locator> (0)</A>
+<H2><A NAME="ss11.149">11.149</A> <A HREF="adminmanual_en.html#toc11.149">set/qra <locator> (0)</A>
</H2>
<P><CODE><B>set/qra <locator></B> Set your QRA Grid locator</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.122">11.122</A> <A HREF="adminmanual_en.html#toc11.122">set/qth <your qth> (0)</A>
+<H2><A NAME="ss11.150">11.150</A> <A HREF="adminmanual_en.html#toc11.150">set/qth <your qth> (0)</A>
</H2>
<P><CODE><B>set/qth <your qth></B> Set your QTH</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.123">11.123</A> <A HREF="adminmanual_en.html#toc11.123">set/spider <call> [<call>..] (5)</A>
+<H2><A NAME="ss11.151">11.151</A> <A HREF="adminmanual_en.html#toc11.151">set/register <call> ... (9)</A>
+</H2>
+
+<P><CODE><B>set/register <call> ...</B> Mark a user as registered</CODE></P>
+
+<H2><A NAME="ss11.152">11.152</A> <A HREF="adminmanual_en.html#toc11.152">set/spider <call> [<call>..] (5)</A>
</H2>
<P><CODE><B>set/spider <call> [<call>..]</B> Make the callsign an DXSpider node</CODE></P>
<P>Tell the system that the call(s) are to be treated as DXSpider node andfed new style DX Protocol rather normal user commands.</P>
-<H2><A NAME="ss11.124">11.124</A> <A HREF="adminmanual_en.html#toc11.124">set/talk (0)</A>
+<H2><A NAME="ss11.153">11.153</A> <A HREF="adminmanual_en.html#toc11.153">set/sys_location <lat & long> (9)</A>
+</H2>
+
+<P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE></P>
+<P>In order to get accurate headings and such like you must tell the systemwhat your latitude and longitude is. If you have not yet done a SET/QRAthen this command will set your QRA locator for you. For example:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/LOCATION 52 22 N 0 57 E
+</PRE>
+</CODE></BLOCKQUOTE>
+</P>
+<H2><A NAME="ss11.154">11.154</A> <A HREF="adminmanual_en.html#toc11.154">set/sys_qra <locator> (9)</A>
+</H2>
+
+<P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA Grid locator</CODE></P>
+
+<H2><A NAME="ss11.155">11.155</A> <A HREF="adminmanual_en.html#toc11.155">set/talk (0)</A>
</H2>
<P><CODE><B>set/talk</B> Allow TALK messages to come out on your terminal</CODE></P>
-<H2><A NAME="ss11.125">11.125</A> <A HREF="adminmanual_en.html#toc11.125">set/usstate (0)</A>
+<H2><A NAME="ss11.156">11.156</A> <A HREF="adminmanual_en.html#toc11.156">set/usdb <call> <state> <city> (9)</A>
+</H2>
+
+<P><CODE><B>set/usdb <call> <state> <city></B> add/update a US DB callsign</CODE></P>
+<P>This command allows you to add or alter a callsign in the US statedatabase. Use with extreme caution. Anything you do here will beoverwritten by any weekly updates that affect this callsign
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/usdb g1tlh nh downtown rindge
+</PRE>
+</CODE></BLOCKQUOTE>
+see also DELETE/USDB</P>
+<H2><A NAME="ss11.157">11.157</A> <A HREF="adminmanual_en.html#toc11.157">set/usstate (0)</A>
</H2>
<P><CODE><B>set/usstate</B> Allow US State info on the end of DX announcements</CODE></P>
-<H2><A NAME="ss11.126">11.126</A> <A HREF="adminmanual_en.html#toc11.126">set/wcy (0)</A>
+<H2><A NAME="ss11.158">11.158</A> <A HREF="adminmanual_en.html#toc11.158">set/wcy (0)</A>
</H2>
<P><CODE><B>set/wcy</B> Allow WCY messages to come out on your terminal</CODE></P>
-<H2><A NAME="ss11.127">11.127</A> <A HREF="adminmanual_en.html#toc11.127">set/wwv (0)</A>
+<H2><A NAME="ss11.159">11.159</A> <A HREF="adminmanual_en.html#toc11.159">set/wwv (0)</A>
</H2>
<P><CODE><B>set/wwv</B> Allow WWV messages to come out on your terminal</CODE></P>
-<H2><A NAME="ss11.128">11.128</A> <A HREF="adminmanual_en.html#toc11.128">set/wx (0)</A>
+<H2><A NAME="ss11.160">11.160</A> <A HREF="adminmanual_en.html#toc11.160">set/wx (0)</A>
</H2>
<P><CODE><B>set/wx</B> Allow WX messages to come out on your terminal</CODE></P>
-<H2><A NAME="ss11.129">11.129</A> <A HREF="adminmanual_en.html#toc11.129">show/baddx (1)</A>
+<H2><A NAME="ss11.161">11.161</A> <A HREF="adminmanual_en.html#toc11.161">show/baddx (1)</A>
</H2>
<P><CODE><B>show/baddx</B> Show all the bad dx calls in the system</CODE></P>
<P>Display all the bad dx callsigns in the system, see SET/BADDXfor more information.</P>
-<H2><A NAME="ss11.130">11.130</A> <A HREF="adminmanual_en.html#toc11.130">show/badnode (1)</A>
+<H2><A NAME="ss11.162">11.162</A> <A HREF="adminmanual_en.html#toc11.162">show/badnode (1)</A>
</H2>
<P><CODE><B>show/badnode</B> Show all the bad nodes in the system</CODE></P>
<P>Display all the bad node callsigns in the system, see SET/BADNODEfor more information.</P>
-<H2><A NAME="ss11.131">11.131</A> <A HREF="adminmanual_en.html#toc11.131">show/badspotter (1)</A>
+<H2><A NAME="ss11.163">11.163</A> <A HREF="adminmanual_en.html#toc11.163">show/badspotter (1)</A>
</H2>
<P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE></P>
<P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTERfor more information.</P>
-<H2><A NAME="ss11.132">11.132</A> <A HREF="adminmanual_en.html#toc11.132">show/badword (1)</A>
+<H2><A NAME="ss11.164">11.164</A> <A HREF="adminmanual_en.html#toc11.164">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/BADWORDfor more information.</P>
-<H2><A NAME="ss11.133">11.133</A> <A HREF="adminmanual_en.html#toc11.133">show/configuration [<node>] (0)</A>
+<H2><A NAME="ss11.165">11.165</A> <A HREF="adminmanual_en.html#toc11.165">show/configuration [<node>] (0)</A>
</H2>
<P><CODE><B>show/configuration [<node>]</B> Show all the nodes and users visible</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.134">11.134</A> <A HREF="adminmanual_en.html#toc11.134">show/configuration/node (0)</A>
+<H2><A NAME="ss11.166">11.166</A> <A HREF="adminmanual_en.html#toc11.166">show/configuration/node (0)</A>
</H2>
<P><CODE><B>show/configuration/node</B> Show all the nodes connected locally</CODE></P>
<P>Show all the nodes connected to this node.</P>
-<H2><A NAME="ss11.135">11.135</A> <A HREF="adminmanual_en.html#toc11.135">show/connect (1)</A>
+<H2><A NAME="ss11.167">11.167</A> <A HREF="adminmanual_en.html#toc11.167">show/connect (1)</A>
</H2>
<P><CODE><B>show/connect</B> Show all the active connections</CODE></P>
<P>This command shows information on all the active connections known tothe node. This command gives slightly more information than WHO.</P>
-<H2><A NAME="ss11.136">11.136</A> <A HREF="adminmanual_en.html#toc11.136">show/contest <year and month> (0)</A>
+<H2><A NAME="ss11.168">11.168</A> <A HREF="adminmanual_en.html#toc11.168">show/contest <year and month> (0)</A>
</H2>
<P><CODE><B>show/contest <year and month></B> Show all the contests for a month</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.137">11.137</A> <A HREF="adminmanual_en.html#toc11.137">show/date [<prefix>|<callsign>] (0)</A>
+<H2><A NAME="ss11.169">11.169</A> <A HREF="adminmanual_en.html#toc11.169">show/date [<prefix>|<callsign>] (0)</A>
</H2>
<P><CODE><B>show/date [<prefix>|<callsign>]</B> Show the local time </CODE></P>
<P>This is very nearly the same as SHOW/TIME, the only difference the formatof the date string if no arguments are given.If no prefixes or callsigns are given then this command returns the localtime and UTC as the computer has it right now. If you give some prefixesthen it will show UTC and UTC + the local offset (not including DST) atthe prefixes or callsigns that you specify.</P>
-<H2><A NAME="ss11.138">11.138</A> <A HREF="adminmanual_en.html#toc11.138">show/db0sdx <callsign> (0)</A>
+<H2><A NAME="ss11.170">11.170</A> <A HREF="adminmanual_en.html#toc11.170">show/db0sdx <callsign> (0)</A>
</H2>
<P><CODE><B>show/db0sdx <callsign></B> Show QSL infomation from DB0SDX database</CODE></P>
<P>This command queries the DB0SDX QSL server on the internetand returns any information available for that callsign. This serviceis provided for users of this software by http://www.qslinfo.de.See also SHOW/QRZ, SHOW/WM7D.</P>
-<H2><A NAME="ss11.139">11.139</A> <A HREF="adminmanual_en.html#toc11.139">show/dx (0)</A>
+<H2><A NAME="ss11.171">11.171</A> <A HREF="adminmanual_en.html#toc11.171">show/debug (9)</A>
+</H2>
+
+<P><CODE><B>show/debug</B> Show what levels of debug information you are logging</CODE></P>
+
+<H2><A NAME="ss11.172">11.172</A> <A HREF="adminmanual_en.html#toc11.172">show/dx (0)</A>
</H2>
<P><CODE><B>show/dx</B> Interrogate the spot database</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.140">11.140</A> <A HREF="adminmanual_en.html#toc11.140">show/dxcc <prefix> (0)</A>
+<H2><A NAME="ss11.173">11.173</A> <A HREF="adminmanual_en.html#toc11.173">show/dxcc <prefix> (0)</A>
</H2>
<P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.141">11.141</A> <A HREF="adminmanual_en.html#toc11.141">show/dxqsl <callsign> (0)</A>
+<H2><A NAME="ss11.174">11.174</A> <A HREF="adminmanual_en.html#toc11.174">show/dxqsl <callsign> (0)</A>
</H2>
<P><CODE><B>show/dxqsl <callsign></B> Show any QSL info gathered from spots</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
This gives you more background information.</P>
-<H2><A NAME="ss11.142">11.142</A> <A HREF="adminmanual_en.html#toc11.142">show/dxstats [days] [date] (0)</A>
+<H2><A NAME="ss11.175">11.175</A> <A HREF="adminmanual_en.html#toc11.175">show/dxstats [days] [date] (0)</A>
</H2>
<P><CODE><B>show/dxstats [days] [date]</B> Show the DX Statistics</CODE></P>
<P>Show the total DX spots for the last <days> no of days (default is 31), starting from a <date> (default: today).</P>
-<H2><A NAME="ss11.143">11.143</A> <A HREF="adminmanual_en.html#toc11.143">show/files [<filearea> [<string>]] (0)</A>
+<H2><A NAME="ss11.176">11.176</A> <A HREF="adminmanual_en.html#toc11.176">show/files [<filearea> [<string>]] (0)</A>
</H2>
<P><CODE><B>show/files [<filearea> [<string>]]</B> List the contents of a filearea</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
See also TYPE - to see the contents of a file.</P>
-<H2><A NAME="ss11.144">11.144</A> <A HREF="adminmanual_en.html#toc11.144">show/filter (0)</A>
+<H2><A NAME="ss11.177">11.177</A> <A HREF="adminmanual_en.html#toc11.177">show/filter (0)</A>
</H2>
<P><CODE><B>show/filter</B> Show the contents of all the filters you have set</CODE></P>
<P>Show the contents of all the filters that are set. This command displaysall the filters set - for all the various categories.</P>
-<H2><A NAME="ss11.145">11.145</A> <A HREF="adminmanual_en.html#toc11.145">show/hfstats [days] [date] (0)</A>
+<H2><A NAME="ss11.178">11.178</A> <A HREF="adminmanual_en.html#toc11.178">show/hfstats [days] [date] (0)</A>
</H2>
<P><CODE><B>show/hfstats [days] [date]</B> Show the HF DX Statistics </CODE></P>
<P>Show the HF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a <date> (default: today).</P>
-<H2><A NAME="ss11.146">11.146</A> <A HREF="adminmanual_en.html#toc11.146">show/hftable [days] [date] [prefix ...] (0)</A>
+<H2><A NAME="ss11.179">11.179</A> <A HREF="adminmanual_en.html#toc11.179">show/hftable [days] [date] [prefix ...] (0)</A>
</H2>
<P><CODE><B>show/hftable [days] [date] [prefix ...]</B> Show the HF DX Spotter Table</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.147">11.147</A> <A HREF="adminmanual_en.html#toc11.147">show/hops <call> [ann|spots|route|wcy|wwv] (8)</A>
+<H2><A NAME="ss11.180">11.180</A> <A HREF="adminmanual_en.html#toc11.180">show/hops <call> [ann|spots|route|wcy|wwv] (8)</A>
</H2>
<P><CODE><B>show/hops <call> [ann|spots|route|wcy|wwv]</B> Show the hop counts for a node</CODE></P>
<P>This command shows the hop counts set up for a node. You can specifywhich category you want to see. If you leave the category out then all the categories will be listed.</P>
-<H2><A NAME="ss11.148">11.148</A> <A HREF="adminmanual_en.html#toc11.148">show/isolate (1)</A>
+<H2><A NAME="ss11.181">11.181</A> <A HREF="adminmanual_en.html#toc11.181">show/isolate (1)</A>
</H2>
<P><CODE><B>show/isolate</B> Show list of ISOLATED nodes</CODE></P>
-<H2><A NAME="ss11.149">11.149</A> <A HREF="adminmanual_en.html#toc11.149">show/log [<callsign>] (8)</A>
+<H2><A NAME="ss11.182">11.182</A> <A HREF="adminmanual_en.html#toc11.182">show/lockout <prefix>|all (9)</A>
+</H2>
+
+<P><CODE><B>show/lockout <prefix>|all</B> Show the list of locked out or excluded callsigns</CODE></P>
+
+<H2><A NAME="ss11.183">11.183</A> <A HREF="adminmanual_en.html#toc11.183">show/log [<callsign>] (8)</A>
</H2>
<P><CODE><B>show/log [<callsign>]</B> Show excerpts from the system log</CODE></P>
<P>This command outputs a short section of the system log. On its ownit will output a general logfile. With the optional callsign it willshow output from the log associated with that callsign.</P>
-<H2><A NAME="ss11.150">11.150</A> <A HREF="adminmanual_en.html#toc11.150">show/moon [ndays] [<prefix>|<callsign>] (0)</A>
+<H2><A NAME="ss11.184">11.184</A> <A HREF="adminmanual_en.html#toc11.184">show/moon [ndays] [<prefix>|<callsign>] (0)</A>
</H2>
<P><CODE><B>show/moon [ndays] [<prefix>|<callsign>]</B> Show Moon rise and set times</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
Upto 366 days can be checked both in the past and in the future.Please note that the rise and set times are given as the UT times of rise and set on the requested UT day.</P>
-<H2><A NAME="ss11.151">11.151</A> <A HREF="adminmanual_en.html#toc11.151">show/muf <prefix> [<hours>][long] (0)</A>
+<H2><A NAME="ss11.185">11.185</A> <A HREF="adminmanual_en.html#toc11.185">show/muf <prefix> [<hours>][long] (0)</A>
</H2>
<P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show the likely propagation to a prefix</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
Gives you an estimate of the long path propagation characterics. Itshould be noted that the figures will probably not be very useful, norterrible accurate, but it is included for completeness.</P>
-<H2><A NAME="ss11.152">11.152</A> <A HREF="adminmanual_en.html#toc11.152">show/newconfiguration [<node>] (0)</A>
+<H2><A NAME="ss11.186">11.186</A> <A HREF="adminmanual_en.html#toc11.186">show/newconfiguration [<node>] (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 seenand the nodes to which they are connected. This command produces essentially the same information as SHOW/CONFIGURATION except that it shows all the duplication ofany routes that might be present It also uses a different formatwhich may not take up quite as much space if you don't have anyloops.BE WARNED: the list that is returned can be VERY long</P>
-<H2><A NAME="ss11.153">11.153</A> <A HREF="adminmanual_en.html#toc11.153">show/newconfiguration/node (0)</A>
+<H2><A NAME="ss11.187">11.187</A> <A HREF="adminmanual_en.html#toc11.187">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="ss11.154">11.154</A> <A HREF="adminmanual_en.html#toc11.154">show/node [<callsign> ...] (1)</A>
+<H2><A NAME="ss11.188">11.188</A> <A HREF="adminmanual_en.html#toc11.188">show/node [<callsign> ...] (1)</A>
</H2>
<P><CODE><B>show/node [<callsign> ...]</B> Show the type and version number of nodes</CODE></P>
<P>Show the type and version (if connected) of the nodes specified on thecommand line. If no callsigns are specified then a sorted list of allthe non-user callsigns known to the system will be displayed.</P>
-<H2><A NAME="ss11.155">11.155</A> <A HREF="adminmanual_en.html#toc11.155">show/prefix <callsign> (0)</A>
+<H2><A NAME="ss11.189">11.189</A> <A HREF="adminmanual_en.html#toc11.189">show/prefix <callsign> (0)</A>
</H2>
<P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database </CODE></P>
<P>This command takes the <callsign> (which can be a full or partial callsign or a prefix), looks up which internal country number it is and then displays all the relevant prefixes for that countrytogether with the internal country no, the CQ and ITU regions. See also SHOW/DXCC</P>
-<H2><A NAME="ss11.156">11.156</A> <A HREF="adminmanual_en.html#toc11.156">show/program (5)</A>
+<H2><A NAME="ss11.190">11.190</A> <A HREF="adminmanual_en.html#toc11.190">show/program (5)</A>
</H2>
<P><CODE><B>show/program</B> Show the locations of all the included program modules</CODE></P>
<P>Show the name and location where every program module was load from. Thisis useful for checking where you think you have loaded a .pm file from. </P>
-<H2><A NAME="ss11.157">11.157</A> <A HREF="adminmanual_en.html#toc11.157">show/qra <lat> <long> (0)</A>
+<H2><A NAME="ss11.191">11.191</A> <A HREF="adminmanual_en.html#toc11.191">show/qra <lat> <long> (0)</A>
</H2>
<P><CODE><B>show/qra <lat> <long></B> Convert lat/long to a QRA Grid locator</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.158">11.158</A> <A HREF="adminmanual_en.html#toc11.158">show/qra <locator> [<locator>] (0)</A>
+<H2><A NAME="ss11.192">11.192</A> <A HREF="adminmanual_en.html#toc11.192">show/qra <locator> [<locator>] (0)</A>
</H2>
<P><CODE><B>show/qra <locator> [<locator>]</B> Show distance between QRA Grid locators</CODE></P>
-<H2><A NAME="ss11.159">11.159</A> <A HREF="adminmanual_en.html#toc11.159">show/qrz <callsign> (0)</A>
+<H2><A NAME="ss11.193">11.193</A> <A HREF="adminmanual_en.html#toc11.193">show/qrz <callsign> (0)</A>
</H2>
<P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE></P>
<P>This command queries the QRZ callbook server on the internetand returns any information available for that callsign. This serviceis provided for users of this software by http://www.qrz.com See also SHOW/WM7D for an alternative.</P>
-<H2><A NAME="ss11.160">11.160</A> <A HREF="adminmanual_en.html#toc11.160">show/route <callsign> ... (0)</A>
+<H2><A NAME="ss11.194">11.194</A> <A HREF="adminmanual_en.html#toc11.194">show/registered [<prefix>] (9)</A>
+</H2>
+
+<P><CODE><B>show/registered [<prefix>]</B> Show the registered users</CODE></P>
+
+<H2><A NAME="ss11.195">11.195</A> <A HREF="adminmanual_en.html#toc11.195">show/route <callsign> ... (0)</A>
</H2>
<P><CODE><B>show/route <callsign> ...</B> Show the route to the callsign</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.161">11.161</A> <A HREF="adminmanual_en.html#toc11.161">show/satellite <name> [<hours> <interval>] (0)</A>
+<H2><A NAME="ss11.196">11.196</A> <A HREF="adminmanual_en.html#toc11.196">show/satellite <name> [<hours> <interval>] (0)</A>
</H2>
<P><CODE><B>show/satellite <name> [<hours> <interval>]</B> Show tracking data</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.162">11.162</A> <A HREF="adminmanual_en.html#toc11.162">show/station all [<regex>] (6)</A>
+<H2><A NAME="ss11.197">11.197</A> <A HREF="adminmanual_en.html#toc11.197">show/station all [<regex>] (6)</A>
</H2>
<P><CODE><B>show/station all [<regex>]</B> Show list of users in the system</CODE></P>
-<H2><A NAME="ss11.163">11.163</A> <A HREF="adminmanual_en.html#toc11.163">show/station [<callsign> ..] (0)</A>
+<H2><A NAME="ss11.198">11.198</A> <A HREF="adminmanual_en.html#toc11.198">show/station [<callsign> ..] (0)</A>
</H2>
<P><CODE><B>show/station [<callsign> ..]</B> Show information about a callsign</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
If no callsign is given then show the information for yourself.</P>
-<H2><A NAME="ss11.164">11.164</A> <A HREF="adminmanual_en.html#toc11.164">show/sun [ndays] [<prefix>|<callsign>] (0)</A>
+<H2><A NAME="ss11.199">11.199</A> <A HREF="adminmanual_en.html#toc11.199">show/sun [ndays] [<prefix>|<callsign>] (0)</A>
</H2>
<P><CODE><B>show/sun [ndays] [<prefix>|<callsign>]</B> Show sun rise and set times</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
Upto 366 days can be checked both in the past and in the future.Please note that the rise and set times are given as the UT times of rise and set on the requested UT day.</P>
-<H2><A NAME="ss11.165">11.165</A> <A HREF="adminmanual_en.html#toc11.165">show/time [<prefix>|<callsign>] (0)</A>
+<H2><A NAME="ss11.200">11.200</A> <A HREF="adminmanual_en.html#toc11.200">show/time [<prefix>|<callsign>] (0)</A>
</H2>
<P><CODE><B>show/time [<prefix>|<callsign>]</B> Show the local time </CODE></P>
<P>If no prefixes or callsigns are given then this command returns the localtime and UTC as the computer has it right now. If you give some prefixesthen it will show UTC and UTC + the local offset (not including DST) atthe prefixes or callsigns that you specify.</P>
-<H2><A NAME="ss11.166">11.166</A> <A HREF="adminmanual_en.html#toc11.166">show/usdb [call ..] (0)</A>
+<H2><A NAME="ss11.201">11.201</A> <A HREF="adminmanual_en.html#toc11.201">show/usdb [call ..] (0)</A>
</H2>
<P><CODE><B>show/usdb [call ..]</B> Show information held on the FCC Call database</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.167">11.167</A> <A HREF="adminmanual_en.html#toc11.167">show/vhfstats [days] [date] (0)</A>
+<H2><A NAME="ss11.202">11.202</A> <A HREF="adminmanual_en.html#toc11.202">show/vhfstats [days] [date] (0)</A>
</H2>
<P><CODE><B>show/vhfstats [days] [date]</B> Show the VHF DX Statistics</CODE></P>
<P>Show the VHF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a date (default: today).</P>
-<H2><A NAME="ss11.168">11.168</A> <A HREF="adminmanual_en.html#toc11.168">show/vhftable [days] [date] [prefix ...] (0)</A>
+<H2><A NAME="ss11.203">11.203</A> <A HREF="adminmanual_en.html#toc11.203">show/vhftable [days] [date] [prefix ...] (0)</A>
</H2>
<P><CODE><B>show/vhftable [days] [date] [prefix ...]</B> Show the VHF DX Spotter Table</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.169">11.169</A> <A HREF="adminmanual_en.html#toc11.169">show/wcy (0)</A>
+<H2><A NAME="ss11.204">11.204</A> <A HREF="adminmanual_en.html#toc11.204">show/wcy (0)</A>
</H2>
<P><CODE><B>show/wcy</B> Show last 10 WCY broadcasts</CODE></P>
-<H2><A NAME="ss11.170">11.170</A> <A HREF="adminmanual_en.html#toc11.170">show/wcy <n> (0)</A>
+<H2><A NAME="ss11.205">11.205</A> <A HREF="adminmanual_en.html#toc11.205">show/wcy <n> (0)</A>
</H2>
<P><CODE><B>show/wcy <n></B> Show last <n> WCY broadcasts</CODE></P>
<P>Display the most recent WCY information that has been received by the system</P>
-<H2><A NAME="ss11.171">11.171</A> <A HREF="adminmanual_en.html#toc11.171">show/wm7d <callsign> (0)</A>
+<H2><A NAME="ss11.206">11.206</A> <A HREF="adminmanual_en.html#toc11.206">show/wm7d <callsign> (0)</A>
</H2>
<P><CODE><B>show/wm7d <callsign></B> Show callbook details on a US callsigns</CODE></P>
<P>This command queries the WM7D callbook server on the internetand returns any information available for that US callsign. This serviceis provided for users of this software by http://www.wm7d.net.See also SHOW/QRZ. </P>
-<H2><A NAME="ss11.172">11.172</A> <A HREF="adminmanual_en.html#toc11.172">show/wwv (0)</A>
+<H2><A NAME="ss11.207">11.207</A> <A HREF="adminmanual_en.html#toc11.207">show/wwv (0)</A>
</H2>
<P><CODE><B>show/wwv</B> Show last 10 WWV broadcasts</CODE></P>
-<H2><A NAME="ss11.173">11.173</A> <A HREF="adminmanual_en.html#toc11.173">show/wwv <n> (0)</A>
+<H2><A NAME="ss11.208">11.208</A> <A HREF="adminmanual_en.html#toc11.208">show/wwv <n> (0)</A>
</H2>
<P><CODE><B>show/wwv <n></B> Show last <n> WWV broadcasts</CODE></P>
<P>Display the most recent WWV information that has been received by the system</P>
-<H2><A NAME="ss11.174">11.174</A> <A HREF="adminmanual_en.html#toc11.174">shutdown (5)</A>
+<H2><A NAME="ss11.209">11.209</A> <A HREF="adminmanual_en.html#toc11.209">shutdown (5)</A>
</H2>
<P><CODE><B>shutdown</B> Shutdown the cluster</CODE></P>
<P>Shutdown the cluster and disconnect all the users </P>
-<H2><A NAME="ss11.175">11.175</A> <A HREF="adminmanual_en.html#toc11.175">stat/channel [<callsign>] (5)</A>
+<H2><A NAME="ss11.210">11.210</A> <A HREF="adminmanual_en.html#toc11.210">spoof <call> <command> (9)</A>
+</H2>
+
+<P><CODE><B>spoof <call> <command></B> Do a command as though you are another user</CODE></P>
+<P>This command is provided so that sysops can set a user's parameters withoutme having to write a special 'sysop' version for every user command. Itallows you to pretend that you are doing the command as the user you specify.eg:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ SPOOF G1TLH set/name Dirk SPOOF G1TLH set/qra JO02LQ
+</PRE>
+</CODE></BLOCKQUOTE>
+</P>
+<H2><A NAME="ss11.211">11.211</A> <A HREF="adminmanual_en.html#toc11.211">stat/channel [<callsign>] (5)</A>
</H2>
<P><CODE><B>stat/channel [<callsign>]</B> Show the status of a channel on the cluster</CODE></P>
<P>Show the internal status of the channel object either for the channel that you are on or else for the callsign that you asked for.Only the fields that are defined (in perl term) will be displayed.</P>
-<H2><A NAME="ss11.176">11.176</A> <A HREF="adminmanual_en.html#toc11.176">stat/db <dbname> (5)</A>
+<H2><A NAME="ss11.212">11.212</A> <A HREF="adminmanual_en.html#toc11.212">stat/db <dbname> (5)</A>
</H2>
<P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE></P>
<P>Show the internal status of a database descriptor.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="ss11.177">11.177</A> <A HREF="adminmanual_en.html#toc11.177">stat/msg (1)</A>
+<H2><A NAME="ss11.213">11.213</A> <A HREF="adminmanual_en.html#toc11.213">stat/msg (1)</A>
</H2>
<P><CODE><B>stat/msg</B> Show the status of the message system</CODE></P>
-<H2><A NAME="ss11.178">11.178</A> <A HREF="adminmanual_en.html#toc11.178">stat/msg <msgno> (1)</A>
+<H2><A NAME="ss11.214">11.214</A> <A HREF="adminmanual_en.html#toc11.214">stat/msg <msgno> (1)</A>
</H2>
<P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE></P>
<P>This command shows the internal status of a message and includes informationsuch as to whom it has been forwarded, its size, origin etc etc.If no message number is given then the status of the message system is displayed.</P>
-<H2><A NAME="ss11.179">11.179</A> <A HREF="adminmanual_en.html#toc11.179">stat/route_node <callsign> (5)</A>
+<H2><A NAME="ss11.215">11.215</A> <A HREF="adminmanual_en.html#toc11.215">stat/route_node <callsign> (5)</A>
</H2>
<P><CODE><B>stat/route_node <callsign></B> Show the data in a Route::Node object</CODE></P>
-<H2><A NAME="ss11.180">11.180</A> <A HREF="adminmanual_en.html#toc11.180">stat/route_node all (5)</A>
+<H2><A NAME="ss11.216">11.216</A> <A HREF="adminmanual_en.html#toc11.216">stat/route_node all (5)</A>
</H2>
<P><CODE><B>stat/route_node all</B> Show list of all Route::Node objects</CODE></P>
-<H2><A NAME="ss11.181">11.181</A> <A HREF="adminmanual_en.html#toc11.181">stat/route_user <callsign> (5)</A>
+<H2><A NAME="ss11.217">11.217</A> <A HREF="adminmanual_en.html#toc11.217">stat/route_user <callsign> (5)</A>
</H2>
<P><CODE><B>stat/route_user <callsign></B> Show the data in a Route::User object</CODE></P>
-<H2><A NAME="ss11.182">11.182</A> <A HREF="adminmanual_en.html#toc11.182">stat/route_user all (5)</A>
+<H2><A NAME="ss11.218">11.218</A> <A HREF="adminmanual_en.html#toc11.218">stat/route_user all (5)</A>
</H2>
<P><CODE><B>stat/route_user all</B> Show list of all Route::User objects</CODE></P>
-<H2><A NAME="ss11.183">11.183</A> <A HREF="adminmanual_en.html#toc11.183">stat/user [<callsign>] (5)</A>
+<H2><A NAME="ss11.219">11.219</A> <A HREF="adminmanual_en.html#toc11.219">stat/user [<callsign>] (5)</A>
</H2>
<P><CODE><B>stat/user [<callsign>]</B> Show the full status of a user</CODE></P>
<P>Shows the full contents of a user record including all the secret flagsand stuff.Only the fields that are defined (in perl term) will be displayed.</P>
-<H2><A NAME="ss11.184">11.184</A> <A HREF="adminmanual_en.html#toc11.184">sysop (0)</A>
+<H2><A NAME="ss11.220">11.220</A> <A HREF="adminmanual_en.html#toc11.220">sysop (0)</A>
</H2>
<P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
They will all match. If there is no password you will still be offerednumbers but nothing will happen when you input a string. Any match iscase sensitive.</P>
-<H2><A NAME="ss11.185">11.185</A> <A HREF="adminmanual_en.html#toc11.185">talk <call> > <node> [<text>] (0)</A>
+<H2><A NAME="ss11.221">11.221</A> <A HREF="adminmanual_en.html#toc11.221">talk <call> > <node> [<text>] (0)</A>
</H2>
<P><CODE><B>talk <call> > <node> [<text>]</B> Send a text message to another station via a node</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
will send the hftable as you have it to all the people you are currently talking to.</P>
-<H2><A NAME="ss11.186">11.186</A> <A HREF="adminmanual_en.html#toc11.186">talk <call> [<text>] (0)</A>
+<H2><A NAME="ss11.222">11.222</A> <A HREF="adminmanual_en.html#toc11.222">talk <call> [<text>] (0)</A>
</H2>
<P><CODE><B>talk <call> [<text>]</B> Send a text message to another station</CODE></P>
-<H2><A NAME="ss11.187">11.187</A> <A HREF="adminmanual_en.html#toc11.187">type <filearea>/<name> (0)</A>
+<H2><A NAME="ss11.223">11.223</A> <A HREF="adminmanual_en.html#toc11.223">type <filearea>/<name> (0)</A>
</H2>
<P><CODE><B>type <filearea>/<name></B> Look at the contents of a file in one of the fileareas</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
See also SHOW/FILES to see what fileareas are available and a list of content.</P>
-<H2><A NAME="ss11.188">11.188</A> <A HREF="adminmanual_en.html#toc11.188">uncatchup <node call> all|[msgno> ...] (5)</A>
+<H2><A NAME="ss11.224">11.224</A> <A HREF="adminmanual_en.html#toc11.224">uncatchup <node call> all|[msgno> ...] (5)</A>
</H2>
<P><CODE><B>uncatchup <node call> all|[msgno> ...]</B> Unmark a message as sent</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
which will arrange for them to be forward candidates again.Order is not important.</P>
-<H2><A NAME="ss11.189">11.189</A> <A HREF="adminmanual_en.html#toc11.189">unset/announce (0)</A>
+<H2><A NAME="ss11.225">11.225</A> <A HREF="adminmanual_en.html#toc11.225">unset/announce (0)</A>
</H2>
<P><CODE><B>unset/announce</B> Stop announce messages coming out on your terminal</CODE></P>
-<H2><A NAME="ss11.190">11.190</A> <A HREF="adminmanual_en.html#toc11.190">unset/anntalk (0)</A>
+<H2><A NAME="ss11.226">11.226</A> <A HREF="adminmanual_en.html#toc11.226">unset/anntalk (0)</A>
</H2>
<P><CODE><B>unset/anntalk</B> Stop talk like announce messages on your terminal</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
allows you to see them again. This is the default.</P>
-<H2><A NAME="ss11.191">11.191</A> <A HREF="adminmanual_en.html#toc11.191">unset/baddx <call>.. (8)</A>
+<H2><A NAME="ss11.227">11.227</A> <A HREF="adminmanual_en.html#toc11.227">unset/baddx <call>.. (8)</A>
</H2>
<P><CODE><B>unset/baddx <call>..</B> Propagate a dx spot with this callsign again</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.192">11.192</A> <A HREF="adminmanual_en.html#toc11.192">unset/badnode <call>.. (8)</A>
+<H2><A NAME="ss11.228">11.228</A> <A HREF="adminmanual_en.html#toc11.228">unset/badnode <call>.. (8)</A>
</H2>
<P><CODE><B>unset/badnode <call>..</B> Allow spots from this node again</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
will allow spots from him again.Use with extreme care. This command may well be superceeded by FILTERing.</P>
-<H2><A NAME="ss11.193">11.193</A> <A HREF="adminmanual_en.html#toc11.193">unset/badspotter <call>.. (8)</A>
+<H2><A NAME="ss11.229">11.229</A> <A HREF="adminmanual_en.html#toc11.229">unset/badspotter <call>.. (8)</A>
</H2>
<P><CODE><B>unset/badspotter <call>..</B> Allow spots from this callsign again</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
will allow spots from him again.Use with extreme care. This command may well be superceded by FILTERing.</P>
-<H2><A NAME="ss11.194">11.194</A> <A HREF="adminmanual_en.html#toc11.194">unset/badword <word>.. (8)</A>
+<H2><A NAME="ss11.230">11.230</A> <A HREF="adminmanual_en.html#toc11.230">unset/badword <word>.. (8)</A>
</H2>
<P><CODE><B>unset/badword <word>..</B> Propagate things with this word again</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
will allow text with this word again.</P>
-<H2><A NAME="ss11.195">11.195</A> <A HREF="adminmanual_en.html#toc11.195">unset/beep (0)</A>
+<H2><A NAME="ss11.231">11.231</A> <A HREF="adminmanual_en.html#toc11.231">unset/beep (0)</A>
</H2>
<P><CODE><B>unset/beep</B> Stop beeps for DX and other messages on your terminal</CODE></P>
-<H2><A NAME="ss11.196">11.196</A> <A HREF="adminmanual_en.html#toc11.196">unset/dx (0)</A>
+<H2><A NAME="ss11.232">11.232</A> <A HREF="adminmanual_en.html#toc11.232">unset/debug <name> (9)</A>
+</H2>
+
+<P><CODE><B>unset/debug <name></B> Remove a debug level from the debug set</CODE></P>
+<P>You can choose to log several different levels. The levels are
+<BLOCKQUOTE><CODE>
+<PRE>
+ chan state msg cron connect
+</PRE>
+</CODE></BLOCKQUOTE>
+You can show what levels you are logging with SHOW/DEBUG</P>
+<H2><A NAME="ss11.233">11.233</A> <A HREF="adminmanual_en.html#toc11.233">unset/dx (0)</A>
</H2>
<P><CODE><B>unset/dx</B> Stop DX messages coming out on your terminal</CODE></P>
-<H2><A NAME="ss11.197">11.197</A> <A HREF="adminmanual_en.html#toc11.197">unset/dxcq (0)</A>
+<H2><A NAME="ss11.234">11.234</A> <A HREF="adminmanual_en.html#toc11.234">unset/dxcq (0)</A>
</H2>
<P><CODE><B>unset/dxcq</B> Stop CQ Zones on the end of DX announcements</CODE></P>
<P>Display both the Spotter's and the Spotted's CQ Zone on the endof a DX announcement (there is just enough room). Some user programscannot cope with this. The Spotter's CQ is on the RHS of the time, the Spotted's CQ is on the LHS.Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are confused. </P>
-<H2><A NAME="ss11.198">11.198</A> <A HREF="adminmanual_en.html#toc11.198">unset/dxgrid (0)</A>
+<H2><A NAME="ss11.235">11.235</A> <A HREF="adminmanual_en.html#toc11.235">unset/dxgrid (0)</A>
</H2>
<P><CODE><B>unset/dxgrid</B> Stop QRA Grid Squares on the end of DX announcements</CODE></P>
<P>A standard feature which is enabled in version 1.43 and above is that if the spotter's grid square is known it is output on the endof a DX announcement (there is just enough room). Some user programscannot cope with this. You can use this command to reset (or set)this feature.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which flags you have set if you are confused. </P>
-<H2><A NAME="ss11.199">11.199</A> <A HREF="adminmanual_en.html#toc11.199">unset/dxitu (0)</A>
+<H2><A NAME="ss11.236">11.236</A> <A HREF="adminmanual_en.html#toc11.236">unset/dxitu (0)</A>
</H2>
<P><CODE><B>unset/dxitu</B> Stop ITU Zones on the end of DX announcements</CODE></P>
<P>Display both the Spotter's and the Spotted's ITU Zone on the endof a DX announcement (there is just enough room). Some user programscannot cope with this. The Spotter's ITU is on the RHS of the time, the Spotted's ITU is on the LHS.Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are confused. </P>
-<H2><A NAME="ss11.200">11.200</A> <A HREF="adminmanual_en.html#toc11.200">unset/echo (0)</A>
+<H2><A NAME="ss11.237">11.237</A> <A HREF="adminmanual_en.html#toc11.237">unset/echo (0)</A>
</H2>
<P><CODE><B>unset/echo</B> Stop the cluster echoing your input</CODE></P>
<P>If you are connected via a telnet session, different implimentationsof telnet handle echo differently depending on whether you are connected via port 23 or some other port. You can use this commandto change the setting appropriately. The setting is stored in your user profile.YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.</P>
-<H2><A NAME="ss11.201">11.201</A> <A HREF="adminmanual_en.html#toc11.201">unset/email (0)</A>
+<H2><A NAME="ss11.238">11.238</A> <A HREF="adminmanual_en.html#toc11.238">unset/email (0)</A>
</H2>
<P><CODE><B>unset/email</B> Stop personal msgs being forwarded by email</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.202">11.202</A> <A HREF="adminmanual_en.html#toc11.202">unset/here (0)</A>
+<H2><A NAME="ss11.239">11.239</A> <A HREF="adminmanual_en.html#toc11.239">unset/here (0)</A>
</H2>
<P><CODE><B>unset/here</B> Tell the system you are absent from your terminal</CODE></P>
-<H2><A NAME="ss11.203">11.203</A> <A HREF="adminmanual_en.html#toc11.203">unset/hops <call> ann|spots|route|wwv|wcy (8)</A>
+<H2><A NAME="ss11.240">11.240</A> <A HREF="adminmanual_en.html#toc11.240">unset/hops <call> ann|spots|route|wwv|wcy (8)</A>
</H2>
<P><CODE><B>unset/hops <call> ann|spots|route|wwv|wcy</B> Unset hop count </CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
</P>
-<H2><A NAME="ss11.204">11.204</A> <A HREF="adminmanual_en.html#toc11.204">unset/logininfo (0)</A>
+<H2><A NAME="ss11.241">11.241</A> <A HREF="adminmanual_en.html#toc11.241">unset/isolate (9)</A>
+</H2>
+
+<P><CODE><B>unset/isolate</B> Stop Isolation of a node from the rest of the network</CODE></P>
+<P>Remove isolation from a node - SET/ISOLATE</P>
+<H2><A NAME="ss11.242">11.242</A> <A HREF="adminmanual_en.html#toc11.242">unset/lockout <call> (9)</A>
+</H2>
+
+<P><CODE><B>unset/lockout <call></B> Allow a callsign to connect to the cluster</CODE></P>
+
+<H2><A NAME="ss11.243">11.243</A> <A HREF="adminmanual_en.html#toc11.243">unset/logininfo (0)</A>
</H2>
<P><CODE><B>unset/logininfo</B> Inform when a station logs out locally</CODE></P>
-<H2><A NAME="ss11.205">11.205</A> <A HREF="adminmanual_en.html#toc11.205">unset/privilege (0)</A>
+<H2><A NAME="ss11.244">11.244</A> <A HREF="adminmanual_en.html#toc11.244">unset/password <call> ... (9)</A>
+</H2>
+
+<P><CODE><B>unset/password <call> ...</B> Delete (remove) a user's password</CODE></P>
+<P>This command allows the sysop to completely delete and remove a password for a user. </P>
+<H2><A NAME="ss11.245">11.245</A> <A HREF="adminmanual_en.html#toc11.245">unset/privilege (0)</A>
</H2>
<P><CODE><B>unset/privilege</B> Remove any privilege for this session</CODE></P>
<P>You can use this command to 'protect' this session from unauthoriseduse. If you want to get your normal privilege back you will need toeither logout and login again (if you are on a console) or use theSYSOP command.</P>
-<H2><A NAME="ss11.206">11.206</A> <A HREF="adminmanual_en.html#toc11.206">unset/prompt (0)</A>
+<H2><A NAME="ss11.246">11.246</A> <A HREF="adminmanual_en.html#toc11.246">unset/prompt (0)</A>
</H2>
<P><CODE><B>unset/prompt</B> Set your prompt back to default</CODE></P>
</PRE>
</CODE></BLOCKQUOTE>
UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back tonormal.</P>
-<H2><A NAME="ss11.207">11.207</A> <A HREF="adminmanual_en.html#toc11.207">unset/talk (0)</A>
+<H2><A NAME="ss11.247">11.247</A> <A HREF="adminmanual_en.html#toc11.247">unset/register <call> ... (9)</A>
+</H2>
+
+<P><CODE><B>unset/register <call> ...</B> Mark a user as not registered</CODE></P>
+<P>Registration is a concept that you can switch on by executing the
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/var $main::regreq = 1
+</PRE>
+</CODE></BLOCKQUOTE>
+command (usually in your startup file)If a user is NOT registered then, firstly, instead of the normalmotd file (/spider/data/motd) being sent to the user at startup, theuser is sent the motd_nor file instead. Secondly, the non registereduser only has READ-ONLY access to the node. The non-registered usercannot use DX, ANN etc. The only exception to this is that a non-registered user can TALK orSEND messages to the sysop.</P>
+<H2><A NAME="ss11.248">11.248</A> <A HREF="adminmanual_en.html#toc11.248">unset/talk (0)</A>
</H2>
<P><CODE><B>unset/talk</B> Stop TALK messages coming out on your terminal</CODE></P>
-<H2><A NAME="ss11.208">11.208</A> <A HREF="adminmanual_en.html#toc11.208">unset/usstate (0)</A>
+<H2><A NAME="ss11.249">11.249</A> <A HREF="adminmanual_en.html#toc11.249">unset/usstate (0)</A>
</H2>
<P><CODE><B>unset/usstate</B> Stop US State info on the end of DX announcements</CODE></P>
<P>If the spotter's or spotted's US State is known it is output on the end of a DX announcement (there is just enough room). A spotter's state will appear on the RHS of the time (like SET/DXGRID) and the spotted's State will appear on the LHS of thetime field. Any information found will override any locator information from SET/DXGRID.Some user programs cannot cope with this. You can use this command to reset (or set) this feature.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which flags you have set if you are confused. </P>
-<H2><A NAME="ss11.209">11.209</A> <A HREF="adminmanual_en.html#toc11.209">unset/wcy (0)</A>
+<H2><A NAME="ss11.250">11.250</A> <A HREF="adminmanual_en.html#toc11.250">unset/wcy (0)</A>
</H2>
<P><CODE><B>unset/wcy</B> Stop WCY messages coming out on your terminal</CODE></P>
-<H2><A NAME="ss11.210">11.210</A> <A HREF="adminmanual_en.html#toc11.210">unset/wwv (0)</A>
+<H2><A NAME="ss11.251">11.251</A> <A HREF="adminmanual_en.html#toc11.251">unset/wwv (0)</A>
</H2>
<P><CODE><B>unset/wwv</B> Stop WWV messages coming out on your terminal</CODE></P>
-<H2><A NAME="ss11.211">11.211</A> <A HREF="adminmanual_en.html#toc11.211">unset/wx (0)</A>
+<H2><A NAME="ss11.252">11.252</A> <A HREF="adminmanual_en.html#toc11.252">unset/wx (0)</A>
</H2>
<P><CODE><B>unset/wx</B> Stop WX messages coming out on your terminal</CODE></P>
-<H2><A NAME="ss11.212">11.212</A> <A HREF="adminmanual_en.html#toc11.212">who (0)</A>
+<H2><A NAME="ss11.253">11.253</A> <A HREF="adminmanual_en.html#toc11.253">who (0)</A>
</H2>
<P><CODE><B>who</B> Show who is physically connected</CODE></P>
<P>This is a quick listing that shows which callsigns are connected andwhat sort of connection they have</P>
-<H2><A NAME="ss11.213">11.213</A> <A HREF="adminmanual_en.html#toc11.213">wx <text> (0)</A>
+<H2><A NAME="ss11.254">11.254</A> <A HREF="adminmanual_en.html#toc11.254">wx <text> (0)</A>
</H2>
<P><CODE><B>wx <text></B> Send a weather message to local users</CODE></P>
-<H2><A NAME="ss11.214">11.214</A> <A HREF="adminmanual_en.html#toc11.214">wx full <text> (0)</A>
+<H2><A NAME="ss11.255">11.255</A> <A HREF="adminmanual_en.html#toc11.255">wx full <text> (0)</A>
</H2>
<P><CODE><B>wx full <text></B> Send a weather message to all cluster users</CODE></P>
-<H2><A NAME="ss11.215">11.215</A> <A HREF="adminmanual_en.html#toc11.215">wx sysop <text> (5)</A>
+<H2><A NAME="ss11.256">11.256</A> <A HREF="adminmanual_en.html#toc11.256">wx sysop <text> (5)</A>
</H2>
<P><CODE><B>wx sysop <text></B> Send a weather message to other clusters only</CODE></P>
projects / spider.git / blobdiff