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: The DXSpider command set</TITLE>
6 <LINK HREF="adminmanual-10.html" REL=previous>
7 <LINK HREF="adminmanual.html#toc11" REL=contents>
8 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="adminmanual-10.html">Previous</A>
13 <A HREF="adminmanual.html#toc11">Contents</A>
15 <H2><A NAME="s11">11.</A> <A HREF="adminmanual.html#toc11">The DXSpider command set</A></H2>
17 <P>Below is a complete list of commands available from the cluster prompt.
18 Most maintenance tasks are automatic but there are some commands that are useful
19 for a sysop. These are listed below in alphabetical order. The number in
20 brackets following the command name is the permissions level needed to use
23 <H2><A NAME="ss11.1">11.1</A> <A HREF="adminmanual.html#toc11.1">accept/announce (0)</A>
26 <P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter
27 line for announce</CODE></P>
29 <P>Create an 'accept this announce' line for a filter.</P>
30 <P>An accept filter line means that if the announce matches this filter it is
31 passed onto the user. See HELP FILTERS for more info. Please read this
32 to understand how filters work - it will save a lot of grief later on.</P>
33 <P>You can use any of the following things in this line:-</P>
37 info <string> eg: iota or qsl
38 by <prefixes> eg: G,M,2
40 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
41 origin_itu <numbers>
42 origin_zone <numbers>
47 wx 1 filter WX announces
48 dest <prefixes> eg: 6MUK,WDX (distros)
52 <P>some examples:-</P>
57 acc/ann 2 by_zone 14,15,16
58 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
70 <P>This filter would only allow announces that were posted buy UK stations.
71 You can use the tag 'all' to accept everything eg:</P>
79 <P>but this probably for advanced users...</P>
81 <H2><A NAME="ss11.2">11.2</A> <A HREF="adminmanual.html#toc11.2">accept/announce (extended for sysops) (8)</A>
84 <P><CODE><B>accept/announce <call> [input] [0-9]<pattern></B> Announce filter sysop version</CODE></P>
86 <P>This version allows a sysop to set a filter for a callsign as well as the
87 default for nodes and users eg:-</P>
92 accept/ann input node_default by G,M,2
93 accept/ann user_default by G,M,2
98 <H2><A NAME="ss11.3">11.3</A> <A HREF="adminmanual.html#toc11.3">accept/route (8)</A>
101 <P><CODE><B>accept/route <call> [0-9] <pattern></B> Set an 'accept' filter line for routing</CODE></P>
103 <P>Create an 'accept this routing PC Protocol' line for a filter. </P>
105 <P>An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
106 it is passed thru that interface. See HELP FILTERING for more info. Please read this
107 to understand how filters work - it will save a lot of grief later on.</P>
109 <P>You can use any of the following things in this line:-</P>
113 call <prefixes> the callsign of the thingy
114 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
115 call_itu <numbers>
116 call_zone <numbers>
117 origin <prefixes> really the interface it came in on
118 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
119 origin_itu <numbers>
120 origin_zone <numbers>
125 <P>some examples:-</P>
129 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
130 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
135 <P>You can use the tag 'all' to accept everything eg:</P>
144 <H2><A NAME="ss11.4">11.4</A> <A HREF="adminmanual.html#toc11.4">accept/spots (0)</A>
147 <P><CODE><B>accept/spots [0-9] <pattern></B> Set an accept filter line for spots</CODE></P>
149 <P>Create an 'accept this spot' line for a filter.</P>
151 <P>An accept filter line means that if the spot matches this filter it is
152 passed onto the user. See HELP FILTERS for more info. Please read this
153 to understand how filters work - it will save a lot of grief later on.</P>
154 <P>Please read the following section carefully. Though it looks similar,
155 reformatting, corrections, and hopefully clarifications have been added.</P>
156 <P>You can use any of the following things in this line:-</P>
160 Filters for the station being spotted:
161 call <letters of the prefix, but NOT country inclusive>
162 call G --> G1AAA, GJ2BBB, GU3CCC, etc will be spotted
163 call K --> K1XX, K1XXX will be spotted
164 W1XX, W1XXX will NOT be spotted
165 call PA --> PA3EZL will be spotted
166 PB2FG will NOT be spotted
168 call_dxcc <numbers or prefixes>
169 call_dxcc G --> G1AAA will be spotted
170 GU1AAA will NOT be spotted (different country)
171 call_dxcc K --> K1XX, W1XX will be spotted (same country)
172 call_dxcc 139 --> PA3EZL and PB2FG will be spotted
174 call_itu <numbers>
175 call_zone <numbers>
177 Filters for the callsign of the station doing the spotting:
178 by <letters of the prefix, but NOT country inclusive>
179 by G --> spots from G1AAA, GJ2BBB, GU3CCC, etc will be spotted
180 by K --> spots from K1XX, K1XXX will be spotted
181 spots from W1XX, W1XXX will NOT be spotted
183 by_dxcc <numbers or prefixes>
184 by_dxcc G --> spots from G1AAA will be spotted
185 spots from GU1AAA will NOT be spotted (different
187 by_dxcc K --> spots from K1XX, W1XX will be spotted (same country)
188 by_dxcc 139 --> spots from PA3EZL or PB2FG will be spotted
193 Filters for the callsign of the "node" doing the spotting:
194 origin <letters of the prefix, but NOT country inclusive>
195 origin K --> spots from a node starting with K will be spotted
196 spots from a node starting with KK will NOT be spotted
197 spots from a node starting with W will NOT be spotted
199 Filters for the callsign of the connected node or user (channel) doing the spotting:
200 channel <prefixes>
201 channel W1HR --> spots from the connected node W1HR will be spotted
202 channel K1QX --> spots from the connected user K1QX will be spotted
204 info <string> eg: iota or qsl
205 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
206 on <range> same as 'freq'
211 <P>For frequencies, you can use any of the band names defined in
212 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
213 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
214 this is more efficient than saying simply: freq HF (but don't get
215 too hung up about that)</P>
216 <P>some examples:-</P>
221 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
225 <P>You can use the tag 'all' to accept everything, eg:</P>
233 <P>but this probably for advanced users...</P>
235 <H2><A NAME="ss11.5">11.5</A> <A HREF="adminmanual.html#toc11.5">accept/spots (extended for sysops) (8)</A>
238 <P><CODE><B>accept/spots <call> [input] [0-9] <pattern></B> Spot filter sysop version</CODE></P>
240 <P>This version allows a sysop to set a filter for a callsign as well as the
241 default for nodes and users eg:-</P>
245 accept/spot db0sue-7 1 by_zone 14,15,16
246 accept/spot node_default all
247 set/hops node_default 10
249 accept/spot user_default by G,M,2
254 <H2><A NAME="ss11.6">11.6</A> <A HREF="adminmanual.html#toc11.6">accept/wcy (0)</A>
257 <P><CODE><B>accept/wcy [0-9] <pattern></B> set an accept WCY filter</CODE></P>
259 <P>It is unlikely that you will want to do this, but if you do then you can
260 filter on the following fields:-</P>
264 by <prefixes> eg: G,M,2
266 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
267 origin_itu <numbers>
268 origin_zone <numbers>
272 channel <prefixes>
277 <P>There are no examples because WCY Broadcasts only come from one place and
278 you either want them or not (see UNSET/WCY if you don't want them).</P>
279 <P>This command is really provided for future use.</P>
280 <P>See HELP FILTER for information.</P>
282 <H2><A NAME="ss11.7">11.7</A> <A HREF="adminmanual.html#toc11.7">accept/wcy (extended for sysops) (8)</A>
285 <P><CODE><B>accept/wcy <call> [input] [0-9] <pattern></B>
286 WCY filter sysop version</CODE></P>
288 <P>This version allows a sysop to set a filter for a callsign as well as the
289 default for nodes and users eg:-</P>
293 accept/wcy node_default all
294 set/hops node_default 10
299 <H2><A NAME="ss11.8">11.8</A> <A HREF="adminmanual.html#toc11.8">accept/wwv (0)</A>
302 <P><CODE><B>accept/wwv [0-9] <pattern></B> Set an accept WWV filter</CODE></P>
304 <P>It is unlikely that you will want to do this, but if you do then you can
305 filter on the following fields:-</P>
309 by <prefixes> eg: G,M,2
311 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
312 origin_itu <numbers>
313 origin_zone <numbers>
317 channel <prefixes>
329 <P>is probably the only useful thing to do (which will only show WWV broadcasts
330 by stations in the US).</P>
331 <P>See HELP FILTER for information.</P>
333 <H2><A NAME="ss11.9">11.9</A> <A HREF="adminmanual.html#toc11.9">accept/wwv (extended for sysops) (8)</A>
336 <P><CODE><B>accept/wwv <call> [input] [0-9] <pattern></B>
337 WWV filter sysop version</CODE></P>
339 <P>This version allows a sysop to set a filter for a callsign as well as the
340 default for nodes and users eg:-</P>
344 accept/wwv db0sue-7 1 by_zone 4
345 accept/wwv node_default all
346 set/hops node_default 10
348 accept/wwv user_default by W,K
353 <H2><A NAME="ss11.10">11.10</A> <A HREF="adminmanual.html#toc11.10">announce (0)</A>
356 <P><CODE><B>announce <text></B> Send an announcement to local users</CODE></P>
358 <P>Send an announcement to LOCAL users only, where <text> is the text
359 of the announcement you wish to broadcast. If you do not wish to receive
360 announces, use the <EM>set/noannounce</EM> command. Any announces made by
361 a sysop will override set/noannounce.</P>
363 <H2><A NAME="ss11.11">11.11</A> <A HREF="adminmanual.html#toc11.11">announce full (0)</A>
366 <P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE></P>
368 <P>This command will send your announcement across the whole cluster
372 <H2><A NAME="ss11.12">11.12</A> <A HREF="adminmanual.html#toc11.12">announce sysop (5)</A>
375 <P><CODE><B>announce sysop <text></B></CODE></P>
377 <P>Send an announcement to Sysops only</P>
379 <H2><A NAME="ss11.13">11.13</A> <A HREF="adminmanual.html#toc11.13">apropos (0)</A>
382 <P><CODE><B>apropos <string></B> Search the help database</CODE></P>
384 <P>Search the help database for <string> (it isn't case sensitive),
385 and print the names of all the commands that may be relevant.</P>
387 <H2><A NAME="ss11.14">11.14</A> <A HREF="adminmanual.html#toc11.14">bye (0)</A>
390 <P><CODE><B>bye</B> Exit from the cluster</CODE></P>
392 <P>This will disconnect you from the cluster</P>
394 <H2><A NAME="ss11.15">11.15</A> <A HREF="adminmanual.html#toc11.15">catchup (5)</A>
397 <P><CODE><B>catchup <node_call> All|[<msgno> ...]</B> Mark a message as sent</CODE></P>
399 <P>When you send messages the fact that you have forwarded it to another node
400 is remembered so that it isn't sent again. When you have a new partner
401 node and you add their callsign to your /spider/msg/forward.pl file, all
402 outstanding non-private messages will be forwarded to them. This may well
403 be ALL the non-private messages. You can prevent this by using these
409 catchup GB7DJK 300 301 302 303 500-510
413 <P>and to undo what you have just done:-</P>
418 uncatchup GB7DJK 300 301 302 303 500-510
422 <P>which will arrange for them to be forward candidates again.</P>
423 <P>Order is not important.</P>
425 <H2><A NAME="ss11.16">11.16</A> <A HREF="adminmanual.html#toc11.16">clear/announce (8)</A>
428 <P><CODE><B>clear/announce <callsign> [input] [0-9|all]</B> Clear an announce filter line</CODE></P>
430 <P>A sysop can clear an input or normal output filter for a user or the
431 node_default or user_default. </P>
433 <H2><A NAME="ss11.17">11.17</A> <A HREF="adminmanual.html#toc11.17">clear/route (8)</A>
436 <P><CODE><B>clear/route <callsign> [input] [0-9|all]</B> Clear a route filter line</CODE></P>
438 <P>This command allows you to clear (remove) a line in a route filter or to
439 remove the whole filter.</P>
440 <P>see CLEAR/SPOTS for a more detailed explanation.</P>
441 <P>A sysop can clear an input or normal output filter for a user or the
442 node_default or user_default. </P>
444 <H2><A NAME="ss11.18">11.18</A> <A HREF="adminmanual.html#toc11.18">clear/spots (0)</A>
447 <P><CODE><B>clear/spots [1|all]</B> Clear a spot filter line</CODE></P>
449 <P>This command allows you to clear (remove) a line in a spot filter or to
450 remove the whole filter.</P>
451 <P>If you have a filter:-</P>
456 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
468 <P>you will be left with:-</P>
472 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
484 <P>the filter will be completely removed.</P>
486 <H2><A NAME="ss11.19">11.19</A> <A HREF="adminmanual.html#toc11.19">clear/spots (extended for sysops) (8)</A>
489 <P><CODE><B>clear/spots <callsign> [input] [0-9|all]</B> Clear a spot filter line</CODE></P>
491 <P>A sysop can clear an input or normal output filter for a user or the
492 node_default or user_default. </P>
494 <H2><A NAME="ss11.20">11.20</A> <A HREF="adminmanual.html#toc11.20">clear/wcy (0)</A>
497 <P><CODE><B>clear/wcy [1|all]</B> Clear a WCY filter line</CODE></P>
499 <P>This command allows you to clear (remove) a line in a WCY filter or to
500 remove the whole filter.</P>
501 <P>see CLEAR/SPOTS for a more detailed explanation.</P>
503 <H2><A NAME="ss11.21">11.21</A> <A HREF="adminmanual.html#toc11.21">clear/wcy (extended for sysops) (8)</A>
506 <P><CODE><B>clear/wcy <callsign> [input] [0-9|all]</B> Clear a WCY filter line</CODE></P>
508 <P>A sysop can clear an input or normal output filter for a user or the
509 node_default or user_default. </P>
511 <H2><A NAME="ss11.22">11.22</A> <A HREF="adminmanual.html#toc11.22">clear/wwv (0)</A>
514 <P><CODE><B>clear/wwv [1|all]</B> Clear a WWV filter line</CODE></P>
516 <P>This command allows you to clear (remove) a line in a WWV filter or to
517 remove the whole filter.</P>
518 <P>see CLEAR/SPOTS for a more detailed explanation.</P>
520 <H2><A NAME="ss11.23">11.23</A> <A HREF="adminmanual.html#toc11.23">clear/wwv (extended for sysops) (8)</A>
523 <P><CODE><B>clear/wwv <callsign> [input] [0-9|all]</B> Clear a WWV filter line</CODE></P>
525 <P>A sysop can clear an input or normal output filter for a user or the
526 node_default or user_default.</P>
528 <H2><A NAME="ss11.24">11.24</A> <A HREF="adminmanual.html#toc11.24">connect (5) </A>
531 <P><CODE><B>connect <callsign></B> Start a connection to another DX Cluster</CODE></P>
533 <P>Start a connection process that will culminate in a new connection to the
534 DX cluster <callsign>. This process creates a new 'client' process which will
535 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
536 necessary to traverse the network(s) to logon to the cluster <callsign>.</P>
538 <H2><A NAME="ss11.25">11.25</A> <A HREF="adminmanual.html#toc11.25">dbavail (0)</A>
541 <P><CODE><B>dbavail</B> Show a list of all the databases in the system</CODE></P>
543 <P>The title says it all really, this command lists all the databases defined
544 in the system. It is also aliased to SHOW/COMMAND.</P>
546 <H2><A NAME="ss11.26">11.26</A> <A HREF="adminmanual.html#toc11.26">dbcreate (9)</A>
549 <P><CODE><B>dbcreate <name></B> Create a database entry<BR>
550 <B>dbcreate <name> chain <name> [<name>..]</B> Create a chained database entry<BR>
551 <B>dbcreate <name> remote <node></B> Create a remote database
554 <P>DBCREATE allows you to define a database in the system. It doesn't actually
555 create anything, just defines it.</P>
556 <P>The databases that are created are simple DB_File hash databases, they are
557 therefore already 'indexed'.</P>
558 <P>You can define a local database with the first form of the command eg:</P>
559 <P>DBCREATE oblast</P>
560 <P>You can also chain databases with the addition of the 'chain' keyword.
561 This will search each database one after the other. A typical example
563 <P>DBCREATE sdx_qsl chain sql_ad</P>
564 <P>No checking is done to see if the any of the chained databases exist, in
565 fact it is usually better to do the above statement first then do each of
566 the chained databases.</P>
567 <P>Databases can exist offsite. To define a database that lives on another
569 <P>DBCREATE buckmaster remote gb7dxc</P>
570 <P>Remote databases cannot be chained; however, the last database in a
571 a chain can be a remote database eg:</P>
572 <P>DBCREATE qsl chain gb7dxc</P>
573 <P>To see what databases have been defined do:</P>
574 <P>DBAVAIL (or it will have been aliased to SHOW/COMMAND)</P>
575 <P>It would be normal for you to add an entry into your local Aliases file
576 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
577 need to add a line like:-</P>
584 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
593 <P>to work as they may be used to.</P>
594 <P>See DBIMPORT for the importing of existing AK1A format data to databases.
595 See DBSHOW for generic database enquiry</P>
597 <H2><A NAME="ss11.27">11.27</A> <A HREF="adminmanual.html#toc11.27">dbimport (9)</A>
600 <P><CODE><B>dbimport <dbname></B> Import AK1A data into a database</CODE></P>
602 <P>If you want to import or update data in bulk to a database you can use
603 this command. It will either create or update entries into an existing
604 database. For example:-</P>
605 <P>DBIMPORT oblast /tmp/OBLAST.FUL</P>
606 <P>will import the standard OBLAST database that comes with AK1A into the
607 oblast database held locally.</P>
609 <H2><A NAME="ss11.28">11.28</A> <A HREF="adminmanual.html#toc11.28">dbremove (9)</A>
612 <P><CODE><B>dbremove <dbname></B> Delete a database</CODE></P>
614 <P>DBREMOVE will completely remove a database entry and also delete any data
615 file that is associated with it. </P>
616 <P>There is no warning, no comeback, no safety net. </P>
618 <P>DBREMOVE oblast </P>
619 <P>will remove the oblast database from the system and it will also remove
620 the associated datafile.</P>
622 <P>There is no warning, no comeback, no safety net.</P>
623 <P>You have been warned.</P>
625 <H2><A NAME="ss11.29">11.29</A> <A HREF="adminmanual.html#toc11.29">dbshow (0)</A>
628 <P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE></P>
630 <P>This is the generic user interface to the database to the database system.
631 It is expected that the sysop will add an entry to the local Aliases file
632 so that users can use the more familiar AK1A style of enquiry such as:</P>
640 <P>but if he hasn't and the database really does exist (use DBAVAIL or
641 SHOW/COMMAND to find out) you can do the same thing with:</P>
651 <H2><A NAME="ss11.30">11.30</A> <A HREF="adminmanual.html#toc11.30">debug (9)</A>
654 <P><CODE><B>debug</B> Set the cluster program into debug mode</CODE></P>
656 <P>Executing this command will only have an effect if you are running the cluster
657 in debug mode i.e.</P>
665 <P>It will interrupt the cluster just after the debug command has finished.</P>
667 <H2><A NAME="ss11.31">11.31</A> <A HREF="adminmanual.html#toc11.31">delete/user (9)</A>
670 <P><CODE><B>delete/user <callsign></B> Delete a user from the User Database</CODE></P>
672 <P>This command will completely remove a one or more users from the database.</P>
673 <P>There is NO SECOND CHANCE.</P>
674 <P>It goes without saying that you should use this command CAREFULLY!</P>
676 <H2><A NAME="ss11.32">11.32</A> <A HREF="adminmanual.html#toc11.32">demonstrate (9)</A>
679 <P><CODE><B>demonstrate <call> <command></B> Demonstrate a command to another user</CODE></P>
681 <P>This command is provided so that sysops can demonstrate commands to
682 other users. It runs a command as though that user had typed it in and
683 then sends the output to that user, together with the command that
688 DEMO g7brn sh/dx iota oc209
693 <P>Note that this command is similar to SPOOF and will have the same side
694 effects. Commands are run at the privilege of the user which is being
697 <H2><A NAME="ss11.33">11.33</A> <A HREF="adminmanual.html#toc11.33">directory (0)</A>
700 <P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
701 <B>directory own</B> List your own messages<BR>
702 <B>directory new</B> List all new messages<BR>
703 <B>directory to <call></B> List all messages to <call><BR>
704 <B>directory from <call></B> List all messages from <call><BR>
705 <B>directory subject <string></B> List all messages with <string> in subject<BR>
706 <B>directory <nn></B> List last <nn> messages<BR>
707 <B>directory <from>-<to></B> List messages <from> message <to> message <BR></CODE></P>
709 <P>List the messages in the messages directory.</P>
710 <P>If there is a 'p' one space after the message number then it is a
711 personal message. If there is a '-' between the message number and the
712 'p' then this indicates that the message has been read.</P>
713 <P>You can use shell escape characters such as '*' and '?' in the <call>
715 <P>You can combine some of the various directory commands together eg:-</P>
721 DIR SUBJECT IOTA 200-250
725 <P>You can abbreviate all the commands to one letter and use ak1a syntax:-</P>
736 <H2><A NAME="ss11.34">11.34</A> <A HREF="adminmanual.html#toc11.34">directory (extended for sysops) (5)</A>
739 <P>Works just like the user command except that sysops can see ALL messages.</P>
741 <H2><A NAME="ss11.35">11.35</A> <A HREF="adminmanual.html#toc11.35">disconnect (8)</A>
744 <P><CODE><B>disconnect <call> [<call> ...]</B> Disconnect a user or node</CODE></P>
746 <P>Disconnect any <call> connected locally</P>
748 <H2><A NAME="ss11.36">11.36</A> <A HREF="adminmanual.html#toc11.36">dx (0)</A>
751 <P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE></P>
753 <P>This is how you send a DX Spot to other users. You can, in fact, now
754 enter the <freq> and the <call> either way round. </P>
764 <P>will all give the same result. You can add some remarks to the end
765 of the command and they will be added to the spot.</P>
769 DX FR0G 144600 this is a test
773 <P>You can credit someone else by saying:-</P>
777 DX by G1TLH FR0G 144.600 he isn't on the cluster
781 <P>The <freq> is compared against the available bands set up in the
782 cluster. See SHOW/BANDS for more information.</P>
784 <H2><A NAME="ss11.37">11.37</A> <A HREF="adminmanual.html#toc11.37">export (9)</A>
787 <P><CODE><B>export <msgno> <filename></B> Export a message to a file</CODE></P>
789 <P>Export a message to a file. This command can only be executed on a local
790 console with a fully privileged user. The file produced will be in a form
791 ready to be imported back into the cluster by placing it in the import
792 directory (/spider/msg/import).</P>
793 <P>This command cannot overwrite an existing file. This is to provide some
794 measure of security. Any files written will owned by the same user as the
795 main cluster, otherwise you can put the new files anywhere the cluster can
796 access. For example:-</P>
797 <P>EXPORT 2345 /tmp/a</P>
799 <H2><A NAME="ss11.38">11.38</A> <A HREF="adminmanual.html#toc11.38">export_users (9)</A>
802 <P><CODE><B>export_users [<filename>]</B> Export the users database to ascii</CODE></P>
804 <P>Export the users database to a file in ascii format. If no filename
805 is given then it will export the file to /spider/data/user_asc.</P>
806 <P>If the file already exists it will be renamed to <filename>.o. In fact
807 up to 5 generations of the file can be kept each one with an extra 'o' on the
809 <P>BE WARNED: this will write to any file you have write access to. No check is
810 made on the filename (if any) that you specify.</P>
812 <H2><A NAME="ss11.39">11.39</A> <A HREF="adminmanual.html#toc11.39">filtering (0)</A>
815 <P><CODE><B>filtering</B> Filtering things in DXSpider</CODE></P>
817 <P>There are a number of things you can filter in the DXSpider system. They
818 all use the same general mechanism.</P>
819 <P>In general terms you can create a 'reject' or an 'accept' filter which
820 can have up to 10 lines in it. You do this using, for example:-</P>
821 <P>accept/spots .....
822 reject/spots .....</P>
823 <P>where ..... are the specific commands for that type of filter. There
824 are filters for spots, wwv, announce, wcy and (for sysops)
825 connects. See each different accept or reject command reference for
827 <P>There is also a command to clear out one or more lines in a filter and
828 one to show you what you have set. They are:-</P>
833 <P>There is clear/xxxx command for each type of filter.</P>
834 <P>For now we are going to use spots for the examples, but you can apply
835 the principles to all types of filter.</P>
836 <P>There are two main types of filter 'accept' or 'reject'; which you use
837 depends entirely on how you look at the world and what is least
838 writing to achieve what you want. Each filter has 10 lines (of any
839 length) which are tried in order. If a line matches then the action
840 you have specified is taken (ie reject means ignore it and accept
842 <P>The important thing to remember is that if you specify a 'reject'
843 filter (all the lines in it say 'reject/spots' (for instance) then if
844 a spot comes in that doesn't match any of the lines then you will get
845 it BUT if you specify an 'accept' filter then any spots that don't
846 match are dumped. For example if I have a one line accept filter:-</P>
847 <P>accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)</P>
848 <P>then automatically you will ONLY get VHF spots from or to CQ zones 14
849 15 and 16. If you set a reject filter like:</P>
850 <P>reject/spots on hf/cw</P>
851 <P>Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
852 and will work it even on CW then you could say:-</P>
853 <P>reject/spots on hf/cw and not info iota</P>
854 <P>But in that case you might only be interested in iota and say:-</P>
855 <P>accept/spots not on hf/cw or info iota</P>
856 <P>which is exactly the same. You should choose one or the other until
857 you are confortable with the way it works. Yes, you can mix them
858 (actually you can have an accept AND a reject on the same line) but
859 don't try this at home until you can analyse the results that you get
860 without ringing up the sysop for help.</P>
861 <P>You can arrange your filter lines into logical units, either for your
862 own understanding or simply convenience. I have one set frequently:-</P>
863 <P>reject/spots 1 on hf/cw
864 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16) </P>
865 <P>What this does is to ignore all HF CW spots (being a class B I can't
866 read any CW and couldn't possibly be interested in HF :-) and also
867 rejects any spots on VHF which don't either originate or spot someone
869 <P>This is an exmaple where you would use the line number (1 and 2 in
870 this case), if you leave the digit out, the system assumes '1'. Digits
871 '0'-'9' are available.</P>
872 <P>You can leave the word 'and' out if you want, it is implied. You can
873 use any number of brackets to make the 'expression' as you want
874 it. There are things called precedence rules working here which mean
875 that you will NEED brackets in a situation like line 2 because,
876 without it, will assume:-</P>
877 <P>(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16 </P>
878 <P>annoying, but that is the way it is. If you use OR - use
879 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
880 just 'and by_zone'.</P>
881 <P>If you want to alter your filter you can just redefine one or more
882 lines of it or clear out one line. For example:-</P>
883 <P>reject/spots 1 on hf/ssb</P>
886 <P>To remove the filter in its entirty:-</P>
887 <P>clear/spots all</P>
888 <P>There are similar CLEAR commands for the other filters:-</P>
892 <P>ADVANCED USERS:-</P>
893 <P>Once you are happy with the results you get, you may like to experiment. </P>
894 <P>my example that filters hf/cw spots and accepts vhf/uhf spots from EU
895 can be written with a mixed filter, eg:</P>
898 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)</P>
899 <P>each filter slot actually has a 'reject' slot and an 'accept'
900 slot. The reject slot is executed BEFORE the accept slot.</P>
901 <P>It was mentioned earlier that after a reject test that doesn't match,
902 the default for following tests is 'accept', the reverse is true for
903 'accept'. In the example what happens is that the reject is executed
904 first, any non hf/cw spot is passed to the accept line, which lets
905 thru everything else on HF.</P>
906 <P>The next filter line lets through just VHF/UHF spots from EU.</P>
908 <H2><A NAME="ss11.40">11.40</A> <A HREF="adminmanual.html#toc11.40">forward/latlong (8)</A>
911 <P><CODE><B>forward/latlong <node_call></B> Send latitude and longitude information to another cluster</CODE></P>
913 <P>This command sends all the latitude and longitude information that your
914 cluster is holding against callsigns. One advantage of recieving this
915 information is that more locator information is held by you. This
916 means that more locators are given on the DX line assuming you have
917 <EM>set/dxgrid</EM> enabled. This could be a LOT of information though, so
918 it is not recommended on slow links.</P>
920 <H2><A NAME="ss11.41">11.41</A> <A HREF="adminmanual.html#toc11.41">forward/opername (1)</A>
923 <P><CODE><B>forward/opername <call></B> Send out information on this <call> to all clusters</CODE></P>
925 <P>This command sends out any information held in the user file which can
926 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
927 and Homenode. PC41s are only sent for the information that is available.</P>
929 <H2><A NAME="ss11.42">11.42</A> <A HREF="adminmanual.html#toc11.42">help (0)</A>
932 <P><CODE><B>help <cmd></B> Get help on a command</CODE></P>
934 <P>All commands can be abbreviated, so SHOW/DX can be abbreviated
935 to SH/DX, ANNOUNCE can be shortened to AN and so on.</P>
936 <P>Look at the APROPOS <string> command which will search the help database
937 for the <string> you specify and give you a list of likely commands
938 to look at with HELP.</P>
940 <H2><A NAME="ss11.43">11.43</A> <A HREF="adminmanual.html#toc11.43">init (5)</A>
943 <P><CODE><B>init <node call></B> Re-initialise a link to an AK1A compatible node</CODE></P>
945 <P>This command attempts to re-initialise a link to a (usually) AK1A node
946 that has got confused, usually by a protocol loop of some kind. It may
947 work - but you usually will be better off simply disconnecting it (or
948 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
950 <P>Best of luck - you will need it.</P>
952 <H2><A NAME="ss11.44">11.44</A> <A HREF="adminmanual.html#toc11.44">kill (0)</A>
955 <P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE></P>
957 <P>Delete a message from the local system. You will only be able to
958 delete messages that you have originated or been sent (unless you are
961 <H2><A NAME="ss11.45">11.45</A> <A HREF="adminmanual.html#toc11.45">kill (5)</A>
964 <P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system<BR>
965 <B>kill from <call></B> Remove all messages from a callsign<BR>
966 <B>kill to <call></B> Remove all messages to a callsign<BR></CODE></P>
968 <P>You can get rid of any message to or originating from your callsign using
969 this command. You can remove more than one message at a time.</P>
970 <P>As a sysop you can kill any message on the system.</P>
972 <H2><A NAME="ss11.46">11.46</A> <A HREF="adminmanual.html#toc11.46">kill full (5)</A>
975 <P><CODE><B>kill full <msgno> [<msgno>]</B> Delete a message from the whole cluster</CODE></P>
977 <P>Delete a message (usually a 'bulletin') from the whole cluster system. </P>
978 <P>This uses the subject field, so any messages that have exactly the same subject
979 will be deleted. Beware!</P>
981 <H2><A NAME="ss11.47">11.47</A> <A HREF="adminmanual.html#toc11.47">kill/expunge (6)</A>
984 <P><CODE><B>kill/expunge <msgno> [<msgno>..]</B>Expunge a message</CODE></P>
986 <P>Deleting a message using the normal KILL commands only marks that message
987 for deletion. The actual deletion only happens later (usually two days later).</P>
988 <P>The KILL EXPUNGE command causes the message to be truly deleted more or less
990 <P>It otherwise is used in the same way as the KILL command.</P>
993 <H2><A NAME="ss11.48">11.48</A> <A HREF="adminmanual.html#toc11.48">links (0)</A>
996 <P><CODE><B>links</B> Show which nodes are physically connected</CODE></P>
998 <P>This is a quick listing that shows which links are connected and
999 some information about them. See WHO for a list of all connections.</P>
1002 <H2><A NAME="ss11.49">11.49</A> <A HREF="adminmanual.html#toc11.49">load/aliases (9)</A>
1005 <P><CODE><B>load/aliases</B> Reload the command alias table</CODE></P>
1007 <P>Reload the /spider/cmd/Aliases file after you have editted it. You will need to
1008 do this if you change this file whilst the cluster is running in order for the
1009 changes to take effect.</P>
1011 <H2><A NAME="ss11.50">11.50</A> <A HREF="adminmanual.html#toc11.50">load/badmsg (9)</A>
1014 <P><CODE><B>load/badmsg</B> Reload the bad message table</CODE></P>
1016 <P>Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
1017 the cluster is running. This table contains a number of perl regular
1018 expressions which are searched for in the fields targetted of each message.
1019 If any of them match then that message is immediately deleted on receipt. </P>
1021 <H2><A NAME="ss11.51">11.51</A> <A HREF="adminmanual.html#toc11.51">load/badwords (9)</A>
1024 <P><CODE><B>load/badwords</B> Reload the bad words table</CODE></P>
1026 <P>Reload the /spider/data/badwords file if you have changed it manually whilst
1027 the cluster is running. This file contains a list of words which, if found
1028 on certain text portions of PC protocol, will cause those protocol frames
1029 to be rejected. It will all put out a message if any of these words are
1030 used on the announce, dx and talk commands. The words can be one or
1031 more on a line, lines starting with '#' are ignored.</P>
1033 <H2><A NAME="ss11.52">11.52</A> <A HREF="adminmanual.html#toc11.52">load/bands (9)</A>
1036 <P><CODE><B>load/bands</B> Reload the band limits table</CODE></P>
1038 <P>Reload the /spider/data/bands.pl file if you have changed it manually whilst
1039 the cluster is running. </P>
1041 <H2><A NAME="ss11.53">11.53</A> <A HREF="adminmanual.html#toc11.53">load/cmd_cache (9)</A>
1044 <P><CODE><B>load/cmd_cache</B> Reload the automatic command cache</CODE></P>
1046 <P>Normally, if you change a command file in the cmd or local_cmd tree it will
1047 automatially be picked up by the cluster program. Sometimes it can get confused
1048 if you are doing a lot of moving commands about or delete a command in the
1049 local_cmd tree and want to use the normal one again. Execute this command to
1050 reset everything back to the state it was just after a cluster restart.</P>
1052 <H2><A NAME="ss11.54">11.54</A> <A HREF="adminmanual.html#toc11.54">load/forward (9)</A>
1055 <P><CODE><B>load/forward</B> Reload the msg forwarding routing table</CODE></P>
1056 <P>Reload the /spider/msg/forward.pl file if you have changed it
1057 manually whilst the cluster is running.</P>
1059 <H2><A NAME="ss11.55">11.55</A> <A HREF="adminmanual.html#toc11.55">load/messages (9)</A>
1062 <P><CODE><B>load/messages</B> Reload the system messages file</CODE></P>
1064 <P>If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne
1065 commands) you can have them take effect during a cluster session by executing this
1066 command. You need to do this if get something like :-</P>
1067 <P>unknown message 'xxxx' in lang 'en'</P>
1069 <H2><A NAME="ss11.56">11.56</A> <A HREF="adminmanual.html#toc11.56">load/prefixes (9)</A>
1072 <P><CODE><B>load/prefixes</B> Reload the prefix table</CODE></P>
1074 <P>Reload the /spider/data/prefix_data.pl file if you have changed it manually
1075 whilst the cluster is running. </P>
1077 <H2><A NAME="ss11.57">11.57</A> <A HREF="adminmanual.html#toc11.57">merge (5)</A>
1080 <P><CODE><B>merge <node> [<no spots>/<no wwv>]</B> Ask for the latest spots and WWV</CODE></P>
1082 <P>MERGE allows you to bring your spot and wwv database up to date. By default
1083 it will request the last 10 spots and 5 WWVs from the node you select. The
1084 node must be connected locally.</P>
1085 <P>You can request any number of spots or wwv and although they will be appended
1086 to your databases they will not duplicate any that have recently been added
1087 (the last 2 days for spots and last month for WWV data).</P>
1089 <H2><A NAME="ss11.58">11.58</A> <A HREF="adminmanual.html#toc11.58">msg (9)</A>
1092 <P><CODE><B>msg <cmd> <msgno> [data ...]</B> Alter various message parameters</CODE></P>
1094 <P>Alter message parameters like To, From, Subject, whether private or bulletin
1095 or return receipt (RR) is required or whether to keep this message from timing
1100 MSG TO <msgno> <call> - change TO callsign to <call>
1101 MSG FRom <msgno> <call> - change FROM callsign to <call>
1102 MSG PRrivate <msgno> - set private flag
1103 MSG NOPRrivate <msgno> - unset private flag
1104 MSG RR <msgno> - set RR flag
1105 MSG NORR <msgno> - unset RR flag
1106 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1107 MSG NOKEep <msgno> - unset the keep flag
1108 MSG SUbject <msgno> <new> - change the subject to <new>
1109 MSG WAittime <msgno> - remove any waitting time for this message
1110 MSG NOREad <msgno> - mark message as unread
1111 MSG REad <msgno> - mark message as read
1112 MSG QUeue - queue any outstanding bulletins
1113 MSG QUeue 1 - queue any outstanding private messages
1115 </CODE></BLOCKQUOTE>
1117 <P>You can look at the status of a message by using:-</P>
1118 <P>STAT/MSG <msgno> </P>
1119 <P>This will display more information on the message than DIR does.</P>
1121 <H2><A NAME="ss11.59">11.59</A> <A HREF="adminmanual.html#toc11.59">pc (8)</A>
1124 <P><CODE><B>pc <call> <text></B> Send text (eg PC Protocol) to <call></CODE></P>
1126 <P>Send some arbitrary text to a locally connected callsign. No processing is done on
1127 the text. This command allows you to send PC Protocol to unstick things if problems
1128 arise (messages get stuck etc). eg:-</P>
1129 <P>pc gb7djk PC33^GB7TLH^GB7DJK^400^</P>
1130 <P>You can also use in the same way as a talk command to a connected user but
1131 without any processing, added of "from <blah> to <blah>" or whatever.</P>
1132 <P>pc G1TLH Try doing that properly!!!</P>
1134 <H2><A NAME="ss11.60">11.60</A> <A HREF="adminmanual.html#toc11.60">ping (1)</A>
1137 <P><CODE><B>ping <node></B> Check the link quality between nodes</CODE></P>
1139 <P>his command allows you to send a frame to another cluster node on
1140 the network and get a return frame. The time it takes to do this
1141 is a good indication of the quality of the link. The actual time
1142 it takes is output to the console in seconds.
1143 Any visible cluster node can be PINGed.</P>
1146 <H2><A NAME="ss11.61">11.61</A> <A HREF="adminmanual.html#toc11.61">rcmd (1)</A>
1149 <P><CODE><B>rcmd <node call> <cmd></B> Send a command to another DX cluster</CODE></P>
1151 <P>This command allows you to send nearly any command to another DX Cluster
1152 node that is connected to the system. </P>
1153 <P>Whether you get any output is dependant on a) whether the other system knows
1154 that the node callsign of this cluster is in fact a node b) whether the
1155 other system is allowing RCMDs from this node and c) whether you have
1156 permission to send this command at all.</P>
1158 <H2><A NAME="ss11.62">11.62</A> <A HREF="adminmanual.html#toc11.62">read (0)</A>
1161 <P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
1162 <B>read <msgno></B> Read the specified message<BR></CODE></P>
1164 <P>You can read any messages that are sent as 'non-personal' and also any
1165 message either sent by or sent to your callsign.</P>
1168 <H2><A NAME="ss11.63">11.63</A> <A HREF="adminmanual.html#toc11.63">read (extended for sysops) (5) </A>
1171 <P><CODE><B>read <msgno></B> Read a message on the system</CODE></P>
1173 <P>As a sysop you may read any message on the system</P>
1175 <H2><A NAME="ss11.64">11.64</A> <A HREF="adminmanual.html#toc11.64">reject/announce</A>
1178 <P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
1179 for announce</CODE></P>
1181 <P>Create an 'reject this announce' line for a filter. </P>
1182 <P>An reject filter line means that if the announce matches this filter it is
1183 passed onto the user. See HELP FILTERS for more info. Please read this
1184 to understand how filters work - it will save a lot of grief later on.</P>
1185 <P>You can use any of the following things in this line:-</P>
1189 info <string> eg: iota or qsl
1190 by <prefixes> eg: G,M,2
1191 origin <prefixes>
1192 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1193 origin_itu <numbers>
1194 origin_zone <numbers>
1195 by_dxcc <numbers>
1197 by_zone <numbers>
1198 channel <prefixes>
1199 wx 1 filter WX announces
1200 dest <prefixes> eg: 6MUK,WDX (distros)
1202 </CODE></BLOCKQUOTE>
1204 <P>some examples:-</P>
1208 rej/ann by_zone 14,15,16 and not by G,M,2
1210 </CODE></BLOCKQUOTE>
1212 <P>You can use the tag 'all' to reject everything eg:</P>
1218 </CODE></BLOCKQUOTE>
1220 <P>but this probably for advanced users...</P>
1222 <H2><A NAME="ss11.65">11.65</A> <A HREF="adminmanual.html#toc11.65">reject/announce (extended for sysops) (8)</A>
1225 <P><CODE><B>reject/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE></P>
1227 <P>This version allows a sysop to set a filter for a callsign as well as the
1228 default for nodes and users eg:-</P>
1233 reject/ann input node_default by G,M,2
1234 reject/ann user_default by G,M,2
1236 </CODE></BLOCKQUOTE>
1239 <H2><A NAME="ss11.66">11.66</A> <A HREF="adminmanual.html#toc11.66">reject/route (8)</A>
1242 <P><CODE><B>reject/route <call> [0-9] <pattern></B> Set an 'reject' filter line for routing</CODE></P>
1244 <P>Create an 'reject this routing PC Protocol' line for a filter. </P>
1246 <P>An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1247 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
1248 read this to understand how filters work - it will save a lot of grief later on.
1249 You can use any of the following things in this line:-</P>
1253 call <prefixes> the callsign of the thingy
1254 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1255 call_itu <numbers>
1256 call_zone <numbers>
1257 origin <prefixes> really the interface it came in on
1258 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1259 origin_itu <numbers>
1260 origin_zone <numbers>
1262 </CODE></BLOCKQUOTE>
1265 <P>some examples:-</P>
1269 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
1271 </CODE></BLOCKQUOTE>
1274 <P>You can use the tag 'all' to reject everything eg:</P>
1278 rej/route all (equiv to [very] restricted mode)
1280 </CODE></BLOCKQUOTE>
1283 <H2><A NAME="ss11.67">11.67</A> <A HREF="adminmanual.html#toc11.67">reject/spots (0)</A>
1286 <P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE></P>
1288 <P>Create a 'reject this spot' line for a filter. </P>
1289 <P>A reject filter line means that if the spot matches this filter it is
1290 dumped (not passed on). See HELP FILTERS for more info. Please read this
1291 to understand how filters work - it will save a lot of grief later on.</P>
1292 <P>You can use any of the following things in this line:-</P>
1296 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1297 on <range> same as 'freq'
1298 call <prefixes> eg: G,PA,HB9
1299 info <string> eg: iota or qsl
1301 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1302 call_itu <numbers>
1303 call_zone <numbers>
1304 by_dxcc <numbers>
1306 by_zone <numbers>
1307 origin <prefixes>
1308 channel <prefixes>
1310 </CODE></BLOCKQUOTE>
1312 <P>For frequencies, you can use any of the band names defined in
1313 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1314 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1315 this is more efficient than saying simply: on HF (but don't get
1316 too hung up about that)</P>
1317 <P>some examples:-</P>
1322 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1324 </CODE></BLOCKQUOTE>
1326 <P>You can use the tag 'all' to reject everything eg:</P>
1332 </CODE></BLOCKQUOTE>
1334 <P>but this probably for advanced users...</P>
1336 <H2><A NAME="ss11.68">11.68</A> <A HREF="adminmanual.html#toc11.68">reject/spots (extended for sysops) (8)</A>
1339 <P><CODE><B>reject/spots <call> [input] [0-9] <pattern></B>
1340 Reject spot filter sysop version </CODE></P>
1342 <P>This version allows a sysop to set a filter for a callsign as well as the
1343 default for nodes and users eg:-</P>
1347 reject/spot db0sue-7 1 by_zone 14,15,16
1348 reject/spot node_default all
1349 set/hops node_default 10
1351 reject/spot user_default by G,M,2
1353 </CODE></BLOCKQUOTE>
1356 <H2><A NAME="ss11.69">11.69</A> <A HREF="adminmanual.html#toc11.69">reject/wcy (0)</A>
1359 <P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE></P>
1361 <P>It is unlikely that you will want to do this, but if you do then you can
1362 filter on the following fields:-</P>
1366 by <prefixes> eg: G,M,2
1367 origin <prefixes>
1368 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1369 origin_itu <numbers>
1370 origin_zone <numbers>
1371 by_dxcc <numbers>
1373 by_zone <numbers>
1374 channel <prefixes>
1376 </CODE></BLOCKQUOTE>
1378 <P>There are no examples because WCY Broadcasts only come from one place and
1379 you either want them or not (see UNSET/WCY if you don't want them).</P>
1380 <P>This command is really provided for future use.</P>
1381 <P>See HELP FILTER for information.</P>
1383 <H2><A NAME="ss11.70">11.70</A> <A HREF="adminmanual.html#toc11.70">reject/wcy (extended for sysops) (8)</A>
1386 <P><CODE><B>reject/wcy <call> [input] [0-9] <pattern></B>
1387 WCY reject filter sysop version</CODE></P>
1389 <P>This version allows a sysop to set a filter for a callsign as well as the
1390 default for nodes and users eg:-</P>
1391 <P>reject/wcy gb7djk all</P>
1393 <H2><A NAME="ss11.71">11.71</A> <A HREF="adminmanual.html#toc11.71">reject/wwv (0)</A>
1396 <P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE></P>
1398 <P>It is unlikely that you will want to do this, but if you do then you can
1399 filter on the following fields:-</P>
1403 by <prefixes> eg: G,M,2
1404 origin <prefixes>
1405 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1406 origin_itu <numbers>
1407 origin_zone <numbers>
1408 by_dxcc <numbers>
1410 by_zone <numbers>
1411 channel <prefixes>
1413 </CODE></BLOCKQUOTE>
1419 reject/wwv by_zone 14,15,16
1421 </CODE></BLOCKQUOTE>
1423 <P>is probably the only useful thing to do (which will only show WWV broadcasts
1424 by stations in the US).</P>
1425 <P>See HELP FILTER for information.</P>
1427 <H2><A NAME="ss11.72">11.72</A> <A HREF="adminmanual.html#toc11.72">reject/wwv (extended for sysops) (8)</A>
1430 <P><CODE><B>reject/wwv <call> [input] [0-9] <pattern></B>
1431 WWV reject filter sysop version</CODE></P>
1433 <P>This version allows a sysop to set a filter for a callsign as well as the
1434 default for nodes and users eg:-</P>
1438 reject/wwv db0sue-7 1 by_zone 4
1439 reject/wwv node_default all
1441 reject/wwv user_default by W
1443 </CODE></BLOCKQUOTE>
1446 <H2><A NAME="ss11.73">11.73</A> <A HREF="adminmanual.html#toc11.73">reply (0)</A>
1449 <P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
1450 <B>reply <msgno></B> Reply (privately) to the specified message<BR>
1451 <B>reply B <msgno></B> Reply as a Bulletin to the specified message<BR>
1452 <B>reply NOPrivate <msgno></B> Reply as a Bulletin to the specified
1454 <B>reply RR <msgno></B> Reply to the specified message with read receipt<BR></CODE></P>
1456 <P>You can reply to a message and the subject will automatically have
1457 "Re:" inserted in front of it, if it isn't already present.</P>
1458 <P>You can also use all the extra qualifiers such as RR, PRIVATE,
1459 NOPRIVATE, B that you can use with the SEND command (see SEND
1460 for further details)</P>
1462 <H2><A NAME="ss11.74">11.74</A> <A HREF="adminmanual.html#toc11.74">send (0)</A>
1465 <P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
1466 <B>send RR <call></B> Send a message and ask for a read receipt<BR>
1467 <B>send COPY <msgno> <call></B> Send a copy of a message to someone<BR>
1468 <B>send PRIVATE <call></B> Send a personal message<BR>
1469 <B>send NOPRIVATE <call></B> Send a message to all stations<BR></CODE></P>
1471 <P>All the SEND commands will create a message which will be sent either to
1472 an individual callsign or to one of the 'bulletin' addresses. </P>
1473 <P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1474 it will mark the message as personal and send it to the cluster node that
1475 that callsign is connected to.</P>
1476 <P>You can have more than one callsign in all of the SEND commands.</P>
1477 <P>You can have multiple qualifiers so that you can have for example:-</P>
1481 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1483 </CODE></BLOCKQUOTE>
1485 <P>which should send a copy of message 123 to G1TLH and G0RDI and you will
1486 receive a read receipt when they have read the message.</P>
1487 <P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1488 SP is an alias for SEND PRIVATE</P>
1490 <H2><A NAME="ss11.75">11.75</A> <A HREF="adminmanual.html#toc11.75">set/address (0)</A>
1493 <P><CODE><B>set/address <your_address></B> Record your postal address</CODE></P>
1495 <P>Literally, record your address details on the cluster.</P>
1497 <H2><A NAME="ss11.76">11.76</A> <A HREF="adminmanual.html#toc11.76">set/announce (0)</A>
1500 <P><CODE><B>set/announce</B> Allow announce messages</CODE></P>
1502 <P>Allow announce messages to arrive at your terminal.</P>
1504 <H2><A NAME="ss11.77">11.77</A> <A HREF="adminmanual.html#toc11.77">set/arcluster (5)</A>
1507 <P><CODE><B>set/arcluster <node_call> [<node_call> ...]</B> Make
1508 the node_call an AR-Cluster type node</CODE></P>
1510 <P>Set the node_call as an AR-Cluster type node</P>
1512 <H2><A NAME="ss11.78">11.78</A> <A HREF="adminmanual.html#toc11.78">set/baddx (8)</A>
1515 <P><CODE><B>set/baddx <call></B> Stop words we do not wish to see in the callsign field
1516 of a dx spot being propagated</CODE></P>
1518 <P>Setting a word as 'baddx' will prevent spots with that word in the callsign
1519 field of a DX spot from going any further. They will not be displayed and they
1520 will not be sent onto other nodes.</P>
1521 <P>The word must be wriiten in full, no wild cards are allowed eg:-</P>
1525 set/baddx FORSALE VIDEO FR0G
1527 </CODE></BLOCKQUOTE>
1529 <P>To allow a word again, use the following command ...</P>
1535 </CODE></BLOCKQUOTE>
1538 <H2><A NAME="ss11.79">11.79</A> <A HREF="adminmanual.html#toc11.79">set/badnode (6)</A>
1541 <P><CODE><B>set/badnode <node_call></B> Stop spots from this node_call
1542 being propagated</CODE></P>
1544 <P>Setting a callsign as a 'badnode' will prevent spots from that node
1545 going any further. They will not be displayed and they will not be
1546 sent onto other nodes.</P>
1547 <P>The call can be a full or partial call (or a prefix), eg:-</P>
1553 </CODE></BLOCKQUOTE>
1555 <P>will stop anything from K1TTT (including any SSID's)</P>
1561 </CODE></BLOCKQUOTE>
1563 <P>will allow spots from him again.</P>
1564 <P>Use with extreme care. This command may well be superceded by FILTERing.</P>
1566 <H2><A NAME="ss11.80">11.80</A> <A HREF="adminmanual.html#toc11.80">set/badspotter (8)</A>
1569 <P><CODE><B>set/badspotter <call></B> Stop spots from this callsign being propagated</CODE></P>
1571 <P>Setting a callsign as a 'badspotter' will prevent spots from this callsign
1572 going any further. They will not be displayed and they will not be
1573 sent onto other nodes.</P>
1574 <P>The call must be written in full, no wild cards are allowed eg:-</P>
1578 set/badspotter VE2STN
1580 </CODE></BLOCKQUOTE>
1582 <P>will stop anything from VE2STN. If you want SSIDs as well then you must
1583 enter them specifically.</P>
1587 unset/badspotter VE2STN
1589 </CODE></BLOCKQUOTE>
1591 <P>will allow spots from him again.</P>
1592 <P>Use with extreme care. This command may well be superceded by FILTERing.</P>
1594 <H2><A NAME="ss11.81">11.81</A> <A HREF="adminmanual.html#toc11.81">set/badword (8)</A>
1597 <P><CODE><B>set/badword <word></B> Stop things with this word being propogated</CODE></P>
1599 <P>Setting a word as a 'badword' will prevent things like spots,
1600 announces or talks with this word in the the text part from going any
1601 further. They will not be displayed and they will not be sent onto
1603 <P>The word must be written in full, no wild cards are allowed eg:-</P>
1604 <P>set/badword annihilate annihilated annihilation </P>
1605 <P>will stop anything with these words in the text.</P>
1606 <P>unset/badword annihilated</P>
1607 <P>will allow text with this word again.</P>
1610 <H2><A NAME="ss11.82">11.82</A> <A HREF="adminmanual.html#toc11.82">set/beep (0)</A>
1613 <P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE></P>
1615 <P>Add a beep to DX and other terminal messages.</P>
1617 <H2><A NAME="ss11.83">11.83</A> <A HREF="adminmanual.html#toc11.83">set/bbs (5)</A>
1620 <P><CODE><B>set/bbs <call> [<call>..]</B>Make <call> a BBS</CODE></P>
1622 <H2><A NAME="ss11.84">11.84</A> <A HREF="adminmanual.html#toc11.84">set/clx (5)</A>
1625 <P><CODE><B>set/clx <node_call> [<node_call> ...]</B> Make
1626 the node_call a CLX type node</CODE></P>
1628 <P>Set the node_call as a CLX type node</P>
1630 <H2><A NAME="ss11.85">11.85</A> <A HREF="adminmanual.html#toc11.85">set/debug (9)</A>
1633 <P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE></P>
1635 <P>You can choose to log several different levels. The levels are</P>
1641 <P>You can show what levels you are logging with the <EM>show/debug</EM>
1643 <P>You can remove a debug level with unset/debug <name></P>
1645 <H2><A NAME="ss11.86">11.86</A> <A HREF="adminmanual.html#toc11.86">set/dx (0)</A>
1648 <P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE></P>
1650 <P>You can stop DX messages with the <EM>unset/dx</EM> command</P>
1652 <H2><A NAME="ss11.87">11.87</A> <A HREF="adminmanual.html#toc11.87">set/dxgrid (0)</A>
1655 <P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE></P>
1657 <P>Some logging programs do not like the additional information at
1658 the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
1659 command to remove the grid squares.</P>
1661 <H2><A NAME="ss11.88">11.88</A> <A HREF="adminmanual.html#toc11.88">set/dxnet (5)</A>
1664 <P><CODE><B>set/dxnet <node_call> [<node_call> ...]</B> Make
1665 the node_call a DXNet type node</CODE></P>
1667 <P>Set the node_call as a DXNet type node</P>
1669 <H2><A NAME="ss11.89">11.89</A> <A HREF="adminmanual.html#toc11.89">set/echo (0)</A>
1672 <P><CODE><B>set/echo</B> Make the cluster echo your input</CODE></P>
1674 <P>If you are connected via a telnet session, different implimentations
1675 of telnet handle echo differently depending on whether you are
1676 connected via port 23 or some other port. You can use this command
1677 to change the setting appropriately. </P>
1678 <P>You can remove the echo with the <EM>unset/echo</EM> command</P>
1679 <P>The setting is stored in your user profile.</P>
1680 <P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.</P>
1682 <H2><A NAME="ss11.90">11.90</A> <A HREF="adminmanual.html#toc11.90">set/email (0)</A>
1685 <P><CODE><B>set/email <email_address></B> Set email address(es) and forward your personals</CODE></P>
1687 <P>If any personal messages come in for your callsign then you can use
1688 these commands to control whether they are forwarded onto your email
1689 address. To enable the forwarding do something like:-</P>
1690 <P>SET/EMAIL mike.tubby@somewhere.com</P>
1691 <P>You can have more than one email address (each one separated by a space).
1692 Emails are forwarded to all the email addresses you specify.</P>
1693 <P>You can disable forwarding by:-</P>
1696 <H2><A NAME="ss11.91">11.91</A> <A HREF="adminmanual.html#toc11.91">set/here (0)</A>
1699 <P><CODE><B>set/here</B> Set the here flag</CODE></P>
1701 <P>Let others on the cluster know you are here by only displaying your
1702 callsign. If you are away from your terminal you can use the <EM>unset/here</EM>
1703 command to let people know you are away. This simply puts brackets
1704 around your callsign to indicate you are not available.</P>
1706 <H2><A NAME="ss11.92">11.92</A> <A HREF="adminmanual.html#toc11.92">set/homenode (0)</A>
1709 <P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE></P>
1711 <P>Tell the cluster system where you normally connect to. Any Messages sent
1712 to you will normally find their way there should you not be connected.
1719 </CODE></BLOCKQUOTE>
1722 <H2><A NAME="ss11.93">11.93</A> <A HREF="adminmanual.html#toc11.93">set/hops (8)</A>
1725 <P><CODE><B>set/hops <node_call> ann|spots|wwv|wcy <n></B>
1726 Set hop count</CODE></P>
1728 <P>Set the hop count for a particular type of broadcast for a node.</P>
1729 <P>This command allows you to set up special hop counts for a node
1730 for currently: announce, spots, wwv and wcy broadcasts.</P>
1735 set/hops gb7djk ann 10
1736 set/hops gb7mbc spots 20
1738 </CODE></BLOCKQUOTE>
1740 <P>Set SHOW/HOPS for information on what is already set. This command
1741 creates a filter and works in conjunction with the filter system. </P>
1743 <H2><A NAME="ss11.94">11.94</A> <A HREF="adminmanual.html#toc11.94">set/isolate (9)</A>
1746 <P><CODE><B>set/isolate <node call></B> Isolate a node from the rest of the network</CODE></P>
1748 <P>Connect a node to your system in such a way that you are a full protocol
1749 member of its network and can see all spots on it, but nothing either leaks
1750 out from it nor goes back into from the rest of the nodes connected to you.</P>
1751 <P>You can potentially connect several nodes in this way.</P>
1752 <P>You can see which nodes are isolated with the show/isolate (1) command.</P>
1753 <P>You can remove the isolation with the command unset/isolate.</P>
1755 <H2><A NAME="ss11.95">11.95</A> <A HREF="adminmanual.html#toc11.95">set/language (0)</A>
1758 <P><CODE><B>set/language <language></B> Set the language you wish to use</CODE></P>
1760 <P>You can select the language that you want the cluster to use. Currently
1761 the languages available are <EM>en</EM> (English) and <EM>nl</EM> (Dutch).</P>
1763 <H2><A NAME="ss11.96">11.96</A> <A HREF="adminmanual.html#toc11.96">set/location (0)</A>
1766 <P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE></P>
1768 <P>You can set your latitude and longitude manually or alternatively use the
1769 <EM>set/qra</EM> command which will do the conversion for you.</P>
1773 set/location 54 04 N 2 02 E
1775 </CODE></BLOCKQUOTE>
1779 <H2><A NAME="ss11.97">11.97</A> <A HREF="adminmanual.html#toc11.97">set/sys_location (9)</A>
1782 <P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE></P>
1784 <P>In order to get accurate headings and such like you must tell the system
1785 what your latitude and longitude is. If you have not yet done a SET/QRA
1786 then this command will set your QRA locator for you. For example:-</P>
1790 SET/LOCATION 52 22 N 0 57 E
1792 </CODE></BLOCKQUOTE>
1795 <H2><A NAME="ss11.98">11.98</A> <A HREF="adminmanual.html#toc11.98">set/logininfo (0)</A>
1798 <P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE></P>
1800 <P>Show users and nodes when they log in and out of the local cluster. You
1801 can stop these messages by using the <EM>unset/logininfo</EM> command.</P>
1804 <H2><A NAME="ss11.99">11.99</A> <A HREF="adminmanual.html#toc11.99">set/lockout (9)</A>
1807 <P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE></P>
1809 <P>You can show who is locked out with the <EM>show/lockout</EM> command.
1810 To allow the user to connect again, use the <EM>unset/lockout</EM> command.</P>
1812 <H2><A NAME="ss11.100">11.100</A> <A HREF="adminmanual.html#toc11.100">set/name (0)</A>
1815 <P><CODE><B>set/name <your_name></B> Set your name</CODE></P>
1817 <P>Tell the cluster what your name is, eg:-</P>
1823 </CODE></BLOCKQUOTE>
1826 <H2><A NAME="ss11.101">11.101</A> <A HREF="adminmanual.html#toc11.101">set/node (9)</A>
1829 <P><CODE><B>set/node <call> [<call> ...]</B> Make the callsign an AK1A cluster</CODE></P>
1831 <P>Tell the system that the call(s) are to be treated as AK1A cluster and
1832 fed PC Protocol rather normal user commands.</P>
1833 <P>From version 1.41 you can also set the following types of cluster</P>
1842 </CODE></BLOCKQUOTE>
1844 <P>To see what your nodes are set to, use the <EM>show/nodes</EM> command.</P>
1846 <H2><A NAME="ss11.102">11.102</A> <A HREF="adminmanual.html#toc11.102">set/obscount (9)</A>
1849 <P><CODE><B>set/obscount <count> <node call></B> Set the 'pump-up' obsolescence counter</CODE></P>
1851 <P>From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1852 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1853 counter which is decremented on every outgoing ping and then reset to
1854 the 'obscount' value on every incoming ping. The default value of this
1855 parameter is 2. </P>
1856 <P>What this means is that a neighbouring node will be pinged twice at
1857 (default) 300 second intervals and if no reply has been heard just before
1858 what would be the third attempt, that node is disconnected.</P>
1859 <P>If a ping is heard then the obscount is reset to the full value. Using
1860 default values, if a node has not responded to a ping within 15 minutes,
1861 it is disconnected.</P>
1863 <H2><A NAME="ss11.103">11.103</A> <A HREF="adminmanual.html#toc11.103">set/page (0)</A>
1866 <P><CODE><B>set/page <n></B> Set the number of lines per page</CODE></P>
1868 <P>Tell the system how many lines you wish on a page when the number of lines
1869 of output from a command is more than this. The default is 20. Setting it
1870 explicitly to 0 will disable paging. </P>
1877 </CODE></BLOCKQUOTE>
1879 <P>The setting is stored in your user profile.</P>
1881 <H2><A NAME="ss11.104">11.104</A> <A HREF="adminmanual.html#toc11.104">set/password (0)</A>
1884 <P><CODE><B>set/password</B> Set your own password</CODE></P>
1886 <P>This command only works for a 'telnet' user (currently). It will
1887 only work if you have a password already set. This initial password
1888 can only be set by the sysop.</P>
1889 <P>When you execute this command it will ask you for your old password,
1890 then ask you to type in your new password twice (to make sure you
1891 get it right). You may or may not see the data echoed on the screen
1892 as you type, depending on the type of telnet client you have.</P>
1894 <H2><A NAME="ss11.105">11.105</A> <A HREF="adminmanual.html#toc11.105">set/password (9)</A>
1897 <P><CODE><B>set/password <callsign> <string></B> Set a users password</CODE></P>
1899 <P>The password for a user can only be set by a full sysop. The string
1900 can contain any characters. </P>
1901 <P>The way this field is used depends on context. If it is being used in
1902 the SYSOP command context then you are offered 5 random numbers and you
1903 have to supply the corresponding letters. This is now mainly for ax25
1905 <P>If it is being used on incoming telnet connections then, if a password
1907 <P>set/var $main::passwdreq = 1</P>
1908 <P>command is executed in the startup script, then a password prompt is
1909 given after the normal 'login: ' prompt. </P>
1910 <P>The command "unset/password" is provided to allow a sysop to remove a
1911 users password completely in case a user forgets or loses their password.</P>
1913 <H2><A NAME="ss11.106">11.106</A> <A HREF="adminmanual.html#toc11.106">set/pinginterval (9)</A>
1916 <P><CODE><B>set/pinginterval <time> <node call></B> Set the ping time to neighbouring nodes</CODE></P>
1918 <P>As from version 1.35 all neighbouring nodes are pinged at regular intervals
1919 in order to determine the rolling quality of the link and, in future, to
1920 affect routing decisions. The default interval is 300 secs or 5 minutes.</P>
1921 <P>You can use this command to set a different interval. Please don't. </P>
1922 <P>But if you do the value you enter is treated as minutes up 60 and seconds
1923 for numbers greater than that.</P>
1924 <P>This is used also to help determine when a link is down at the far end
1925 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1926 for more information.</P>
1928 <H2><A NAME="ss11.107">11.107</A> <A HREF="adminmanual.html#toc11.107">set/privilege (9)</A>
1931 <P><CODE><B>set/privilege <n> <call> [<call> ...]</B> Set the privilege level on a call</CODE></P>
1933 <P>Set the privilege level on a callsign. The privilege levels that pertain
1934 to commands are as default:-</P>
1939 1 - allow remote nodes normal user RCMDs
1940 5 - various privileged commands (including shutdown, but not disc-
1941 connect), the normal level for another node.
1942 8 - more privileged commands (including disconnect)
1943 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1946 </CODE></BLOCKQUOTE>
1948 <P>If you are a sysop and you come in as a normal user on a remote connection
1949 your privilege will automatically be set to 0.</P>
1951 <H2><A NAME="ss11.108">11.108</A> <A HREF="adminmanual.html#toc11.108">set/spider (5)</A>
1954 <P><CODE><B>set/spider <node_call> [<node_call> ...]</B> Make
1955 the node_call a DXSpider type node</CODE></P>
1957 <P>Set the node_call as a DXSpider type node</P>
1959 <H2><A NAME="ss11.109">11.109</A> <A HREF="adminmanual.html#toc11.109">set/sys_qra (9)</A>
1962 <P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA locator</CODE></P>
1964 <H2><A NAME="ss11.110">11.110</A> <A HREF="adminmanual.html#toc11.110">set/qra (0)</A>
1967 <P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE></P>
1969 <P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
1970 done a SET/LOCATION then your latitude and longitude will be set roughly
1971 correctly (assuming your locator is correct ;-). For example:-</P>
1977 </CODE></BLOCKQUOTE>
1980 <H2><A NAME="ss11.111">11.111</A> <A HREF="adminmanual.html#toc11.111">set/qth (0)</A>
1983 <P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE></P>
1985 <P>Tell the system where your are. For example:-</P>
1989 set/qth East Dereham, Norfolk
1991 </CODE></BLOCKQUOTE>
1994 <H2><A NAME="ss11.112">11.112</A> <A HREF="adminmanual.html#toc11.112">set/register (9)</A>
1997 <P><CODE><B>set/register <call></B> Mark a user as registered</CODE></P>
1999 <P>Registration is a concept that you can switch on by executing the</P>
2000 <P>set/var $main::regreq = 1 </P>
2001 <P>command (usually in your startup file)</P>
2002 <P>If a user is NOT registered then, firstly, instead of the normal
2003 motd file (/spider/data/motd) being sent to the user at startup, the
2004 user is sent the motd_nor file instead. Secondly, the non registered
2005 user only has READ-ONLY access to the node. The non-registered user
2006 cannot use DX, ANN etc. </P>
2007 <P>The only exception to this is that a non-registered user can TALK or
2008 SEND messages to the sysop.</P>
2009 <P>To unset a user use the 'unset/register' command</P>
2011 <H2><A NAME="ss11.113">11.113</A> <A HREF="adminmanual.html#toc11.113">set/talk (0)</A>
2014 <P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE></P>
2016 <P>Allow talk messages to arrive at your console. You can switch off
2017 talks with the <EM>unset/talk</EM> command.</P>
2019 <H2><A NAME="ss11.114">11.114</A> <A HREF="adminmanual.html#toc11.114">set/wcy (0)</A>
2022 <P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE></P>
2024 <P>Allow WCY information to be seen at your console. You can switch off
2025 WCY messages with the <EM>unset/wcy</EM> command.</P>
2027 <H2><A NAME="ss11.115">11.115</A> <A HREF="adminmanual.html#toc11.115">set/wwv (0)</A>
2030 <P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE></P>
2032 <P>Allow WWV information to be seen at your console. You can switch off
2033 WWV messages with the <EM>unset/wwv</EM> command.</P>
2035 <H2><A NAME="ss11.116">11.116</A> <A HREF="adminmanual.html#toc11.116">set/wx (0)</A>
2038 <P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE></P>
2040 <P>Allow WX information to be seen at your console. You can switch off
2041 WX messages with the <EM>unset/wx</EM> command.</P>
2043 <H2><A NAME="ss11.117">11.117</A> <A HREF="adminmanual.html#toc11.117">show/baddx (1)</A>
2046 <P><CODE><B>show/baddx</B>Show all the bad dx calls in the system</CODE></P>
2048 <P>Display all the bad dx callsigns in the system, see SET/BADDX
2049 for more information.</P>
2051 <H2><A NAME="ss11.118">11.118</A> <A HREF="adminmanual.html#toc11.118">show/badnode (6)</A>
2054 <P><CODE><B>show/badnode</B> Show all the bad nodes in the system</CODE></P>
2056 <P>Display all the bad node callsigns in the system, see SET/BADNODE
2057 for more information.</P>
2059 <H2><A NAME="ss11.119">11.119</A> <A HREF="adminmanual.html#toc11.119">show/badspotter (1)</A>
2062 <P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE></P>
2064 <P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
2065 for more information.</P>
2067 <H2><A NAME="ss11.120">11.120</A> <A HREF="adminmanual.html#toc11.120">show/badword (1)</A>
2070 <P><CODE><B>show/badword</B> Show all the bad words in the system</CODE></P>
2072 <P>Display all the bad words in the system, see SET/BADWORD
2073 for more information.</P>
2075 <H2><A NAME="ss11.121">11.121</A> <A HREF="adminmanual.html#toc11.121">show/configuration (0)</A>
2078 <P><CODE><B>show/configuration [<node>]</B> Show all visible nodes and their users</CODE></P>
2080 <P>This command allows you to see all the users that can be seen
2081 and the nodes to which they are connected. With the optional <EM>node</EM>,
2082 you can specify a particular node to look at.</P>
2083 <P>This command is normally abbreviated to: sh/c</P>
2084 <P>BE WARNED: the list that is returned can be VERY long</P>
2086 <H2><A NAME="ss11.122">11.122</A> <A HREF="adminmanual.html#toc11.122">show/configuration/node (0)</A>
2089 <P><CODE><B>show/configuration/node</B> Show all the nodes connected</CODE></P>
2091 <P>Show all the nodes connected locally and the nodes they have connected.</P>
2093 <H2><A NAME="ss11.123">11.123</A> <A HREF="adminmanual.html#toc11.123">show/connect (1)</A>
2096 <P><CODE><B>show/connect</B> Show all the active connections</CODE></P>
2098 <P>This command shows information on all the active connections known to
2099 the node. This command gives slightly more information than WHO.</P>
2101 <H2><A NAME="ss11.124">11.124</A> <A HREF="adminmanual.html#toc11.124">show/date (0)</A>
2104 <P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
2105 the local time</CODE></P>
2107 <P>This is very nearly the same as SHOW/TIME, the only difference the format
2108 of the date string if no arguments are given.</P>
2109 <P>If no prefixes or callsigns are given then this command returns the local
2110 time and UTC as the computer has it right now. If you give some prefixes
2111 then it will show UTC and UTC + the local offset (not including DST) at
2112 the prefixes or callsigns that you specify.</P>
2114 <H2><A NAME="ss11.125">11.125</A> <A HREF="adminmanual.html#toc11.125">show/debug (9)</A>
2117 <P><CODE><B>show/debug</B> Show what levels of debug you are logging</CODE></P>
2119 <P>The levels can be set with <EM>set/debug</EM></P>
2121 <H2><A NAME="ss11.126">11.126</A> <A HREF="adminmanual.html#toc11.126">show/dx (0)</A>
2124 <P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE></P>
2126 <P>If you just type SHOW/DX you will get the last so many spots
2127 (sysop configurable, but usually 10).</P>
2128 <P>In addition you can add any number of these options in very nearly
2129 any order to the basic SHOW/DX command, they are:-</P>
2134 on <band> - eg 160m 20m 2m 23cm 6mm
2135 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
2137 <number> - the number of spots you want
2138 <from>-<to> - <from> spot no <to> spot no in
2141 <prefix> - for a spotted callsign beginning with <prefix>
2142 *<suffix> - for a spotted callsign ending in <suffix>
2143 *<string>* - for a spotted callsign containing <string>
2145 day <number> - starting <number> days ago
2146 day <from>-<to> - <from> days <to> days ago
2148 info <text> - any spots containing <text> in the info or remarks
2150 by <call> - any spots spotted by <call> (spotter <call>
2153 qsl - this automatically looks for any qsl info on the call
2154 held in the spot database.
2156 iota [<iota>] - If the iota island number is missing it will
2157 look for the string iota and anything which looks like
2158 an iota island number. If you specify then it will look
2161 qra [<locator>] - this will look for the specific locator if
2162 you specify one or else anything that looks like a locator.
2164 </CODE></BLOCKQUOTE>
2172 SH/DX on 20m info iota
2173 SH/DX 9a on vhf day 30
2179 </CODE></BLOCKQUOTE>
2182 <H2><A NAME="ss11.127">11.127</A> <A HREF="adminmanual.html#toc11.127">show/dxcc (0)</A>
2185 <P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE></P>
2187 <P>This command takes the <prefix> (which can be a full or partial
2188 callsign if desired), looks up which internal country number it is
2189 and then displays all the spots as per SH/DX for that country.</P>
2190 <P>The options for SHOW/DX also apply to this command.
2197 SH/DXCC W on 20m info iota
2199 </CODE></BLOCKQUOTE>
2202 <H2><A NAME="ss11.128">11.128</A> <A HREF="adminmanual.html#toc11.128">sh/dxstats (0)</A>
2205 <P><CODE><B>sh/dxstats</B> Show the DX Statistics for last 31 days</CODE></P>
2207 <P>Show the total DX spots for the last 31 days</P>
2210 <H2><A NAME="ss11.129">11.129</A> <A HREF="adminmanual.html#toc11.129">show/files (0)</A>
2213 <P><CODE><B>show/files [<filearea> [<string>]]</B> List
2214 the contents of a filearea</CODE></P>
2216 <P>SHOW/FILES on its own will show you a list of the various fileareas
2217 available on the system. To see the contents of a particular file
2222 SH/FILES <filearea>
2224 </CODE></BLOCKQUOTE>
2226 <P>where <filearea> is the name of the filearea you want to see the
2228 <P>You can also use shell globbing characters like '*' and '?' in a
2229 string to see a selection of files in a filearea eg:-</P>
2233 SH/FILES bulletins arld*
2235 </CODE></BLOCKQUOTE>
2237 <P>See also TYPE - to see the contents of a file.</P>
2239 <H2><A NAME="ss11.130">11.130</A> <A HREF="adminmanual.html#toc11.130">show/filter (0)</A>
2242 <P><CODE><B>show/filter</B> Show the filters you have set</CODE></P>
2244 <P>Show the contents of all the filters that are set by you. This command
2245 displays all the filters set - for all the various categories.</P>
2247 <H2><A NAME="ss11.131">11.131</A> <A HREF="adminmanual.html#toc11.131">show/filter (extended for sysops) (5)</A>
2250 <P><CODE><B>show/filter <callsign></B> Show the filters set by <callsign></CODE></P>
2252 <P>A sysop can look at any filters that have been set.</P>
2254 <H2><A NAME="ss11.132">11.132</A> <A HREF="adminmanual.html#toc11.132">show/hfstats (0)</A>
2257 <P><CODE><B>show/hfstats</B> Show the HF DX Statistics for last 31 days</CODE></P>
2259 <P>Show the HF DX spots breakdown by band for the last 31 days</P>
2261 <H2><A NAME="ss11.133">11.133</A> <A HREF="adminmanual.html#toc11.133">show/hftable (0)</A>
2264 <P><CODE><B>show/hftable</B> Show the HF DX Spotter Table for your country</CODE></P>
2266 <P>Show the HF DX Spotter table for your country for the last 31 days</P>
2268 <H2><A NAME="ss11.134">11.134</A> <A HREF="adminmanual.html#toc11.134">show/hops (8)</A>
2271 <P><CODE><B>show/hops <node_call> [ann|spots|wcy|wwv|]</B> Show the hop counts for a node</CODE></P>
2273 <P>This command shows the hop counts set up for a node. You can specify
2274 which category you want to see. If you leave the category out then
2275 all the categories will be listed.</P>
2277 <H2><A NAME="ss11.135">11.135</A> <A HREF="adminmanual.html#toc11.135">show/isolate (1)</A>
2280 <P><CODE><B>show/isolate</B> Show a list of isolated nodes</CODE></P>
2282 <P>Show which nodes are currently set to be isolated.</P>
2284 <H2><A NAME="ss11.136">11.136</A> <A HREF="adminmanual.html#toc11.136">show/lockout (9)</A>
2287 <P><CODE><B>show/lockout</B> Show a list of excluded callsigns</CODE></P>
2289 <P>Show a list of callsigns that have been excluded (locked out) of the
2290 cluster locally with the <EM>set/lockout</EM> command</P>
2292 <H2><A NAME="ss11.137">11.137</A> <A HREF="adminmanual.html#toc11.137">show/log (8)</A>
2295 <P><CODE><B>show/log [<callsign>]</B> Show excerpts from the system log</CODE></P>
2297 <P>This command outputs a short section of the system log. On its own
2298 it will output a general logfile. With the optional callsign it will
2299 show output from the log associated with that callsign.</P>
2301 <H2><A NAME="ss11.138">11.138</A> <A HREF="adminmanual.html#toc11.138">show/moon (0)</A>
2304 <P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
2305 rise and set times</CODE></P>
2307 <P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
2308 together with the azimuth and elevation of the sun currently at those
2310 <P>If you don't specify any prefixes or callsigns, it will show the times for
2311 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2312 together with the current azimuth and elevation.</P>
2313 <P>In addition, it will show the gain or loss dB relative to the nominal
2314 distance of 385,000Km due to the ellipsoidal nature of the orbit.</P>
2315 <P>If all else fails it will show the Moonrise and set times for the node
2316 that you are connected to. </P>
2317 <P>For example:-</P>
2324 </CODE></BLOCKQUOTE>
2327 <H2><A NAME="ss11.139">11.139</A> <A HREF="adminmanual.html#toc11.139">show/muf (0)</A>
2330 <P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
2331 the likely propagation to <prefix></CODE></P>
2333 <P>This command allow you to estimate the likelihood of you contacting
2334 a station with the prefix you have specified. The output assumes a modest
2335 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)</P>
2336 <P>The result predicts the most likely operating frequencies and signal
2337 levels for high frequency (shortwave) radio propagation paths on
2338 specified days of the year and hours of the day. It is most useful for
2339 paths between 250 km and 6000 km, but can be used with reduced accuracy
2340 for paths shorter or longer than this.</P>
2341 <P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
2342 used to predict the MUF given the predicted flux, day of the year,
2343 hour of the day and geographic coordinates of the transmitter and
2344 receiver. This routine is reasonably accurate for the purposes here,
2345 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
2346 than the programs used by major shortwave broadcasting organizations,
2347 such as the Voice of America.</P>
2348 <P>The command will display some header information detailing its
2349 assumptions, together with the locations, latitude and longitudes and
2350 bearings. It will then show UTC (UT), local time at the other end
2351 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
2352 (Zen) and the likely signal strengths. Then for each frequency for which
2353 the system thinks there is a likelihood of a circuit it prints a value.</P>
2354 <P>The value is currently a likely S meter reading based on the conventional
2355 6dB / S point scale. If the value has a '+' appended it means that it is
2356 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
2357 there is likely to be much fading and by an 's' that the signal is likely
2359 <P>By default SHOW/MUF will show the next two hours worth of data. You
2360 can specify anything up to 24 hours worth of data by appending the no of
2361 hours required after the prefix. For example:-</P>
2367 </CODE></BLOCKQUOTE>
2373 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
2374 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
2375 Location Lat / Long Azim
2376 East Dereham, Norfolk 52 41 N 0 57 E 47
2377 United-States-W 43 0 N 87 54 W 299
2378 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
2379 18 23 11.5 -35 mS0+ mS2 S3
2380 19 0 11.2 -41 mS0+ mS2 S3
2382 </CODE></BLOCKQUOTE>
2384 <P>indicating that you will have weak, fading circuits on top band and
2385 80m but usable signals on 40m (about S3).</P>
2392 </CODE></BLOCKQUOTE>
2394 <P>will get you the above display, but with the next 24 hours worth of
2395 propagation data.</P>
2402 </CODE></BLOCKQUOTE>
2404 <P>Gives you an estimate of the long path propagation characterics. It
2405 should be noted that the figures will probably not be very useful, nor
2406 terrible accurate, but it is included for completeness.</P>
2408 <H2><A NAME="ss11.140">11.140</A> <A HREF="adminmanual.html#toc11.140">show/newconfiguration (0)</A>
2411 <P><CODE><B>show/newconfiguration [<node>]</B> Show all the nodes and users visible</CODE></P>
2413 <P>This command allows you to see all the users that can be seen
2414 and the nodes to which they are connected. </P>
2415 <P>This command produces essentially the same information as
2416 SHOW/CONFIGURATION except that it shows all the duplication of
2417 any routes that might be present It also uses a different format
2418 which may not take up quite as much space if you don't have any
2420 <P>BE WARNED: the list that is returned can be VERY long</P>
2422 <H2><A NAME="ss11.141">11.141</A> <A HREF="adminmanual.html#toc11.141">show/newconfiguration/node (0)</A>
2425 <P><CODE><B>show/newconfiguration/node</B> Show all the nodes connected locally</CODE></P>
2427 <P>Show all the nodes connected to this node in the new format.</P>
2429 <H2><A NAME="ss11.142">11.142</A> <A HREF="adminmanual.html#toc11.142">show/node (1)</A>
2432 <P><CODE><B>show/node [<node_call> ...]</B> Show the type and version
2433 number of nodes</CODE></P>
2435 <P>Show the type and version (if connected) of the nodes specified on the
2436 command line. If no callsigns are specified then a sorted list of all
2437 the non-user callsigns known to the system will be displayed.</P>
2439 <H2><A NAME="ss11.143">11.143</A> <A HREF="adminmanual.html#toc11.143">show/prefix (0)</A>
2442 <P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE></P>
2444 <P>This command takes the <callsign> (which can be a full or partial
2445 callsign or a prefix), looks up which internal country number
2446 it is and then displays all the relevant prefixes for that country
2447 together with the internal country no, the CQ and ITU regions. </P>
2448 <P>See also SHOW/DXCC</P>
2451 <H2><A NAME="ss11.144">11.144</A> <A HREF="adminmanual.html#toc11.144">show/program (5)</A>
2454 <P><CODE><B>show/program</B> Show the locations of all the included program modules</CODE></P>
2456 <P>Show the name and location where every program module was load from. This
2457 is useful for checking where you think you have loaded a .pm file from.</P>
2459 <H2><A NAME="ss11.145">11.145</A> <A HREF="adminmanual.html#toc11.145">show/qra (0)</A>
2462 <P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
2463 between locators<BR>
2464 <B>show/qra <lat> <long></B> Convert latitude and longitude to a locator</CODE></P>
2466 <P>This is a multipurpose command that allows you either to calculate the
2467 distance and bearing between two locators or (if only one locator is
2468 given on the command line) the distance and beraing from your station
2469 to the locator. For example:-</P>
2476 </CODE></BLOCKQUOTE>
2478 <P>The first example will show the distance and bearing to the locator from
2479 yourself, the second example will calculate the distance and bearing from
2480 the first locator to the second. You can use 4 or 6 character locators.</P>
2481 <P>It is also possible to convert a latitude and longitude to a locator by
2482 using this command with a latitude and longitude as an argument, for
2487 SH/QRA 52 41 N 0 58 E
2489 </CODE></BLOCKQUOTE>
2492 <H2><A NAME="ss11.146">11.146</A> <A HREF="adminmanual.html#toc11.146">show/qrz (0)</A>
2495 <P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE></P>
2497 <P>This command queries the QRZ callbook server on the internet
2498 and returns any information available for that callsign. This service
2499 is provided for users of this software by http://www.qrz.com </P>
2501 <H2><A NAME="ss11.147">11.147</A> <A HREF="adminmanual.html#toc11.147">show/registered (9)</A>
2504 <P><CODE><B>show/registered [<prefix>[</B> Show the registered users</CODE></P>
2506 <H2><A NAME="ss11.148">11.148</A> <A HREF="adminmanual.html#toc11.148">show/route (0)</A>
2509 <P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE></P>
2511 <P>This command allows you to see to which node the callsigns specified are
2512 connected. It is a sort of inverse sh/config.</P>
2518 </CODE></BLOCKQUOTE>
2521 <H2><A NAME="ss11.149">11.149</A> <A HREF="adminmanual.html#toc11.149">show/satellite (0)</A>
2524 <P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
2525 Show satellite tracking data</CODE></P>
2527 <P>Show the tracking data from your location to the satellite of your choice
2528 from now on for the next few hours.</P>
2529 <P>If you use this command without a satellite name it will display a list
2530 of all the satellites known currently to the system. </P>
2531 <P>If you give a name then you can obtain tracking data of all the passes
2532 that start and finish 5 degrees below the horizon. As default it will
2533 give information for the next three hours for every five minute period.</P>
2534 <P>You can alter the number of hours and the step size, within certain
2536 <P>Each pass in a period is separated with a row of '-----' characters</P>
2537 <P>So for example:-</P>
2542 SH/SAT FENGYUN1 12 2
2544 </CODE></BLOCKQUOTE>
2547 <H2><A NAME="ss11.150">11.150</A> <A HREF="adminmanual.html#toc11.150">show/sun (0)</A>
2550 <P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
2551 sun rise and set times</CODE></P>
2553 <P>Show the sun rise and set times for a (list of) prefixes or callsigns,
2554 together with the azimuth and elevation of the sun currently at those
2556 <P>If you don't specify any prefixes or callsigns, it will show the times for
2557 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2558 together with the current azimuth and elevation.</P>
2559 <P>If all else fails it will show the sunrise and set times for the node
2560 that you are connected to. </P>
2561 <P>For example:-</P>
2566 SH/SUN G1TLH K9CW ZS
2568 </CODE></BLOCKQUOTE>
2571 <H2><A NAME="ss11.151">11.151</A> <A HREF="adminmanual.html#toc11.151">show/time (0)</A>
2574 <P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
2575 the local time</CODE></P>
2577 <P>If no prefixes or callsigns are given then this command returns the local
2578 time and UTC as the computer has it right now. If you give some prefixes
2579 then it will show UTC and UTC + the local offset (not including DST) at
2580 the prefixes or callsigns that you specify.</P>
2582 <H2><A NAME="ss11.152">11.152</A> <A HREF="adminmanual.html#toc11.152">show/vhfstats (0)</A>
2585 <P><CODE><B>show/vhfstats</B> Show the VHF DX Statistics for last 31 days</CODE></P>
2587 <P>Show the VHF DX spots breakdown by band for the last 31 days</P>
2589 <H2><A NAME="ss11.153">11.153</A> <A HREF="adminmanual.html#toc11.153">show/vhftable (0)</A>
2592 <P><CODE><B>show/vhftable</B> Show the VHF DX Spotter Table for your country</CODE></P>
2594 <P>Show the VHF DX Spotter table for your country for the last 31 days</P>
2596 <H2><A NAME="ss11.154">11.154</A> <A HREF="adminmanual.html#toc11.154">show/wcy (0)</A>
2599 <P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
2600 <B>show/wcy <n></B> Show the last <n> WCY broadcasts</CODE></P>
2602 <P>Display the most recent WCY information that has been received by the system</P>
2604 <H2><A NAME="ss11.155">11.155</A> <A HREF="adminmanual.html#toc11.155">show/wwv (0)</A>
2607 <P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
2608 <B>show/wwv <n></B> Show the last <n> WWV broadcasts</CODE></P>
2610 <P>Display the most recent WWV information that has been received by the system</P>
2613 <H2><A NAME="ss11.156">11.156</A> <A HREF="adminmanual.html#toc11.156">shutdown (5)</A>
2616 <P><CODE><B>shutdown</B> Shutdown the cluster</CODE></P>
2618 <P>Shutdown the cluster and disconnect all the users. If you have Spider
2619 set to respawn in /etc/inittab it will of course restart.</P>
2621 <H2><A NAME="ss11.157">11.157</A> <A HREF="adminmanual.html#toc11.157">spoof (9)</A>
2624 <P><CODE><B>spoof <callsign> <command></B> Run commands as another user</CODE></P>
2626 <P>This is a very simple yet powerful command for the sysop. It allows you to
2627 issue commands as if you were a different user. This is very useful for the
2628 kind of things that users seem to always get wrong.. like home_node for
2631 <H2><A NAME="ss11.158">11.158</A> <A HREF="adminmanual.html#toc11.158">stat/db (5)</A>
2634 <P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE></P>
2636 <P>Show the internal status of a database descriptor.</P>
2637 <P>Depending on your privilege level you will see more or less information.
2638 This command is unlikely to be of much use to anyone other than a sysop.</P>
2640 <H2><A NAME="ss11.159">11.159</A> <A HREF="adminmanual.html#toc11.159">stat/channel (5)</A>
2643 <P><CODE><B>stat/channel <callsign></B> Show the status of a channel on the cluster</CODE></P>
2645 <P>Show the internal status of the channel object either for the channel that
2646 you are on or else for the callsign that you asked for.</P>
2647 <P>Only the fields that are defined (in perl term) will be displayed.</P>
2649 <H2><A NAME="ss11.160">11.160</A> <A HREF="adminmanual.html#toc11.160">stat/msg (5)</A>
2652 <P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE></P>
2654 <P>This command shows the internal status of a message and includes information
2655 such as to whom it has been forwarded, its size, origin etc etc.</P>
2657 <P>If no message number is given then the status of the message system is
2660 <H2><A NAME="ss11.161">11.161</A> <A HREF="adminmanual.html#toc11.161">stat/route_node (5)</A>
2663 <P><CODE><B>stat/route_node <callsign></B> Show the data in a Route::Node object</CODE></P>
2665 <H2><A NAME="ss11.162">11.162</A> <A HREF="adminmanual.html#toc11.162">stat/route_user (5)</A>
2668 <P><CODE><B>stat/route_user <callsign></B> Show the data in a Route::User object</CODE></P>
2670 <H2><A NAME="ss11.163">11.163</A> <A HREF="adminmanual.html#toc11.163">stat/user (5)</A>
2673 <P><CODE><B>stat/user <callsign></B> Show the full status of a user</CODE></P>
2675 <P>Shows the full contents of a user record including all the secret flags
2677 <P>Only the fields that are defined (in perl term) will be displayed.</P>
2679 <H2><A NAME="ss11.164">11.164</A> <A HREF="adminmanual.html#toc11.164">sysop (0)</A>
2682 <P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE></P>
2684 <P>The system automatically reduces your privilege level to that of a
2685 normal user if you login in remotely. This command allows you to
2686 regain your normal privilege level. It uses the normal system: five
2687 numbers are returned that are indexes into the character array that is
2688 your assigned password (see SET/PASSWORD). The indexes start from
2690 <P>You are expected to return a string which contains the characters
2691 required in the correct order. You may intersperse those characters
2692 with others to obscure your reply for any watchers. For example (and
2693 these values are for explanation :-):</P>
2697 password = 012345678901234567890123456789
2701 </CODE></BLOCKQUOTE>
2707 aa2bbbb0ccc5ddd7xxx3n
2711 </CODE></BLOCKQUOTE>
2713 <P>They will all match. If there is no password you will still be offered
2714 numbers but nothing will happen when you input a string. Any match is
2717 <H2><A NAME="ss11.165">11.165</A> <A HREF="adminmanual.html#toc11.165">talk (0)</A>
2720 <P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
2721 <B>talk <callsign> <text></B> Send a text message to <callsign><BR>
2722 <B>talk <callsign> > <node_call> [<text>]</B>
2723 Send a text message to <callsign> via <node_call></CODE></P>
2725 <P>Send a short message to any other station that is visible on the cluster
2726 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2727 command, they don't have to be connected locally.</P>
2728 <P>The second form of TALK is used when other cluster nodes are connected
2729 with restricted information. This usually means that they don't send
2730 the user information usually associated with logging on and off the cluster.</P>
2731 <P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
2732 see GB7TLH in the SH/C list but with no users, then you would use the
2733 second form of the talk message.</P>
2734 <P>If you want to have a ragchew with someone you can leave the text message
2735 out and the system will go into 'Talk' mode. What this means is that a
2736 short message is sent to the recipient telling them that you are in a 'Talking'
2737 frame of mind and then you just type - everything you send will go to the
2738 station that you asked for. </P>
2739 <P>All the usual announcements, spots and so on will still come out on your
2741 <P>If you want to do something (such as send a spot) you precede the normal
2742 command with a '/' character, eg:-</P>
2746 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2749 </CODE></BLOCKQUOTE>
2751 <P>To leave talk mode type:</P>
2757 </CODE></BLOCKQUOTE>
2760 <H2><A NAME="ss11.166">11.166</A> <A HREF="adminmanual.html#toc11.166">type (0)</A>
2763 <P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE></P>
2765 <P>Type out the contents of a file in a filearea. So, for example, in
2766 filearea 'bulletins' you want to look at file 'arld051' you would
2771 TYPE bulletins/arld051
2773 </CODE></BLOCKQUOTE>
2775 <P>See also SHOW/FILES to see what fileareas are available and a
2776 list of content.</P>
2778 <H2><A NAME="ss11.167">11.167</A> <A HREF="adminmanual.html#toc11.167">who (0)</A>
2781 <P><CODE><B>who</B> Show who is physically connected locally</CODE></P>
2783 <P>This is a quick listing that shows which callsigns are connected and
2784 what sort of connection they have</P>
2786 <H2><A NAME="ss11.168">11.168</A> <A HREF="adminmanual.html#toc11.168">wx (0)</A>
2789 <P><CODE><B>wx <text></B> Send a weather message to local users<BR>
2790 <B>wx full <text> </B> Send a weather message to all cluster users</CODE></P>
2792 <P>Weather messages can sometimes be useful if you are experiencing an extreme
2793 that may indicate enhanced conditions</P>
2795 <H2><A NAME="ss11.169">11.169</A> <A HREF="adminmanual.html#toc11.169">wx (enhanced for sysops) (5)</A>
2798 <P><CODE><B>wx sysop <text></B> Send a weather message to other clusters only</CODE></P>
2800 <P>Send a weather message only to other cluster nodes and not to general users.</P>
2806 <A HREF="adminmanual-10.html">Previous</A>
2807 <A HREF="adminmanual.html#toc11">Contents</A>