1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
4 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
5 <TITLE>The DXSpider Administration Manual v1.50: The DXSpider command set</TITLE>
6 <LINK HREF="adminmanual-9.html" REL=previous>
7 <LINK HREF="adminmanual.html#toc10" REL=contents>
8 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="adminmanual-9.html">Previous</A>
13 <A HREF="adminmanual.html#toc10">Contents</A>
15 <H2><A NAME="s10">10. 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="ss10.1">10.1 accept/announce (0)</A>
26 <P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter
27 line for announce</CODE>
29 <P>Create an 'accept this announce' line for a filter.
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.
33 <P>You can use any of the following things in this line:-
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)
56 acc/ann 2 by_zone 14,15,16
57 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
67 <P>This filter would only allow announces that were posted buy UK stations.
68 You can use the tag 'all' to accept everything eg:
75 <P>but this probably for advanced users...
77 <H2><A NAME="ss10.2">10.2 accept/announce (extended for sysops) (8)</A>
80 <P><CODE><B>accept/announce <call> [input] [0-9]<pattern></B> Announce filter sysop version</CODE>
82 <P>This version allows a sysop to set a filter for a callsign as well as the
83 default for nodes and users eg:-
88 accept/ann input node_default by G,M,2
89 accept/ann user_default by G,M,2
93 <H2><A NAME="ss10.3">10.3 accept/route (8)</A>
96 <P><CODE><B>accept/route <call> [0-9] <pattern></B> Set an 'accept' filter line for routing</CODE>
98 <P>Create an 'accept this routing PC Protocol' line for a filter.
100 <P>An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
101 it is passed thru that interface. See HELP FILTERING for more info. Please read this
102 to understand how filters work - it will save a lot of grief later on.
104 <P>You can use any of the following things in this line:-
108 call <prefixes> the callsign of the thingy
109 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
110 call_itu <numbers>
111 call_zone <numbers>
112 origin <prefixes> really the interface it came in on
113 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
114 origin_itu <numbers>
115 origin_zone <numbers>
123 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
124 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
128 <P>You can use the tag 'all' to accept everything eg:
136 <H2><A NAME="ss10.4">10.4 accept/spots (0)</A>
139 <P><CODE><B>accept/spots [0-9] <pattern></B> Set an accept filter line for spots</CODE>
141 <P>Create an 'accept this spot' line for a filter.
143 <P>An accept filter line means that if the spot matches this filter it is
144 passed onto the user. See HELP FILTERS for more info. Please read this
145 to understand how filters work - it will save a lot of grief later on.
146 <P>You can use any of the following things in this line:-
150 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
151 on <range> same as 'freq'
152 call <prefixes> eg: G,PA,HB9
153 info <string> eg: iota or qsl
155 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
156 call_itu <numbers>
157 call_zone <numbers>
162 channel <prefixes>
166 <P>For frequencies, you can use any of the band names defined in
167 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
168 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
169 this is more efficient than saying simply: freq HF (but don't get
170 too hung up about that)
176 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
179 <P>You can use the tag 'all' to accept everything, eg:
186 <P>but this probably for advanced users...
188 <H2><A NAME="ss10.5">10.5 accept/spots (extended for sysops) (8)</A>
191 <P><CODE><B>accept/spots <call> [input] [0-9] <pattern></B> Spot filter sysop version</CODE>
193 <P>This version allows a sysop to set a filter for a callsign as well as the
194 default for nodes and users eg:-
198 accept/spot db0sue-7 1 by_zone 14,15,16
199 accept/spot node_default all
200 set/hops node_default 10
202 accept/spot user_default by G,M,2
206 <H2><A NAME="ss10.6">10.6 accept/wcy (0)</A>
209 <P><CODE><B>accept/wcy [0-9] <pattern></B> set an accept WCY filter</CODE>
211 <P>It is unlikely that you will want to do this, but if you do then you can
212 filter on the following fields:-
216 by <prefixes> eg: G,M,2
218 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
219 origin_itu <numbers>
220 origin_zone <numbers>
224 channel <prefixes>
228 <P>There are no examples because WCY Broadcasts only come from one place and
229 you either want them or not (see UNSET/WCY if you don't want them).
230 <P>This command is really provided for future use.
231 <P>See HELP FILTER for information.
233 <H2><A NAME="ss10.7">10.7 accept/wcy (extended for sysops) (8)</A>
236 <P><CODE><B>accept/wcy <call> [input] [0-9] <pattern></B>
237 WCY filter sysop version</CODE>
239 <P>This version allows a sysop to set a filter for a callsign as well as the
240 default for nodes and users eg:-
244 accept/wcy node_default all
245 set/hops node_default 10
249 <H2><A NAME="ss10.8">10.8 accept/wwv (0)</A>
252 <P><CODE><B>accept/wwv [0-9] <pattern></B> Set an accept WWV filter</CODE>
254 <P>It is unlikely that you will want to do this, but if you do then you can
255 filter on the following fields:-
259 by <prefixes> eg: G,M,2
261 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
262 origin_itu <numbers>
263 origin_zone <numbers>
267 channel <prefixes>
277 <P>is probably the only useful thing to do (which will only show WWV broadcasts
278 by stations in the US).
279 <P>See HELP FILTER for information.
281 <H2><A NAME="ss10.9">10.9 accept/wwv (extended for sysops) (8)</A>
284 <P><CODE><B>accept/wwv <call> [input] [0-9] <pattern></B>
285 WWV filter sysop version</CODE>
287 <P>This version allows a sysop to set a filter for a callsign as well as the
288 default for nodes and users eg:-
292 accept/wwv db0sue-7 1 by_zone 4
293 accept/wwv node_default all
294 set/hops node_default 10
296 accept/wwv user_default by W,K
300 <H2><A NAME="ss10.10">10.10 announce (0)</A>
303 <P><CODE><B>announce <text></B> Send an announcement to local users</CODE>
305 <P>Send an announcement to LOCAL users only, where <text> is the text
306 of the announcement you wish to broadcast. If you do not wish to receive
307 announces, use the <EM>set/noannounce</EM> command. Any announces made by
308 a sysop will override set/noannounce.
310 <H2><A NAME="ss10.11">10.11 announce full (0)</A>
313 <P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE>
315 <P>This command will send your announcement across the whole cluster
319 <H2><A NAME="ss10.12">10.12 announce sysop (5)</A>
322 <P><CODE><B>announce sysop <text></B></CODE>
324 <P>Send an announcement to Sysops only
326 <H2><A NAME="ss10.13">10.13 apropos (0)</A>
329 <P><CODE><B>apropos <string></B> Search the help database</CODE>
331 <P>Search the help database for <string> (it isn't case sensitive),
332 and print the names of all the commands that may be relevant.
334 <H2><A NAME="ss10.14">10.14 bye (0)</A>
337 <P><CODE><B>bye</B> Exit from the cluster</CODE>
339 <P>This will disconnect you from the cluster
341 <H2><A NAME="ss10.15">10.15 catchup (5)</A>
344 <P><CODE><B>catchup <node_call> All|[<msgno> ...]</B> Mark a message as sent</CODE>
346 <P>When you send messages the fact that you have forwarded it to another node
347 is remembered so that it isn't sent again. When you have a new partner
348 node and you add their callsign to your /spider/msg/forward.pl file, all
349 outstanding non-private messages will be forwarded to them. This may well
350 be ALL the non-private messages. You can prevent this by using these
356 catchup GB7DJK 300 301 302 303 500-510
359 <P>and to undo what you have just done:-
364 uncatchup GB7DJK 300 301 302 303 500-510
367 <P>which will arrange for them to be forward candidates again.
368 <P>Order is not important.
370 <H2><A NAME="ss10.16">10.16 clear/announce (8)</A>
373 <P><CODE><B>clear/announce [input] <callsign> [0-9|all]</B> Clear an announce filter line</CODE>
375 <P>A sysop can clear an input or normal output filter for a user or the
376 node_default or user_default.
378 <H2><A NAME="ss10.17">10.17 clear/route (8)</A>
381 <P><CODE><B>clear/route [input] ^lt;callsign> [0-9|all]</B> Clear a route filter line</CODE>
383 <P>This command allows you to clear (remove) a line in a route filter or to
384 remove the whole filter.
385 <P>see CLEAR/SPOTS for a more detailed explanation.
386 <P>A sysop can clear an input or normal output filter for a user or the
387 node_default or user_default.
389 <H2><A NAME="ss10.18">10.18 clear/spots (0)</A>
392 <P><CODE><B>clear/spots [1|all]</B> Clear a spot filter line</CODE>
394 <P>This command allows you to clear (remove) a line in a spot filter or to
395 remove the whole filter.
396 <P>If you have a filter:-
401 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
411 <P>you will be left with:-
415 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
425 <P>the filter will be completely removed.
427 <H2><A NAME="ss10.19">10.19 clear/spots (extended for sysops) (8)</A>
430 <P><CODE><B>clear/spots [input] <callsign> [0-9|all]</B> Clear a spot filter line</CODE>
432 <P>A sysop can clear an input or normal output filter for a user or the
433 node_default or user_default.
435 <H2><A NAME="ss10.20">10.20 clear/wcy (0)</A>
438 <P><CODE><B>clear/wcy [1|all]</B> Clear a WCY filter line</CODE>
440 <P>This command allows you to clear (remove) a line in a WCY filter or to
441 remove the whole filter.
442 <P>see CLEAR/SPOTS for a more detailed explanation.
444 <H2><A NAME="ss10.21">10.21 clear/wcy (extended for sysops) (8)</A>
447 <P><CODE><B>clear/wcy [input] <callsign> [0-9|all]</B> Clear a WCY filter line</CODE>
449 <P>A sysop can clear an input or normal output filter for a user or the
450 node_default or user_default.
452 <H2><A NAME="ss10.22">10.22 clear/wwv (0)</A>
455 <P><CODE><B>clear/wwv [1|all]</B> Clear a WWV filter line</CODE>
457 <P>This command allows you to clear (remove) a line in a WWV filter or to
458 remove the whole filter.
459 <P>see CLEAR/SPOTS for a more detailed explanation.
461 <H2><A NAME="ss10.23">10.23 clear/wwv (extended for sysops) (8)</A>
464 <P><CODE><B>clear/wwv [input] <callsign> [0-9|all]</B> Clear a WWV filter line</CODE>
466 <P>A sysop can clear an input or normal output filter for a user or the
467 node_default or user_default.
469 <H2><A NAME="ss10.24">10.24 connect (5) </A>
472 <P><CODE><B>connect <callsign></B> Start a connection to another DX Cluster</CODE>
474 <P>Start a connection process that will culminate in a new connection to the
475 DX cluster <callsign>. This process creates a new 'client' process which will
476 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
477 necessary to traverse the network(s) to logon to the cluster <callsign>.
479 <H2><A NAME="ss10.25">10.25 dbavail (0)</A>
482 <P><CODE><B>dbavail</B> Show a list of all the databases in the system</CODE>
484 <P>The title says it all really, this command lists all the databases defined
485 in the system. It is also aliased to SHOW/COMMAND.
487 <H2><A NAME="ss10.26">10.26 dbcreate (9)</A>
490 <P><CODE><B>dbcreate <name></B> Create a database entry<BR>
491 <B>dbcreate <name> chain <name> [<name>..]</B> Create a chained database entry<BR>
492 <B>dbcreate <name> remote <node></B> Create a remote database
495 <P>DBCREATE allows you to define a database in the system. It doesn't actually
496 create anything, just defines it.
497 <P>The databases that are created are simple DB_File hash databases, they are
498 therefore already 'indexed'.
499 <P>You can define a local database with the first form of the command eg:
501 <P>You can also chain databases with the addition of the 'chain' keyword.
502 This will search each database one after the other. A typical example
504 <P>DBCREATE sdx_qsl chain sql_ad
505 <P>No checking is done to see if the any of the chained databases exist, in
506 fact it is usually better to do the above statement first then do each of
507 the chained databases.
508 <P>Databases can exist offsite. To define a database that lives on another
510 <P>DBCREATE buckmaster remote gb7dxc
511 <P>Remote databases cannot be chained; however, the last database in a
512 a chain can be a remote database eg:
513 <P>DBCREATE qsl chain gb7dxc
514 <P>To see what databases have been defined do:
515 <P>DBAVAIL (or it will have been aliased to SHOW/COMMAND)
516 <P>It would be normal for you to add an entry into your local Aliases file
517 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
518 need to add a line like:-
525 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
533 <P>to work as they may be used to.
534 <P>See DBIMPORT for the importing of existing AK1A format data to databases.
535 See DBSHOW for generic database enquiry
537 <H2><A NAME="ss10.27">10.27 dbimport (9)</A>
540 <P><CODE><B>dbimport <dbname></B> Import AK1A data into a database</CODE>
542 <P>If you want to import or update data in bulk to a database you can use
543 this command. It will either create or update entries into an existing
544 database. For example:-
545 <P>DBIMPORT oblast /tmp/OBLAST.FUL
546 <P>will import the standard OBLAST database that comes with AK1A into the
547 oblast database held locally.
549 <H2><A NAME="ss10.28">10.28 dbremove (9)</A>
552 <P><CODE><B>dbremove <dbname></B> Delete a database</CODE>
554 <P>DBREMOVE will completely remove a database entry and also delete any data
555 file that is associated with it.
556 <P>There is no warning, no comeback, no safety net.
559 <P>will remove the oblast database from the system and it will also remove
560 the associated datafile.
562 <P>There is no warning, no comeback, no safety net.
563 <P>You have been warned.
565 <H2><A NAME="ss10.29">10.29 dbshow (0)</A>
568 <P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE>
570 <P>This is the generic user interface to the database to the database system.
571 It is expected that the sysop will add an entry to the local Aliases file
572 so that users can use the more familiar AK1A style of enquiry such as:
579 <P>but if he hasn't and the database really does exist (use DBAVAIL or
580 SHOW/COMMAND to find out) you can do the same thing with:
589 <H2><A NAME="ss10.30">10.30 debug (9)</A>
592 <P><CODE><B>debug</B> Set the cluster program into debug mode</CODE>
594 <P>Executing this command will only have an effect if you are running the cluster
602 <P>It will interrupt the cluster just after the debug command has finished.
604 <H2><A NAME="ss10.31">10.31 delete/user (9)</A>
607 <P><CODE><B>delete/user <callsign></B> Delete a user from the User Database</CODE>
609 <P>This command will completely remove a one or more users from the database.
610 <P>There is NO SECOND CHANCE.
611 <P>It goes without saying that you should use this command CAREFULLY!
613 <H2><A NAME="ss10.32">10.32 demonstrate (9)</A>
616 <P><CODE><B>demonstrate <call> <command></B> Demonstrate a command to another user</CODE>
618 <P>This command is provided so that sysops can demonstrate commands to
619 other users. It runs a command as though that user had typed it in and
620 then sends the output to that user, together with the command that
625 DEMO g7brn sh/dx iota oc209
629 <P>Note that this command is similar to SPOOF and will have the same side
630 effects. Commands are run at the privilege of the user which is being
633 <H2><A NAME="ss10.33">10.33 directory (0)</A>
636 <P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
637 <B>directory own</B> List your own messages<BR>
638 <B>directory new</B> List all new messages<BR>
639 <B>directory to <call></B> List all messages to <call><BR>
640 <B>directory from <call></B> List all messages from <call><BR>
641 <B>directory subject <string></B> List all messages with <string> in subject<BR>
642 <B>directory <nn></B> List last <nn> messages<BR>
643 <B>directory <from>-<to></B> List messages <from> message <to> message <BR></CODE>
645 <P>List the messages in the messages directory.
646 <P>If there is a 'p' one space after the message number then it is a
647 personal message. If there is a '-' between the message number and the
648 'p' then this indicates that the message has been read.
649 <P>You can use shell escape characters such as '*' and '?' in the <call>
651 <P>You can combine some of the various directory commands together eg:-
657 DIR SUBJECT IOTA 200-250
660 <P>You can abbreviate all the commands to one letter and use ak1a syntax:-
670 <H2><A NAME="ss10.34">10.34 directory (extended for sysops) (5)</A>
673 <P>Works just like the user command except that sysops can see ALL messages.
675 <H2><A NAME="ss10.35">10.35 disconnect (8)</A>
678 <P><CODE><B>disconnect <call> [<call> ...]</B> Disconnect a user or node</CODE>
680 <P>Disconnect any <call> connected locally
682 <H2><A NAME="ss10.36">10.36 dx (0)</A>
685 <P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE>
687 <P>This is how you send a DX Spot to other users. You can, in fact, now
688 enter the <freq> and the <call> either way round.
697 <P>will all give the same result. You can add some remarks to the end
698 of the command and they will be added to the spot.
702 DX FR0G 144600 this is a test
705 <P>You can credit someone else by saying:-
709 DX by G1TLH FR0G 144.600 he isn't on the cluster
712 <P>The <freq> is compared against the available bands set up in the
713 cluster. See SHOW/BANDS for more information.
715 <H2><A NAME="ss10.37">10.37 export (9)</A>
718 <P><CODE><B>export <msgno> <filename></B> Export a message to a file</CODE>
720 <P>Export a message to a file. This command can only be executed on a local
721 console with a fully privileged user. The file produced will be in a form
722 ready to be imported back into the cluster by placing it in the import
723 directory (/spider/msg/import).
724 <P>This command cannot overwrite an existing file. This is to provide some
725 measure of security. Any files written will owned by the same user as the
726 main cluster, otherwise you can put the new files anywhere the cluster can
727 access. For example:-
728 <P>EXPORT 2345 /tmp/a
730 <H2><A NAME="ss10.38">10.38 export_users (9)</A>
733 <P><CODE><B>export_users [<filename>]</B> Export the users database to ascii</CODE>
735 <P>Export the users database to a file in ascii format. If no filename
736 is given then it will export the file to /spider/data/user_asc.
737 <P>If the file already exists it will be renamed to <filename>.o. In fact
738 up to 5 generations of the file can be kept each one with an extra 'o' on the
740 <P>BE WARNED: this will write to any file you have write access to. No check is
741 made on the filename (if any) that you specify.
743 <H2><A NAME="ss10.39">10.39 filtering (0)</A>
746 <P><CODE><B>filtering</B> Filtering things in DXSpider</CODE>
748 <P>There are a number of things you can filter in the DXSpider system. They
749 all use the same general mechanism.
750 <P>In general terms you can create a 'reject' or an 'accept' filter which
751 can have up to 10 lines in it. You do this using, for example:-
752 <P>accept/spots .....
754 <P>where ..... are the specific commands for that type of filter. There
755 are filters for spots, wwv, announce, wcy and (for sysops)
756 connects. See each different accept or reject command reference for
758 <P>There is also a command to clear out one or more lines in a filter and
759 one to show you what you have set. They are:-
764 <P>There is clear/xxxx command for each type of filter.
765 <P>For now we are going to use spots for the examples, but you can apply
766 the principles to all types of filter.
767 <P>There are two main types of filter 'accept' or 'reject'; which you use
768 depends entirely on how you look at the world and what is least
769 writing to achieve what you want. Each filter has 10 lines (of any
770 length) which are tried in order. If a line matches then the action
771 you have specified is taken (ie reject means ignore it and accept
773 <P>The important thing to remember is that if you specify a 'reject'
774 filter (all the lines in it say 'reject/spots' (for instance) then if
775 a spot comes in that doesn't match any of the lines then you will get
776 it BUT if you specify an 'accept' filter then any spots that don't
777 match are dumped. For example if I have a one line accept filter:-
778 <P>accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
779 <P>then automatically you will ONLY get VHF spots from or to CQ zones 14
780 15 and 16. If you set a reject filter like:
781 <P>reject/spots on hf/cw
782 <P>Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
783 and will work it even on CW then you could say:-
784 <P>reject/spots on hf/cw and not info iota
785 <P>But in that case you might only be interested in iota and say:-
786 <P>accept/spots not on hf/cw or info iota
787 <P>which is exactly the same. You should choose one or the other until
788 you are confortable with the way it works. Yes, you can mix them
789 (actually you can have an accept AND a reject on the same line) but
790 don't try this at home until you can analyse the results that you get
791 without ringing up the sysop for help.
792 <P>You can arrange your filter lines into logical units, either for your
793 own understanding or simply convenience. I have one set frequently:-
794 <P>reject/spots 1 on hf/cw
795 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
796 <P>What this does is to ignore all HF CW spots (being a class B I can't
797 read any CW and couldn't possibly be interested in HF :-) and also
798 rejects any spots on VHF which don't either originate or spot someone
800 <P>This is an exmaple where you would use the line number (1 and 2 in
801 this case), if you leave the digit out, the system assumes '1'. Digits
802 '0'-'9' are available.
803 <P>You can leave the word 'and' out if you want, it is implied. You can
804 use any number of brackets to make the 'expression' as you want
805 it. There are things called precedence rules working here which mean
806 that you will NEED brackets in a situation like line 2 because,
807 without it, will assume:-
808 <P>(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
809 <P>annoying, but that is the way it is. If you use OR - use
810 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
812 <P>If you want to alter your filter you can just redefine one or more
813 lines of it or clear out one line. For example:-
814 <P>reject/spots 1 on hf/ssb
817 <P>To remove the filter in its entirty:-
819 <P>There are similar CLEAR commands for the other filters:-
824 <P>Once you are happy with the results you get, you may like to experiment.
825 <P>my example that filters hf/cw spots and accepts vhf/uhf spots from EU
826 can be written with a mixed filter, eg:
829 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
830 <P>each filter slot actually has a 'reject' slot and an 'accept'
831 slot. The reject slot is executed BEFORE the accept slot.
832 <P>It was mentioned earlier that after a reject test that doesn't match,
833 the default for following tests is 'accept', the reverse is true for
834 'accept'. In the example what happens is that the reject is executed
835 first, any non hf/cw spot is passed to the accept line, which lets
836 thru everything else on HF.
837 <P>The next filter line lets through just VHF/UHF spots from EU.
839 <H2><A NAME="ss10.40">10.40 forward/latlong (8)</A>
842 <P><CODE><B>forward/latlong <node_call></B> Send latitude and longitude information to another cluster</CODE>
844 <P>This command sends all the latitude and longitude information that your
845 cluster is holding against callsigns. One advantage of recieving this
846 information is that more locator information is held by you. This
847 means that more locators are given on the DX line assuming you have
848 <EM>set/dxgrid</EM> enabled. This could be a LOT of information though, so
849 it is not recommended on slow links.
851 <H2><A NAME="ss10.41">10.41 forward/opername (1)</A>
854 <P><CODE><B>forward/opername <call></B> Send out information on this <call> to all clusters</CODE>
856 <P>This command sends out any information held in the user file which can
857 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
858 and Homenode. PC41s are only sent for the information that is available.
860 <H2><A NAME="ss10.42">10.42 help (0)</A>
863 <P><CODE><B>help <cmd></B> Get help on a command</CODE>
865 <P>All commands can be abbreviated, so SHOW/DX can be abbreviated
866 to SH/DX, ANNOUNCE can be shortened to AN and so on.
867 <P>Look at the APROPOS <string> command which will search the help database
868 for the <string> you specify and give you a list of likely commands
869 to look at with HELP.
871 <H2><A NAME="ss10.43">10.43 init (5)</A>
874 <P><CODE><B>init <node call></B> Re-initialise a link to an AK1A compatible node</CODE>
876 <P>This command attempts to re-initialise a link to a (usually) AK1A node
877 that has got confused, usually by a protocol loop of some kind. It may
878 work - but you usually will be better off simply disconnecting it (or
879 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
881 <P>Best of luck - you will need it.
883 <H2><A NAME="ss10.44">10.44 kill (0)</A>
886 <P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE>
888 <P>Delete a message from the local system. You will only be able to
889 delete messages that you have originated or been sent (unless you are
892 <H2><A NAME="ss10.45">10.45 kill (5)</A>
895 <P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system<BR>
896 <B>kill from <call></B> Remove all messages from a callsign<BR>
897 <B>kill to <call></B> Remove all messages to a callsign<BR></CODE>
899 <P>You can get rid of any message to or originating from your callsign using
900 this command. You can remove more than one message at a time.
901 <P>As a sysop you can kill any message on the system.
903 <H2><A NAME="ss10.46">10.46 kill full (5)</A>
906 <P><CODE><B>kill full <msgno> [<msgno>]</B> Delete a message from the whole cluster</CODE>
908 <P>Delete a message (usually a 'bulletin') from the whole cluster system.
909 <P>This uses the subject field, so any messages that have exactly the same subject
910 will be deleted. Beware!
912 <H2><A NAME="ss10.47">10.47 kill/expunge (6)</A>
915 <P><CODE><B>kill/expunge <msgno> [<msgno>..]</B>Expunge a message</CODE>
917 <P>Deleting a message using the normal KILL commands only marks that message
918 for deletion. The actual deletion only happens later (usually two days later).
919 <P>The KILL EXPUNGE command causes the message to be truly deleted more or less
921 <P>It otherwise is used in the same way as the KILL command.
924 <H2><A NAME="ss10.48">10.48 links (0)</A>
927 <P><CODE><B>links</B> Show which nodes are physically connected</CODE>
929 <P>This is a quick listing that shows which links are connected and
930 some information about them. See WHO for a list of all connections.
933 <H2><A NAME="ss10.49">10.49 load/aliases (9)</A>
936 <P><CODE><B>load/aliases</B> Reload the command alias table</CODE>
938 <P>Reload the /spider/cmd/Aliases file after you have editted it. You will need to
939 do this if you change this file whilst the cluster is running in order for the
940 changes to take effect.
942 <H2><A NAME="ss10.50">10.50 load/badmsg (9)</A>
945 <P><CODE><B>load/badmsg</B> Reload the bad message table</CODE>
947 <P>Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
948 the cluster is running. This table contains a number of perl regular
949 expressions which are searched for in the fields targetted of each message.
950 If any of them match then that message is immediately deleted on receipt.
952 <H2><A NAME="ss10.51">10.51 load/badwords (9)</A>
955 <P><CODE><B>load/badwords</B> Reload the bad words table</CODE>
957 <P>Reload the /spider/data/badwords file if you have changed it manually whilst
958 the cluster is running. This file contains a list of words which, if found
959 on certain text portions of PC protocol, will cause those protocol frames
960 to be rejected. It will all put out a message if any of these words are
961 used on the announce, dx and talk commands. The words can be one or
962 more on a line, lines starting with '#' are ignored.
964 <H2><A NAME="ss10.52">10.52 load/bands (9)</A>
967 <P><CODE><B>load/bands</B> Reload the band limits table</CODE>
969 <P>Reload the /spider/data/bands.pl file if you have changed it manually whilst
970 the cluster is running.
972 <H2><A NAME="ss10.53">10.53 load/cmd_cache (9)</A>
975 <P><CODE><B>load/cmd_cache</B> Reload the automatic command cache</CODE>
977 <P>Normally, if you change a command file in the cmd or local_cmd tree it will
978 automatially be picked up by the cluster program. Sometimes it can get confused
979 if you are doing a lot of moving commands about or delete a command in the
980 local_cmd tree and want to use the normal one again. Execute this command to
981 reset everything back to the state it was just after a cluster restart.
983 <H2><A NAME="ss10.54">10.54 load/forward (9)</A>
986 <P><CODE><B>load/forward</B> Reload the msg forwarding routing table</CODE>
987 <P>Reload the /spider/msg/forward.pl file if you have changed it
988 manually whilst the cluster is running.
990 <H2><A NAME="ss10.55">10.55 load/messages (9)</A>
993 <P><CODE><B>load/messages</B> Reload the system messages file</CODE>
995 <P>If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne
996 commands) you can have them take effect during a cluster session by executing this
997 command. You need to do this if get something like :-
998 <P>unknown message 'xxxx' in lang 'en'
1000 <H2><A NAME="ss10.56">10.56 load/prefixes (9)</A>
1003 <P><CODE><B>load/prefixes</B> Reload the prefix table</CODE>
1005 <P>Reload the /spider/data/prefix_data.pl file if you have changed it manually
1006 whilst the cluster is running.
1008 <H2><A NAME="ss10.57">10.57 merge (5)</A>
1011 <P><CODE><B>merge <node> [<no spots>/<no wwv>]</B> Ask for the latest spots and WWV</CODE>
1013 <P>MERGE allows you to bring your spot and wwv database up to date. By default
1014 it will request the last 10 spots and 5 WWVs from the node you select. The
1015 node must be connected locally.
1016 <P>You can request any number of spots or wwv and although they will be appended
1017 to your databases they will not duplicate any that have recently been added
1018 (the last 2 days for spots and last month for WWV data).
1020 <H2><A NAME="ss10.58">10.58 msg (9)</A>
1023 <P><CODE><B>msg <cmd> <msgno> [data ...]</B> Alter various message parameters</CODE>
1025 <P>Alter message parameters like To, From, Subject, whether private or bulletin
1026 or return receipt (RR) is required or whether to keep this message from timing
1031 MSG TO <msgno> <call> - change TO callsign to <call>
1032 MSG FRom <msgno> <call> - change FROM callsign to <call>
1033 MSG PRrivate <msgno> - set private flag
1034 MSG NOPRrivate <msgno> - unset private flag
1035 MSG RR <msgno> - set RR flag
1036 MSG NORR <msgno> - unset RR flag
1037 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1038 MSG NOKEep <msgno> - unset the keep flag
1039 MSG SUbject <msgno> <new> - change the subject to <new>
1040 MSG WAittime <msgno> - remove any waitting time for this message
1041 MSG NOREad <msgno> - mark message as unread
1042 MSG REad <msgno> - mark message as read
1043 MSG QUeue - queue any outstanding bulletins
1044 MSG QUeue 1 - queue any outstanding private messages
1046 </CODE></BLOCKQUOTE>
1047 <P>You can look at the status of a message by using:-
1048 <P>STAT/MSG <msgno>
1049 <P>This will display more information on the message than DIR does.
1051 <H2><A NAME="ss10.59">10.59 pc (8)</A>
1054 <P><CODE><B>pc <call> <text></B> Send text (eg PC Protocol) to <call></CODE>
1056 <P>Send some arbitrary text to a locally connected callsign. No processing is done on
1057 the text. This command allows you to send PC Protocol to unstick things if problems
1058 arise (messages get stuck etc). eg:-
1059 <P>pc gb7djk PC33^GB7TLH^GB7DJK^400^
1060 <P>You can also use in the same way as a talk command to a connected user but
1061 without any processing, added of "from <blah> to <blah>" or whatever.
1062 <P>pc G1TLH Try doing that properly!!!
1064 <H2><A NAME="ss10.60">10.60 ping (1)</A>
1067 <P><CODE><B>ping <node></B> Check the link quality between nodes</CODE>
1069 <P>his command allows you to send a frame to another cluster node on
1070 the network and get a return frame. The time it takes to do this
1071 is a good indication of the quality of the link. The actual time
1072 it takes is output to the console in seconds.
1073 Any visible cluster node can be PINGed.
1076 <H2><A NAME="ss10.61">10.61 rcmd (1)</A>
1079 <P><CODE><B>rcmd <node call> <cmd></B> Send a command to another DX cluster</CODE>
1081 <P>This command allows you to send nearly any command to another DX Cluster
1082 node that is connected to the system.
1083 <P>Whether you get any output is dependant on a) whether the other system knows
1084 that the node callsign of this cluster is in fact a node b) whether the
1085 other system is allowing RCMDs from this node and c) whether you have
1086 permission to send this command at all.
1088 <H2><A NAME="ss10.62">10.62 read (0)</A>
1091 <P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
1092 <B>read <msgno></B> Read the specified message<BR></CODE>
1094 <P>You can read any messages that are sent as 'non-personal' and also any
1095 message either sent by or sent to your callsign.
1098 <H2><A NAME="ss10.63">10.63 read (extended for sysops) (5) </A>
1101 <P><CODE><B>read <msgno></B> Read a message on the system</CODE>
1103 <P>As a sysop you may read any message on the system
1105 <H2><A NAME="ss10.64">10.64 reject/announce</A>
1108 <P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
1111 <P>Create an 'reject this announce' line for a filter.
1112 <P>An reject filter line means that if the announce matches this filter it is
1113 passed onto the user. See HELP FILTERS for more info. Please read this
1114 to understand how filters work - it will save a lot of grief later on.
1115 <P>You can use any of the following things in this line:-
1119 info <string> eg: iota or qsl
1120 by <prefixes> eg: G,M,2
1121 origin <prefixes>
1122 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1123 origin_itu <numbers>
1124 origin_zone <numbers>
1125 by_dxcc <numbers>
1127 by_zone <numbers>
1128 channel <prefixes>
1129 wx 1 filter WX announces
1130 dest <prefixes> eg: 6MUK,WDX (distros)
1132 </CODE></BLOCKQUOTE>
1137 rej/ann by_zone 14,15,16 and not by G,M,2
1139 </CODE></BLOCKQUOTE>
1140 <P>You can use the tag 'all' to reject everything eg:
1146 </CODE></BLOCKQUOTE>
1147 <P>but this probably for advanced users...
1149 <H2><A NAME="ss10.65">10.65 reject/announce (extended for sysops) (8)</A>
1152 <P><CODE><B>reject/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE>
1154 <P>This version allows a sysop to set a filter for a callsign as well as the
1155 default for nodes and users eg:-
1160 reject/ann input node_default by G,M,2
1161 reject/ann user_default by G,M,2
1163 </CODE></BLOCKQUOTE>
1165 <H2><A NAME="ss10.66">10.66 reject/route (8)</A>
1168 <P><CODE><B>reject/route <call> [0-9] <pattern></B> Set an 'reject' filter line for routing</CODE>
1170 <P>Create an 'reject this routing PC Protocol' line for a filter.
1172 <P>An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1173 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
1174 read this to understand how filters work - it will save a lot of grief later on.
1175 You can use any of the following things in this line:-
1179 call <prefixes> the callsign of the thingy
1180 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1181 call_itu <numbers>
1182 call_zone <numbers>
1183 origin <prefixes> really the interface it came in on
1184 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1185 origin_itu <numbers>
1186 origin_zone <numbers>
1188 </CODE></BLOCKQUOTE>
1194 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
1196 </CODE></BLOCKQUOTE>
1198 <P>You can use the tag 'all' to reject everything eg:
1202 rej/route all (equiv to [very] restricted mode)
1204 </CODE></BLOCKQUOTE>
1206 <H2><A NAME="ss10.67">10.67 reject/spots (0)</A>
1209 <P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE>
1211 <P>Create a 'reject this spot' line for a filter.
1212 <P>A reject filter line means that if the spot matches this filter it is
1213 dumped (not passed on). See HELP FILTERS for more info. Please read this
1214 to understand how filters work - it will save a lot of grief later on.
1215 <P>You can use any of the following things in this line:-
1219 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1220 on <range> same as 'freq'
1221 call <prefixes> eg: G,PA,HB9
1222 info <string> eg: iota or qsl
1224 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1225 call_itu <numbers>
1226 call_zone <numbers>
1227 by_dxcc <numbers>
1229 by_zone <numbers>
1230 origin <prefixes>
1231 channel <prefixes>
1233 </CODE></BLOCKQUOTE>
1234 <P>For frequencies, you can use any of the band names defined in
1235 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1236 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1237 this is more efficient than saying simply: on HF (but don't get
1238 too hung up about that)
1244 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1246 </CODE></BLOCKQUOTE>
1247 <P>You can use the tag 'all' to reject everything eg:
1253 </CODE></BLOCKQUOTE>
1254 <P>but this probably for advanced users...
1256 <H2><A NAME="ss10.68">10.68 reject/spots (extended for sysops) (8)</A>
1259 <P><CODE><B>reject/spots <call> [input] [0-9] <pattern></B>
1260 Reject spot filter sysop version </CODE>
1262 <P>This version allows a sysop to set a filter for a callsign as well as the
1263 default for nodes and users eg:-
1267 reject/spot db0sue-7 1 by_zone 14,15,16
1268 reject/spot node_default all
1269 set/hops node_default 10
1271 reject/spot user_default by G,M,2
1273 </CODE></BLOCKQUOTE>
1275 <H2><A NAME="ss10.69">10.69 reject/wcy (0)</A>
1278 <P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE>
1280 <P>It is unlikely that you will want to do this, but if you do then you can
1281 filter on the following fields:-
1285 by <prefixes> eg: G,M,2
1286 origin <prefixes>
1287 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1288 origin_itu <numbers>
1289 origin_zone <numbers>
1290 by_dxcc <numbers>
1292 by_zone <numbers>
1293 channel <prefixes>
1295 </CODE></BLOCKQUOTE>
1296 <P>There are no examples because WCY Broadcasts only come from one place and
1297 you either want them or not (see UNSET/WCY if you don't want them).
1298 <P>This command is really provided for future use.
1299 <P>See HELP FILTER for information.
1301 <H2><A NAME="ss10.70">10.70 reject/wcy (extended for sysops) (8)</A>
1304 <P><CODE><B>reject/wcy <call> [input] [0-9] <pattern></B>
1305 WCY reject filter sysop version</CODE>
1307 <P>This version allows a sysop to set a filter for a callsign as well as the
1308 default for nodes and users eg:-
1309 <P>reject/wcy gb7djk all
1311 <H2><A NAME="ss10.71">10.71 reject/wwv (0)</A>
1314 <P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE>
1316 <P>It is unlikely that you will want to do this, but if you do then you can
1317 filter on the following fields:-
1321 by <prefixes> eg: G,M,2
1322 origin <prefixes>
1323 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1324 origin_itu <numbers>
1325 origin_zone <numbers>
1326 by_dxcc <numbers>
1328 by_zone <numbers>
1329 channel <prefixes>
1331 </CODE></BLOCKQUOTE>
1336 reject/wwv by_zone 14,15,16
1338 </CODE></BLOCKQUOTE>
1339 <P>is probably the only useful thing to do (which will only show WWV broadcasts
1340 by stations in the US).
1341 <P>See HELP FILTER for information.
1343 <H2><A NAME="ss10.72">10.72 reject/wwv (extended for sysops) (8)</A>
1346 <P><CODE><B>reject/wwv <call> [input] [0-9] <pattern></B>
1347 WWV reject filter sysop version</CODE>
1349 <P>This version allows a sysop to set a filter for a callsign as well as the
1350 default for nodes and users eg:-
1354 reject/wwv db0sue-7 1 by_zone 4
1355 reject/wwv node_default all
1357 reject/wwv user_default by W
1359 </CODE></BLOCKQUOTE>
1361 <H2><A NAME="ss10.73">10.73 reply (0)</A>
1364 <P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
1365 <B>reply <msgno></B> Reply (privately) to the specified message<BR>
1366 <B>reply B <msgno></B> Reply as a Bulletin to the specified message<BR>
1367 <B>reply NOPrivate <msgno></B> Reply as a Bulletin to the specified
1369 <B>reply RR <msgno></B> Reply to the specified message with read receipt<BR></CODE>
1371 <P>You can reply to a message and the subject will automatically have
1372 "Re:" inserted in front of it, if it isn't already present.
1373 <P>You can also use all the extra qualifiers such as RR, PRIVATE,
1374 NOPRIVATE, B that you can use with the SEND command (see SEND
1375 for further details)
1377 <H2><A NAME="ss10.74">10.74 send (0)</A>
1380 <P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
1381 <B>send RR <call></B> Send a message and ask for a read receipt<BR>
1382 <B>send COPY <msgno> <call></B> Send a copy of a message to someone<BR>
1383 <B>send PRIVATE <call></B> Send a personal message<BR>
1384 <B>send NOPRIVATE <call></B> Send a message to all stations<BR></CODE>
1386 <P>All the SEND commands will create a message which will be sent either to
1387 an individual callsign or to one of the 'bulletin' addresses.
1388 <P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1389 it will mark the message as personal and send it to the cluster node that
1390 that callsign is connected to.
1391 <P>You can have more than one callsign in all of the SEND commands.
1392 <P>You can have multiple qualifiers so that you can have for example:-
1396 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1398 </CODE></BLOCKQUOTE>
1399 <P>which should send a copy of message 123 to G1TLH and G0RDI and you will
1400 receive a read receipt when they have read the message.
1401 <P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1402 SP is an alias for SEND PRIVATE
1404 <H2><A NAME="ss10.75">10.75 set/address (0)</A>
1407 <P><CODE><B>set/address <your_address></B> Record your postal address</CODE>
1409 <P>Literally, record your address details on the cluster.
1411 <H2><A NAME="ss10.76">10.76 set/announce (0)</A>
1414 <P><CODE><B>set/announce</B> Allow announce messages</CODE>
1416 <P>Allow announce messages to arrive at your terminal.
1418 <H2><A NAME="ss10.77">10.77 set/arcluster (5)</A>
1421 <P><CODE><B>set/arcluster <node_call> [<node_call> ...]</B> Make
1422 the node_call an AR-Cluster type node</CODE>
1424 <P>Set the node_call as an AR-Cluster type node
1426 <H2><A NAME="ss10.78">10.78 set/baddx (8)</A>
1429 <P><CODE><B>set/baddx <call></B> Stop words we do not wish to see in the callsign field
1430 of a dx spot being propagated</CODE>
1432 <P>Setting a word as 'baddx' will prevent spots with that word in the callsign
1433 field of a DX spot from going any further. They will not be displayed and they
1434 will not be sent onto other nodes.
1435 <P>The word must be wriiten in full, no wild cards are allowed eg:-
1439 set/baddx FORSALE VIDEO FR0G
1441 </CODE></BLOCKQUOTE>
1442 <P>To allow a word again, use the following command ...
1448 </CODE></BLOCKQUOTE>
1450 <H2><A NAME="ss10.79">10.79 set/badnode (6)</A>
1453 <P><CODE><B>set/badnode <node_call></B> Stop spots from this node_call
1454 being propagated</CODE>
1456 <P>Setting a callsign as a 'badnode' will prevent spots from that node
1457 going any further. They will not be displayed and they will not be
1458 sent onto other nodes.
1459 <P>The call can be a full or partial call (or a prefix), eg:-
1465 </CODE></BLOCKQUOTE>
1466 <P>will stop anything from K1TTT (including any SSID's)
1472 </CODE></BLOCKQUOTE>
1473 <P>will allow spots from him again.
1474 <P>Use with extreme care. This command may well be superceded by FILTERing.
1476 <H2><A NAME="ss10.80">10.80 set/badspotter (8)</A>
1479 <P><CODE><B>set/badspotter <call></B> Stop spots from this callsign being propagated</CODE>
1481 <P>Setting a callsign as a 'badspotter' will prevent spots from this callsign
1482 going any further. They will not be displayed and they will not be
1483 sent onto other nodes.
1484 <P>The call must be written in full, no wild cards are allowed eg:-
1488 set/badspotter VE2STN
1490 </CODE></BLOCKQUOTE>
1491 <P>will stop anything from VE2STN. If you want SSIDs as well then you must
1492 enter them specifically.
1496 unset/badspotter VE2STN
1498 </CODE></BLOCKQUOTE>
1499 <P>will allow spots from him again.
1500 <P>Use with extreme care. This command may well be superceded by FILTERing.
1502 <H2><A NAME="ss10.81">10.81 set/badword (8)</A>
1505 <P><CODE><B>set/badword <word></B> Stop things with this word being propogated</CODE>
1507 <P>Setting a word as a 'badword' will prevent things like spots,
1508 announces or talks with this word in the the text part from going any
1509 further. They will not be displayed and they will not be sent onto
1511 <P>The word must be written in full, no wild cards are allowed eg:-
1512 <P>set/badword annihilate annihilated annihilation
1513 <P>will stop anything with these words in the text.
1514 <P>unset/badword annihilated
1515 <P>will allow text with this word again.
1518 <H2><A NAME="ss10.82">10.82 set/beep (0)</A>
1521 <P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE>
1523 <P>Add a beep to DX and other terminal messages.
1525 <H2><A NAME="ss10.83">10.83 set/bbs (5)</A>
1528 <P><CODE><B>set/bbs <call> [<call>..]</B>Make <call> a BBS</CODE>
1530 <H2><A NAME="ss10.84">10.84 set/clx (5)</A>
1533 <P><CODE><B>set/clx <node_call> [<node_call> ...]</B> Make
1534 the node_call a CLX type node</CODE>
1536 <P>Set the node_call as a CLX type node
1538 <H2><A NAME="ss10.85">10.85 set/debug (9)</A>
1541 <P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE>
1543 <P>You can choose to log several different levels. The levels are
1549 <P>You can show what levels you are logging with the <EM>show/debug</EM>
1551 <P>You can remove a debug level with unset/debug <name>
1553 <H2><A NAME="ss10.86">10.86 set/dx (0)</A>
1556 <P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE>
1558 <P>You can stop DX messages with the <EM>unset/dx</EM> command
1560 <H2><A NAME="ss10.87">10.87 set/dxgrid (0)</A>
1563 <P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE>
1565 <P>Some logging programs do not like the additional information at
1566 the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
1567 command to remove the grid squares.
1569 <H2><A NAME="ss10.88">10.88 set/dxnet (5)</A>
1572 <P><CODE><B>set/dxnet <node_call> [<node_call> ...]</B> Make
1573 the node_call a DXNet type node</CODE>
1575 <P>Set the node_call as a DXNet type node
1577 <H2><A NAME="ss10.89">10.89 set/echo (0)</A>
1580 <P><CODE><B>set/echo</B> Make the cluster echo your input</CODE>
1582 <P>If you are connected via a telnet session, different implimentations
1583 of telnet handle echo differently depending on whether you are
1584 connected via port 23 or some other port. You can use this command
1585 to change the setting appropriately.
1586 <P>You can remove the echo with the <EM>unset/echo</EM> command
1587 <P>The setting is stored in your user profile.
1588 <P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1590 <H2><A NAME="ss10.90">10.90 set/email (0)</A>
1593 <P><CODE><B>set/email <email_address></B> Set email address(es) and forward your personals</CODE>
1595 <P>If any personal messages come in for your callsign then you can use
1596 these commands to control whether they are forwarded onto your email
1597 address. To enable the forwarding do something like:-
1598 <P>SET/EMAIL mike.tubby@somewhere.com
1599 <P>You can have more than one email address (each one separated by a space).
1600 Emails are forwarded to all the email addresses you specify.
1601 <P>You can disable forwarding by:-
1604 <H2><A NAME="ss10.91">10.91 set/here (0)</A>
1607 <P><CODE><B>set/here</B> Set the here flag</CODE>
1609 <P>Let others on the cluster know you are here by only displaying your
1610 callsign. If you are away from your terminal you can use the <EM>unset/here</EM>
1611 command to let people know you are away. This simply puts brackets
1612 around your callsign to indicate you are not available.
1614 <H2><A NAME="ss10.92">10.92 set/homenode (0)</A>
1617 <P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE>
1619 <P>Tell the cluster system where you normally connect to. Any Messages sent
1620 to you will normally find their way there should you not be connected.
1627 </CODE></BLOCKQUOTE>
1629 <H2><A NAME="ss10.93">10.93 set/hops (8)</A>
1632 <P><CODE><B>set/hops <node_call> ann|spots|wwv|wcy <n></B>
1633 Set hop count</CODE>
1635 <P>Set the hop count for a particular type of broadcast for a node.
1636 <P>This command allows you to set up special hop counts for a node
1637 for currently: announce, spots, wwv and wcy broadcasts.
1642 set/hops gb7djk ann 10
1643 set/hops gb7mbc spots 20
1645 </CODE></BLOCKQUOTE>
1646 <P>Set SHOW/HOPS for information on what is already set. This command
1647 creates a filter and works in conjunction with the filter system.
1649 <H2><A NAME="ss10.94">10.94 set/isolate (9)</A>
1652 <P><CODE><B>set/isolate <node call></B> Isolate a node from the rest of the network</CODE>
1654 <P>Connect a node to your system in such a way that you are a full protocol
1655 member of its network and can see all spots on it, but nothing either leaks
1656 out from it nor goes back into from the rest of the nodes connected to you.
1657 <P>You can potentially connect several nodes in this way.
1658 <P>You can see which nodes are isolated with the show/isolate (1) command.
1659 <P>You can remove the isolation with the command unset/isolate.
1661 <H2><A NAME="ss10.95">10.95 set/language (0)</A>
1664 <P><CODE><B>set/language <language></B> Set the language you wish to use</CODE>
1666 <P>You can select the language that you want the cluster to use. Currently
1667 the languages available are <EM>en</EM> (English) and <EM>nl</EM> (Dutch).
1669 <H2><A NAME="ss10.96">10.96 set/location (0)</A>
1672 <P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE>
1674 <P>You can set your latitude and longitude manually or alternatively use the
1675 <EM>set/qra</EM> command which will do the conversion for you.
1679 set/location 54 04 N 2 02 E
1681 </CODE></BLOCKQUOTE>
1684 <H2><A NAME="ss10.97">10.97 set/sys_location (9)</A>
1687 <P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE>
1689 <P>In order to get accurate headings and such like you must tell the system
1690 what your latitude and longitude is. If you have not yet done a SET/QRA
1691 then this command will set your QRA locator for you. For example:-
1695 SET/LOCATION 52 22 N 0 57 E
1697 </CODE></BLOCKQUOTE>
1699 <H2><A NAME="ss10.98">10.98 set/logininfo (0)</A>
1702 <P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE>
1704 <P>Show users and nodes when they log in and out of the local cluster. You
1705 can stop these messages by using the <EM>unset/logininfo</EM> command.
1708 <H2><A NAME="ss10.99">10.99 set/lockout (9)</A>
1711 <P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE>
1713 <P>You can show who is locked out with the <EM>show/lockout</EM> command.
1714 To allow the user to connect again, use the <EM>unset/lockout</EM> command.
1716 <H2><A NAME="ss10.100">10.100 set/name (0)</A>
1719 <P><CODE><B>set/name <your_name></B> Set your name</CODE>
1721 <P>Tell the cluster what your name is, eg:-
1727 </CODE></BLOCKQUOTE>
1729 <H2><A NAME="ss10.101">10.101 set/node (9)</A>
1732 <P><CODE><B>set/node <call> [<call> ...]</B> Make the callsign an AK1A cluster</CODE>
1734 <P>Tell the system that the call(s) are to be treated as AK1A cluster and
1735 fed PC Protocol rather normal user commands.
1736 <P>From version 1.41 you can also set the following types of cluster
1745 </CODE></BLOCKQUOTE>
1746 <P>To see what your nodes are set to, use the <EM>show/nodes</EM> command.
1748 <H2><A NAME="ss10.102">10.102 set/obscount (9)</A>
1751 <P><CODE><B>set/obscount <count> <node call></B> Set the 'pump-up' obsolescence counter</CODE>
1753 <P>From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1754 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1755 counter which is decremented on every outgoing ping and then reset to
1756 the 'obscount' value on every incoming ping. The default value of this
1758 <P>What this means is that a neighbouring node will be pinged twice at
1759 (default) 300 second intervals and if no reply has been heard just before
1760 what would be the third attempt, that node is disconnected.
1761 <P>If a ping is heard then the obscount is reset to the full value. Using
1762 default values, if a node has not responded to a ping within 15 minutes,
1765 <H2><A NAME="ss10.103">10.103 set/page (0)</A>
1768 <P><CODE><B>set/page <n></B> Set the number of lines per page</CODE>
1770 <P>Tell the system how many lines you wish on a page when the number of lines
1771 of output from a command is more than this. The default is 20. Setting it
1772 explicitly to 0 will disable paging.
1779 </CODE></BLOCKQUOTE>
1780 <P>The setting is stored in your user profile.
1782 <H2><A NAME="ss10.104">10.104 set/password (0)</A>
1785 <P><CODE><B>set/password</B> Set your own password</CODE>
1787 <P>This command only works for a 'telnet' user (currently). It will
1788 only work if you have a password already set. This initial password
1789 can only be set by the sysop.
1790 <P>When you execute this command it will ask you for your old password,
1791 then ask you to type in your new password twice (to make sure you
1792 get it right). You may or may not see the data echoed on the screen
1793 as you type, depending on the type of telnet client you have.
1795 <H2><A NAME="ss10.105">10.105 set/password (9)</A>
1798 <P><CODE><B>set/password <callsign> <string></B> Set a users password</CODE>
1800 <P>The password for a user can only be set by a full sysop. The string
1801 can contain any characters.
1802 <P>The way this field is used depends on context. If it is being used in
1803 the SYSOP command context then you are offered 5 random numbers and you
1804 have to supply the corresponding letters. This is now mainly for ax25
1806 <P>If it is being used on incoming telnet connections then, if a password
1808 <P>set/var $main::passwdreq = 1
1809 <P>command is executed in the startup script, then a password prompt is
1810 given after the normal 'login: ' prompt.
1811 <P>The command "unset/password" is provided to allow a sysop to remove a
1812 users password completely in case a user forgets or loses their password.
1814 <H2><A NAME="ss10.106">10.106 set/pinginterval (9)</A>
1817 <P><CODE><B>set/pinginterval <time> <node call></B> Set the ping time to neighbouring nodes</CODE>
1819 <P>As from version 1.35 all neighbouring nodes are pinged at regular intervals
1820 in order to determine the rolling quality of the link and, in future, to
1821 affect routing decisions. The default interval is 300 secs or 5 minutes.
1822 <P>You can use this command to set a different interval. Please don't.
1823 <P>But if you do the value you enter is treated as minutes up 60 and seconds
1824 for numbers greater than that.
1825 <P>This is used also to help determine when a link is down at the far end
1826 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1827 for more information.
1829 <H2><A NAME="ss10.107">10.107 set/privilege (9)</A>
1832 <P><CODE><B>set/privilege <n> <call> [<call> ...]</B> Set the privilege level on a call</CODE>
1834 <P>Set the privilege level on a callsign. The privilege levels that pertain
1835 to commands are as default:-
1840 1 - allow remote nodes normal user RCMDs
1841 5 - various privileged commands (including shutdown, but not disc-
1842 connect), the normal level for another node.
1843 8 - more privileged commands (including disconnect)
1844 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1847 </CODE></BLOCKQUOTE>
1848 <P>If you are a sysop and you come in as a normal user on a remote connection
1849 your privilege will automatically be set to 0.
1851 <H2><A NAME="ss10.108">10.108 set/spider (5)</A>
1854 <P><CODE><B>set/spider <node_call> [<node_call> ...]</B> Make
1855 the node_call a DXSpider type node</CODE>
1857 <P>Set the node_call as a DXSpider type node
1859 <H2><A NAME="ss10.109">10.109 set/sys_qra (9)</A>
1862 <P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA locator</CODE>
1864 <H2><A NAME="ss10.110">10.110 set/qra (0)</A>
1867 <P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE>
1869 <P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
1870 done a SET/LOCATION then your latitude and longitude will be set roughly
1871 correctly (assuming your locator is correct ;-). For example:-
1877 </CODE></BLOCKQUOTE>
1879 <H2><A NAME="ss10.111">10.111 set/qth (0)</A>
1882 <P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE>
1884 <P>Tell the system where your are. For example:-
1888 set/qth East Dereham, Norfolk
1890 </CODE></BLOCKQUOTE>
1892 <H2><A NAME="ss10.112">10.112 set/register (9)</A>
1895 <P><CODE><B>set/register <call></B> Mark a user as registered</CODE>
1897 <P>Registration is a concept that you can switch on by executing the
1898 <P>set/var $main::regreq = 1
1899 <P>command (usually in your startup file)
1900 <P>If a user is NOT registered then, firstly, instead of the normal
1901 motd file (/spider/data/motd) being sent to the user at startup, the
1902 user is sent the motd_nor file instead. Secondly, the non registered
1903 user only has READ-ONLY access to the node. The non-registered user
1904 cannot use DX, ANN etc.
1905 <P>The only exception to this is that a non-registered user can TALK or
1906 SEND messages to the sysop.
1907 <P>To unset a user use the 'unset/register' command
1909 <H2><A NAME="ss10.113">10.113 set/talk (0)</A>
1912 <P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE>
1914 <P>Allow talk messages to arrive at your console. You can switch off
1915 talks with the <EM>unset/talk</EM> command.
1917 <H2><A NAME="ss10.114">10.114 set/wcy (0)</A>
1920 <P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE>
1922 <P>Allow WCY information to be seen at your console. You can switch off
1923 WCY messages with the <EM>unset/wcy</EM> command.
1925 <H2><A NAME="ss10.115">10.115 set/wwv (0)</A>
1928 <P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE>
1930 <P>Allow WWV information to be seen at your console. You can switch off
1931 WWV messages with the <EM>unset/wwv</EM> command.
1933 <H2><A NAME="ss10.116">10.116 set/wx (0)</A>
1936 <P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE>
1938 <P>Allow WX information to be seen at your console. You can switch off
1939 WX messages with the <EM>unset/wx</EM> command.
1941 <H2><A NAME="ss10.117">10.117 show/baddx (1)</A>
1944 <P><CODE><B>show/baddx</B>Show all the bad dx calls in the system</CODE>
1946 <P>Display all the bad dx callsigns in the system, see SET/BADDX
1947 for more information.
1949 <H2><A NAME="ss10.118">10.118 show/badnode (6)</A>
1952 <P><CODE><B>show/badnode</B> Show all the bad nodes in the system</CODE>
1954 <P>Display all the bad node callsigns in the system, see SET/BADNODE
1955 for more information.
1957 <H2><A NAME="ss10.119">10.119 show/badspotter (1)</A>
1960 <P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE>
1962 <P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1963 for more information.
1965 <H2><A NAME="ss10.120">10.120 show/badword (1)</A>
1968 <P><CODE><B>show/badword</B> Show all the bad words in the system</CODE>
1970 <P>Display all the bad words in the system, see SET/BADWORD
1971 for more information.
1973 <H2><A NAME="ss10.121">10.121 show/configuration (0)</A>
1976 <P><CODE><B>show/configuration [<node>]</B> Show all visible nodes and their users</CODE>
1978 <P>This command allows you to see all the users that can be seen
1979 and the nodes to which they are connected. With the optional <EM>node</EM>,
1980 you can specify a particular node to look at.
1981 <P>This command is normally abbreviated to: sh/c
1982 <P>BE WARNED: the list that is returned can be VERY long
1984 <H2><A NAME="ss10.122">10.122 show/configuration/node (0)</A>
1987 <P><CODE><B>show/configuration/node</B> Show all the nodes connected</CODE>
1989 <P>Show all the nodes connected locally and the nodes they have connected.
1991 <H2><A NAME="ss10.123">10.123 show/connect (1)</A>
1994 <P><CODE><B>show/connect</B> Show all the active connections</CODE>
1996 <P>This command shows information on all the active connections known to
1997 the node. This command gives slightly more information than WHO.
1999 <H2><A NAME="ss10.124">10.124 show/date (0)</A>
2002 <P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
2003 the local time</CODE>
2005 <P>This is very nearly the same as SHOW/TIME, the only difference the format
2006 of the date string if no arguments are given.
2007 <P>If no prefixes or callsigns are given then this command returns the local
2008 time and UTC as the computer has it right now. If you give some prefixes
2009 then it will show UTC and UTC + the local offset (not including DST) at
2010 the prefixes or callsigns that you specify.
2012 <H2><A NAME="ss10.125">10.125 show/debug (9)</A>
2015 <P><CODE><B>show/debug</B> Show what levels of debug you are logging</CODE>
2017 <P>The levels can be set with <EM>set/debug</EM>
2019 <H2><A NAME="ss10.126">10.126 show/dx (0)</A>
2022 <P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE>
2024 <P>If you just type SHOW/DX you will get the last so many spots
2025 (sysop configurable, but usually 10).
2026 <P>In addition you can add any number of these options in very nearly
2027 any order to the basic SHOW/DX command, they are:-
2032 on <band> - eg 160m 20m 2m 23cm 6mm
2033 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
2035 <number> - the number of spots you want
2036 <from>-<to> - <from> spot no <to> spot no in
2039 <prefix> - for a spotted callsign beginning with <prefix>
2040 *<suffix> - for a spotted callsign ending in <suffix>
2041 *<string>* - for a spotted callsign containing <string>
2043 day <number> - starting <number> days ago
2044 day <from>-<to> - <from> days <to> days ago
2046 info <text> - any spots containing <text> in the info or remarks
2048 by <call> - any spots spotted by <call> (spotter <call>
2051 qsl - this automatically looks for any qsl info on the call
2052 held in the spot database.
2054 iota [<iota>] - If the iota island number is missing it will
2055 look for the string iota and anything which looks like
2056 an iota island number. If you specify then it will look
2059 qra [<locator>] - this will look for the specific locator if
2060 you specify one or else anything that looks like a locator.
2062 </CODE></BLOCKQUOTE>
2069 SH/DX on 20m info iota
2070 SH/DX 9a on vhf day 30
2076 </CODE></BLOCKQUOTE>
2078 <H2><A NAME="ss10.127">10.127 show/dxcc (0)</A>
2081 <P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE>
2083 <P>This command takes the <prefix> (which can be a full or partial
2084 callsign if desired), looks up which internal country number it is
2085 and then displays all the spots as per SH/DX for that country.
2086 <P>The options for SHOW/DX also apply to this command.
2093 SH/DXCC W on 20m info iota
2095 </CODE></BLOCKQUOTE>
2097 <H2><A NAME="ss10.128">10.128 sh/dxstats (0)</A>
2100 <P><CODE><B>sh/dxstats</B> Show the DX Statistics for last 31 days</CODE>
2102 <P>Show the total DX spots for the last 31 days
2105 <H2><A NAME="ss10.129">10.129 show/files (0)</A>
2108 <P><CODE><B>show/files [<filearea> [<string>]]</B> List
2109 the contents of a filearea</CODE>
2111 <P>SHOW/FILES on its own will show you a list of the various fileareas
2112 available on the system. To see the contents of a particular file
2117 SH/FILES <filearea>
2119 </CODE></BLOCKQUOTE>
2120 <P>where <filearea> is the name of the filearea you want to see the
2122 <P>You can also use shell globbing characters like '*' and '?' in a
2123 string to see a selection of files in a filearea eg:-
2127 SH/FILES bulletins arld*
2129 </CODE></BLOCKQUOTE>
2130 <P>See also TYPE - to see the contents of a file.
2132 <H2><A NAME="ss10.130">10.130 show/filter (0)</A>
2135 <P><CODE><B>show/filter</B> Show the filters you have set</CODE>
2137 <P>Show the contents of all the filters that are set by you. This command
2138 displays all the filters set - for all the various categories.
2140 <H2><A NAME="ss10.131">10.131 show/filter (extended for sysops) (5)</A>
2143 <P><CODE><B>show/filter <callsign></B> Show the filters set by <callsign></CODE>
2145 <P>A sysop can look at any filters that have been set.
2147 <H2><A NAME="ss10.132">10.132 show/hfstats (0)</A>
2150 <P><CODE><B>show/hfstats</B> Show the HF DX Statistics for last 31 days</CODE>
2152 <P>Show the HF DX spots breakdown by band for the last 31 days
2154 <H2><A NAME="ss10.133">10.133 show/hftable (0)</A>
2157 <P><CODE><B>show/hftable</B> Show the HF DX Spotter Table for your country</CODE>
2159 <P>Show the HF DX Spotter table for your country for the last 31 days
2161 <H2><A NAME="ss10.134">10.134 show/hops (8)</A>
2164 <P><CODE><B>show/hops <node_call> [ann|spots|wcy|wwv|]</B> Show the hop counts for a node</CODE>
2166 <P>This command shows the hop counts set up for a node. You can specify
2167 which category you want to see. If you leave the category out then
2168 all the categories will be listed.
2170 <H2><A NAME="ss10.135">10.135 show/isolate (1)</A>
2173 <P><CODE><B>show/isolate</B> Show a list of isolated nodes</CODE>
2175 <P>Show which nodes are currently set to be isolated.
2177 <H2><A NAME="ss10.136">10.136 show/lockout (9)</A>
2180 <P><CODE><B>show/lockout</B> Show a list of excluded callsigns</CODE>
2182 <P>Show a list of callsigns that have been excluded (locked out) of the
2183 cluster locally with the <EM>set/lockout</EM> command
2185 <H2><A NAME="ss10.137">10.137 show/log (8)</A>
2188 <P><CODE><B>show/log [<callsign>]</B> Show excerpts from the system log</CODE>
2190 <P>This command outputs a short section of the system log. On its own
2191 it will output a general logfile. With the optional callsign it will
2192 show output from the log associated with that callsign.
2194 <H2><A NAME="ss10.138">10.138 show/moon (0)</A>
2197 <P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
2198 rise and set times</CODE>
2200 <P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
2201 together with the azimuth and elevation of the sun currently at those
2203 <P>If you don't specify any prefixes or callsigns, it will show the times for
2204 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2205 together with the current azimuth and elevation.
2206 <P>In addition, it will show the gain or loss dB relative to the nominal
2207 distance of 385,000Km due to the ellipsoidal nature of the orbit.
2208 <P>If all else fails it will show the Moonrise and set times for the node
2209 that you are connected to.
2217 </CODE></BLOCKQUOTE>
2219 <H2><A NAME="ss10.139">10.139 show/muf (0)</A>
2222 <P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
2223 the likely propagation to <prefix></CODE>
2225 <P>This command allow you to estimate the likelihood of you contacting
2226 a station with the prefix you have specified. The output assumes a modest
2227 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
2228 <P>The result predicts the most likely operating frequencies and signal
2229 levels for high frequency (shortwave) radio propagation paths on
2230 specified days of the year and hours of the day. It is most useful for
2231 paths between 250 km and 6000 km, but can be used with reduced accuracy
2232 for paths shorter or longer than this.
2233 <P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
2234 used to predict the MUF given the predicted flux, day of the year,
2235 hour of the day and geographic coordinates of the transmitter and
2236 receiver. This routine is reasonably accurate for the purposes here,
2237 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
2238 than the programs used by major shortwave broadcasting organizations,
2239 such as the Voice of America.
2240 <P>The command will display some header information detailing its
2241 assumptions, together with the locations, latitude and longitudes and
2242 bearings. It will then show UTC (UT), local time at the other end
2243 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
2244 (Zen) and the likely signal strengths. Then for each frequency for which
2245 the system thinks there is a likelihood of a circuit it prints a value.
2246 <P>The value is currently a likely S meter reading based on the conventional
2247 6dB / S point scale. If the value has a '+' appended it means that it is
2248 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
2249 there is likely to be much fading and by an 's' that the signal is likely
2251 <P>By default SHOW/MUF will show the next two hours worth of data. You
2252 can specify anything up to 24 hours worth of data by appending the no of
2253 hours required after the prefix. For example:-
2259 </CODE></BLOCKQUOTE>
2264 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
2265 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
2266 Location Lat / Long Azim
2267 East Dereham, Norfolk 52 41 N 0 57 E 47
2268 United-States-W 43 0 N 87 54 W 299
2269 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
2270 18 23 11.5 -35 mS0+ mS2 S3
2271 19 0 11.2 -41 mS0+ mS2 S3
2273 </CODE></BLOCKQUOTE>
2274 <P>indicating that you will have weak, fading circuits on top band and
2275 80m but usable signals on 40m (about S3).
2282 </CODE></BLOCKQUOTE>
2283 <P>will get you the above display, but with the next 24 hours worth of
2291 </CODE></BLOCKQUOTE>
2292 <P>Gives you an estimate of the long path propagation characterics. It
2293 should be noted that the figures will probably not be very useful, nor
2294 terrible accurate, but it is included for completeness.
2296 <H2><A NAME="ss10.140">10.140 show/newconfiguration (0)</A>
2299 <P><CODE><B>show/newconfiguration [<node>]</B> Show all the nodes and users visible</CODE>
2301 <P>This command allows you to see all the users that can be seen
2302 and the nodes to which they are connected.
2303 <P>This command produces essentially the same information as
2304 SHOW/CONFIGURATION except that it shows all the duplication of
2305 any routes that might be present It also uses a different format
2306 which may not take up quite as much space if you don't have any
2308 <P>BE WARNED: the list that is returned can be VERY long
2310 <H2><A NAME="ss10.141">10.141 show/newconfiguration/node (0)</A>
2313 <P><CODE><B>show/newconfiguration/node</B> Show all the nodes connected locally</CODE>
2315 <P>Show all the nodes connected to this node in the new format.
2317 <H2><A NAME="ss10.142">10.142 show/node (1)</A>
2320 <P><CODE><B>show/node [<node_call> ...]</B> Show the type and version
2321 number of nodes</CODE>
2323 <P>Show the type and version (if connected) of the nodes specified on the
2324 command line. If no callsigns are specified then a sorted list of all
2325 the non-user callsigns known to the system will be displayed.
2327 <H2><A NAME="ss10.143">10.143 show/prefix (0)</A>
2330 <P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE>
2332 <P>This command takes the <callsign> (which can be a full or partial
2333 callsign or a prefix), looks up which internal country number
2334 it is and then displays all the relevant prefixes for that country
2335 together with the internal country no, the CQ and ITU regions.
2336 <P>See also SHOW/DXCC
2339 <H2><A NAME="ss10.144">10.144 show/program (5)</A>
2342 <P><CODE><B>show/program</B> Show the locations of all the included program modules</CODE>
2344 <P>Show the name and location where every program module was load from. This
2345 is useful for checking where you think you have loaded a .pm file from.
2347 <H2><A NAME="ss10.145">10.145 show/qra (0)</A>
2350 <P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
2351 between locators<BR>
2352 <B>show/qra <lat> <long></B> Convert latitude and longitude to a locator</CODE>
2354 <P>This is a multipurpose command that allows you either to calculate the
2355 distance and bearing between two locators or (if only one locator is
2356 given on the command line) the distance and beraing from your station
2357 to the locator. For example:-
2364 </CODE></BLOCKQUOTE>
2365 <P>The first example will show the distance and bearing to the locator from
2366 yourself, the second example will calculate the distance and bearing from
2367 the first locator to the second. You can use 4 or 6 character locators.
2368 <P>It is also possible to convert a latitude and longitude to a locator by
2369 using this command with a latitude and longitude as an argument, for
2374 SH/QRA 52 41 N 0 58 E
2376 </CODE></BLOCKQUOTE>
2378 <H2><A NAME="ss10.146">10.146 show/qrz (0)</A>
2381 <P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE>
2383 <P>This command queries the QRZ callbook server on the internet
2384 and returns any information available for that callsign. This service
2385 is provided for users of this software by http://www.qrz.com
2387 <H2><A NAME="ss10.147">10.147 show/registered (9)</A>
2390 <P><CODE><B>show/registered [<prefix>[</B> Show the registered users</CODE>
2392 <H2><A NAME="ss10.148">10.148 show/route (0)</A>
2395 <P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE>
2397 <P>This command allows you to see to which node the callsigns specified are
2398 connected. It is a sort of inverse sh/config.
2404 </CODE></BLOCKQUOTE>
2406 <H2><A NAME="ss10.149">10.149 show/satellite (0)</A>
2409 <P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
2410 Show satellite tracking data</CODE>
2412 <P>Show the tracking data from your location to the satellite of your choice
2413 from now on for the next few hours.
2414 <P>If you use this command without a satellite name it will display a list
2415 of all the satellites known currently to the system.
2416 <P>If you give a name then you can obtain tracking data of all the passes
2417 that start and finish 5 degrees below the horizon. As default it will
2418 give information for the next three hours for every five minute period.
2419 <P>You can alter the number of hours and the step size, within certain
2421 <P>Each pass in a period is separated with a row of '-----' characters
2427 SH/SAT FENGYUN1 12 2
2429 </CODE></BLOCKQUOTE>
2431 <H2><A NAME="ss10.150">10.150 show/sun (0)</A>
2434 <P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
2435 sun rise and set times</CODE>
2437 <P>Show the sun rise and set times for a (list of) prefixes or callsigns,
2438 together with the azimuth and elevation of the sun currently at those
2440 <P>If you don't specify any prefixes or callsigns, it will show the times for
2441 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2442 together with the current azimuth and elevation.
2443 <P>If all else fails it will show the sunrise and set times for the node
2444 that you are connected to.
2450 SH/SUN G1TLH K9CW ZS
2452 </CODE></BLOCKQUOTE>
2454 <H2><A NAME="ss10.151">10.151 show/time (0)</A>
2457 <P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
2458 the local time</CODE>
2460 <P>If no prefixes or callsigns are given then this command returns the local
2461 time and UTC as the computer has it right now. If you give some prefixes
2462 then it will show UTC and UTC + the local offset (not including DST) at
2463 the prefixes or callsigns that you specify.
2465 <H2><A NAME="ss10.152">10.152 show/vhfstats (0)</A>
2468 <P><CODE><B>show/vhfstats</B> Show the VHF DX Statistics for last 31 days</CODE>
2470 <P>Show the VHF DX spots breakdown by band for the last 31 days
2472 <H2><A NAME="ss10.153">10.153 show/vhftable (0)</A>
2475 <P><CODE><B>show/vhftable</B> Show the VHF DX Spotter Table for your country</CODE>
2477 <P>Show the VHF DX Spotter table for your country for the last 31 days
2479 <H2><A NAME="ss10.154">10.154 show/wcy (0)</A>
2482 <P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
2483 <B>show/wcy <n></B> Show the last <n> WCY broadcasts</CODE>
2485 <P>Display the most recent WCY information that has been received by the system
2487 <H2><A NAME="ss10.155">10.155 show/wwv (0)</A>
2490 <P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
2491 <B>show/wwv <n></B> Show the last <n> WWV broadcasts</CODE>
2493 <P>Display the most recent WWV information that has been received by the system
2496 <H2><A NAME="ss10.156">10.156 shutdown (5)</A>
2499 <P><CODE><B>shutdown</B> Shutdown the cluster</CODE>
2501 <P>Shutdown the cluster and disconnect all the users. If you have Spider
2502 set to respawn in /etc/inittab it will of course restart.
2504 <H2><A NAME="ss10.157">10.157 spoof (9)</A>
2507 <P><CODE><B>spoof <callsign> <command></B> Run commands as another user</CODE>
2509 <P>This is a very simple yet powerful command for the sysop. It allows you to
2510 issue commands as if you were a different user. This is very useful for the
2511 kind of things that users seem to always get wrong.. like home_node for
2514 <H2><A NAME="ss10.158">10.158 stat/db (5)</A>
2517 <P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE>
2519 <P>Show the internal status of a database descriptor.
2520 <P>Depending on your privilege level you will see more or less information.
2521 This command is unlikely to be of much use to anyone other than a sysop.
2523 <H2><A NAME="ss10.159">10.159 stat/channel (5)</A>
2526 <P><CODE><B>stat/channel <callsign></B> Show the status of a channel on the cluster</CODE>
2528 <P>Show the internal status of the channel object either for the channel that
2529 you are on or else for the callsign that you asked for.
2530 <P>Only the fields that are defined (in perl term) will be displayed.
2532 <H2><A NAME="ss10.160">10.160 stat/msg (5)</A>
2535 <P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE>
2537 <P>This command shows the internal status of a message and includes information
2538 such as to whom it has been forwarded, its size, origin etc etc.
2540 <P>If no message number is given then the status of the message system is
2543 <H2><A NAME="ss10.161">10.161 stat/route_node (5)</A>
2546 <P><CODE><B>stat/route_node <callsign></B> Show the data in a Route::Node object</CODE>
2548 <H2><A NAME="ss10.162">10.162 stat/route_user (5)</A>
2551 <P><CODE><B>stat/route_user <callsign></B> Show the data in a Route::User object</CODE>
2553 <H2><A NAME="ss10.163">10.163 stat/user (5)</A>
2556 <P><CODE><B>stat/user <callsign></B> Show the full status of a user</CODE>
2558 <P>Shows the full contents of a user record including all the secret flags
2560 <P>Only the fields that are defined (in perl term) will be displayed.
2562 <H2><A NAME="ss10.164">10.164 sysop (0)</A>
2565 <P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE>
2567 <P>The system automatically reduces your privilege level to that of a
2568 normal user if you login in remotely. This command allows you to
2569 regain your normal privilege level. It uses the normal system: five
2570 numbers are returned that are indexes into the character array that is
2571 your assigned password (see SET/PASSWORD). The indexes start from
2573 <P>You are expected to return a string which contains the characters
2574 required in the correct order. You may intersperse those characters
2575 with others to obscure your reply for any watchers. For example (and
2576 these values are for explanation :-):
2580 password = 012345678901234567890123456789
2584 </CODE></BLOCKQUOTE>
2589 aa2bbbb0ccc5ddd7xxx3n
2593 </CODE></BLOCKQUOTE>
2594 <P>They will all match. If there is no password you will still be offered
2595 numbers but nothing will happen when you input a string. Any match is
2598 <H2><A NAME="ss10.165">10.165 talk (0)</A>
2601 <P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
2602 <B>talk <callsign> <text></B> Send a text message to <callsign><BR>
2603 <B>talk <callsign> > <node_call> [<text>]</B>
2604 Send a text message to <callsign> via <node_call></CODE>
2606 <P>Send a short message to any other station that is visible on the cluster
2607 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2608 command, they don't have to be connected locally.
2609 <P>The second form of TALK is used when other cluster nodes are connected
2610 with restricted information. This usually means that they don't send
2611 the user information usually associated with logging on and off the cluster.
2612 <P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
2613 see GB7TLH in the SH/C list but with no users, then you would use the
2614 second form of the talk message.
2615 <P>If you want to have a ragchew with someone you can leave the text message
2616 out and the system will go into 'Talk' mode. What this means is that a
2617 short message is sent to the recipient telling them that you are in a 'Talking'
2618 frame of mind and then you just type - everything you send will go to the
2619 station that you asked for.
2620 <P>All the usual announcements, spots and so on will still come out on your
2622 <P>If you want to do something (such as send a spot) you precede the normal
2623 command with a '/' character, eg:-
2627 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2630 </CODE></BLOCKQUOTE>
2631 <P>To leave talk mode type:
2637 </CODE></BLOCKQUOTE>
2639 <H2><A NAME="ss10.166">10.166 type (0)</A>
2642 <P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE>
2644 <P>Type out the contents of a file in a filearea. So, for example, in
2645 filearea 'bulletins' you want to look at file 'arld051' you would
2650 TYPE bulletins/arld051
2652 </CODE></BLOCKQUOTE>
2653 <P>See also SHOW/FILES to see what fileareas are available and a
2656 <H2><A NAME="ss10.167">10.167 who (0)</A>
2659 <P><CODE><B>who</B> Show who is physically connected locally</CODE>
2661 <P>This is a quick listing that shows which callsigns are connected and
2662 what sort of connection they have
2664 <H2><A NAME="ss10.168">10.168 wx (0)</A>
2667 <P><CODE><B>wx <text></B> Send a weather message to local users<BR>
2668 <B>wx full <text> </B> Send a weather message to all cluster users</CODE>
2670 <P>Weather messages can sometimes be useful if you are experiencing an extreme
2671 that may indicate enhanced conditions
2673 <H2><A NAME="ss10.169">10.169 wx (enhanced for sysops) (5)</A>
2676 <P><CODE><B>wx sysop <text></B> Send a weather message to other clusters only</CODE>
2678 <P>Send a weather message only to other cluster nodes and not to general users.
2684 <A HREF="adminmanual-9.html">Previous</A>
2685 <A HREF="adminmanual.html#toc10">Contents</A>
projects / spider.git / blob