1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
4 <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
5 <TITLE>The DXSpider Administration Manual v1.50: CVS</TITLE>
6 <LINK HREF="adminmanual_en-9.html" REL=previous>
7 <LINK HREF="adminmanual_en.html#toc10" REL=contents>
8 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="adminmanual_en-9.html">Previous</A>
13 <A HREF="adminmanual_en.html#toc10">Contents</A>
15 <H2><A NAME="s10">10.</A> <A HREF="adminmanual_en.html#toc10">CVS</A></H2>
17 <H2><A NAME="ss10.1">10.1</A> <A HREF="adminmanual_en.html#toc10.1">CVS from a Linux platform</A>
20 <P>CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held
22 <A HREF="http://www.sourceforge.net">Sourceforge</A>. This means
23 that it is possible to update your DXSpider installation to the latest
24 sources by using a few simple commands. A graphical interface to CVS for
25 Windows is explained in the next section.</P>
27 <P>Please be aware that if you update your system using CVS, it is possible that
28 you could be running code that is very beta and not fully tested. There is
29 a possibility that it could be unstable.</P>
31 <P>I am of course assuming that you have a machine with both DXSpider and
32 Internet access running.</P>
34 <P>BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
35 ENTIRE SPIDER TREE!!</P>
37 <P>Assuming you are connected to the Internet, you need to login to the
38 CVS repository and then update your Spider source. There are several
39 steps which are listed below ...</P>
41 <P>First login as the user <EM>sysop</EM>. Next you need to connect to the CVS
42 repository. You do this with the command below ...</P>
45 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
48 <P>You will get a password prompt. Simply hit return here and your machine should
49 return to a normal linux prompt.</P>
51 <P>What happens next depends on whether you have an existing installation that
52 you want to update with the latest and greatest or whether you just want
53 to see what is there and/or run it on a new machine for testing.</P>
54 <P>If you are installing Spider from CVS then change directory to /home/sysop</P>
55 <P>If you are wanting to update Spider then cd to /tmp</P>
57 <P>The next step will create a brand new 'spider' directory in your current
61 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
64 <P>This command is all on one line.</P>
66 <P>Hopefully your screen should show you downloading files. The -z3 simply compresses
67 the download to improve speed.
68 When this has finished, you will have exactly the same as if you had untarred a full
69 tarball PLUS some extra directories and files that CVS needs to do the magic that
72 <P>Now if you are doing a new installation, that's it. Carry on as if you have
73 just downloaded and untarred the lastest tarball.</P>
75 <P>If you want to upgrade your current installation then do this ...</P>
79 tar cvfz /tmp/s.tgz spider
85 <P>This is assuming you downloaded to the /tmp directory of course.</P>
87 <P>NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions
88 correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????</P>
89 <P>Remember to recompile the C client (cd /spider/src; make)</P>
91 <P>At this point the files have been upgraded. You can (usually) restart the cluster
92 in your own time. However, if you attempt to use any new commands or features
93 expect it to be fatal! At least your cluster will have been restarted then so it
94 will be too late to worry about it!</P>
96 <P>Now the magic part! From now on when you want to update, simply connect to the
97 Internet and then, as the user <EM>sysop</EM> ...</P>
106 <P>and your files will be updated. As above, remember to recompile the "C" client
107 if it has been updated (CVS will tell you) and restart if any of the perl scripts
108 have been altered or added, again, CVS will tell you.</P>
110 <P>You will find any changes documented in the /spider/Changes file.</P>
112 <H2><A NAME="ss10.2">10.2</A> <A HREF="adminmanual_en.html#toc10.2">CVS from a Windows platform</A>
115 <P>After the initial setup, an update to your DXSpider software is no more than a couple
116 of clicks away. This section is intended to explain and illustrate the use of the
117 WinCVS application to update your DXSpider software. The current stable version of
118 WinCVS is Ver. 1.2. You can get this software at:</P>
120 <A HREF="http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip">http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip</A></P>
121 <P>Pick your download mirror and then install WinCVS after the download is complete.</P>
122 <P>In this next section I have included a series of links to .jpg files to take advantage of the
123 picture and 1000 words equivalency. The .jpg files are in the C:\spider\html directory. If
124 someone using a Linux system is reading this section from boredom, the files are in
125 /home/sysop/spider/html. One aside, a Linux user can also get a copy of gcvs and do your updates
126 graphically as opposed to from the command line. The following descriptions are almost identical
127 between WinCvs and gcvs. The following screen shots have duplicate links, depending upon whether
128 you are viewing this information under the Windows or Linux operating system.</P>
129 <P>When WinCVS is installed, running, and you are connected to the internet, the initial screen looks like:</P>
131 <A HREF="initial.jpg">initial.jpg</A></P>
132 <P>If you want, you can also look at these .jpg files with another viewer that might provide some
133 better clarity to the image. On the left is the directory tree for your hard disk. Notice that
134 the spider directory has a gray highlight.</P>
135 <P>To start configuring WinCVS, click on Admin at the top of the screen and then Preferences. This
138 <A HREF="pref-gen.jpg">pref-gen.jpg</A></P>
139 <P>In the top line for CVSROOT, enter:
142 anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
149 "passwd" file on the cvs server
153 <P>for Authentication on the General tab.</P>
154 <P>Next, move to the right to the Ports tab.</P>
156 <A HREF="pref-ports.jpg">pref-ports.jpg</A></P>
157 <P>In here, check the box on the second line down for the "pserver" port. Enter a port number of 2401.</P>
158 <P>Finally, go to the WinCvs tab all the way to the right.</P>
160 <A HREF="pref-wincvs.jpg">pref-wincvs.jpg</A></P>
161 <P>Enter Notepad as the viewer to open files. For the HOME folder, put "C:\spider" and click OK
162 because the configuration is now complete.</P>
163 <P>You are now ready to upgrade your copy of DXSpider. Click on the greyed Spider folder
164 shown in the directory tree on the left of the WinCVS display. Two things should happen. The Spider
165 folder will be selected and the greyed-out arrow located just below the word Query in the top line will
166 turn to solid green.</P>
167 <P>For anyone using gcvs under Linux, the green arrow is located on the extreme left of the display,
168 under the word File. A gcvs screen looks like:</P>
170 <A HREF="gcvs.jpg">gcvs.jpg</A></P>
171 <P>Click on the now green arrow to start the download process. An Update Settings box will be displayed
172 to which you can simply say OK.</P>
174 <A HREF="update-OK.jpg">update-OK.jpg</A></P>
175 <P>For future reference, the Update Settings box is the place where you can enter information to revert
176 to a prior version of DXSpider. Information on reverting to a Before Date is contained in the WinCVS
178 <P>After a short period of time, a series of file names will scroll by in the lower pane of the WinCVS
179 window. Eventually you should see
182 *****CVS exited normally with code 0*****
186 appear in the lower pane. You're done. The updated files are in place ready for you to stop and then
187 restart your DXSpider. After the restart, you're running with the latest version of DXSpider.</P>
189 <A HREF="completed.jpg">completed.jpg</A></P>
190 <P>To paraphrase from the CVS section... Now the magic part! From now on when you want to update, simply
191 connect to the Internet and start WinCVS.
194 Click on the greyed-out Spider directory in the left screen
195 Click on the green down arrow
196 Click OK on the Update Settings dialog box
197 Restart your Spider software
202 <H2><A NAME="ss10.3">10.3</A> <A HREF="adminmanual_en.html#toc10.3">accept (0)</A>
205 <P><CODE><B>accept</B> Set a filter to accept something</CODE></P>
206 <P>Create a filter to accept somethingThere are 2 types of filter, accept and reject. See HELP FILTERING for moreinfo.</P>
207 <H2><A NAME="ss10.4">10.4</A> <A HREF="adminmanual_en.html#toc10.4">accept/announce <call> [input] [0-9] <pattern> (8)</A>
210 <P><CODE><B>accept/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE></P>
211 <P>This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-
214 accept/ann by G,M,2 accept/ann input node_default by G,M,2 accept/ann user_default by G,M,2
218 <H2><A NAME="ss10.5">10.5</A> <A HREF="adminmanual_en.html#toc10.5">accept/announce [0-9] <pattern> (0)</A>
221 <P><CODE><B>accept/announce [0-9] <pattern></B> Set an 'accept' filter line for announce</CODE></P>
222 <P>Create an 'accept this announce' line for a filter. An accept filter line means that if the announce matches this filter it ispassed onto the user. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:-
225 info <string> eg: iota or qsl by <prefixes> eg: G,M,2 origin <prefixes> origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> origin_state <states> eg: VA,NH,RI,NH by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> by_state <states> channel <prefixes> wx 1 filter WX announces dest <prefixes> eg: 6MUK,WDX (distros)
231 acc/ann dest 6MUK acc/ann 2 by_zone 14,15,16 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
243 acc/ann by_state va,nh,ri,nh
246 You can use the tag 'all' to accept everything eg:
252 but this probably for advanced users...</P>
253 <H2><A NAME="ss10.6">10.6</A> <A HREF="adminmanual_en.html#toc10.6">accept/route <call> [0-9] <pattern> (8)</A>
256 <P><CODE><B>accept/route <call> [0-9] <pattern></B> Set an 'accept' filter line for routing</CODE></P>
257 <P>Create an 'accept this routing PC Protocol' line for a filter. An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter it is passed thru that interface. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:-
260 call <prefixes> the callsign of the thingy call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) call_itu <prefixes or numbers> or: G,GM,GW call_zone <prefixes or numbers> call_state <states> eg: VA,NH,RI,NH origin <prefixes> really the interface it came in on origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> origin_state <states> eg: VA,NH,RI,NH
266 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
269 you can now use 'by' as a synonym for 'call' so:
272 by = call by_dxcc = call_dxcc
275 and so onYou can use the tag 'all' to accept everything eg:
282 <H2><A NAME="ss10.7">10.7</A> <A HREF="adminmanual_en.html#toc10.7">accept/spots <call> [input] [0-9] <pattern> (8)</A>
285 <P><CODE><B>accept/spots <call> [input] [0-9] <pattern></B> Spot filter sysop version</CODE></P>
286 <P>This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-
289 accept/spot db0sue-7 1 by_zone 14,15,16 accept/spot node_default all set/hops node_default 10
294 accept/spot user_default by G,M,2
298 <H2><A NAME="ss10.8">10.8</A> <A HREF="adminmanual_en.html#toc10.8">accept/spots [0-9] <pattern> (0)</A>
301 <P><CODE><B>accept/spots [0-9] <pattern></B> Set an 'accept' filter line for spots</CODE></P>
302 <P>Create an 'accept this spot' line for a filter. An accept filter line means that if the spot matches this filter it ispassed onto the user. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:-
305 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m on <range> same as 'freq' call <prefixes> eg: G,PA,HB9 info <string> eg: iota or qsl by <prefixes> call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) call_itu <prefixes or numbers> or: G,GM,GW call_zone <prefixes or numbers> call_state <states> eg: VA,NH,RI,ME by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> by_state <states> eg: VA,NH,RI,ME origin <prefixes> channel <prefixes>
308 'call' means the callsign that has spotted 'by' whoever.For frequencies, you can use any of the band names defined inSHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -thus: hf/ssb. You can also just have a simple range like: 0/30000 -this is more efficient than saying simply: freq HF (but don't gettoo hung up about that)some examples:-
311 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
314 You can use the tag 'all' to accept everything, eg:
323 acc/spots by_state VA,NH,RI,MA,ME
326 but this probably for advanced users...</P>
327 <H2><A NAME="ss10.9">10.9</A> <A HREF="adminmanual_en.html#toc10.9">accept/wcy <call> [input] [0-9] <pattern> (8)</A>
330 <P><CODE><B>accept/wcy <call> [input] [0-9] <pattern></B> WCY filter sysop version</CODE></P>
331 <P>This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-
334 accept/wcy node_default all set/hops node_default 10
338 <H2><A NAME="ss10.10">10.10</A> <A HREF="adminmanual_en.html#toc10.10">accept/wcy [0-9] <pattern> (0)</A>
341 <P><CODE><B>accept/wcy [0-9] <pattern></B> set an 'accept' WCY filter</CODE></P>
342 <P>It is unlikely that you will want to do this, but if you do then you canfilter on the following fields:-
345 by <prefixes> eg: G,M,2 origin <prefixes> origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> channel <prefixes>
348 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>
349 <H2><A NAME="ss10.11">10.11</A> <A HREF="adminmanual_en.html#toc10.11">accept/wwv <call> [input] [0-9] <pattern> (8)</A>
352 <P><CODE><B>accept/wwv <call> [input] [0-9] <pattern></B> WWV filter sysop version</CODE></P>
353 <P>This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-
356 accept/wwv db0sue-7 1 by_zone 4 accept/wwv node_default all set/hops node_default 10
361 accept/wwv user_default by W,K
365 <H2><A NAME="ss10.12">10.12</A> <A HREF="adminmanual_en.html#toc10.12">accept/wwv [0-9] <pattern> (0)</A>
368 <P><CODE><B>accept/wwv [0-9] <pattern></B> set an 'accept' WWV filter</CODE></P>
369 <P>It is unlikely that you will want to do this, but if you do then you canfilter on the following fields:-
372 by <prefixes> eg: G,M,2 origin <prefixes> origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> channel <prefixes>
381 is probably the only useful thing to do (which will only show WWV broadcastsby stations in the US).See HELP FILTER for information.</P>
382 <H2><A NAME="ss10.13">10.13</A> <A HREF="adminmanual_en.html#toc10.13">announce <text> (0)</A>
385 <P><CODE><B>announce <text></B> Send an announcement to LOCAL users only</CODE></P>
386 <P><text> is the text of the announcement you wish to broadcast </P>
387 <H2><A NAME="ss10.14">10.14</A> <A HREF="adminmanual_en.html#toc10.14">announce full <text> (0)</A>
390 <P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE></P>
391 <P>This will send your announcement cluster wide</P>
392 <H2><A NAME="ss10.15">10.15</A> <A HREF="adminmanual_en.html#toc10.15">announce sysop <text> (5)</A>
395 <P><CODE><B>announce sysop <text></B> Send an announcement to Sysops only</CODE></P>
397 <H2><A NAME="ss10.16">10.16</A> <A HREF="adminmanual_en.html#toc10.16">apropos <string> (0)</A>
400 <P><CODE><B>apropos <string></B> Search help database for <string></CODE></P>
401 <P>Search the help database for <string> (it isn't case sensitive), and printthe names of all the commands that may be relevant.</P>
402 <H2><A NAME="ss10.17">10.17</A> <A HREF="adminmanual_en.html#toc10.17">blank [<string>] [<nn>] (0)</A>
405 <P><CODE><B>blank [<string>] [<nn>]</B> Print nn (default 1) blank lines (or strings)</CODE></P>
406 <P>In its basic form this command prints one or more blank lines. However ifyou pass it a string it will replicate the string for the width of the screen (default 80) and then print that one or more times, so:
412 prints two blank lines
418 prints a row of - characters once.
424 prints 'abcabcabcabcabcabc....'This is really only of any use in a script file and you can print a maximumof 9 lines.</P>
425 <H2><A NAME="ss10.18">10.18</A> <A HREF="adminmanual_en.html#toc10.18">bye (0)</A>
428 <P><CODE><B>bye</B> Exit from the cluster</CODE></P>
429 <P>This will disconnect you from the cluster</P>
430 <H2><A NAME="ss10.19">10.19</A> <A HREF="adminmanual_en.html#toc10.19">catchup <node call> all|[<msgno> ...] (5)</A>
433 <P><CODE><B>catchup <node call> all|[<msgno> ...]</B> Mark a message as sent</CODE></P>
435 <H2><A NAME="ss10.20">10.20</A> <A HREF="adminmanual_en.html#toc10.20">chat <group> <text> (0)</A>
438 <P><CODE><B>chat <group> <text></B> Chat or Conference to a group</CODE></P>
439 <P>It is now possible to JOIN a group and have network wide conferencing to thatgroup. DXSpider does not (and probably will not) implement the AK1A conference mode as this seems very limiting, is hardly used and doesn't seemto work too well anyway.This system uses the existing ANN system and is compatible with both otherDXSpider nodes and AK1A clusters (they use ANN/<group>). You can be a member of as many "groups" as you want. To join a group type:-
442 JOIN FOC (where FOC is the group name)
445 To leave a group type:-
451 You can see which groups you are in by typing:-
457 and you can see whether your mate is in the group, if he connects to thesame node as you, by typing:-
463 To send a message to a group type:-
466 CHAT FOC hello everyone
472 CH #9000 hello I am back
475 See also JOIN, LEAVE, SHOW/CHAT</P>
476 <H2><A NAME="ss10.21">10.21</A> <A HREF="adminmanual_en.html#toc10.21">clear/announce <callsign> [input] [0-9|all] (8)</A>
479 <P><CODE><B>clear/announce <callsign> [input] [0-9|all]</B> Clear a announce filter line</CODE></P>
480 <P>A sysop can clear an input or normal output filter for a user or thenode_default or user_default. </P>
481 <H2><A NAME="ss10.22">10.22</A> <A HREF="adminmanual_en.html#toc10.22">clear/announce [1|all] (0)</A>
484 <P><CODE><B>clear/announce [1|all]</B> Clear a announce filter line</CODE></P>
485 <P>This command allows you to clear (remove) a line in a annouce filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation.</P>
486 <H2><A NAME="ss10.23">10.23</A> <A HREF="adminmanual_en.html#toc10.23">clear/route <callsign> [input] [0-9|all] (8)</A>
489 <P><CODE><B>clear/route <callsign> [input] [0-9|all]</B> Clear a route filter line</CODE></P>
490 <P>A sysop can clear an input or normal output filter for a user or thenode_default or user_default. </P>
491 <H2><A NAME="ss10.24">10.24</A> <A HREF="adminmanual_en.html#toc10.24">clear/route [1|all] (0)</A>
494 <P><CODE><B>clear/route [1|all]</B> Clear a route filter line</CODE></P>
495 <P>This command allows you to clear (remove) a line in a route filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation.</P>
496 <H2><A NAME="ss10.25">10.25</A> <A HREF="adminmanual_en.html#toc10.25">clear/spots <callsign> [input] [0-9|all] (8)</A>
499 <P><CODE><B>clear/spots <callsign> [input] [0-9|all]</B> Clear a spot filter line</CODE></P>
500 <P>A sysop can clear an input or normal output filter for a user or thenode_default or user_default. </P>
501 <H2><A NAME="ss10.26">10.26</A> <A HREF="adminmanual_en.html#toc10.26">clear/spots [0-9|all] (0)</A>
504 <P><CODE><B>clear/spots [0-9|all]</B> Clear a spot filter line</CODE></P>
505 <P>This command allows you to clear (remove) a line in a spot filter or to remove the whole filter.If you have a filter:-
508 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
517 you will be left with:-
520 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
529 the filter will be completely removed.</P>
530 <H2><A NAME="ss10.27">10.27</A> <A HREF="adminmanual_en.html#toc10.27">clear/wcy <callsign> [input] [0-9|all] (8)</A>
533 <P><CODE><B>clear/wcy <callsign> [input] [0-9|all]</B> Clear a WCY filter line</CODE></P>
534 <P>A sysop can clear an input or normal output filter for a user or thenode_default or user_default. </P>
535 <H2><A NAME="ss10.28">10.28</A> <A HREF="adminmanual_en.html#toc10.28">clear/wcy [1|all] (0)</A>
538 <P><CODE><B>clear/wcy [1|all]</B> Clear a WCY filter line</CODE></P>
539 <P>This command allows you to clear (remove) a line in a WCY filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation.</P>
540 <H2><A NAME="ss10.29">10.29</A> <A HREF="adminmanual_en.html#toc10.29">clear/wwv <callsign> [input] [0-9|all] (8)</A>
543 <P><CODE><B>clear/wwv <callsign> [input] [0-9|all]</B> Clear a WWV filter line</CODE></P>
544 <P>A sysop can clear an input or normal output filter for a user or thenode_default or user_default. </P>
545 <H2><A NAME="ss10.30">10.30</A> <A HREF="adminmanual_en.html#toc10.30">clear/wwv [1|all] (0)</A>
548 <P><CODE><B>clear/wwv [1|all]</B> Clear a WWV filter line</CODE></P>
549 <P>This command allows you to clear (remove) a line in a WWV filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation.</P>
550 <H2><A NAME="ss10.31">10.31</A> <A HREF="adminmanual_en.html#toc10.31">connect <callsign> (5)</A>
553 <P><CODE><B>connect <callsign></B> Start a connection to another DX Cluster</CODE></P>
554 <P>Start a connection process that will culminate in a new connection to theDX cluster <callsign>. This process creates a new 'client' process which willuse the script in /spider/connect/<callsign> to effect the 'chat' exchangenecessary to traverse the network(s) to logon to the cluster <callsign>.</P>
555 <H2><A NAME="ss10.32">10.32</A> <A HREF="adminmanual_en.html#toc10.32">dbavail (0)</A>
558 <P><CODE><B>dbavail</B> Show a list of all the Databases in the system</CODE></P>
559 <P>Title says it all really, this command lists all the databases definedin the system. It is also aliased to SHOW/COMMAND.</P>
560 <H2><A NAME="ss10.33">10.33</A> <A HREF="adminmanual_en.html#toc10.33">dbcreate <name> (9)</A>
563 <P><CODE><B>dbcreate <name></B> Create a database entry</CODE></P>
565 <H2><A NAME="ss10.34">10.34</A> <A HREF="adminmanual_en.html#toc10.34">dbcreate <name> chain <name> [<name>..] (9)</A>
568 <P><CODE><B>dbcreate <name> chain <name> [<name>..]</B> Create a chained database entry</CODE></P>
570 <H2><A NAME="ss10.35">10.35</A> <A HREF="adminmanual_en.html#toc10.35">dbcreate <name> cmd <dxspider command> (9)</A>
573 <P><CODE><B>dbcreate <name> cmd <dxspider command></B> make a local command available as a DB</CODE></P>
574 <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:
580 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:
583 DBCREATE sdx_qsl chain sql_ad
586 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:
589 DBCREATE buckmaster remote gb7dxc
592 Remote databases cannot be chained; however, the last database in a a chain can be a remote database eg:
595 DBCREATE qsl chain gb7dxc
598 To see what databases have been defined do:
601 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
604 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:-
607 's' => [ .. .. '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', .. .. ],
616 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:-
619 DBCREATE dxqsl cmd show/dxqsl
622 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>
623 <H2><A NAME="ss10.36">10.36</A> <A HREF="adminmanual_en.html#toc10.36">dbcreate <name> remote <node> (9)</A>
626 <P><CODE><B>dbcreate <name> remote <node></B> Create a remote database entry</CODE></P>
628 <H2><A NAME="ss10.37">10.37</A> <A HREF="adminmanual_en.html#toc10.37">dbimport <dbname> <filename> (9)</A>
631 <P><CODE><B>dbimport <dbname> <filename></B> Import AK1A data into a database</CODE></P>
632 <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:-
635 DBIMPORT oblast /tmp/OBLAST.FUL
638 will import the standard OBLAST database that comes with AK1A into theoblast database held locally.</P>
639 <H2><A NAME="ss10.38">10.38</A> <A HREF="adminmanual_en.html#toc10.38">dbremove <dbname> (9)</A>
642 <P><CODE><B>dbremove <dbname></B> Delete a database</CODE></P>
643 <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:
649 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>
650 <H2><A NAME="ss10.39">10.39</A> <A HREF="adminmanual_en.html#toc10.39">dbshow <dbname> <key> (0)</A>
653 <P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE></P>
654 <P>This is the generic user interface to the database to the database system.It is expected that the sysop will add an entry to the local Aliases fileso that users can use the more familiar AK1A style of enquiry such as:
660 but if he hasn't and the database really does exist (use DBAVAIL orSHOW/COMMAND to find out) you can do the same thing with:
667 <H2><A NAME="ss10.40">10.40</A> <A HREF="adminmanual_en.html#toc10.40">debug (9)</A>
670 <P><CODE><B>debug</B> Set the cluster program into debug mode</CODE></P>
671 <P>Executing this command will only have an effect if you are running the clusterin debug mode i.e.
677 It will interrupt the cluster just after the debug command has finished.</P>
678 <H2><A NAME="ss10.41">10.41</A> <A HREF="adminmanual_en.html#toc10.41">delete/usdb <callsign> ... (9)</A>
681 <P><CODE><B>delete/usdb <callsign> ...</B> Delete this user from the US State Database</CODE></P>
682 <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>
683 <H2><A NAME="ss10.42">10.42</A> <A HREF="adminmanual_en.html#toc10.42">delete/user <callsign> ... (9)</A>
686 <P><CODE><B>delete/user <callsign> ...</B> Delete this user from the User Database</CODE></P>
687 <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>
688 <H2><A NAME="ss10.43">10.43</A> <A HREF="adminmanual_en.html#toc10.43">demonstrate <call> <command> (9)</A>
691 <P><CODE><B>demonstrate <call> <command></B> Demonstrate a command to another user</CODE></P>
692 <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.
695 DEMO g7brn sh/dx iota oc209 DEMO g1tlh set/here
698 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>
699 <H2><A NAME="ss10.44">10.44</A> <A HREF="adminmanual_en.html#toc10.44">directory (0)</A>
702 <P><CODE><B>directory</B> List messages </CODE></P>
704 <H2><A NAME="ss10.45">10.45</A> <A HREF="adminmanual_en.html#toc10.45">directory <from>-<to> (0)</A>
707 <P><CODE><B>directory <from>-<to></B> List messages <from> message <to> message </CODE></P>
708 <P>List the messages in the messages directory.If there is a 'p' one space after the message number then it is a personal message. If there is a '-' between the message number and the'p' then this indicates that the message has been read.You can use shell escape characters such as '*' and '?' in the <call>fields.You can combine some of the various directory commands together eg:-
717 DIR SUBJECT IOTA 200-250
720 You can abbreviate all the commands to one letter and use ak1a syntax:-
723 DIR/T G1* 10 DIR/S QSL 10-100 5
727 <H2><A NAME="ss10.46">10.46</A> <A HREF="adminmanual_en.html#toc10.46">directory <nn> (0)</A>
730 <P><CODE><B>directory <nn></B> List last <nn> messages</CODE></P>
732 <H2><A NAME="ss10.47">10.47</A> <A HREF="adminmanual_en.html#toc10.47">directory all (0)</A>
735 <P><CODE><B>directory all</B> List all messages</CODE></P>
737 <H2><A NAME="ss10.48">10.48</A> <A HREF="adminmanual_en.html#toc10.48">directory from <call> (0)</A>
740 <P><CODE><B>directory from <call></B> List all messages from <call></CODE></P>
742 <H2><A NAME="ss10.49">10.49</A> <A HREF="adminmanual_en.html#toc10.49">directory new (0)</A>
745 <P><CODE><B>directory new</B> List all new messages</CODE></P>
747 <H2><A NAME="ss10.50">10.50</A> <A HREF="adminmanual_en.html#toc10.50">directory own (0)</A>
750 <P><CODE><B>directory own</B> List your own messages</CODE></P>
752 <H2><A NAME="ss10.51">10.51</A> <A HREF="adminmanual_en.html#toc10.51">directory subject <string> (0)</A>
755 <P><CODE><B>directory subject <string></B> List all messages with <string> in subject</CODE></P>
757 <H2><A NAME="ss10.52">10.52</A> <A HREF="adminmanual_en.html#toc10.52">directory to <call> (0)</A>
760 <P><CODE><B>directory to <call></B> List all messages to <call></CODE></P>
762 <H2><A NAME="ss10.53">10.53</A> <A HREF="adminmanual_en.html#toc10.53">directory- (5)</A>
765 <P><CODE><B>directory-</B> </CODE></P>
766 <P>Sysops can see all users' messages.</P>
767 <H2><A NAME="ss10.54">10.54</A> <A HREF="adminmanual_en.html#toc10.54">disconnect <call> [<call> ...] (8)</A>
770 <P><CODE><B>disconnect <call> [<call> ...]</B> Disconnect a user or cluster</CODE></P>
771 <P>Disconnect any <call> connected locally</P>
772 <H2><A NAME="ss10.55">10.55</A> <A HREF="adminmanual_en.html#toc10.55">dx [by <call>] <freq> <call> <remarks> (0)</A>
775 <P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE></P>
776 <P>This is how you send a DX Spot to other users. You can, in fact, nowenter the <freq> and the <call> either way round.
779 DX FR0G 144.600 DX 144.600 FR0G DX 144600 FR0G
782 will all give the same result. You can add some remarks to the endof the command and they will be added to the spot.
785 DX FR0G 144600 this is a test
788 You can credit someone else by saying:-
791 DX by G1TLH FR0G 144.600 he isn't on the cluster
794 The <freq> is compared against the available bands set up in the cluster. See SHOW/BANDS for more information.</P>
795 <H2><A NAME="ss10.56">10.56</A> <A HREF="adminmanual_en.html#toc10.56">echo <line> (0)</A>
798 <P><CODE><B>echo <line></B> Echo the line to the output</CODE></P>
799 <P>This command is useful in scripts and so forth for printing theline that you give to the command to the output. You can use thisin user_default scripts and the SAVE command for titling and so forthThe script will interpret certain standard "escape" sequences as follows:-
802 \t - becomes a TAB character (0x09 in ascii) \a - becomes a BEEP character (0x07 in ascii) \n - prints a new line
805 So the following example:-
808 echo GB7DJK is a dxcluster
814 GB7DJK is a dxcluster
817 on the output. You don't need a \n on the end of the line you want to send.A more complex example:-
820 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
826 GB7DJK g1tlh Dirk g3xvf Richard
830 <H2><A NAME="ss10.57">10.57</A> <A HREF="adminmanual_en.html#toc10.57">export <msgno> <filename> (9)</A>
833 <P><CODE><B>export <msgno> <filename></B> Export a message to a file</CODE></P>
834 <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:-
841 <H2><A NAME="ss10.58">10.58</A> <A HREF="adminmanual_en.html#toc10.58">export_users [<filename>] (9)</A>
844 <P><CODE><B>export_users [<filename>]</B> Export the users database to ascii</CODE></P>
845 <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>
846 <H2><A NAME="ss10.59">10.59</A> <A HREF="adminmanual_en.html#toc10.59">filtering... (0)</A>
849 <P><CODE><B>filtering...</B> Filtering things in DXSpider</CODE></P>
850 <P>There are a number of things you can filter in the DXSpider system. Theyall use the same general mechanism.In general terms you can create a 'reject' or an 'accept' filter whichcan have up to 10 lines in it. You do this using, for example:-
853 accept/spots ..... reject/spots .....
856 where ..... are the specific commands for that type of filter. Thereare filters for spots, wwv, announce, wcy and (for sysops)connects. See each different accept or reject command reference formore details.There is also a command to clear out one or more lines in a filter andone to show you what you have set. They are:-
859 clear/spots 1 clear/spots all
868 There is clear/xxxx command for each type of filter.For now we are going to use spots for the examples, but you can applythe principles to all types of filter.There are two main types of filter 'accept' or 'reject'; which you usedepends entirely on how you look at the world and what is leastwriting to achieve what you want. Each filter has 10 lines (of anylength) which are tried in order. If a line matches then the actionyou have specified is taken (ie reject means ignore it and acceptmeans gimme it).The important thing to remember is that if you specify a 'reject'filter (all the lines in it say 'reject/spots' (for instance)) then ifa spot comes in that doesn't match any of the lines then you will getit BUT if you specify an 'accept' filter then any spots that don'tmatch are dumped. For example if I have a one line accept filter:-
871 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
874 then automatically you will ONLY get VHF spots from or to CQ zones 1415 and 16. If you set a reject filter like:
877 reject/spots on hf/cw
880 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTAand will work it even on CW then you could say:-
883 reject/spots on hf/cw and not info iota
886 But in that case you might only be interested in iota and say:-
889 accept/spots not on hf/cw or info iota
892 which is exactly the same. You should choose one or the other untilyou are confortable with the way it works. Yes, you can mix them(actually you can have an accept AND a reject on the same line) butdon't try this at home until you can analyse the results that you getwithout ringing up the sysop for help.Another useful addition now is filtering by US state
895 accept/spots by_state VA,NH,RI,ME
898 You can arrange your filter lines into logical units, either for yourown understanding or simply convenience. I have one set frequently:-
901 reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
904 What this does is to ignore all HF CW spots (being a class B I can'tread any CW and couldn't possibly be interested in HF :-) and alsorejects any spots on VHF which don't either originate or spot someonein Europe.This is an exmaple where you would use the line number (1 and 2 inthis case), if you leave the digit out, the system assumes '1'. Digits'0'-'9' are available.You can leave the word 'and' out if you want, it is implied. You canuse any number of brackets to make the 'expression' as you wantit. There are things called precedence rules working here which meanthat you will NEED brackets in a situation like line 2 because,without it, will assume:-
907 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
910 annoying, but that is the way it is. If you use OR - usebrackets. Whilst we are here CASE is not important. 'And BY_Zone' isjust 'and by_zone'.If you want to alter your filter you can just redefine one or morelines of it or clear out one line. For example:-
913 reject/spots 1 on hf/ssb
922 To remove the filter in its entirty:-
928 There are similar CLEAR commands for the other filters:-
931 clear/announce clear/wcy clear/wwv
934 ADVANCED USERS:-Once you are happy with the results you get, you may like to experiment. my example that filters hf/cw spots and accepts vhf/uhf spots from EUcan be written with a mixed filter, eg:
937 rej/spot on hf/cw acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
940 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>
941 <H2><A NAME="ss10.60">10.60</A> <A HREF="adminmanual_en.html#toc10.60">forward/latlong <node_call> (8)</A>
944 <P><CODE><B>forward/latlong <node_call></B> Send latitude and longitude information to another cluster</CODE></P>
945 <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>
946 <H2><A NAME="ss10.61">10.61</A> <A HREF="adminmanual_en.html#toc10.61">forward/opernam <call> (1)</A>
949 <P><CODE><B>forward/opernam <call></B> Send out information on this <call> to all clusters</CODE></P>
950 <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>
951 <H2><A NAME="ss10.62">10.62</A> <A HREF="adminmanual_en.html#toc10.62">help (0)</A>
954 <P><CODE><B>help</B> The HELP Command</CODE></P>
955 <P>HELP is available for a number of commands. The syntax is:-
961 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>
962 <H2><A NAME="ss10.63">10.63</A> <A HREF="adminmanual_en.html#toc10.63">init <node> (5)</A>
965 <P><CODE><B>init <node></B> Re-initialise a link to an AK1A compatible node</CODE></P>
966 <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>
967 <H2><A NAME="ss10.64">10.64</A> <A HREF="adminmanual_en.html#toc10.64">join <group> (0)</A>
970 <P><CODE><B>join <group></B> Join a chat or conference group</CODE></P>
971 <P>JOIN allows you to join a network wide conference group. To join agroup (called FOC in this case) type:-
977 See also CHAT, LEAVE, SHOW/CHAT</P>
978 <H2><A NAME="ss10.65">10.65</A> <A HREF="adminmanual_en.html#toc10.65">kill (5)</A>
981 <P><CODE><B>kill</B> </CODE></P>
982 <P>As a sysop you can kill any message on the system.</P>
983 <H2><A NAME="ss10.66">10.66</A> <A HREF="adminmanual_en.html#toc10.66">kill <from msgno>-<to msgno> (0)</A>
986 <P><CODE><B>kill <from msgno>-<to msgno></B> Delete a range of messages</CODE></P>
988 <H2><A NAME="ss10.67">10.67</A> <A HREF="adminmanual_en.html#toc10.67">kill <from>-<to> (5)</A>
991 <P><CODE><B>kill <from>-<to></B> Remove a range of messages from the system</CODE></P>
993 <H2><A NAME="ss10.68">10.68</A> <A HREF="adminmanual_en.html#toc10.68">kill <msgno> [<msgno..] (0)</A>
996 <P><CODE><B>kill <msgno> [<msgno..]</B> Delete a message from the local system</CODE></P>
998 <H2><A NAME="ss10.69">10.69</A> <A HREF="adminmanual_en.html#toc10.69">kill <msgno> [<msgno> ...] (0)</A>
1001 <P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system</CODE></P>
1002 <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>
1003 <H2><A NAME="ss10.70">10.70</A> <A HREF="adminmanual_en.html#toc10.70">kill expunge <msgno> [<msgno..] (6)</A>
1006 <P><CODE><B>kill expunge <msgno> [<msgno..]</B> Expunge a message</CODE></P>
1007 <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>
1008 <H2><A NAME="ss10.71">10.71</A> <A HREF="adminmanual_en.html#toc10.71">kill from <call> (5)</A>
1011 <P><CODE><B>kill from <call></B> Remove all messages from a callsign</CODE></P>
1013 <H2><A NAME="ss10.72">10.72</A> <A HREF="adminmanual_en.html#toc10.72">kill full <msgno> [<msgno..] (5)</A>
1016 <P><CODE><B>kill full <msgno> [<msgno..]</B> Delete a message from the whole cluster</CODE></P>
1017 <P>Delete a message from the local system. You will only be able todelete messages that you have originated or been sent (unless you arethe sysop).
1022 </CODE></BLOCKQUOTE>
1023 Will delete all the messages that you own between msgnos 1234 and 1255.
1028 </CODE></BLOCKQUOTE>
1029 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
1034 </CODE></BLOCKQUOTE>
1035 will delete all messages to g1tlh.
1040 </CODE></BLOCKQUOTE>
1041 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>
1042 <H2><A NAME="ss10.73">10.73</A> <A HREF="adminmanual_en.html#toc10.73">kill full <msgno> [<msgno] (5)</A>
1045 <P><CODE><B>kill full <msgno> [<msgno]</B> Remove a message from the entire cluster</CODE></P>
1046 <P>Remove this message from the entire cluster system as well as your node.</P>
1047 <H2><A NAME="ss10.74">10.74</A> <A HREF="adminmanual_en.html#toc10.74">kill to <call> (5)</A>
1050 <P><CODE><B>kill to <call></B> Remove all messages to a callsign</CODE></P>
1052 <H2><A NAME="ss10.75">10.75</A> <A HREF="adminmanual_en.html#toc10.75">kill from <regex> (0)</A>
1055 <P><CODE><B>kill from <regex></B> Delete messages FROM a callsign or pattern</CODE></P>
1057 <H2><A NAME="ss10.76">10.76</A> <A HREF="adminmanual_en.html#toc10.76">kill to <regex> (0)</A>
1060 <P><CODE><B>kill to <regex></B> Delete messages TO a callsign or pattern</CODE></P>
1062 <H2><A NAME="ss10.77">10.77</A> <A HREF="adminmanual_en.html#toc10.77">leave <group> (0)</A>
1065 <P><CODE><B>leave <group></B> Leave a chat or conference group</CODE></P>
1066 <P>LEAVE allows you to leave a network wide conference group. To leave agroup (called FOC in this case) type:-
1071 </CODE></BLOCKQUOTE>
1072 See also CHAT, JOIN, SHOW/CHAT</P>
1073 <H2><A NAME="ss10.78">10.78</A> <A HREF="adminmanual_en.html#toc10.78">links (0)</A>
1076 <P><CODE><B>links</B> Show which nodes is physically connected</CODE></P>
1077 <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>
1078 <H2><A NAME="ss10.79">10.79</A> <A HREF="adminmanual_en.html#toc10.79">load/aliases (9)</A>
1081 <P><CODE><B>load/aliases</B> Reload the command alias table</CODE></P>
1082 <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>
1083 <H2><A NAME="ss10.80">10.80</A> <A HREF="adminmanual_en.html#toc10.80">load/badmsg (9)</A>
1086 <P><CODE><B>load/badmsg</B> Reload the bad msg table</CODE></P>
1087 <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>
1088 <H2><A NAME="ss10.81">10.81</A> <A HREF="adminmanual_en.html#toc10.81">load/badwords (9)</A>
1091 <P><CODE><B>load/badwords</B> Reload the bad words table</CODE></P>
1092 <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>
1093 <H2><A NAME="ss10.82">10.82</A> <A HREF="adminmanual_en.html#toc10.82">load/bands (9)</A>
1096 <P><CODE><B>load/bands</B> Reload the band limits table</CODE></P>
1097 <P>Reload the /spider/data/bands.pl file if you have changed it manually whilstthe cluster is running. </P>
1098 <H2><A NAME="ss10.83">10.83</A> <A HREF="adminmanual_en.html#toc10.83">load/cmd_cache (9)</A>
1101 <P><CODE><B>load/cmd_cache</B> Reload the automatic command cache</CODE></P>
1102 <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>
1103 <H2><A NAME="ss10.84">10.84</A> <A HREF="adminmanual_en.html#toc10.84">load/forward (9)</A>
1106 <P><CODE><B>load/forward</B> Reload the msg forwarding routing table</CODE></P>
1107 <P>Reload the /spider/msg/forward.pl file if you have changed itmanually whilst the cluster is running.</P>
1108 <H2><A NAME="ss10.85">10.85</A> <A HREF="adminmanual_en.html#toc10.85">load/keps (5)</A>
1111 <P><CODE><B>load/keps</B> Load new keps data</CODE></P>
1113 <H2><A NAME="ss10.86">10.86</A> <A HREF="adminmanual_en.html#toc10.86">load/keps [nn] (5)</A>
1116 <P><CODE><B>load/keps [nn]</B> Load new keps data from message</CODE></P>
1117 <P>If there is no message number then reload the current Keps data fromthe Keps.pm data file. You create this file by running
1120 /spider/perl/convkeps.pl <filename>
1122 </CODE></BLOCKQUOTE>
1123 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>
1124 <H2><A NAME="ss10.87">10.87</A> <A HREF="adminmanual_en.html#toc10.87">load/messages (9)</A>
1127 <P><CODE><B>load/messages</B> Reload the system messages file</CODE></P>
1128 <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>
1129 <H2><A NAME="ss10.88">10.88</A> <A HREF="adminmanual_en.html#toc10.88">load/prefixes (9)</A>
1132 <P><CODE><B>load/prefixes</B> Reload the prefix table</CODE></P>
1133 <P>Reload the /spider/data/prefix_data.pl file if you have changed itmanually whilst the cluster is running.</P>
1134 <H2><A NAME="ss10.89">10.89</A> <A HREF="adminmanual_en.html#toc10.89">merge <node> [<no spots>/<no wwv>] (5)</A>
1137 <P><CODE><B>merge <node> [<no spots>/<no wwv>]</B> Ask for the latest spots and WWV </CODE></P>
1138 <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>
1139 <H2><A NAME="ss10.90">10.90</A> <A HREF="adminmanual_en.html#toc10.90">msg <cmd> <msgno> [data ... ] (9)</A>
1142 <P><CODE><B>msg <cmd> <msgno> [data ... ]</B> Alter various message parameters</CODE></P>
1143 <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.
1146 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
1148 </CODE></BLOCKQUOTE>
1149 You can look at the status of a message by using:-
1152 STAT/MSG <msgno>
1154 </CODE></BLOCKQUOTE>
1155 This will display more information on the message than DIR does.</P>
1156 <H2><A NAME="ss10.91">10.91</A> <A HREF="adminmanual_en.html#toc10.91">pc <call> <text> (8)</A>
1159 <P><CODE><B>pc <call> <text></B> Send arbitrary text to a connected callsign</CODE></P>
1160 <P>Send some arbitrary text to a locally connected callsign. Noprocessing is done on the text. This command allows you to send PCProtocol to unstick things if problems arise (messages get stucketc). eg:-
1163 pc gb7djk PC33^GB7TLH^GB7DJK^400^
1165 </CODE></BLOCKQUOTE>
1169 pc G1TLH Try doing that properly!!!
1171 </CODE></BLOCKQUOTE>
1172 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>
1173 <H2><A NAME="ss10.92">10.92</A> <A HREF="adminmanual_en.html#toc10.92">ping <node call> (1)</A>
1176 <P><CODE><B>ping <node call></B> Check the link quality between nodes</CODE></P>
1177 <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>
1178 <H2><A NAME="ss10.93">10.93</A> <A HREF="adminmanual_en.html#toc10.93">rcmd <node call> <cmd> (1)</A>
1181 <P><CODE><B>rcmd <node call> <cmd></B> Send a command to another DX Cluster</CODE></P>
1182 <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>
1183 <H2><A NAME="ss10.94">10.94</A> <A HREF="adminmanual_en.html#toc10.94">read (0)</A>
1186 <P><CODE><B>read</B> Read the next unread personal message addressed to you</CODE></P>
1188 <H2><A NAME="ss10.95">10.95</A> <A HREF="adminmanual_en.html#toc10.95">read <msgno> (0)</A>
1191 <P><CODE><B>read <msgno></B> Read the specified message</CODE></P>
1192 <P>You can read any messages that are sent as 'non-personal' and also anymessage either sent by or sent to your callsign.</P>
1193 <H2><A NAME="ss10.96">10.96</A> <A HREF="adminmanual_en.html#toc10.96">read- (5)</A>
1196 <P><CODE><B>read-</B> </CODE></P>
1197 <P>As a sysop you may read any message on the system</P>
1198 <H2><A NAME="ss10.97">10.97</A> <A HREF="adminmanual_en.html#toc10.97">reject (0)</A>
1201 <P><CODE><B>reject</B> Set a filter to reject something</CODE></P>
1202 <P>Create a filter to reject somethingThere are 2 types of filter, accept and reject. See HELP FILTERING for moreinfo.</P>
1203 <H2><A NAME="ss10.98">10.98</A> <A HREF="adminmanual_en.html#toc10.98">reject/announce <call> [input] [0-9] <pattern> (8)</A>
1206 <P><CODE><B>reject/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE></P>
1207 <P>This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-
1210 reject/ann by G,M,2 reject/ann input node_default by G,M,2 reject/ann user_default by G,M,2
1212 </CODE></BLOCKQUOTE>
1214 <H2><A NAME="ss10.99">10.99</A> <A HREF="adminmanual_en.html#toc10.99">reject/announce [0-9] <pattern> (0)</A>
1217 <P><CODE><B>reject/announce [0-9] <pattern></B> Set a 'reject' filter line for announce</CODE></P>
1218 <P>Create an 'reject this announce' line for a filter. A reject filter line means that if the announce matches this filter it ispassed onto the user. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:-
1221 info <string> eg: iota or qsl by <prefixes> eg: G,M,2 origin <prefixes> origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> origin_state <states> eg: VA,NH,RI,ME by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> by_state <states> eg: VA,NH,RI,ME channel <prefixes> wx 1 filter WX announces dest <prefixes> eg: 6MUK,WDX (distros)
1223 </CODE></BLOCKQUOTE>
1227 rej/ann by_zone 14,15,16 and not by G,M,2
1229 </CODE></BLOCKQUOTE>
1230 You can use the tag 'all' to reject everything eg:
1235 </CODE></BLOCKQUOTE>
1236 but this probably for advanced users...</P>
1237 <H2><A NAME="ss10.100">10.100</A> <A HREF="adminmanual_en.html#toc10.100">reject/route <call> [0-9] <pattern> (8)</A>
1240 <P><CODE><B>reject/route <call> [0-9] <pattern></B> Set an 'reject' filter line for routing</CODE></P>
1241 <P>Create an 'reject this routing PC Protocol' line for a filter. An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter it is NOT passed thru that interface. See HELP FILTERING for more info. Please read this to understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:-
1244 call <prefixes> the callsign of the thingy call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) call_itu <prefixes or numbers> or: G,GM,GW call_zone <prefixes or numbers> call_state <states> eg: VA,NH,RI,ME origin <prefixes> really the interface it came in on origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> origin_state <states> eg: VA,NH,RI,ME
1246 </CODE></BLOCKQUOTE>
1250 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
1252 </CODE></BLOCKQUOTE>
1253 You can use the tag 'all' to reject everything eg:
1256 rej/route all (equiv to [very] restricted mode)
1258 </CODE></BLOCKQUOTE>
1259 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.</P>
1260 <H2><A NAME="ss10.101">10.101</A> <A HREF="adminmanual_en.html#toc10.101">reject/spots <call> [input] [0-9] <pattern> (8)</A>
1263 <P><CODE><B>reject/spots <call> [input] [0-9] <pattern></B> Spot filter sysop version</CODE></P>
1264 <P>This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-
1267 reject/spot db0sue-7 1 by_zone 14,15,16 reject/spot node_default all set/hops node_default 10
1269 </CODE></BLOCKQUOTE>
1272 reject/spot user_default by G,M,2
1274 </CODE></BLOCKQUOTE>
1276 <H2><A NAME="ss10.102">10.102</A> <A HREF="adminmanual_en.html#toc10.102">reject/spots [0-9] <pattern> (0)</A>
1279 <P><CODE><B>reject/spots [0-9] <pattern></B> Set a 'reject' filter line for spots</CODE></P>
1280 <P>Create a 'reject this spot' line for a filter. A reject filter line means that if the spot matches this filter it isdumped (not passed on). See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:-
1283 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m on <range> same as 'freq' call <prefixes> eg: G,PA,HB9 info <string> eg: iota or qsl by <prefixes> call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) call_itu <prefixes or numbers> or: G,GM,GW call_zone <prefixes or numbers> call_state <states> eg: VA,NH,RI,ME by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> by_state <states> eg: VA,NH,RI,ME origin <prefixes> channel <prefixes>
1285 </CODE></BLOCKQUOTE>
1286 'call' means the callsign that has spotted 'by' whoever.For frequencies, you can use any of the band names defined inSHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -thus: hf/ssb. You can also just have a simple range like: 0/30000 -this is more efficient than saying simply: on HF (but don't gettoo hung up about that)some examples:-
1289 rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1291 </CODE></BLOCKQUOTE>
1292 You can use the tag 'all' to reject everything eg:
1297 </CODE></BLOCKQUOTE>
1298 but this probably for advanced users...</P>
1299 <H2><A NAME="ss10.103">10.103</A> <A HREF="adminmanual_en.html#toc10.103">reject/wcy <call> [input] [0-9] <pattern> (8)</A>
1302 <P><CODE><B>reject/wcy <call> [input] [0-9] <pattern></B> WCY filter sysop version</CODE></P>
1303 <P>This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-
1306 reject/wcy gb7djk all
1308 </CODE></BLOCKQUOTE>
1310 <H2><A NAME="ss10.104">10.104</A> <A HREF="adminmanual_en.html#toc10.104">reject/wcy [0-9] <pattern> (0)</A>
1313 <P><CODE><B>reject/wcy [0-9] <pattern></B> set a 'reject' WCY filter</CODE></P>
1314 <P>It is unlikely that you will want to do this, but if you do then you canfilter on the following fields:-
1317 by <prefixes> eg: G,M,2 origin <prefixes> origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> channel <prefixes>
1319 </CODE></BLOCKQUOTE>
1320 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>
1321 <H2><A NAME="ss10.105">10.105</A> <A HREF="adminmanual_en.html#toc10.105">reject/wwv <call> [input] [0-9] <pattern> (8)</A>
1324 <P><CODE><B>reject/wwv <call> [input] [0-9] <pattern></B> WWV filter sysop version</CODE></P>
1325 <P>This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-
1328 reject/wwv db0sue-7 1 by_zone 4 reject/wwv node_default all
1330 </CODE></BLOCKQUOTE>
1333 reject/wwv user_default by W
1335 </CODE></BLOCKQUOTE>
1337 <H2><A NAME="ss10.106">10.106</A> <A HREF="adminmanual_en.html#toc10.106">reject/wwv [0-9] <pattern> (0)</A>
1340 <P><CODE><B>reject/wwv [0-9] <pattern></B> set a 'reject' WWV filter</CODE></P>
1341 <P>It is unlikely that you will want to do this, but if you do then you canfilter on the following fields:-
1344 by <prefixes> eg: G,M,2 origin <prefixes> origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> channel <prefixes>
1346 </CODE></BLOCKQUOTE>
1350 reject/wwv by_zone 14,15,16
1352 </CODE></BLOCKQUOTE>
1353 is probably the only useful thing to do (which will only show WWV broadcastsby stations in the US).See HELP FILTER for information.</P>
1354 <H2><A NAME="ss10.107">10.107</A> <A HREF="adminmanual_en.html#toc10.107">reply (0)</A>
1357 <P><CODE><B>reply</B> Reply (privately) to the last message that you have read</CODE></P>
1359 <H2><A NAME="ss10.108">10.108</A> <A HREF="adminmanual_en.html#toc10.108">reply <msgno> (0)</A>
1362 <P><CODE><B>reply <msgno></B> Reply (privately) to the specified message</CODE></P>
1364 <H2><A NAME="ss10.109">10.109</A> <A HREF="adminmanual_en.html#toc10.109">reply b <msgno> (0)</A>
1367 <P><CODE><B>reply b <msgno></B> Reply as a Bulletin to the specified message</CODE></P>
1369 <H2><A NAME="ss10.110">10.110</A> <A HREF="adminmanual_en.html#toc10.110">reply noprivate <msgno> (0)</A>
1372 <P><CODE><B>reply noprivate <msgno></B> Reply as a Bulletin to the specified message</CODE></P>
1374 <H2><A NAME="ss10.111">10.111</A> <A HREF="adminmanual_en.html#toc10.111">reply rr <msgno> (0)</A>
1377 <P><CODE><B>reply rr <msgno></B> Reply to the specified message with read receipt</CODE></P>
1378 <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>
1379 <H2><A NAME="ss10.112">10.112</A> <A HREF="adminmanual_en.html#toc10.112">save [-d -t -a] <filename> "<cmd>" [...] (9)</A>
1382 <P><CODE><B>save [-d -t -a] <filename> "<cmd>" [...]</B> Save command output to a file</CODE></P>
1383 <P>This sysop only cammand allows you to save the output of one or morecommands to a file. For example:-
1386 save /spider/packclus/dxstats show/dxstat
1388 </CODE></BLOCKQUOTE>
1389 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:-
1392 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
1394 </CODE></BLOCKQUOTE>
1395 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:-
1398 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
1400 </CODE></BLOCKQUOTE>
1404 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
1406 </CODE></BLOCKQUOTE>
1407 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:-
1410 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
1412 </CODE></BLOCKQUOTE>
1413 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>
1414 <H2><A NAME="ss10.113">10.113</A> <A HREF="adminmanual_en.html#toc10.113">send <call> [<call> ...] (0)</A>
1417 <P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns</CODE></P>
1419 <H2><A NAME="ss10.114">10.114</A> <A HREF="adminmanual_en.html#toc10.114">send copy <msgno> <call> (0)</A>
1422 <P><CODE><B>send copy <msgno> <call></B> Send a copy of a message to someone</CODE></P>
1424 <H2><A NAME="ss10.115">10.115</A> <A HREF="adminmanual_en.html#toc10.115">send noprivate <call> (0)</A>
1427 <P><CODE><B>send noprivate <call></B> Send a message to all stations</CODE></P>
1428 <P>All the SEND commands will create a message which will be sent either toan individual callsign or to one of the 'bulletin' addresses. SEND <call> on its own acts as though you had typed SEND PRIVATE, that isit will mark the message as personal and send it to the cluster node thatthat callsign is connected to. If the <call> you have specified is in facta known bulletin category on your node (eg: ALL) then the message shouldautomatically become a bulletin.You can have more than one callsign in all of the SEND commands.You can have multiple qualifiers so that you can have for example:-
1431 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1433 </CODE></BLOCKQUOTE>
1434 which should send a copy of message 123 to G1TLH and G0RDI and you willreceive a read receipt when they have read the message.SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)SP is an alias for SEND PRIVATEThe system will ask you for a subject. Conventionally this should be no longer than 29 characters for compatibility. Most modern clustersoftware should accept more.You will now be prompted to start entering your text. You finish the message by entering '/EX' on a new line. For instance:
1437 ... bye then Jim 73 Dirk /ex
1439 </CODE></BLOCKQUOTE>
1440 If you have started a message and you don't want to keep it then youcan abandon the message with '/ABORT' on a new line, like:-
1443 line 1 line 2 oh I just can't be bothered with this /abort
1445 </CODE></BLOCKQUOTE>
1446 If you abort the message it will NOT be sent.When you are entering the text of your message, most normal output (suchas DX announcements and so on are suppressed and stored for latter display(upto 20 such lines are stored, as new ones come along, so the oldestlines are dropped).Also, you can enter normal commands commands (and get the output immediately) whilst in the middle of a message. You do this by typingthe command preceeded by a '/' character on a new line, so:-
1449 /dx g1tlh 144010 strong signal
1451 </CODE></BLOCKQUOTE>
1452 Will issue a dx annoucement to the rest of the cluster. Also, you can add the output of a command to your message by preceeding the command with '//', thus :-
1457 </CODE></BLOCKQUOTE>
1458 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>
1459 <H2><A NAME="ss10.116">10.116</A> <A HREF="adminmanual_en.html#toc10.116">send private <call> (0)</A>
1462 <P><CODE><B>send private <call></B> Send a personal message</CODE></P>
1464 <H2><A NAME="ss10.117">10.117</A> <A HREF="adminmanual_en.html#toc10.117">send rr <call> (0)</A>
1467 <P><CODE><B>send rr <call></B> Send a message and ask for a read receipt</CODE></P>
1469 <H2><A NAME="ss10.118">10.118</A> <A HREF="adminmanual_en.html#toc10.118">set/address <your address> (0)</A>
1472 <P><CODE><B>set/address <your address></B> Record your postal address</CODE></P>
1474 <H2><A NAME="ss10.119">10.119</A> <A HREF="adminmanual_en.html#toc10.119">set/announce (0)</A>
1477 <P><CODE><B>set/announce</B> Allow announce messages to come out on your terminal</CODE></P>
1479 <H2><A NAME="ss10.120">10.120</A> <A HREF="adminmanual_en.html#toc10.120">set/anntalk (0)</A>
1482 <P><CODE><B>set/anntalk</B> Allow talk like announce messages on your terminal</CODE></P>
1484 <H2><A NAME="ss10.121">10.121</A> <A HREF="adminmanual_en.html#toc10.121">set/arcluster <call> [<call>..] (5)</A>
1487 <P><CODE><B>set/arcluster <call> [<call>..]</B> Make the callsign an AR-Cluster node</CODE></P>
1489 <H2><A NAME="ss10.122">10.122</A> <A HREF="adminmanual_en.html#toc10.122">set/baddx <call>.. (8)</A>
1492 <P><CODE><B>set/baddx <call>..</B> Stop callsigns in a dx spot being propagated</CODE></P>
1494 <H2><A NAME="ss10.123">10.123</A> <A HREF="adminmanual_en.html#toc10.123">set/badnode <call>.. (8)</A>
1497 <P><CODE><B>set/badnode <call>..</B> Stop spots from this node being propagated</CODE></P>
1499 <H2><A NAME="ss10.124">10.124</A> <A HREF="adminmanual_en.html#toc10.124">set/badspotter <call>.. (8)</A>
1502 <P><CODE><B>set/badspotter <call>..</B> Stop spots from this callsign being propagated</CODE></P>
1504 <H2><A NAME="ss10.125">10.125</A> <A HREF="adminmanual_en.html#toc10.125">set/badword <word>.. (8)</A>
1507 <P><CODE><B>set/badword <word>..</B> Stop things with this word being propagated</CODE></P>
1509 <H2><A NAME="ss10.126">10.126</A> <A HREF="adminmanual_en.html#toc10.126">set/bbs <call> [<call>..] (5)</A>
1512 <P><CODE><B>set/bbs <call> [<call>..]</B> Make the callsign a BBS</CODE></P>
1514 <H2><A NAME="ss10.127">10.127</A> <A HREF="adminmanual_en.html#toc10.127">set/beep (0)</A>
1517 <P><CODE><B>set/beep</B> Add a beep to DX and other messages on your terminal</CODE></P>
1519 <H2><A NAME="ss10.128">10.128</A> <A HREF="adminmanual_en.html#toc10.128">set/clx <call> [<call>..] (5)</A>
1522 <P><CODE><B>set/clx <call> [<call>..]</B> Make the callsign an CLX node</CODE></P>
1524 <H2><A NAME="ss10.129">10.129</A> <A HREF="adminmanual_en.html#toc10.129">set/debug <name> (9)</A>
1527 <P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE></P>
1529 <H2><A NAME="ss10.130">10.130</A> <A HREF="adminmanual_en.html#toc10.130">set/dx (0)</A>
1532 <P><CODE><B>set/dx</B> Allow DX messages to come out on your terminal</CODE></P>
1534 <H2><A NAME="ss10.131">10.131</A> <A HREF="adminmanual_en.html#toc10.131">set/dxcq (0)</A>
1537 <P><CODE><B>set/dxcq</B> Show CQ Zones on the end of DX announcements</CODE></P>
1539 <H2><A NAME="ss10.132">10.132</A> <A HREF="adminmanual_en.html#toc10.132">set/dxgrid (0)</A>
1542 <P><CODE><B>set/dxgrid</B> Allow QRA Grid Squares on the end of DX announcements</CODE></P>
1544 <H2><A NAME="ss10.133">10.133</A> <A HREF="adminmanual_en.html#toc10.133">set/dxitu (0)</A>
1547 <P><CODE><B>set/dxitu</B> Show ITU Zones on the end of DX announcements</CODE></P>
1549 <H2><A NAME="ss10.134">10.134</A> <A HREF="adminmanual_en.html#toc10.134">set/dxnet <call> [<call>..] (5)</A>
1552 <P><CODE><B>set/dxnet <call> [<call>..]</B> Make the callsign an DXNet node</CODE></P>
1554 <H2><A NAME="ss10.135">10.135</A> <A HREF="adminmanual_en.html#toc10.135">set/echo (0)</A>
1557 <P><CODE><B>set/echo</B> Make the cluster echo your input</CODE></P>
1559 <H2><A NAME="ss10.136">10.136</A> <A HREF="adminmanual_en.html#toc10.136">set/email <email> ... (0)</A>
1562 <P><CODE><B>set/email <email> ...</B> Set email address(es) and forward your personals</CODE></P>
1564 <H2><A NAME="ss10.137">10.137</A> <A HREF="adminmanual_en.html#toc10.137">set/here (0)</A>
1567 <P><CODE><B>set/here</B> Tell the system you are present at your terminal</CODE></P>
1569 <H2><A NAME="ss10.138">10.138</A> <A HREF="adminmanual_en.html#toc10.138">set/homenode <node> (0)</A>
1572 <P><CODE><B>set/homenode <node> </B> Set your normal cluster callsign</CODE></P>
1573 <P>Tell the cluster system where you normally connect to. Any Messages sentto you will normally find their way there should you not be connected.eg:-
1578 </CODE></BLOCKQUOTE>
1580 <H2><A NAME="ss10.139">10.139</A> <A HREF="adminmanual_en.html#toc10.139">set/hops <call> ann|spots|route|wwv|wcy <n> (8)</A>
1583 <P><CODE><B>set/hops <call> ann|spots|route|wwv|wcy <n></B> Set hop count </CODE></P>
1585 <H2><A NAME="ss10.140">10.140</A> <A HREF="adminmanual_en.html#toc10.140">set/isolate (9)</A>
1588 <P><CODE><B>set/isolate</B> Isolate a node from the rest of the network</CODE></P>
1589 <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>
1590 <H2><A NAME="ss10.141">10.141</A> <A HREF="adminmanual_en.html#toc10.141">set/language <lang> (0)</A>
1593 <P><CODE><B>set/language <lang></B> Set the language you want to use</CODE></P>
1594 <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>
1595 <H2><A NAME="ss10.142">10.142</A> <A HREF="adminmanual_en.html#toc10.142">set/location <lat & long> (0)</A>
1598 <P><CODE><B>set/location <lat & long></B> Set your latitude and longitude</CODE></P>
1600 <H2><A NAME="ss10.143">10.143</A> <A HREF="adminmanual_en.html#toc10.143">set/lockout <call> (9)</A>
1603 <P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE></P>
1605 <H2><A NAME="ss10.144">10.144</A> <A HREF="adminmanual_en.html#toc10.144">set/logininfo (0)</A>
1608 <P><CODE><B>set/logininfo</B> Inform when a station logs in locally</CODE></P>
1610 <H2><A NAME="ss10.145">10.145</A> <A HREF="adminmanual_en.html#toc10.145">set/name <your name> (0)</A>
1613 <P><CODE><B>set/name <your name></B> Set your name</CODE></P>
1614 <P>Tell the system what your name is eg:-
1619 </CODE></BLOCKQUOTE>
1621 <H2><A NAME="ss10.146">10.146</A> <A HREF="adminmanual_en.html#toc10.146">set/node <call> [<call>..] (5)</A>
1624 <P><CODE><B>set/node <call> [<call>..]</B> Make the callsign an AK1A cluster</CODE></P>
1625 <P>Tell the system that the call(s) are to be treated as AK1A cluster andfed PC Protocol rather normal user commands.</P>
1626 <H2><A NAME="ss10.147">10.147</A> <A HREF="adminmanual_en.html#toc10.147">set/obscount <count> <call> (8)</A>
1629 <P><CODE><B>set/obscount <count> <call></B> Set the 'pump-up' obscelence PING counter </CODE></P>
1630 <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>
1631 <H2><A NAME="ss10.148">10.148</A> <A HREF="adminmanual_en.html#toc10.148">set/page <lines per page> (0)</A>
1634 <P><CODE><B>set/page <lines per page></B> Set the lines per page</CODE></P>
1635 <P>Tell the system how many lines you wish on a page when the number of lineof output from a command is more than this. The default is 20. Setting itexplicitly to 0 will disable paging.
1638 SET/PAGE 30 SET/PAGE 0
1640 </CODE></BLOCKQUOTE>
1641 The setting is stored in your user profile.</P>
1642 <H2><A NAME="ss10.149">10.149</A> <A HREF="adminmanual_en.html#toc10.149">set/password (0)</A>
1645 <P><CODE><B>set/password</B> Set your own password</CODE></P>
1646 <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>
1647 <H2><A NAME="ss10.150">10.150</A> <A HREF="adminmanual_en.html#toc10.150">set/password <callsign> <string> (9)</A>
1650 <P><CODE><B>set/password <callsign> <string></B> Set a users password</CODE></P>
1651 <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:
1654 set/var $main::passwdreq = 1
1656 </CODE></BLOCKQUOTE>
1657 command is executed in the startup script, then a password prompt isgiven after the normal 'login: ' prompt. </P>
1658 <H2><A NAME="ss10.151">10.151</A> <A HREF="adminmanual_en.html#toc10.151">set/pinginterval <time> <nodecall> (9)</A>
1661 <P><CODE><B>set/pinginterval <time> <nodecall></B> Set ping time to neighbouring nodes </CODE></P>
1662 <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:-
1665 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
1667 </CODE></BLOCKQUOTE>
1668 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>
1669 <H2><A NAME="ss10.152">10.152</A> <A HREF="adminmanual_en.html#toc10.152">set/privilege <n> <call> [<call..] (9)</A>
1672 <P><CODE><B>set/privilege <n> <call> [<call..]</B> Set privilege level on a call</CODE></P>
1673 <P>Set the privilege level on a callsign. The privilege levels that pertainto commands are as default:-
1676 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.
1678 </CODE></BLOCKQUOTE>
1679 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>
1680 <H2><A NAME="ss10.153">10.153</A> <A HREF="adminmanual_en.html#toc10.153">set/prompt <string> (0)</A>
1683 <P><CODE><B>set/prompt <string></B> Set your prompt to <string></CODE></P>
1685 <H2><A NAME="ss10.154">10.154</A> <A HREF="adminmanual_en.html#toc10.154">set/qra <locator> (0)</A>
1688 <P><CODE><B>set/qra <locator></B> Set your QRA Grid locator</CODE></P>
1689 <P>Tell the system what your QRA (or Maidenhead) locator is. If you have notdone a SET/LOCATION then your latitude and longitude will be set roughlycorrectly (assuming your locator is correct ;-). For example:-
1694 </CODE></BLOCKQUOTE>
1696 <H2><A NAME="ss10.155">10.155</A> <A HREF="adminmanual_en.html#toc10.155">set/qth <your qth> (0)</A>
1699 <P><CODE><B>set/qth <your qth></B> Set your QTH</CODE></P>
1700 <P>Tell the system where you are. For example:-
1703 SET/QTH East Dereham, Norfolk
1705 </CODE></BLOCKQUOTE>
1707 <H2><A NAME="ss10.156">10.156</A> <A HREF="adminmanual_en.html#toc10.156">set/register <call> ... (9)</A>
1710 <P><CODE><B>set/register <call> ...</B> Mark a user as registered</CODE></P>
1712 <H2><A NAME="ss10.157">10.157</A> <A HREF="adminmanual_en.html#toc10.157">set/spider <call> [<call>..] (5)</A>
1715 <P><CODE><B>set/spider <call> [<call>..]</B> Make the callsign an DXSpider node</CODE></P>
1716 <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>
1717 <H2><A NAME="ss10.158">10.158</A> <A HREF="adminmanual_en.html#toc10.158">set/sys_location <lat & long> (9)</A>
1720 <P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE></P>
1721 <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:-
1724 SET/LOCATION 52 22 N 0 57 E
1726 </CODE></BLOCKQUOTE>
1728 <H2><A NAME="ss10.159">10.159</A> <A HREF="adminmanual_en.html#toc10.159">set/sys_qra <locator> (9)</A>
1731 <P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA Grid locator</CODE></P>
1733 <H2><A NAME="ss10.160">10.160</A> <A HREF="adminmanual_en.html#toc10.160">set/talk (0)</A>
1736 <P><CODE><B>set/talk</B> Allow TALK messages to come out on your terminal</CODE></P>
1738 <H2><A NAME="ss10.161">10.161</A> <A HREF="adminmanual_en.html#toc10.161">set/usdb <call> <state> <city> (9)</A>
1741 <P><CODE><B>set/usdb <call> <state> <city></B> add/update a US DB callsign</CODE></P>
1742 <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
1745 set/usdb g1tlh nh downtown rindge
1747 </CODE></BLOCKQUOTE>
1748 see also DELETE/USDB</P>
1749 <H2><A NAME="ss10.162">10.162</A> <A HREF="adminmanual_en.html#toc10.162">set/usstate (0)</A>
1752 <P><CODE><B>set/usstate</B> Allow US State info on the end of DX announcements</CODE></P>
1754 <H2><A NAME="ss10.163">10.163</A> <A HREF="adminmanual_en.html#toc10.163">set/wcy (0)</A>
1757 <P><CODE><B>set/wcy</B> Allow WCY messages to come out on your terminal</CODE></P>
1759 <H2><A NAME="ss10.164">10.164</A> <A HREF="adminmanual_en.html#toc10.164">set/wwv (0)</A>
1762 <P><CODE><B>set/wwv</B> Allow WWV messages to come out on your terminal</CODE></P>
1764 <H2><A NAME="ss10.165">10.165</A> <A HREF="adminmanual_en.html#toc10.165">set/wx (0)</A>
1767 <P><CODE><B>set/wx</B> Allow WX messages to come out on your terminal</CODE></P>
1769 <H2><A NAME="ss10.166">10.166</A> <A HREF="adminmanual_en.html#toc10.166">show/baddx (1)</A>
1772 <P><CODE><B>show/baddx</B> Show all the bad dx calls in the system</CODE></P>
1773 <P>Display all the bad dx callsigns in the system, see SET/BADDXfor more information.</P>
1774 <H2><A NAME="ss10.167">10.167</A> <A HREF="adminmanual_en.html#toc10.167">show/badnode (1)</A>
1777 <P><CODE><B>show/badnode</B> Show all the bad nodes in the system</CODE></P>
1778 <P>Display all the bad node callsigns in the system, see SET/BADNODEfor more information.</P>
1779 <H2><A NAME="ss10.168">10.168</A> <A HREF="adminmanual_en.html#toc10.168">show/badspotter (1)</A>
1782 <P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE></P>
1783 <P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTERfor more information.</P>
1784 <H2><A NAME="ss10.169">10.169</A> <A HREF="adminmanual_en.html#toc10.169">show/badword (1)</A>
1787 <P><CODE><B>show/badword</B> Show all the bad words in the system</CODE></P>
1788 <P>Display all the bad words in the system, see SET/BADWORDfor more information.</P>
1789 <H2><A NAME="ss10.170">10.170</A> <A HREF="adminmanual_en.html#toc10.170">show/chat [<group>] [<lines>] (0)</A>
1792 <P><CODE><B>show/chat [<group>] [<lines>]</B> Show any chat or conferencing </CODE></P>
1793 <P>This command allows you to see any chat or conferencing that has occurred whilst you were away. SHOW/CHAT on its own will show data forall groups. If you use a group name then it will show only chat forthat group.</P>
1794 <H2><A NAME="ss10.171">10.171</A> <A HREF="adminmanual_en.html#toc10.171">show/configuration [<node>] (0)</A>
1797 <P><CODE><B>show/configuration [<node>]</B> Show all the nodes and users visible</CODE></P>
1798 <P>This command allows you to see all the users that can be seenand the nodes to which they are connected.This command is normally abbreviated to: sh/cNormally, the list returned will be just for the nodes from your country (because the list otherwise will be very long).
1803 </CODE></BLOCKQUOTE>
1804 will produce a complete list of all nodes. BE WARNED: the list that is returned can be VERY longIt is possible to supply a node or part of a prefix and you will get a list of the users for that node or list of nodes starting withthat prefix.
1809 </CODE></BLOCKQUOTE>
1814 </CODE></BLOCKQUOTE>
1816 <H2><A NAME="ss10.172">10.172</A> <A HREF="adminmanual_en.html#toc10.172">show/configuration/node (0)</A>
1819 <P><CODE><B>show/configuration/node</B> Show all the nodes connected locally</CODE></P>
1820 <P>Show all the nodes connected to this node.</P>
1821 <H2><A NAME="ss10.173">10.173</A> <A HREF="adminmanual_en.html#toc10.173">show/connect (1)</A>
1824 <P><CODE><B>show/connect</B> Show all the active connections</CODE></P>
1825 <P>This command shows information on all the active connections known tothe node. This command gives slightly more information than WHO.</P>
1826 <H2><A NAME="ss10.174">10.174</A> <A HREF="adminmanual_en.html#toc10.174">show/contest <year and month> (0)</A>
1829 <P><CODE><B>show/contest <year and month></B> Show all the contests for a month</CODE></P>
1830 <P>Show all known contests which are maintained at http://www.sk3bg.se/contest/for a particular month or year. The format is reasonably flexible.For example:-
1833 SH/CONTEST sep2003 SH/CONTEST 03 march
1835 </CODE></BLOCKQUOTE>
1837 <H2><A NAME="ss10.175">10.175</A> <A HREF="adminmanual_en.html#toc10.175">show/date [<prefix>|<callsign>] (0)</A>
1840 <P><CODE><B>show/date [<prefix>|<callsign>]</B> Show the local time </CODE></P>
1841 <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>
1842 <H2><A NAME="ss10.176">10.176</A> <A HREF="adminmanual_en.html#toc10.176">show/db0sdx <callsign> (0)</A>
1845 <P><CODE><B>show/db0sdx <callsign></B> Show QSL infomation from DB0SDX database</CODE></P>
1846 <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>
1847 <H2><A NAME="ss10.177">10.177</A> <A HREF="adminmanual_en.html#toc10.177">show/debug (9)</A>
1850 <P><CODE><B>show/debug</B> Show what levels of debug information you are logging</CODE></P>
1852 <H2><A NAME="ss10.178">10.178</A> <A HREF="adminmanual_en.html#toc10.178">show/dx (0)</A>
1855 <P><CODE><B>show/dx</B> Interrogate the spot database</CODE></P>
1856 <P>If you just type SHOW/DX you will get the last so many spots(sysop configurable, but usually 10).In addition you can add any number of these commands in very nearlyany order to the basic SHOW/DX command, they are:-
1859 on <band> - eg 160m 20m 2m 23cm 6mm on <region> - eg hf vhf uhf shf (see SHOW/BANDS) on <from>/<to> - eg 1000/4000 14000-30000 (in Khz) <from>-<to>
1861 </CODE></BLOCKQUOTE>
1864 <number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
1866 </CODE></BLOCKQUOTE>
1869 <prefix> - for a spotted callsign beginning with <prefix> *<suffix> - for a spotted callsign ending in <suffix> *<string>* - for a spotted callsign containing <string>
1871 </CODE></BLOCKQUOTE>
1874 day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
1876 </CODE></BLOCKQUOTE>
1879 info <text> - any spots containing <text> in the info or remarks
1881 </CODE></BLOCKQUOTE>
1884 by <call> - any spots spotted by <call> (spotter <call> is the same).
1886 </CODE></BLOCKQUOTE>
1889 qsl - this automatically looks for any qsl info on the call held in the spot database.
1891 </CODE></BLOCKQUOTE>
1894 iota [<iota>] - If the iota island number is missing it will look for the string iota and anything which looks like an iota island number. If you specify then it will look for that island.
1896 </CODE></BLOCKQUOTE>
1899 qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
1901 </CODE></BLOCKQUOTE>
1904 dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2
1906 </CODE></BLOCKQUOTE>
1909 You can also use this with the 'by' keyword so eg by W dxcc
1911 </CODE></BLOCKQUOTE>
1916 </CODE></BLOCKQUOTE>
1919 SH/DX 9m0 SH/DX on 20m info iota SH/DX 9a on vhf day 30 SH/DX rf1p qsl SH/DX iota SH/DX iota eu-064 SH/DX qra jn86 SH/DX dxcc oq2 SH/DX dxcc oq2 by w dxcc
1921 </CODE></BLOCKQUOTE>
1923 <H2><A NAME="ss10.179">10.179</A> <A HREF="adminmanual_en.html#toc10.179">show/dxcc <prefix> (0)</A>
1926 <P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE></P>
1927 <P>This command takes the <prefix> (which can be a full or partial callsign if desired), looks up which internal country number it isand then displays all the spots as per SH/DX for that country.This is now an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this command. e.g.
1930 SH/DXCC G SH/DXCC W on 20m iota
1932 </CODE></BLOCKQUOTE>
1933 This can be done with the SHOW/DX command like this:-
1936 SH/DX dxcc g SH/DX dxcc w on 20m iota
1938 </CODE></BLOCKQUOTE>
1940 <H2><A NAME="ss10.180">10.180</A> <A HREF="adminmanual_en.html#toc10.180">show/dxqsl <callsign> (0)</A>
1943 <P><CODE><B>show/dxqsl <callsign></B> Show any QSL info gathered from spots</CODE></P>
1944 <P>The node collects information from the comment fields in spots (thingslike 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.This command allows you to interrogate that database and if the callsignis found will display the manager(s) that people have spotted. This information is NOT reliable, but it is normally reasonably accurate ifit is spotted enough times.For example:-
1949 </CODE></BLOCKQUOTE>
1950 You can check the raw input spots yourself with:-
1955 </CODE></BLOCKQUOTE>
1956 This gives you more background information.</P>
1957 <H2><A NAME="ss10.181">10.181</A> <A HREF="adminmanual_en.html#toc10.181">show/dxstats [days] [date] (0)</A>
1960 <P><CODE><B>show/dxstats [days] [date]</B> Show the DX Statistics</CODE></P>
1961 <P>Show the total DX spots for the last <days> no of days (default is 31), starting from a <date> (default: today).</P>
1962 <H2><A NAME="ss10.182">10.182</A> <A HREF="adminmanual_en.html#toc10.182">show/files [<filearea> [<string>]] (0)</A>
1965 <P><CODE><B>show/files [<filearea> [<string>]]</B> List the contents of a filearea</CODE></P>
1966 <P>SHOW/FILES on its own will show you a list of the various fileareasavailable on the system. To see the contents of a particular filearea type:-
1969 SH/FILES <filearea>
1971 </CODE></BLOCKQUOTE>
1972 where <filearea> is the name of the filearea you want to see the contents of.You can also use shell globbing characters like '*' and '?' in astring to see a selection of files in a filearea eg:-
1975 SH/FILES bulletins arld*
1977 </CODE></BLOCKQUOTE>
1978 See also TYPE - to see the contents of a file.</P>
1979 <H2><A NAME="ss10.183">10.183</A> <A HREF="adminmanual_en.html#toc10.183">show/filter (0)</A>
1982 <P><CODE><B>show/filter</B> Show the contents of all the filters you have set</CODE></P>
1983 <P>Show the contents of all the filters that are set. This command displaysall the filters set - for all the various categories.</P>
1984 <H2><A NAME="ss10.184">10.184</A> <A HREF="adminmanual_en.html#toc10.184">show/hfstats [days] [date] (0)</A>
1987 <P><CODE><B>show/hfstats [days] [date]</B> Show the HF DX Statistics </CODE></P>
1988 <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>
1989 <H2><A NAME="ss10.185">10.185</A> <A HREF="adminmanual_en.html#toc10.185">show/hftable [days] [date] [prefix ...] (0)</A>
1992 <P><CODE><B>show/hftable [days] [date] [prefix ...]</B> Show the HF DX Spotter Table</CODE></P>
1993 <P>Show the HF DX Spotter table for the list of prefixes for the last <days> no of days (default is 31), starting from a <date> (default: today).If there are no prefixes then it will show the table for your country.Remember that some countries have more than one "DXCC country" in them(eg G :-), to show them (assuming you are not in G already which isspecially treated in the code) you must list all the relevant prefixes
1996 sh/hftable g gm gd gi gj gw gu
1998 </CODE></BLOCKQUOTE>
1999 Note that the prefixes are converted into country codes so you don't haveto list all possible prefixes for each country.If you want more or less days than the default simply include thenumber you require:-
2004 </CODE></BLOCKQUOTE>
2005 If you want to start at a different day, simply add the date in some recognizable form:-
2008 sh/hftable 2 25nov02 sh/hftable 2 25-nov-02 sh/hftable 2 021125 sh/hftable 2 25/11/02
2010 </CODE></BLOCKQUOTE>
2011 This will show the stats for your DXCC for that CQWW contest weekend. You can specify either prefixes or full callsigns (so you can see how youdid against all your mates). You can also say 'all' which will then printthe worldwide statistics.
2016 </CODE></BLOCKQUOTE>
2018 <H2><A NAME="ss10.186">10.186</A> <A HREF="adminmanual_en.html#toc10.186">show/hops <call> [ann|spots|route|wcy|wwv] (8)</A>
2021 <P><CODE><B>show/hops <call> [ann|spots|route|wcy|wwv]</B> Show the hop counts for a node</CODE></P>
2022 <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>
2023 <H2><A NAME="ss10.187">10.187</A> <A HREF="adminmanual_en.html#toc10.187">show/isolate (1)</A>
2026 <P><CODE><B>show/isolate</B> Show list of ISOLATED nodes</CODE></P>
2028 <H2><A NAME="ss10.188">10.188</A> <A HREF="adminmanual_en.html#toc10.188">show/lockout <prefix>|all (9)</A>
2031 <P><CODE><B>show/lockout <prefix>|all</B> Show the list of locked out or excluded callsigns</CODE></P>
2033 <H2><A NAME="ss10.189">10.189</A> <A HREF="adminmanual_en.html#toc10.189">show/log [<callsign>] (8)</A>
2036 <P><CODE><B>show/log [<callsign>]</B> Show excerpts from the system log</CODE></P>
2037 <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>
2038 <H2><A NAME="ss10.190">10.190</A> <A HREF="adminmanual_en.html#toc10.190">show/moon [ndays] [<prefix>|<callsign>] (0)</A>
2041 <P><CODE><B>show/moon [ndays] [<prefix>|<callsign>]</B> Show Moon rise and set times</CODE></P>
2042 <P>Show the Moon rise and set times for a (list of) prefixes or callsigns, together with the azimuth and elevation of the sun currently at thoselocations.If you don't specify any prefixes or callsigns, it will show the times foryour QTH (assuming you have set it with either SET/LOCATION or SET/QRA),together with the current azimuth and elevation.In addition, it will show the illuminated fraction of the moons disk.If all else fails it will show the Moonrise and set times for the nodethat you are connected to. For example:-
2045 SH/MOON SH/MOON G1TLH W5UN
2047 </CODE></BLOCKQUOTE>
2048 You can also use this command to see into the past or the future, soif you want to see yesterday's times then do:-
2053 </CODE></BLOCKQUOTE>
2054 or in three days time:-
2059 </CODE></BLOCKQUOTE>
2060 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>
2061 <H2><A NAME="ss10.191">10.191</A> <A HREF="adminmanual_en.html#toc10.191">show/muf <prefix> [<hours>][long] (0)</A>
2064 <P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show the likely propagation to a prefix</CODE></P>
2065 <P>This command allow you to estimate the likelihood of you contactinga station with the prefix you have specified. The output assumes a modestpower of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)The result predicts the most likely operating frequencies and signallevels for high frequency (shortwave) radio propagation paths onspecified days of the year and hours of the day. It is most useful forpaths between 250 km and 6000 km, but can be used with reduced accuracyfor paths shorter or longer than this.The command uses a routine MINIMUF 3.5 developed by the U.S. Navy andused to predict the MUF given the predicted flux, day of the year,hour of the day and geographic coordinates of the transmitter andreceiver. This routine is reasonably accurate for the purposes here,with a claimed RMS error of 3.8 MHz, but much smaller and less complexthan the programs used by major shortwave broadcasting organizations,such as the Voice of America.The command will display some header information detailing itsassumptions, together with the locations, latitude and longitudes andbearings. It will then show UTC (UT), local time at the other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path(Zen) and the likely signal strengths. Then for each frequency for whichthe system thinks there is a likelihood of a circuit it prints a value.The value is currently a likely S meter reading based on the conventional6dB / S point scale. If the value has a '+' appended it means that it is1/2 an S point stronger. If the value is preceeded by an 'm' it means thatthere is likely to be much fading and by an 's' that the signal is likelyto be noisy. By default SHOW/MUF will show the next two hours worth of data. Youcan specify anything up to 24 hours worth of data by appending the no ofhours required after the prefix. For example:-
2070 </CODE></BLOCKQUOTE>
2074 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms Location Lat / Long Azim East Dereham, Norfolk 52 41 N 0 57 E 47 United-States-W 43 0 N 87 54 W 299 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0 18 23 11.5 -35 mS0+ mS2 S3 19 0 11.2 -41 mS0+ mS2 S3
2076 </CODE></BLOCKQUOTE>
2077 indicating that you will have weak, fading circuits on top band and 80m but usable signals on 40m (about S3).inputing:-
2082 </CODE></BLOCKQUOTE>
2083 will get you the above display, but with the next 24 hours worth ofpropagation data.
2086 SH/MUF W L 24 SH/MUF W 24 Long
2088 </CODE></BLOCKQUOTE>
2089 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>
2090 <H2><A NAME="ss10.192">10.192</A> <A HREF="adminmanual_en.html#toc10.192">show/newconfiguration [<node>] (0)</A>
2093 <P><CODE><B>show/newconfiguration [<node>]</B> Show all the nodes and users visible</CODE></P>
2094 <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>
2095 <H2><A NAME="ss10.193">10.193</A> <A HREF="adminmanual_en.html#toc10.193">show/newconfiguration/node (0)</A>
2098 <P><CODE><B>show/newconfiguration/node</B> Show all the nodes connected locally</CODE></P>
2099 <P>Show all the nodes connected to this node in the new format.</P>
2100 <H2><A NAME="ss10.194">10.194</A> <A HREF="adminmanual_en.html#toc10.194">show/node [<callsign> ...] (1)</A>
2103 <P><CODE><B>show/node [<callsign> ...]</B> Show the type and version number of nodes</CODE></P>
2104 <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>
2105 <H2><A NAME="ss10.195">10.195</A> <A HREF="adminmanual_en.html#toc10.195">show/prefix <callsign> (0)</A>
2108 <P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database </CODE></P>
2109 <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>
2110 <H2><A NAME="ss10.196">10.196</A> <A HREF="adminmanual_en.html#toc10.196">show/program (5)</A>
2113 <P><CODE><B>show/program</B> Show the locations of all the included program modules</CODE></P>
2114 <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>
2115 <H2><A NAME="ss10.197">10.197</A> <A HREF="adminmanual_en.html#toc10.197">show/qra <lat> <long> (0)</A>
2118 <P><CODE><B>show/qra <lat> <long></B> Convert lat/long to a QRA Grid locator</CODE></P>
2119 <P>This is a multipurpose command that allows you either to calculate thedistance and bearing between two locators or (if only one locator isgiven on the command line) the distance and beraing from your stationto the locator. For example:-
2122 SH/QRA IO92QL SH/QRA JN06 IN73
2124 </CODE></BLOCKQUOTE>
2125 The first example will show the distance and bearing to the locator fromyourself, the second example will calculate the distance and bearing fromthe first locator to the second. You can use 4 or 6 character locators.It is also possible to convert a latitude and longitude to a locator by using this command with a latitude and longitude as an argument, forexample:-
2128 SH/QRA 52 41 N 0 58 E
2130 </CODE></BLOCKQUOTE>
2132 <H2><A NAME="ss10.198">10.198</A> <A HREF="adminmanual_en.html#toc10.198">show/qra <locator> [<locator>] (0)</A>
2135 <P><CODE><B>show/qra <locator> [<locator>]</B> Show distance between QRA Grid locators</CODE></P>
2137 <H2><A NAME="ss10.199">10.199</A> <A HREF="adminmanual_en.html#toc10.199">show/qrz <callsign> (0)</A>
2140 <P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE></P>
2141 <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>
2142 <H2><A NAME="ss10.200">10.200</A> <A HREF="adminmanual_en.html#toc10.200">show/registered [<prefix>] (9)</A>
2145 <P><CODE><B>show/registered [<prefix>]</B> Show the registered users</CODE></P>
2147 <H2><A NAME="ss10.201">10.201</A> <A HREF="adminmanual_en.html#toc10.201">show/route <callsign> ... (0)</A>
2150 <P><CODE><B>show/route <callsign> ...</B> Show the route to the callsign</CODE></P>
2151 <P>This command allows you to see to which node the callsigns specified areconnected. It is a sort of inverse sh/config.
2156 </CODE></BLOCKQUOTE>
2158 <H2><A NAME="ss10.202">10.202</A> <A HREF="adminmanual_en.html#toc10.202">show/satellite <name> [<hours> <interval>] (0)</A>
2161 <P><CODE><B>show/satellite <name> [<hours> <interval>]</B> Show tracking data</CODE></P>
2162 <P>Show the tracking data from your location to the satellite of your choicefrom now on for the next few hours.If you use this command without a satellite name it will display a listof all the satellites known currently to the system. If you give a name then you can obtain tracking data of all the passesthat start and finish 5 degrees below the horizon. As default it willgive information for the next three hours for every five minute period.You can alter the number of hours and the step size, within certain limits. Each pass in a period is separated with a row of '-----' charactersSo for example:-
2165 SH/SAT AO-10 SH/SAT FENGYUN1 12 2
2167 </CODE></BLOCKQUOTE>
2169 <H2><A NAME="ss10.203">10.203</A> <A HREF="adminmanual_en.html#toc10.203">show/station all [<regex>] (6)</A>
2172 <P><CODE><B>show/station all [<regex>]</B> Show list of users in the system</CODE></P>
2174 <H2><A NAME="ss10.204">10.204</A> <A HREF="adminmanual_en.html#toc10.204">show/station [<callsign> ..] (0)</A>
2177 <P><CODE><B>show/station [<callsign> ..]</B> Show information about a callsign</CODE></P>
2178 <P>Show the information known about a callsign and whether (and where)that callsign is connected to the cluster.
2183 </CODE></BLOCKQUOTE>
2184 If no callsign is given then show the information for yourself.</P>
2185 <H2><A NAME="ss10.205">10.205</A> <A HREF="adminmanual_en.html#toc10.205">show/sun [ndays] [<prefix>|<callsign>] (0)</A>
2188 <P><CODE><B>show/sun [ndays] [<prefix>|<callsign>]</B> Show sun rise and set times</CODE></P>
2189 <P>Show the sun rise and set times for a (list of) prefixes or callsigns, together with the azimuth and elevation of the sun currently at thoselocations.If you don't specify any prefixes or callsigns, it will show the times foryour QTH (assuming you have set it with either SET/LOCATION or SET/QRA),together with the current azimuth and elevation.If all else fails it will show the sunrise and set times for the nodethat you are connected to. For example:-
2192 SH/SUN SH/SUN G1TLH K9CW ZS
2194 </CODE></BLOCKQUOTE>
2195 You can also use this command to see into the past or the future, soif you want to see yesterday's times then do:-
2200 </CODE></BLOCKQUOTE>
2201 or in three days time:-
2206 </CODE></BLOCKQUOTE>
2207 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>
2208 <H2><A NAME="ss10.206">10.206</A> <A HREF="adminmanual_en.html#toc10.206">show/time [<prefix>|<callsign>] (0)</A>
2211 <P><CODE><B>show/time [<prefix>|<callsign>]</B> Show the local time </CODE></P>
2212 <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>
2213 <H2><A NAME="ss10.207">10.207</A> <A HREF="adminmanual_en.html#toc10.207">show/usdb [call ..] (0)</A>
2216 <P><CODE><B>show/usdb [call ..]</B> Show information held on the FCC Call database</CODE></P>
2217 <P>Show the City and State of a Callsign held on the FCC database ifhis is being run on this system, eg:-
2222 </CODE></BLOCKQUOTE>
2224 <H2><A NAME="ss10.208">10.208</A> <A HREF="adminmanual_en.html#toc10.208">show/vhfstats [days] [date] (0)</A>
2227 <P><CODE><B>show/vhfstats [days] [date]</B> Show the VHF DX Statistics</CODE></P>
2228 <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>
2229 <H2><A NAME="ss10.209">10.209</A> <A HREF="adminmanual_en.html#toc10.209">show/vhftable [days] [date] [prefix ...] (0)</A>
2232 <P><CODE><B>show/vhftable [days] [date] [prefix ...]</B> Show the VHF DX Spotter Table</CODE></P>
2233 <P>Show the VHF DX Spotter table for the list of prefixes for the last <days> no of days (default is 31), starting from a date (default: today).If there are no prefixes then it will show the table for your country.Remember that some countries have more than one "DXCC country" in them(eg G :-), to show them (assuming you are not in G already which isspecially treated in the code) you must list all the relevant prefixes
2236 sh/vhftable g gm gd gi gj gw gu
2238 </CODE></BLOCKQUOTE>
2239 Note that the prefixes are converted into country codes so you don't haveto list all possible prefixes for each country.If you want more or less days than the default simply include thenumber you require:-
2244 </CODE></BLOCKQUOTE>
2245 If you want to start at a different day, simply add the date in some recognizable form:-
2248 sh/vhftable 2 25nov02 sh/vhftable 2 25-nov-02 sh/vhftable 2 021125 sh/vhftable 2 25/11/02
2250 </CODE></BLOCKQUOTE>
2251 This will show the stats for your DXCC for that CQWW contest weekend. You can specify either prefixes or full callsigns (so you can see how youdid against all your mates). You can also say 'all' which will then printthe worldwide statistics.
2256 </CODE></BLOCKQUOTE>
2258 <H2><A NAME="ss10.210">10.210</A> <A HREF="adminmanual_en.html#toc10.210">show/wcy (0)</A>
2261 <P><CODE><B>show/wcy</B> Show last 10 WCY broadcasts</CODE></P>
2263 <H2><A NAME="ss10.211">10.211</A> <A HREF="adminmanual_en.html#toc10.211">show/wcy <n> (0)</A>
2266 <P><CODE><B>show/wcy <n></B> Show last <n> WCY broadcasts</CODE></P>
2267 <P>Display the most recent WCY information that has been received by the system</P>
2268 <H2><A NAME="ss10.212">10.212</A> <A HREF="adminmanual_en.html#toc10.212">show/wm7d <callsign> (0)</A>
2271 <P><CODE><B>show/wm7d <callsign></B> Show callbook details on a US callsigns</CODE></P>
2272 <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>
2273 <H2><A NAME="ss10.213">10.213</A> <A HREF="adminmanual_en.html#toc10.213">show/wwv (0)</A>
2276 <P><CODE><B>show/wwv</B> Show last 10 WWV broadcasts</CODE></P>
2278 <H2><A NAME="ss10.214">10.214</A> <A HREF="adminmanual_en.html#toc10.214">show/wwv <n> (0)</A>
2281 <P><CODE><B>show/wwv <n></B> Show last <n> WWV broadcasts</CODE></P>
2282 <P>Display the most recent WWV information that has been received by the system</P>
2283 <H2><A NAME="ss10.215">10.215</A> <A HREF="adminmanual_en.html#toc10.215">shutdown (5)</A>
2286 <P><CODE><B>shutdown</B> Shutdown the cluster</CODE></P>
2287 <P>Shutdown the cluster and disconnect all the users </P>
2288 <H2><A NAME="ss10.216">10.216</A> <A HREF="adminmanual_en.html#toc10.216">spoof <call> <command> (9)</A>
2291 <P><CODE><B>spoof <call> <command></B> Do a command as though you are another user</CODE></P>
2292 <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:-
2295 SPOOF G1TLH set/name Dirk SPOOF G1TLH set/qra JO02LQ
2297 </CODE></BLOCKQUOTE>
2299 <H2><A NAME="ss10.217">10.217</A> <A HREF="adminmanual_en.html#toc10.217">stat/channel [<callsign>] (5)</A>
2302 <P><CODE><B>stat/channel [<callsign>]</B> Show the status of a channel on the cluster</CODE></P>
2303 <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>
2304 <H2><A NAME="ss10.218">10.218</A> <A HREF="adminmanual_en.html#toc10.218">stat/db <dbname> (5)</A>
2307 <P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE></P>
2308 <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>
2309 <H2><A NAME="ss10.219">10.219</A> <A HREF="adminmanual_en.html#toc10.219">stat/msg (1)</A>
2312 <P><CODE><B>stat/msg</B> Show the status of the message system</CODE></P>
2314 <H2><A NAME="ss10.220">10.220</A> <A HREF="adminmanual_en.html#toc10.220">stat/msg <msgno> (1)</A>
2317 <P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE></P>
2318 <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>
2319 <H2><A NAME="ss10.221">10.221</A> <A HREF="adminmanual_en.html#toc10.221">stat/route_node <callsign> (5)</A>
2322 <P><CODE><B>stat/route_node <callsign></B> Show the data in a Route::Node object</CODE></P>
2324 <H2><A NAME="ss10.222">10.222</A> <A HREF="adminmanual_en.html#toc10.222">stat/route_node all (5)</A>
2327 <P><CODE><B>stat/route_node all</B> Show list of all Route::Node objects</CODE></P>
2329 <H2><A NAME="ss10.223">10.223</A> <A HREF="adminmanual_en.html#toc10.223">stat/route_user <callsign> (5)</A>
2332 <P><CODE><B>stat/route_user <callsign></B> Show the data in a Route::User object</CODE></P>
2334 <H2><A NAME="ss10.224">10.224</A> <A HREF="adminmanual_en.html#toc10.224">stat/route_user all (5)</A>
2337 <P><CODE><B>stat/route_user all</B> Show list of all Route::User objects</CODE></P>
2339 <H2><A NAME="ss10.225">10.225</A> <A HREF="adminmanual_en.html#toc10.225">stat/user [<callsign>] (5)</A>
2342 <P><CODE><B>stat/user [<callsign>]</B> Show the full status of a user</CODE></P>
2343 <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>
2344 <H2><A NAME="ss10.226">10.226</A> <A HREF="adminmanual_en.html#toc10.226">sysop (0)</A>
2347 <P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE></P>
2348 <P>The system automatically reduces your privilege level to that of anormal user if you login in remotely. This command allows you toregain your normal privilege level. It uses the normal system: fivenumbers are returned that are indexes into the character array that isyour assigned password (see SET/PASSWORD). The indexes start fromzero.You are expected to return a string which contains the charactersrequired in the correct order. You may intersperse those characterswith others to obscure your reply for any watchers. For example (andthese values are for explanation :-):
2351 password = 012345678901234567890123456789 > sysop 22 10 15 17 3
2353 </CODE></BLOCKQUOTE>
2357 aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
2359 </CODE></BLOCKQUOTE>
2360 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>
2361 <H2><A NAME="ss10.227">10.227</A> <A HREF="adminmanual_en.html#toc10.227">talk <call> > <node> [<text>] (0)</A>
2364 <P><CODE><B>talk <call> > <node> [<text>]</B> Send a text message to another station via a node</CODE></P>
2365 <P>Send a short message to any other station that is visible on the clustersystem. You can send it to anyone you can see with a SHOW/CONFIGURATION command, they don't have to be connected locally.The second form of TALK is used when other cluster nodes are connectedwith restricted information. This usually means that they don't send the user information usually associated with logging on and off the cluster.If you know that G3JNB is likely to be present on GB7TLH, but you can onlysee GB7TLH in the SH/C list but with no users, then you would use thesecond form of the talk message.If you want to have a ragchew with someone you can leave the text messageout and the system will go into 'Talk' mode. What this means is that ashort message is sent to the recipient telling them that you are in a'Talking' frame of mind and then you just type - everything you send willgo to the station that you asked for. All the usual announcements, spots and so on will still come out on yourterminal.If you want to do something (such as send a spot) you preceed the normal command with a '/' character, eg:-
2368 /DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
2370 </CODE></BLOCKQUOTE>
2371 To leave talk mode type:
2376 </CODE></BLOCKQUOTE>
2377 If you are in 'Talk' mode, there is an extention to the '/' command whichallows you to send the output to all the people you are talking to. You do with the '//' command. For example:-
2382 </CODE></BLOCKQUOTE>
2383 will send the hftable as you have it to all the people you are currently talking to.</P>
2384 <H2><A NAME="ss10.228">10.228</A> <A HREF="adminmanual_en.html#toc10.228">talk <call> [<text>] (0)</A>
2387 <P><CODE><B>talk <call> [<text>]</B> Send a text message to another station</CODE></P>
2389 <H2><A NAME="ss10.229">10.229</A> <A HREF="adminmanual_en.html#toc10.229">type <filearea>/<name> (0)</A>
2392 <P><CODE><B>type <filearea>/<name></B> Look at the contents of a file in one of the fileareas</CODE></P>
2393 <P>Type out the contents of a file in a filearea. So, for example, in filearea 'bulletins' you want to look at file 'arld051' you would enter:-
2396 TYPE bulletins/arld051
2398 </CODE></BLOCKQUOTE>
2399 See also SHOW/FILES to see what fileareas are available and a list of content.</P>
2400 <H2><A NAME="ss10.230">10.230</A> <A HREF="adminmanual_en.html#toc10.230">uncatchup <node call> all|[msgno> ...] (5)</A>
2403 <P><CODE><B>uncatchup <node call> all|[msgno> ...]</B> Unmark a message as sent</CODE></P>
2404 <P>When you send messages the fact that you have forwarded it to another node is remembered so that it isn't sent again. When you have a new partnernode and you add their callsign to your /spider/msg/forward.pl file, alloutstanding non-private messages will be forwarded to them. This may wellbe ALL the non-private messages. You can prevent this by using these commmands:-
2407 catchup GB7DJK all catchup GB7DJK 300 301 302 303 500-510
2409 </CODE></BLOCKQUOTE>
2410 and to undo what you have just done:-
2413 uncatchup GB7DJK all uncatchup GB7DJK 300 301 302 303 500-510
2415 </CODE></BLOCKQUOTE>
2416 which will arrange for them to be forward candidates again.Order is not important.</P>
2417 <H2><A NAME="ss10.231">10.231</A> <A HREF="adminmanual_en.html#toc10.231">unset/announce (0)</A>
2420 <P><CODE><B>unset/announce</B> Stop announce messages coming out on your terminal</CODE></P>
2422 <H2><A NAME="ss10.232">10.232</A> <A HREF="adminmanual_en.html#toc10.232">unset/anntalk (0)</A>
2425 <P><CODE><B>unset/anntalk</B> Stop talk like announce messages on your terminal</CODE></P>
2426 <P>The announce system on legacy cluster nodes is used as a talk substitute because the network is so poorly connected. If you:
2431 </CODE></BLOCKQUOTE>
2432 you will suppress several of these announces, you may miss the odd useful one as well, but you would probably miss them anyway in thewelter of useless ones.
2437 </CODE></BLOCKQUOTE>
2438 allows you to see them again. This is the default.</P>
2439 <H2><A NAME="ss10.233">10.233</A> <A HREF="adminmanual_en.html#toc10.233">unset/baddx <call>.. (8)</A>
2442 <P><CODE><B>unset/baddx <call>..</B> Propagate a dx spot with this callsign again</CODE></P>
2443 <P>Setting a word as 'baddx' will prevent spots with that word in the'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going anyfurther. They will not be displayed and they will not be sent ontoother nodes.The word must be written in full, no wild cards are allowed eg:-
2446 set/baddx FORSALE VIDEO FR0G
2448 </CODE></BLOCKQUOTE>
2449 To allow a word again, use the following command ...
2454 </CODE></BLOCKQUOTE>
2456 <H2><A NAME="ss10.234">10.234</A> <A HREF="adminmanual_en.html#toc10.234">unset/badnode <call>.. (8)</A>
2459 <P><CODE><B>unset/badnode <call>..</B> Allow spots from this node again</CODE></P>
2460 <P>Setting a callsign as a 'badnode' will prevent spots from that node going any further. They will not be displayed and they will not be sent onto other nodes.The call must be a full eg:-
2465 </CODE></BLOCKQUOTE>
2466 will stop anything from K1TTT. If you want SSIDs as well then you mustenter them specifically.
2471 </CODE></BLOCKQUOTE>
2472 will allow spots from him again.Use with extreme care. This command may well be superceeded by FILTERing.</P>
2473 <H2><A NAME="ss10.235">10.235</A> <A HREF="adminmanual_en.html#toc10.235">unset/badspotter <call>.. (8)</A>
2476 <P><CODE><B>unset/badspotter <call>..</B> Allow spots from this callsign again</CODE></P>
2477 <P>Setting a callsign as a 'badspotter' will prevent spots from this callsign going any further. They will not be displayed and they will not be sent onto other nodes.The call must be written in full, no wild cards are allowed eg:-
2480 set/badspotter VE2STN
2482 </CODE></BLOCKQUOTE>
2483 will stop anything from VE2STN. This command will automaticallystop spots from this user, regardless of whether or which SSID he uses. DO NOT USE SSIDs in the callsign, just use the callsignas above or below.
2486 unset/badspotter VE2STN
2488 </CODE></BLOCKQUOTE>
2489 will allow spots from him again.Use with extreme care. This command may well be superceded by FILTERing.</P>
2490 <H2><A NAME="ss10.236">10.236</A> <A HREF="adminmanual_en.html#toc10.236">unset/badword <word>.. (8)</A>
2493 <P><CODE><B>unset/badword <word>..</B> Propagate things with this word again</CODE></P>
2494 <P>Setting a word as a 'badword' will prevent things like spots,announces or talks with this word in the the text part from going anyfurther. They will not be displayed and they will not be sent ontoother nodes.The word must be written in full, no wild cards are allowed eg:-
2497 set/badword annihilate annihilated annihilation
2499 </CODE></BLOCKQUOTE>
2500 will stop anything with these words in the text.
2503 unset/badword annihilated
2505 </CODE></BLOCKQUOTE>
2506 will allow text with this word again.</P>
2507 <H2><A NAME="ss10.237">10.237</A> <A HREF="adminmanual_en.html#toc10.237">unset/beep (0)</A>
2510 <P><CODE><B>unset/beep</B> Stop beeps for DX and other messages on your terminal</CODE></P>
2512 <H2><A NAME="ss10.238">10.238</A> <A HREF="adminmanual_en.html#toc10.238">unset/debug <name> (9)</A>
2515 <P><CODE><B>unset/debug <name></B> Remove a debug level from the debug set</CODE></P>
2516 <P>You can choose to log several different levels. The levels are
2519 chan state msg cron connect
2521 </CODE></BLOCKQUOTE>
2522 You can show what levels you are logging with SHOW/DEBUG</P>
2523 <H2><A NAME="ss10.239">10.239</A> <A HREF="adminmanual_en.html#toc10.239">unset/dx (0)</A>
2526 <P><CODE><B>unset/dx</B> Stop DX messages coming out on your terminal</CODE></P>
2528 <H2><A NAME="ss10.240">10.240</A> <A HREF="adminmanual_en.html#toc10.240">unset/dxcq (0)</A>
2531 <P><CODE><B>unset/dxcq</B> Stop CQ Zones on the end of DX announcements</CODE></P>
2532 <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>
2533 <H2><A NAME="ss10.241">10.241</A> <A HREF="adminmanual_en.html#toc10.241">unset/dxgrid (0)</A>
2536 <P><CODE><B>unset/dxgrid</B> Stop QRA Grid Squares on the end of DX announcements</CODE></P>
2537 <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>
2538 <H2><A NAME="ss10.242">10.242</A> <A HREF="adminmanual_en.html#toc10.242">unset/dxitu (0)</A>
2541 <P><CODE><B>unset/dxitu</B> Stop ITU Zones on the end of DX announcements</CODE></P>
2542 <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>
2543 <H2><A NAME="ss10.243">10.243</A> <A HREF="adminmanual_en.html#toc10.243">unset/echo (0)</A>
2546 <P><CODE><B>unset/echo</B> Stop the cluster echoing your input</CODE></P>
2547 <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>
2548 <H2><A NAME="ss10.244">10.244</A> <A HREF="adminmanual_en.html#toc10.244">unset/email (0)</A>
2551 <P><CODE><B>unset/email</B> Stop personal msgs being forwarded by email</CODE></P>
2552 <P>If any personal messages come in for your callsign then you can usethese commands to control whether they are forwarded onto your emailaddress. To enable the forwarding do something like:-
2555 SET/EMAIL mike.tubby@somewhere.com
2557 </CODE></BLOCKQUOTE>
2558 You can have more than one email address (each one separated by a space).Emails are forwarded to all the email addresses you specify.You can disable forwarding by:-
2563 </CODE></BLOCKQUOTE>
2565 <H2><A NAME="ss10.245">10.245</A> <A HREF="adminmanual_en.html#toc10.245">unset/here (0)</A>
2568 <P><CODE><B>unset/here</B> Tell the system you are absent from your terminal</CODE></P>
2570 <H2><A NAME="ss10.246">10.246</A> <A HREF="adminmanual_en.html#toc10.246">unset/hops <call> ann|spots|route|wwv|wcy (8)</A>
2573 <P><CODE><B>unset/hops <call> ann|spots|route|wwv|wcy</B> Unset hop count </CODE></P>
2574 <P>Set the hop count for a particular type of broadcast for a node.This command allows you to set up special hop counts for a node for currently: announce, spots, wwv and wcy broadcasts.eg:
2577 set/hops gb7djk ann 10 set/hops gb7mbc spots 20
2579 </CODE></BLOCKQUOTE>
2580 Set SHOW/HOPS for information on what is already set. This commandcreates a filter and works in conjunction with the filter system. You can unset the hops with command UNSET/HOPS. For example:-
2583 unset/hops gb7djk ann unset/hops gb7mbc spots
2585 </CODE></BLOCKQUOTE>
2587 <H2><A NAME="ss10.247">10.247</A> <A HREF="adminmanual_en.html#toc10.247">unset/isolate (9)</A>
2590 <P><CODE><B>unset/isolate</B> Stop Isolation of a node from the rest of the network</CODE></P>
2591 <P>Remove isolation from a node - SET/ISOLATE</P>
2592 <H2><A NAME="ss10.248">10.248</A> <A HREF="adminmanual_en.html#toc10.248">unset/lockout <call> (9)</A>
2595 <P><CODE><B>unset/lockout <call></B> Allow a callsign to connect to the cluster</CODE></P>
2597 <H2><A NAME="ss10.249">10.249</A> <A HREF="adminmanual_en.html#toc10.249">unset/logininfo (0)</A>
2600 <P><CODE><B>unset/logininfo</B> Inform when a station logs out locally</CODE></P>
2602 <H2><A NAME="ss10.250">10.250</A> <A HREF="adminmanual_en.html#toc10.250">unset/password <call> ... (9)</A>
2605 <P><CODE><B>unset/password <call> ...</B> Delete (remove) a user's password</CODE></P>
2606 <P>This command allows the sysop to completely delete and remove a password for a user. </P>
2607 <H2><A NAME="ss10.251">10.251</A> <A HREF="adminmanual_en.html#toc10.251">unset/privilege (0)</A>
2610 <P><CODE><B>unset/privilege</B> Remove any privilege for this session</CODE></P>
2611 <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>
2612 <H2><A NAME="ss10.252">10.252</A> <A HREF="adminmanual_en.html#toc10.252">unset/prompt (0)</A>
2615 <P><CODE><B>unset/prompt</B> Set your prompt back to default</CODE></P>
2616 <P>This command will set your user prompt to exactly the string that you say. The point of this command to enable a user to interface to programsthat are looking for a specific prompt (or else you just want a differentfixed prompt).
2621 </CODE></BLOCKQUOTE>
2622 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back tonormal.</P>
2623 <H2><A NAME="ss10.253">10.253</A> <A HREF="adminmanual_en.html#toc10.253">unset/register <call> ... (9)</A>
2626 <P><CODE><B>unset/register <call> ...</B> Mark a user as not registered</CODE></P>
2627 <P>Registration is a concept that you can switch on by executing the
2630 set/var $main::regreq = 1
2632 </CODE></BLOCKQUOTE>
2633 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>
2634 <H2><A NAME="ss10.254">10.254</A> <A HREF="adminmanual_en.html#toc10.254">unset/talk (0)</A>
2637 <P><CODE><B>unset/talk</B> Stop TALK messages coming out on your terminal</CODE></P>
2639 <H2><A NAME="ss10.255">10.255</A> <A HREF="adminmanual_en.html#toc10.255">unset/usstate (0)</A>
2642 <P><CODE><B>unset/usstate</B> Stop US State info on the end of DX announcements</CODE></P>
2643 <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>
2644 <H2><A NAME="ss10.256">10.256</A> <A HREF="adminmanual_en.html#toc10.256">unset/wcy (0)</A>
2647 <P><CODE><B>unset/wcy</B> Stop WCY messages coming out on your terminal</CODE></P>
2649 <H2><A NAME="ss10.257">10.257</A> <A HREF="adminmanual_en.html#toc10.257">unset/wwv (0)</A>
2652 <P><CODE><B>unset/wwv</B> Stop WWV messages coming out on your terminal</CODE></P>
2654 <H2><A NAME="ss10.258">10.258</A> <A HREF="adminmanual_en.html#toc10.258">unset/wx (0)</A>
2657 <P><CODE><B>unset/wx</B> Stop WX messages coming out on your terminal</CODE></P>
2659 <H2><A NAME="ss10.259">10.259</A> <A HREF="adminmanual_en.html#toc10.259">who (0)</A>
2662 <P><CODE><B>who</B> Show who is physically connected</CODE></P>
2663 <P>This is a quick listing that shows which callsigns are connected andwhat sort of connection they have</P>
2664 <H2><A NAME="ss10.260">10.260</A> <A HREF="adminmanual_en.html#toc10.260">wx <text> (0)</A>
2667 <P><CODE><B>wx <text></B> Send a weather message to local users</CODE></P>
2669 <H2><A NAME="ss10.261">10.261</A> <A HREF="adminmanual_en.html#toc10.261">wx full <text> (0)</A>
2672 <P><CODE><B>wx full <text></B> Send a weather message to all cluster users</CODE></P>
2674 <H2><A NAME="ss10.262">10.262</A> <A HREF="adminmanual_en.html#toc10.262">wx sysop <text> (5)</A>
2677 <P><CODE><B>wx sysop <text></B> Send a weather message to other clusters only</CODE></P>
2678 <P>Weather messages can sometimes be useful if you are experiencing an extremethat may indicate enhanced conditions</P>
2681 <A HREF="adminmanual_en-9.html">Previous</A>
2682 <A HREF="adminmanual_en.html#toc10">Contents</A>
projects / spider.git / blob