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.49: The DXSpider command set</TITLE>
6 <LINK HREF="adminmanual-8.html" REL=previous>
7 <LINK HREF="adminmanual.html#toc9" REL=contents>
8 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="adminmanual-8.html">Previous</A>
13 <A HREF="adminmanual.html#toc9">Contents</A>
15 <H2><A NAME="s9">9. 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="ss9.1">9.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="ss9.2">9.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="ss9.3">9.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="ss9.4">9.4 accept/spots (0)</A>
139 <P><CODE><B>accept/announce [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="ss9.5">9.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="ss9.6">9.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="ss9.7">9.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="ss9.8">9.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="ss9.9">9.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="ss9.10">9.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="ss9.11">9.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="ss9.12">9.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="ss9.13">9.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="ss9.14">9.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="ss9.15">9.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="ss9.16">9.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="ss9.17">9.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="ss9.18">9.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="ss9.19">9.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="ss9.20">9.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="ss9.21">9.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="ss9.22">9.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="ss9.23">9.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="ss9.24">9.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="ss9.25">9.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="ss9.26">9.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="ss9.27">9.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="ss9.28">9.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="ss9.29">9.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="ss9.30">9.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="ss9.31">9.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!
614 <H2><A NAME="ss9.32">9.32 directory (0)</A>
617 <P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
618 <B>directory own</B> List your own messages<BR>
619 <B>directory new</B> List all new messages<BR>
620 <B>directory to <call></B> List all messages to <call><BR>
621 <B>directory from <call></B> List all messages from <call><BR>
622 <B>directory subject <string></B> List all messages with <string> in subject<BR>
623 <B>directory <nn></B> List last <nn> messages<BR>
624 <B>directory <from>-<to></B> List messages <from> message <to> message <BR></CODE>
626 <P>List the messages in the messages directory.
627 <P>If there is a 'p' one space after the message number then it is a
628 personal message. If there is a '-' between the message number and the
629 'p' then this indicates that the message has been read.
630 <P>You can use shell escape characters such as '*' and '?' in the <call>
632 <P>You can combine some of the various directory commands together eg:-
638 DIR SUBJECT IOTA 200-250
641 <P>You can abbreviate all the commands to one letter and use ak1a syntax:-
651 <H2><A NAME="ss9.33">9.33 directory (extended for sysops) (5)</A>
654 <P>Works just like the user command except that sysops can see ALL messages.
656 <H2><A NAME="ss9.34">9.34 disconnect (8)</A>
659 <P><CODE><B>disconnect <call> [<call> ...]</B> Disconnect a user or node</CODE>
661 <P>Disconnect any <call> connected locally
663 <H2><A NAME="ss9.35">9.35 dx (0)</A>
666 <P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE>
668 <P>This is how you send a DX Spot to other users. You can, in fact, now
669 enter the <freq> and the <call> either way round.
678 <P>will all give the same result. You can add some remarks to the end
679 of the command and they will be added to the spot.
683 DX FR0G 144600 this is a test
686 <P>You can credit someone else by saying:-
690 DX by G1TLH FR0G 144.600 he isn't on the cluster
693 <P>The <freq> is compared against the available bands set up in the
694 cluster. See SHOW/BANDS for more information.
696 <H2><A NAME="ss9.36">9.36 export (9)</A>
699 <P><CODE><B>export <msgno> <filename></B> Export a message to a file</CODE>
701 <P>Export a message to a file. This command can only be executed on a local
702 console with a fully privileged user. The file produced will be in a form
703 ready to be imported back into the cluster by placing it in the import
704 directory (/spider/msg/import).
705 <P>This command cannot overwrite an existing file. This is to provide some
706 measure of security. Any files written will owned by the same user as the
707 main cluster, otherwise you can put the new files anywhere the cluster can
708 access. For example:-
709 <P>EXPORT 2345 /tmp/a
711 <H2><A NAME="ss9.37">9.37 export_users (9)</A>
714 <P><CODE><B>export_users [<filename>]</B> Export the users database to ascii</CODE>
716 <P>Export the users database to a file in ascii format. If no filename
717 is given then it will export the file to /spider/data/user_asc.
718 <P>If the file already exists it will be renamed to <filename>.o. In fact
719 up to 5 generations of the file can be kept each one with an extra 'o' on the
721 <P>BE WARNED: this will write to any file you have write access to. No check is
722 made on the filename (if any) that you specify.
724 <H2><A NAME="ss9.38">9.38 filtering (0)</A>
727 <P><CODE><B>filtering</B> Filtering things in DXSpider</CODE>
729 <P>There are a number of things you can filter in the DXSpider system. They
730 all use the same general mechanism.
731 <P>In general terms you can create a 'reject' or an 'accept' filter which
732 can have up to 10 lines in it. You do this using, for example:-
733 <P>accept/spots .....
735 <P>where ..... are the specific commands for that type of filter. There
736 are filters for spots, wwv, announce, wcy and (for sysops)
737 connects. See each different accept or reject command reference for
739 <P>There is also a command to clear out one or more lines in a filter and
740 one to show you what you have set. They are:-
745 <P>There is clear/xxxx command for each type of filter.
746 <P>For now we are going to use spots for the examples, but you can apply
747 the principles to all types of filter.
748 <P>There are two main types of filter 'accept' or 'reject'; which you use
749 depends entirely on how you look at the world and what is least
750 writing to achieve what you want. Each filter has 10 lines (of any
751 length) which are tried in order. If a line matches then the action
752 you have specified is taken (ie reject means ignore it and accept
754 <P>The important thing to remember is that if you specify a 'reject'
755 filter (all the lines in it say 'reject/spots' (for instance) then if
756 a spot comes in that doesn't match any of the lines then you will get
757 it BUT if you specify an 'accept' filter then any spots that don't
758 match are dumped. For example if I have a one line accept filter:-
759 <P>accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
760 <P>then automatically you will ONLY get VHF spots from or to CQ zones 14
761 15 and 16. If you set a reject filter like:
762 <P>reject/spots on hf/cw
763 <P>Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
764 and will work it even on CW then you could say:-
765 <P>reject/spots on hf/cw and not info iota
766 <P>But in that case you might only be interested in iota and say:-
767 <P>accept/spots not on hf/cw or info iota
768 <P>which is exactly the same. You should choose one or the other until
769 you are confortable with the way it works. Yes, you can mix them
770 (actually you can have an accept AND a reject on the same line) but
771 don't try this at home until you can analyse the results that you get
772 without ringing up the sysop for help.
773 <P>You can arrange your filter lines into logical units, either for your
774 own understanding or simply convenience. I have one set frequently:-
775 <P>reject/spots 1 on hf/cw
776 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
777 <P>What this does is to ignore all HF CW spots (being a class B I can't
778 read any CW and couldn't possibly be interested in HF :-) and also
779 rejects any spots on VHF which don't either originate or spot someone
781 <P>This is an exmaple where you would use the line number (1 and 2 in
782 this case), if you leave the digit out, the system assumes '1'. Digits
783 '0'-'9' are available.
784 <P>You can leave the word 'and' out if you want, it is implied. You can
785 use any number of brackets to make the 'expression' as you want
786 it. There are things called precedence rules working here which mean
787 that you will NEED brackets in a situation like line 2 because,
788 without it, will assume:-
789 <P>(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
790 <P>annoying, but that is the way it is. If you use OR - use
791 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
793 <P>If you want to alter your filter you can just redefine one or more
794 lines of it or clear out one line. For example:-
795 <P>reject/spots 1 on hf/ssb
798 <P>To remove the filter in its entirty:-
800 <P>There are similar CLEAR commands for the other filters:-
805 <P>Once you are happy with the results you get, you may like to experiment.
806 <P>my example that filters hf/cw spots and accepts vhf/uhf spots from EU
807 can be written with a mixed filter, eg:
810 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
811 <P>each filter slot actually has a 'reject' slot and an 'accept'
812 slot. The reject slot is executed BEFORE the accept slot.
813 <P>It was mentioned earlier that after a reject test that doesn't match,
814 the default for following tests is 'accept', the reverse is true for
815 'accept'. In the example what happens is that the reject is executed
816 first, any non hf/cw spot is passed to the accept line, which lets
817 thru everything else on HF.
818 <P>The next filter line lets through just VHF/UHF spots from EU.
820 <H2><A NAME="ss9.39">9.39 forward/latlong (8)</A>
823 <P><CODE><B>forward/latlong <node_call></B> Send latitude and longitude information to another cluster</CODE>
825 <P>This command sends all the latitude and longitude information that your
826 cluster is holding against callsigns. One advantage of recieving this
827 information is that more locator information is held by you. This
828 means that more locators are given on the DX line assuming you have
829 <EM>set/dxgrid</EM> enabled. This could be a LOT of information though, so
830 it is not recommended on slow links.
832 <H2><A NAME="ss9.40">9.40 forward/opername (1)</A>
835 <P><CODE><B>forward/opername <call></B> Send out information on this <call> to all clusters</CODE>
837 <P>This command sends out any information held in the user file which can
838 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
839 and Homenode. PC41s are only sent for the information that is available.
841 <H2><A NAME="ss9.41">9.41 help (0)</A>
844 <P><CODE><B>help <cmd></B> Get help on a command</CODE>
846 <P>All commands can be abbreviated, so SHOW/DX can be abbreviated
847 to SH/DX, ANNOUNCE can be shortened to AN and so on.
848 <P>Look at the APROPOS <string> command which will search the help database
849 for the <string> you specify and give you a list of likely commands
850 to look at with HELP.
852 <H2><A NAME="ss9.42">9.42 init (5)</A>
855 <P><CODE><B>init <node call></B> Re-initialise a link to an AK1A compatible node</CODE>
857 <P>This command attempts to re-initialise a link to a (usually) AK1A node
858 that has got confused, usually by a protocol loop of some kind. It may
859 work - but you usually will be better off simply disconnecting it (or
860 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
862 <P>Best of luck - you will need it.
864 <H2><A NAME="ss9.43">9.43 kill (0)</A>
867 <P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE>
869 <P>Delete a message from the local system. You will only be able to
870 delete messages that you have originated or been sent (unless you are
873 <H2><A NAME="ss9.44">9.44 kill (5)</A>
876 <P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system<BR>
877 <B>kill from <call></B> Remove all messages from a callsign<BR>
878 <B>kill to <call></B> Remove all messages to a callsign<BR></CODE>
880 <P>You can get rid of any message to or originating from your callsign using
881 this command. You can remove more than one message at a time.
882 <P>As a sysop you can kill any message on the system.
884 <H2><A NAME="ss9.45">9.45 kill full (5)</A>
887 <P><CODE><B>kill full <msgno> [<msgno>]</B> Delete a message from the whole cluster</CODE>
889 <P>Delete a message (usually a 'bulletin') from the whole cluster system.
890 <P>This uses the subject field, so any messages that have exactly the same subject
891 will be deleted. Beware!
893 <H2><A NAME="ss9.46">9.46 kill/expunge (6)</A>
896 <P><CODE><B>kill/expunge <msgno> [<msgno>..]</B>Expunge a message</CODE>
898 <P>Deleting a message using the normal KILL commands only marks that message
899 for deletion. The actual deletion only happens later (usually two days later).
900 <P>The KILL EXPUNGE command causes the message to be truly deleted more or less
902 <P>It otherwise is used in the same way as the KILL command.
905 <H2><A NAME="ss9.47">9.47 links (0)</A>
908 <P><CODE><B>links</B> Show which nodes are physically connected</CODE>
910 <P>This is a quick listing that shows which links are connected and
911 some information about them. See WHO for a list of all connections.
914 <H2><A NAME="ss9.48">9.48 load/aliases (9)</A>
917 <P><CODE><B>load/aliases</B> Reload the command alias table</CODE>
919 <P>Reload the /spider/cmd/Aliases file after you have editted it. You will need to
920 do this if you change this file whilst the cluster is running in order for the
921 changes to take effect.
923 <H2><A NAME="ss9.49">9.49 load/badmsg (9)</A>
926 <P><CODE><B>load/badmsg</B> Reload the bad message table</CODE>
928 <P>Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
929 the cluster is running. This table contains a number of perl regular
930 expressions which are searched for in the fields targetted of each message.
931 If any of them match then that message is immediately deleted on receipt.
933 <H2><A NAME="ss9.50">9.50 load/badwords (9)</A>
936 <P><CODE><B>load/badwords</B> Reload the bad words table</CODE>
938 <P>Reload the /spider/data/badwords file if you have changed it manually whilst
939 the cluster is running. This file contains a list of words which, if found
940 on certain text portions of PC protocol, will cause those protocol frames
941 to be rejected. It will all put out a message if any of these words are
942 used on the announce, dx and talk commands. The words can be one or
943 more on a line, lines starting with '#' are ignored.
945 <H2><A NAME="ss9.51">9.51 load/bands (9)</A>
948 <P><CODE><B>load/bands</B> Reload the band limits table</CODE>
950 <P>Reload the /spider/data/bands.pl file if you have changed it manually whilst
951 the cluster is running.
953 <H2><A NAME="ss9.52">9.52 load/cmd_cache (9)</A>
956 <P><CODE><B>load/cmd_cache</B> Reload the automatic command cache</CODE>
958 <P>Normally, if you change a command file in the cmd or local_cmd tree it will
959 automatially be picked up by the cluster program. Sometimes it can get confused
960 if you are doing a lot of moving commands about or delete a command in the
961 local_cmd tree and want to use the normal one again. Execute this command to
962 reset everything back to the state it was just after a cluster restart.
964 <H2><A NAME="ss9.53">9.53 load/forward (9)</A>
967 <P><CODE><B>load/forward</B> Reload the msg forwarding routing table</CODE>
968 <P>Reload the /spider/msg/forward.pl file if you have changed it
969 manually whilst the cluster is running.
971 <H2><A NAME="ss9.54">9.54 load/messages (9)</A>
974 <P><CODE><B>load/messages</B> Reload the system messages file</CODE>
976 <P>If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne
977 commands) you can have them take effect during a cluster session by executing this
978 command. You need to do this if get something like :-
979 <P>unknown message 'xxxx' in lang 'en'
981 <H2><A NAME="ss9.55">9.55 load/prefixes (9)</A>
984 <P><CODE><B>load/prefixes</B> Reload the prefix table</CODE>
986 <P>Reload the /spider/data/prefix_data.pl file if you have changed it manually
987 whilst the cluster is running.
989 <H2><A NAME="ss9.56">9.56 merge (5)</A>
992 <P><CODE><B>merge <node> [<no spots>/<no wwv>]</B> Ask for the latest spots and WWV</CODE>
994 <P>MERGE allows you to bring your spot and wwv database up to date. By default
995 it will request the last 10 spots and 5 WWVs from the node you select. The
996 node must be connected locally.
997 <P>You can request any number of spots or wwv and although they will be appended
998 to your databases they will not duplicate any that have recently been added
999 (the last 2 days for spots and last month for WWV data).
1001 <H2><A NAME="ss9.57">9.57 msg (9)</A>
1004 <P><CODE><B>msg <cmd> <msgno> [data ...]</B> Alter various message parameters</CODE>
1006 <P>Alter message parameters like To, From, Subject, whether private or bulletin
1007 or return receipt (RR) is required or whether to keep this message from timing
1012 MSG TO <msgno> <call> - change TO callsign to <call>
1013 MSG FRom <msgno> <call> - change FROM callsign to <call>
1014 MSG PRrivate <msgno> - set private flag
1015 MSG NOPRrivate <msgno> - unset private flag
1016 MSG RR <msgno> - set RR flag
1017 MSG NORR <msgno> - unset RR flag
1018 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1019 MSG NOKEep <msgno> - unset the keep flag
1020 MSG SUbject <msgno> <new> - change the subject to <new>
1021 MSG WAittime <msgno> - remove any waitting time for this message
1022 MSG NOREad <msgno> - mark message as unread
1023 MSG REad <msgno> - mark message as read
1024 MSG QUeue - queue any outstanding bulletins
1025 MSG QUeue 1 - queue any outstanding private messages
1027 </CODE></BLOCKQUOTE>
1028 <P>You can look at the status of a message by using:-
1029 <P>STAT/MSG <msgno>
1030 <P>This will display more information on the message than DIR does.
1032 <H2><A NAME="ss9.58">9.58 pc (8)</A>
1035 <P><CODE><B>pc <call> <text></B> Send text (eg PC Protocol) to <call></CODE>
1037 <P>Send some arbitrary text to a locally connected callsign. No processing is done on
1038 the text. This command allows you to send PC Protocol to unstick things if problems
1039 arise (messages get stuck etc). eg:-
1040 <P>pc gb7djk PC33^GB7TLH^GB7DJK^400^
1041 <P>You can also use in the same way as a talk command to a connected user but
1042 without any processing, added of "from <blah> to <blah>" or whatever.
1043 <P>pc G1TLH Try doing that properly!!!
1045 <H2><A NAME="ss9.59">9.59 ping (1)</A>
1048 <P><CODE><B>ping <node></B> Check the link quality between nodes</CODE>
1050 <P>his command allows you to send a frame to another cluster node on
1051 the network and get a return frame. The time it takes to do this
1052 is a good indication of the quality of the link. The actual time
1053 it takes is output to the console in seconds.
1054 Any visible cluster node can be PINGed.
1057 <H2><A NAME="ss9.60">9.60 rcmd (1)</A>
1060 <P><CODE><B>rcmd <node call> <cmd></B> Send a command to another DX cluster</CODE>
1062 <P>This command allows you to send nearly any command to another DX Cluster
1063 node that is connected to the system.
1064 <P>Whether you get any output is dependant on a) whether the other system knows
1065 that the node callsign of this cluster is in fact a node b) whether the
1066 other system is allowing RCMDs from this node and c) whether you have
1067 permission to send this command at all.
1069 <H2><A NAME="ss9.61">9.61 read (0)</A>
1072 <P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
1073 <B>read <msgno></B> Read the specified message<BR></CODE>
1075 <P>You can read any messages that are sent as 'non-personal' and also any
1076 message either sent by or sent to your callsign.
1079 <H2><A NAME="ss9.62">9.62 read (extended for sysops) (5) </A>
1082 <P><CODE><B>read <msgno></B> Read a message on the system</CODE>
1084 <P>As a sysop you may read any message on the system
1086 <H2><A NAME="ss9.63">9.63 reject/announce</A>
1089 <P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
1092 <P>Create an 'reject this announce' line for a filter.
1093 <P>An reject filter line means that if the announce matches this filter it is
1094 passed onto the user. See HELP FILTERS for more info. Please read this
1095 to understand how filters work - it will save a lot of grief later on.
1096 <P>You can use any of the following things in this line:-
1100 info <string> eg: iota or qsl
1101 by <prefixes> eg: G,M,2
1102 origin <prefixes>
1103 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1104 origin_itu <numbers>
1105 origin_zone <numbers>
1106 by_dxcc <numbers>
1108 by_zone <numbers>
1109 channel <prefixes>
1110 wx 1 filter WX announces
1111 dest <prefixes> eg: 6MUK,WDX (distros)
1113 </CODE></BLOCKQUOTE>
1118 rej/ann by_zone 14,15,16 and not by G,M,2
1120 </CODE></BLOCKQUOTE>
1121 <P>You can use the tag 'all' to reject everything eg:
1127 </CODE></BLOCKQUOTE>
1128 <P>but this probably for advanced users...
1130 <H2><A NAME="ss9.64">9.64 reject/announce (extended for sysops) (8)</A>
1133 <P><CODE><B>reject/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE>
1135 <P>This version allows a sysop to set a filter for a callsign as well as the
1136 default for nodes and users eg:-
1141 reject/ann input node_default by G,M,2
1142 reject/ann user_default by G,M,2
1144 </CODE></BLOCKQUOTE>
1146 <H2><A NAME="ss9.65">9.65 reject/route (8)</A>
1149 <P><CODE><B>reject/route <call> [0-9] <pattern></B> Set an 'reject' filter line for routing</CODE>
1151 <P>Create an 'reject this routing PC Protocol' line for a filter.
1153 <P>An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1154 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
1155 read this to understand how filters work - it will save a lot of grief later on.
1156 You can use any of the following things in this line:-
1160 call <prefixes> the callsign of the thingy
1161 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1162 call_itu <numbers>
1163 call_zone <numbers>
1164 origin <prefixes> really the interface it came in on
1165 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1166 origin_itu <numbers>
1167 origin_zone <numbers>
1169 </CODE></BLOCKQUOTE>
1175 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
1177 </CODE></BLOCKQUOTE>
1179 <P>You can use the tag 'all' to reject everything eg:
1183 rej/route all (equiv to [very] restricted mode)
1185 </CODE></BLOCKQUOTE>
1187 <H2><A NAME="ss9.66">9.66 reject/spots (0)</A>
1190 <P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE>
1192 <P>Create a 'reject this spot' line for a filter.
1193 <P>A reject filter line means that if the spot matches this filter it is
1194 dumped (not passed on). See HELP FILTERS for more info. Please read this
1195 to understand how filters work - it will save a lot of grief later on.
1196 <P>You can use any of the following things in this line:-
1200 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1201 on <range> same as 'freq'
1202 call <prefixes> eg: G,PA,HB9
1203 info <string> eg: iota or qsl
1205 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1206 call_itu <numbers>
1207 call_zone <numbers>
1208 by_dxcc <numbers>
1210 by_zone <numbers>
1211 origin <prefixes>
1212 channel <prefixes>
1214 </CODE></BLOCKQUOTE>
1215 <P>For frequencies, you can use any of the band names defined in
1216 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1217 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1218 this is more efficient than saying simply: on HF (but don't get
1219 too hung up about that)
1225 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1227 </CODE></BLOCKQUOTE>
1228 <P>You can use the tag 'all' to reject everything eg:
1234 </CODE></BLOCKQUOTE>
1235 <P>but this probably for advanced users...
1237 <H2><A NAME="ss9.67">9.67 reject/spots (extended for sysops) (8)</A>
1240 <P><CODE><B>reject/spots <call> [input] [0-9] <pattern></B>
1241 Reject spot filter sysop version </CODE>
1243 <P>This version allows a sysop to set a filter for a callsign as well as the
1244 default for nodes and users eg:-
1248 reject/spot db0sue-7 1 by_zone 14,15,16
1249 reject/spot node_default all
1250 set/hops node_default 10
1252 reject/spot user_default by G,M,2
1254 </CODE></BLOCKQUOTE>
1256 <H2><A NAME="ss9.68">9.68 reject/wcy (0)</A>
1259 <P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE>
1261 <P>It is unlikely that you will want to do this, but if you do then you can
1262 filter on the following fields:-
1266 by <prefixes> eg: G,M,2
1267 origin <prefixes>
1268 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1269 origin_itu <numbers>
1270 origin_zone <numbers>
1271 by_dxcc <numbers>
1273 by_zone <numbers>
1274 channel <prefixes>
1276 </CODE></BLOCKQUOTE>
1277 <P>There are no examples because WCY Broadcasts only come from one place and
1278 you either want them or not (see UNSET/WCY if you don't want them).
1279 <P>This command is really provided for future use.
1280 <P>See HELP FILTER for information.
1282 <H2><A NAME="ss9.69">9.69 reject/wcy (extended for sysops) (8)</A>
1285 <P><CODE><B>reject/wcy <call> [input] [0-9] <pattern></B>
1286 WCY reject filter sysop version</CODE>
1288 <P>This version allows a sysop to set a filter for a callsign as well as the
1289 default for nodes and users eg:-
1290 <P>reject/wcy gb7djk all
1292 <H2><A NAME="ss9.70">9.70 reject/wwv (0)</A>
1295 <P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE>
1297 <P>It is unlikely that you will want to do this, but if you do then you can
1298 filter on the following fields:-
1302 by <prefixes> eg: G,M,2
1303 origin <prefixes>
1304 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1305 origin_itu <numbers>
1306 origin_zone <numbers>
1307 by_dxcc <numbers>
1309 by_zone <numbers>
1310 channel <prefixes>
1312 </CODE></BLOCKQUOTE>
1317 reject/wwv by_zone 14,15,16
1319 </CODE></BLOCKQUOTE>
1320 <P>is probably the only useful thing to do (which will only show WWV broadcasts
1321 by stations in the US).
1322 <P>See HELP FILTER for information.
1324 <H2><A NAME="ss9.71">9.71 reject/wwv (extended for sysops) (8)</A>
1327 <P><CODE><B>reject/wwv <call> [input] [0-9] <pattern></B>
1328 WWV reject filter sysop version</CODE>
1330 <P>This version allows a sysop to set a filter for a callsign as well as the
1331 default for nodes and users eg:-
1335 reject/wwv db0sue-7 1 by_zone 4
1336 reject/wwv node_default all
1338 reject/wwv user_default by W
1340 </CODE></BLOCKQUOTE>
1342 <H2><A NAME="ss9.72">9.72 reply (0)</A>
1345 <P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
1346 <B>reply <msgno></B> Reply (privately) to the specified message<BR>
1347 <B>reply B <msgno></B> Reply as a Bulletin to the specified message<BR>
1348 <B>reply NOPrivate <msgno></B> Reply as a Bulletin to the specified
1350 <B>reply RR <msgno></B> Reply to the specified message with read receipt<BR></CODE>
1352 <P>You can reply to a message and the subject will automatically have
1353 "Re:" inserted in front of it, if it isn't already present.
1354 <P>You can also use all the extra qualifiers such as RR, PRIVATE,
1355 NOPRIVATE, B that you can use with the SEND command (see SEND
1356 for further details)
1358 <H2><A NAME="ss9.73">9.73 send (0)</A>
1361 <P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
1362 <B>send RR <call></B> Send a message and ask for a read receipt<BR>
1363 <B>send COPY <msgno> <call></B> Send a copy of a message to someone<BR>
1364 <B>send PRIVATE <call></B> Send a personal message<BR>
1365 <B>send NOPRIVATE <call></B> Send a message to all stations<BR></CODE>
1367 <P>All the SEND commands will create a message which will be sent either to
1368 an individual callsign or to one of the 'bulletin' addresses.
1369 <P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1370 it will mark the message as personal and send it to the cluster node that
1371 that callsign is connected to.
1372 <P>You can have more than one callsign in all of the SEND commands.
1373 <P>You can have multiple qualifiers so that you can have for example:-
1377 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1379 </CODE></BLOCKQUOTE>
1380 <P>which should send a copy of message 123 to G1TLH and G0RDI and you will
1381 receive a read receipt when they have read the message.
1382 <P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1383 SP is an alias for SEND PRIVATE
1385 <H2><A NAME="ss9.74">9.74 set/address (0)</A>
1388 <P><CODE><B>set/address <your_address></B> Record your postal address</CODE>
1390 <P>Literally, record your address details on the cluster.
1392 <H2><A NAME="ss9.75">9.75 set/announce (0)</A>
1395 <P><CODE><B>set/announce</B> Allow announce messages</CODE>
1397 <P>Allow announce messages to arrive at your terminal.
1399 <H2><A NAME="ss9.76">9.76 set/arcluster (5)</A>
1402 <P><CODE><B>set/arcluster <node_call> [<node_call> ...]</B> Make
1403 the node_call an AR-Cluster type node</CODE>
1405 <P>Set the node_call as an AR-Cluster type node
1407 <H2><A NAME="ss9.77">9.77 set/baddx (8)</A>
1410 <P><CODE><B>set/baddx <call></B> Stop words we do not wish to see in the callsign field
1411 of a dx spot being propagated</CODE>
1413 <P>Setting a word as 'baddx' will prevent spots with that word in the callsign
1414 field of a DX spot from going any further. They will not be displayed and they
1415 will not be sent onto other nodes.
1416 <P>The word must be wriiten in full, no wild cards are allowed eg:-
1420 set/baddx FORSALE VIDEO FR0G
1422 </CODE></BLOCKQUOTE>
1423 <P>To allow a word again, use the following command ...
1429 </CODE></BLOCKQUOTE>
1431 <H2><A NAME="ss9.78">9.78 set/badnode (6)</A>
1434 <P><CODE><B>set/badnode <node_call></B> Stop spots from this node_call
1435 being propagated</CODE>
1437 <P>Setting a callsign as a 'badnode' will prevent spots from that node
1438 going any further. They will not be displayed and they will not be
1439 sent onto other nodes.
1440 <P>The call can be a full or partial call (or a prefix), eg:-
1446 </CODE></BLOCKQUOTE>
1447 <P>will stop anything from K1TTT (including any SSID's)
1453 </CODE></BLOCKQUOTE>
1454 <P>will allow spots from him again.
1455 <P>Use with extreme care. This command may well be superceded by FILTERing.
1457 <H2><A NAME="ss9.79">9.79 set/badspotter (8)</A>
1460 <P><CODE><B>set/badspotter <call></B> Stop spots from this callsign being propagated</CODE>
1462 <P>Setting a callsign as a 'badspotter' will prevent spots from this callsign
1463 going any further. They will not be displayed and they will not be
1464 sent onto other nodes.
1465 <P>The call must be written in full, no wild cards are allowed eg:-
1469 set/badspotter VE2STN
1471 </CODE></BLOCKQUOTE>
1472 <P>will stop anything from VE2STN. If you want SSIDs as well then you must
1473 enter them specifically.
1477 unset/badspotter VE2STN
1479 </CODE></BLOCKQUOTE>
1480 <P>will allow spots from him again.
1481 <P>Use with extreme care. This command may well be superceded by FILTERing.
1483 <H2><A NAME="ss9.80">9.80 set/badword (8)</A>
1486 <P><CODE><B>set/badword <word></B> Stop things with this word being propogated</CODE>
1488 <P>Setting a word as a 'badword' will prevent things like spots,
1489 announces or talks with this word in the the text part from going any
1490 further. They will not be displayed and they will not be sent onto
1492 <P>The word must be written in full, no wild cards are allowed eg:-
1493 <P>set/badword annihilate annihilated annihilation
1494 <P>will stop anything with these words in the text.
1495 <P>unset/badword annihilated
1496 <P>will allow text with this word again.
1499 <H2><A NAME="ss9.81">9.81 set/beep (0)</A>
1502 <P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE>
1504 <P>Add a beep to DX and other terminal messages.
1506 <H2><A NAME="ss9.82">9.82 set/bbs (5)</A>
1509 <P><CODE><B>set/bbs <call> [<call>..]</B>Make <call> a BBS</CODE>
1511 <H2><A NAME="ss9.83">9.83 set/clx (5)</A>
1514 <P><CODE><B>set/clx <node_call> [<node_call> ...]</B> Make
1515 the node_call a CLX type node</CODE>
1517 <P>Set the node_call as a CLX type node
1519 <H2><A NAME="ss9.84">9.84 set/debug (9)</A>
1522 <P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE>
1524 <P>You can choose to log several different levels. The levels are
1530 <P>You can show what levels you are logging with the <EM>show/debug</EM>
1532 <P>You can remove a debug level with unset/debug <name>
1534 <H2><A NAME="ss9.85">9.85 set/dx (0)</A>
1537 <P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE>
1539 <P>You can stop DX messages with the <EM>unset/dx</EM> command
1541 <H2><A NAME="ss9.86">9.86 set/dxgrid (0)</A>
1544 <P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE>
1546 <P>Some logging programs do not like the additional information at
1547 the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
1548 command to remove the grid squares.
1550 <H2><A NAME="ss9.87">9.87 set/dxnet (5)</A>
1553 <P><CODE><B>set/dxnet <node_call> [<node_call> ...]</B> Make
1554 the node_call a DXNet type node</CODE>
1556 <P>Set the node_call as a DXNet type node
1558 <H2><A NAME="ss9.88">9.88 set/echo (0)</A>
1561 <P><CODE><B>set/echo</B> Make the cluster echo your input</CODE>
1563 <P>If you are connected via a telnet session, different implimentations
1564 of telnet handle echo differently depending on whether you are
1565 connected via port 23 or some other port. You can use this command
1566 to change the setting appropriately.
1567 <P>You can remove the echo with the <EM>unset/echo</EM> command
1568 <P>The setting is stored in your user profile.
1569 <P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1571 <H2><A NAME="ss9.89">9.89 set/email (0)</A>
1574 <P><CODE><B>set/email <email_address></B> Set email address(es) and forward your personals</CODE>
1576 <P>If any personal messages come in for your callsign then you can use
1577 these commands to control whether they are forwarded onto your email
1578 address. To enable the forwarding do something like:-
1579 <P>SET/EMAIL mike.tubby@somewhere.com
1580 <P>You can have more than one email address (each one separated by a space).
1581 Emails are forwarded to all the email addresses you specify.
1582 <P>You can disable forwarding by:-
1585 <H2><A NAME="ss9.90">9.90 set/here (0)</A>
1588 <P><CODE><B>set/here</B> Set the here flag</CODE>
1590 <P>Let others on the cluster know you are here by only displaying your
1591 callsign. If you are away from your terminal you can use the <EM>unset/here</EM>
1592 command to let people know you are away. This simply puts brackets
1593 around your callsign to indicate you are not available.
1595 <H2><A NAME="ss9.91">9.91 set/homenode (0)</A>
1598 <P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE>
1600 <P>Tell the cluster system where you normally connect to. Any Messages sent
1601 to you will normally find their way there should you not be connected.
1608 </CODE></BLOCKQUOTE>
1610 <H2><A NAME="ss9.92">9.92 set/hops (8)</A>
1613 <P><CODE><B>set/hops <node_call> ann|spots|wwv|wcy <n></B>
1614 Set hop count</CODE>
1616 <P>Set the hop count for a particular type of broadcast for a node.
1617 <P>This command allows you to set up special hop counts for a node
1618 for currently: announce, spots, wwv and wcy broadcasts.
1623 set/hops gb7djk ann 10
1624 set/hops gb7mbc spots 20
1626 </CODE></BLOCKQUOTE>
1627 <P>Set SHOW/HOPS for information on what is already set. This command
1628 creates a filter and works in conjunction with the filter system.
1630 <H2><A NAME="ss9.93">9.93 set/isolate (9)</A>
1633 <P><CODE><B>set/isolate <node call></B> Isolate a node from the rest of the network</CODE>
1635 <P>Connect a node to your system in such a way that you are a full protocol
1636 member of its network and can see all spots on it, but nothing either leaks
1637 out from it nor goes back into from the rest of the nodes connected to you.
1638 <P>You can potentially connect several nodes in this way.
1639 <P>You can see which nodes are isolated with the show/isolate (1) command.
1640 <P>You can remove the isolation with the command unset/isolate.
1642 <H2><A NAME="ss9.94">9.94 set/language (0)</A>
1645 <P><CODE><B>set/language <language></B> Set the language you wish to use</CODE>
1647 <P>You can select the language that you want the cluster to use. Currently
1648 the languages available are <EM>en</EM> (English) and <EM>nl</EM> (Dutch).
1650 <H2><A NAME="ss9.95">9.95 set/location (0)</A>
1653 <P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE>
1655 <P>You can set your latitude and longitude manually or alternatively use the
1656 <EM>set/qra</EM> command which will do the conversion for you.
1660 set/location 54 04 N 2 02 E
1662 </CODE></BLOCKQUOTE>
1665 <H2><A NAME="ss9.96">9.96 set/sys_location (9)</A>
1668 <P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE>
1670 <P>In order to get accurate headings and such like you must tell the system
1671 what your latitude and longitude is. If you have not yet done a SET/QRA
1672 then this command will set your QRA locator for you. For example:-
1676 SET/LOCATION 52 22 N 0 57 E
1678 </CODE></BLOCKQUOTE>
1680 <H2><A NAME="ss9.97">9.97 set/logininfo (0)</A>
1683 <P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE>
1685 <P>Show users and nodes when they log in and out of the local cluster. You
1686 can stop these messages by using the <EM>unset/logininfo</EM> command.
1689 <H2><A NAME="ss9.98">9.98 set/lockout (9)</A>
1692 <P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE>
1694 <P>You can show who is locked out with the <EM>show/lockout</EM> command.
1695 To allow the user to connect again, use the <EM>unset/lockout</EM> command.
1697 <H2><A NAME="ss9.99">9.99 set/name (0)</A>
1700 <P><CODE><B>set/name <your_name></B> Set your name</CODE>
1702 <P>Tell the cluster what your name is, eg:-
1708 </CODE></BLOCKQUOTE>
1710 <H2><A NAME="ss9.100">9.100 set/node (9)</A>
1713 <P><CODE><B>set/node <call> [<call> ...]</B> Make the callsign an AK1A cluster</CODE>
1715 <P>Tell the system that the call(s) are to be treated as AK1A cluster and
1716 fed PC Protocol rather normal user commands.
1717 <P>From version 1.41 you can also set the following types of cluster
1726 </CODE></BLOCKQUOTE>
1727 <P>To see what your nodes are set to, use the <EM>show/nodes</EM> command.
1729 <H2><A NAME="ss9.101">9.101 set/obscount (9)</A>
1732 <P><CODE><B>set/obscount <count> <node call></B> Set the 'pump-up' obsolescence counter</CODE>
1734 <P>From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1735 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1736 counter which is decremented on every outgoing ping and then reset to
1737 the 'obscount' value on every incoming ping. The default value of this
1739 <P>What this means is that a neighbouring node will be pinged twice at
1740 (default) 300 second intervals and if no reply has been heard just before
1741 what would be the third attempt, that node is disconnected.
1742 <P>If a ping is heard then the obscount is reset to the full value. Using
1743 default values, if a node has not responded to a ping within 15 minutes,
1746 <H2><A NAME="ss9.102">9.102 set/page (0)</A>
1749 <P><CODE><B>set/page <n></B> Set the number of lines per page</CODE>
1751 <P>Tell the system how many lines you wish on a page when the number of lines
1752 of output from a command is more than this. The default is 20. Setting it
1753 explicitly to 0 will disable paging.
1760 </CODE></BLOCKQUOTE>
1761 <P>The setting is stored in your user profile.
1763 <H2><A NAME="ss9.103">9.103 set/password (0)</A>
1766 <P><CODE><B>set/password</B> Set your own password</CODE>
1768 <P>This command only works for a 'telnet' user (currently). It will
1769 only work if you have a password already set. This initial password
1770 can only be set by the sysop.
1771 <P>When you execute this command it will ask you for your old password,
1772 then ask you to type in your new password twice (to make sure you
1773 get it right). You may or may not see the data echoed on the screen
1774 as you type, depending on the type of telnet client you have.
1776 <H2><A NAME="ss9.104">9.104 set/password (9)</A>
1779 <P><CODE><B>set/password <callsign> <string></B> Set a users password</CODE>
1781 <P>The password for a user can only be set by a full sysop. The string
1782 can contain any characters.
1783 <P>The way this field is used depends on context. If it is being used in
1784 the SYSOP command context then you are offered 5 random numbers and you
1785 have to supply the corresponding letters. This is now mainly for ax25
1787 <P>If it is being used on incoming telnet connections then, if a password
1789 <P>set/var $main::passwdreq = 1
1790 <P>command is executed in the startup script, then a password prompt is
1791 given after the normal 'login: ' prompt.
1792 <P>The command "unset/password" is provided to allow a sysop to remove a
1793 users password completely in case a user forgets or loses their password.
1795 <H2><A NAME="ss9.105">9.105 set/pinginterval (9)</A>
1798 <P><CODE><B>set/pinginterval <time> <node call></B> Set the ping time to neighbouring nodes</CODE>
1800 <P>As from version 1.35 all neighbouring nodes are pinged at regular intervals
1801 in order to determine the rolling quality of the link and, in future, to
1802 affect routing decisions. The default interval is 300 secs or 5 minutes.
1803 <P>You can use this command to set a different interval. Please don't.
1804 <P>But if you do the value you enter is treated as minutes up 60 and seconds
1805 for numbers greater than that.
1806 <P>This is used also to help determine when a link is down at the far end
1807 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1808 for more information.
1810 <H2><A NAME="ss9.106">9.106 set/privilege (9)</A>
1813 <P><CODE><B>set/privilege <n> <call> [<call> ...]</B> Set the privilege level on a call</CODE>
1815 <P>Set the privilege level on a callsign. The privilege levels that pertain
1816 to commands are as default:-
1821 1 - allow remote nodes normal user RCMDs
1822 5 - various privileged commands (including shutdown, but not disc-
1823 connect), the normal level for another node.
1824 8 - more privileged commands (including disconnect)
1825 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1828 </CODE></BLOCKQUOTE>
1829 <P>If you are a sysop and you come in as a normal user on a remote connection
1830 your privilege will automatically be set to 0.
1832 <H2><A NAME="ss9.107">9.107 set/spider (5)</A>
1835 <P><CODE><B>set/spider <node_call> [<node_call> ...]</B> Make
1836 the node_call a DXSpider type node</CODE>
1838 <P>Set the node_call as a DXSpider type node
1840 <H2><A NAME="ss9.108">9.108 set/sys_qra (9)</A>
1843 <P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA locator</CODE>
1845 <H2><A NAME="ss9.109">9.109 set/qra (0)</A>
1848 <P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE>
1850 <P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
1851 done a SET/LOCATION then your latitude and longitude will be set roughly
1852 correctly (assuming your locator is correct ;-). For example:-
1858 </CODE></BLOCKQUOTE>
1860 <H2><A NAME="ss9.110">9.110 set/qth (0)</A>
1863 <P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE>
1865 <P>Tell the system where your are. For example:-
1869 set/qth East Dereham, Norfolk
1871 </CODE></BLOCKQUOTE>
1873 <H2><A NAME="ss9.111">9.111 set/register (9)</A>
1876 <P><CODE><B>set/register <call></B> Mark a user as registered</CODE>
1878 <P>Registration is a concept that you can switch on by executing the
1879 <P>set/var $main::regreq = 1
1880 <P>command (usually in your startup file)
1881 <P>If a user is NOT registered then, firstly, instead of the normal
1882 motd file (/spider/data/motd) being sent to the user at startup, the
1883 user is sent the motd_nor file instead. Secondly, the non registered
1884 user only has READ-ONLY access to the node. The non-registered user
1885 cannot use DX, ANN etc.
1886 <P>The only exception to this is that a non-registered user can TALK or
1887 SEND messages to the sysop.
1888 <P>To unset a user use the 'unset/register' command
1890 <H2><A NAME="ss9.112">9.112 set/talk (0)</A>
1893 <P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE>
1895 <P>Allow talk messages to arrive at your console. You can switch off
1896 talks with the <EM>unset/talk</EM> command.
1898 <H2><A NAME="ss9.113">9.113 set/wcy (0)</A>
1901 <P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE>
1903 <P>Allow WCY information to be seen at your console. You can switch off
1904 WCY messages with the <EM>unset/wcy</EM> command.
1906 <H2><A NAME="ss9.114">9.114 set/wwv (0)</A>
1909 <P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE>
1911 <P>Allow WWV information to be seen at your console. You can switch off
1912 WWV messages with the <EM>unset/wwv</EM> command.
1914 <H2><A NAME="ss9.115">9.115 set/wx (0)</A>
1917 <P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE>
1919 <P>Allow WX information to be seen at your console. You can switch off
1920 WX messages with the <EM>unset/wx</EM> command.
1922 <H2><A NAME="ss9.116">9.116 show/baddx (1)</A>
1925 <P><CODE><B>show/baddx</B>Show all the bad dx calls in the system</CODE>
1927 <P>Display all the bad dx callsigns in the system, see SET/BADDX
1928 for more information.
1930 <H2><A NAME="ss9.117">9.117 show/badnode (6)</A>
1933 <P><CODE><B>show/badnode</B> Show all the bad nodes in the system</CODE>
1935 <P>Display all the bad node callsigns in the system, see SET/BADNODE
1936 for more information.
1938 <H2><A NAME="ss9.118">9.118 show/badspotter (1)</A>
1941 <P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE>
1943 <P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1944 for more information.
1946 <H2><A NAME="ss9.119">9.119 show/badword (1)</A>
1949 <P><CODE><B>show/badword</B> Show all the bad words in the system</CODE>
1951 <P>Display all the bad words in the system, see SET/BADWORD
1952 for more information.
1954 <H2><A NAME="ss9.120">9.120 show/configuration (0)</A>
1957 <P><CODE><B>show/configuration [<node>]</B> Show all visible nodes and their users</CODE>
1959 <P>This command allows you to see all the users that can be seen
1960 and the nodes to which they are connected. With the optional <EM>node</EM>,
1961 you can specify a particular node to look at.
1962 <P>This command is normally abbreviated to: sh/c
1963 <P>BE WARNED: the list that is returned can be VERY long
1965 <H2><A NAME="ss9.121">9.121 show/configuration/node (0)</A>
1968 <P><CODE><B>show/configuration/node</B> Show all the nodes connected</CODE>
1970 <P>Show all the nodes connected locally and the nodes they have connected.
1972 <H2><A NAME="ss9.122">9.122 show/connect (1)</A>
1975 <P><CODE><B>show/connect</B> Show all the active connections</CODE>
1977 <P>This command shows information on all the active connections known to
1978 the node. This command gives slightly more information than WHO.
1980 <H2><A NAME="ss9.123">9.123 show/date (0)</A>
1983 <P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
1984 the local time</CODE>
1986 <P>This is very nearly the same as SHOW/TIME, the only difference the format
1987 of the date string if no arguments are given.
1988 <P>If no prefixes or callsigns are given then this command returns the local
1989 time and UTC as the computer has it right now. If you give some prefixes
1990 then it will show UTC and UTC + the local offset (not including DST) at
1991 the prefixes or callsigns that you specify.
1993 <H2><A NAME="ss9.124">9.124 show/debug (9)</A>
1996 <P><CODE><B>show/debug</B> Show what levels of debug you are logging</CODE>
1998 <P>The levels can be set with <EM>set/debug</EM>
2000 <H2><A NAME="ss9.125">9.125 show/dx (0)</A>
2003 <P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE>
2005 <P>If you just type SHOW/DX you will get the last so many spots
2006 (sysop configurable, but usually 10).
2007 <P>In addition you can add any number of these options in very nearly
2008 any order to the basic SHOW/DX command, they are:-
2013 on <band> - eg 160m 20m 2m 23cm 6mm
2014 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
2016 <number> - the number of spots you want
2017 <from>-<to> - <from> spot no <to> spot no in
2020 <prefix> - for a spotted callsign beginning with <prefix>
2021 *<suffix> - for a spotted callsign ending in <suffix>
2022 *<string>* - for a spotted callsign containing <string>
2024 day <number> - starting <number> days ago
2025 day <from>-<to> - <from> days <to> days ago
2027 info <text> - any spots containing <text> in the info or remarks
2029 by <call> - any spots spotted by <call> (spotter <call>
2032 qsl - this automatically looks for any qsl info on the call
2033 held in the spot database.
2035 iota [<iota>] - If the iota island number is missing it will
2036 look for the string iota and anything which looks like
2037 an iota island number. If you specify then it will look
2040 qra [<locator>] - this will look for the specific locator if
2041 you specify one or else anything that looks like a locator.
2043 </CODE></BLOCKQUOTE>
2050 SH/DX on 20m info iota
2051 SH/DX 9a on vhf day 30
2057 </CODE></BLOCKQUOTE>
2059 <H2><A NAME="ss9.126">9.126 show/dxcc (0)</A>
2062 <P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE>
2064 <P>This command takes the <prefix> (which can be a full or partial
2065 callsign if desired), looks up which internal country number it is
2066 and then displays all the spots as per SH/DX for that country.
2067 <P>The options for SHOW/DX also apply to this command.
2074 SH/DXCC W on 20m info iota
2076 </CODE></BLOCKQUOTE>
2078 <H2><A NAME="ss9.127">9.127 sh/dxstats (0)</A>
2081 <P><CODE><B>sh/dxstats</B> Show the DX Statistics for last 31 days</CODE>
2083 <P>Show the total DX spots for the last 31 days
2086 <H2><A NAME="ss9.128">9.128 show/files (0)</A>
2089 <P><CODE><B>show/files [<filearea> [<string>]]</B> List
2090 the contents of a filearea</CODE>
2092 <P>SHOW/FILES on its own will show you a list of the various fileareas
2093 available on the system. To see the contents of a particular file
2098 SH/FILES <filearea>
2100 </CODE></BLOCKQUOTE>
2101 <P>where <filearea> is the name of the filearea you want to see the
2103 <P>You can also use shell globbing characters like '*' and '?' in a
2104 string to see a selection of files in a filearea eg:-
2108 SH/FILES bulletins arld*
2110 </CODE></BLOCKQUOTE>
2111 <P>See also TYPE - to see the contents of a file.
2113 <H2><A NAME="ss9.129">9.129 show/filter (0)</A>
2116 <P><CODE><B>show/filter</B> Show the filters you have set</CODE>
2118 <P>Show the contents of all the filters that are set by you. This command
2119 displays all the filters set - for all the various categories.
2121 <H2><A NAME="ss9.130">9.130 show/filter (extended for sysops) (5)</A>
2124 <P><CODE><B>show/filter <callsign></B> Show the filters set by <callsign></CODE>
2126 <P>A sysop can look at any filters that have been set.
2128 <H2><A NAME="ss9.131">9.131 show/hfstats (0)</A>
2131 <P><CODE><B>show/hfstats</B> Show the HF DX Statistics for last 31 days</CODE>
2133 <P>Show the HF DX spots breakdown by band for the last 31 days
2135 <H2><A NAME="ss9.132">9.132 show/hftable (0)</A>
2138 <P><CODE><B>show/hftable</B> Show the HF DX Spotter Table for your country</CODE>
2140 <P>Show the HF DX Spotter table for your country for the last 31 days
2142 <H2><A NAME="ss9.133">9.133 show/hops (8)</A>
2145 <P><CODE><B>show/hops <node_call> [ann|spots|wcy|wwv|]</B> Show the hop counts for a node</CODE>
2147 <P>This command shows the hop counts set up for a node. You can specify
2148 which category you want to see. If you leave the category out then
2149 all the categories will be listed.
2151 <H2><A NAME="ss9.134">9.134 show/isolate (1)</A>
2154 <P><CODE><B>show/isolate</B> Show a list of isolated nodes</CODE>
2156 <P>Show which nodes are currently set to be isolated.
2158 <H2><A NAME="ss9.135">9.135 show/lockout (9)</A>
2161 <P><CODE><B>show/lockout</B> Show a list of excluded callsigns</CODE>
2163 <P>Show a list of callsigns that have been excluded (locked out) of the
2164 cluster locally with the <EM>set/lockout</EM> command
2166 <H2><A NAME="ss9.136">9.136 show/log (8)</A>
2169 <P><CODE><B>show/log [<callsign>]</B> Show excerpts from the system log</CODE>
2171 <P>This command outputs a short section of the system log. On its own
2172 it will output a general logfile. With the optional callsign it will
2173 show output from the log associated with that callsign.
2175 <H2><A NAME="ss9.137">9.137 show/moon (0)</A>
2178 <P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
2179 rise and set times</CODE>
2181 <P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
2182 together with the azimuth and elevation of the sun currently at those
2184 <P>If you don't specify any prefixes or callsigns, it will show the times for
2185 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2186 together with the current azimuth and elevation.
2187 <P>In addition, it will show the gain or loss dB relative to the nominal
2188 distance of 385,000Km due to the ellipsoidal nature of the orbit.
2189 <P>If all else fails it will show the Moonrise and set times for the node
2190 that you are connected to.
2198 </CODE></BLOCKQUOTE>
2200 <H2><A NAME="ss9.138">9.138 show/muf (0)</A>
2203 <P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
2204 the likely propagation to <prefix></CODE>
2206 <P>This command allow you to estimate the likelihood of you contacting
2207 a station with the prefix you have specified. The output assumes a modest
2208 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
2209 <P>The result predicts the most likely operating frequencies and signal
2210 levels for high frequency (shortwave) radio propagation paths on
2211 specified days of the year and hours of the day. It is most useful for
2212 paths between 250 km and 6000 km, but can be used with reduced accuracy
2213 for paths shorter or longer than this.
2214 <P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
2215 used to predict the MUF given the predicted flux, day of the year,
2216 hour of the day and geographic coordinates of the transmitter and
2217 receiver. This routine is reasonably accurate for the purposes here,
2218 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
2219 than the programs used by major shortwave broadcasting organizations,
2220 such as the Voice of America.
2221 <P>The command will display some header information detailing its
2222 assumptions, together with the locations, latitude and longitudes and
2223 bearings. It will then show UTC (UT), local time at the other end
2224 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
2225 (Zen) and the likely signal strengths. Then for each frequency for which
2226 the system thinks there is a likelihood of a circuit it prints a value.
2227 <P>The value is currently a likely S meter reading based on the conventional
2228 6dB / S point scale. If the value has a '+' appended it means that it is
2229 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
2230 there is likely to be much fading and by an 's' that the signal is likely
2232 <P>By default SHOW/MUF will show the next two hours worth of data. You
2233 can specify anything up to 24 hours worth of data by appending the no of
2234 hours required after the prefix. For example:-
2240 </CODE></BLOCKQUOTE>
2245 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
2246 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
2247 Location Lat / Long Azim
2248 East Dereham, Norfolk 52 41 N 0 57 E 47
2249 United-States-W 43 0 N 87 54 W 299
2250 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
2251 18 23 11.5 -35 mS0+ mS2 S3
2252 19 0 11.2 -41 mS0+ mS2 S3
2254 </CODE></BLOCKQUOTE>
2255 <P>indicating that you will have weak, fading circuits on top band and
2256 80m but usable signals on 40m (about S3).
2263 </CODE></BLOCKQUOTE>
2264 <P>will get you the above display, but with the next 24 hours worth of
2272 </CODE></BLOCKQUOTE>
2273 <P>Gives you an estimate of the long path propagation characterics. It
2274 should be noted that the figures will probably not be very useful, nor
2275 terrible accurate, but it is included for completeness.
2277 <H2><A NAME="ss9.139">9.139 show/newconfiguration (0)</A>
2280 <P><CODE><B>show/newconfiguration [<node>]</B> Show all the nodes and users visible</CODE>
2282 <P>This command allows you to see all the users that can be seen
2283 and the nodes to which they are connected.
2284 <P>This command produces essentially the same information as
2285 SHOW/CONFIGURATION except that it shows all the duplication of
2286 any routes that might be present It also uses a different format
2287 which may not take up quite as much space if you don't have any
2289 <P>BE WARNED: the list that is returned can be VERY long
2291 <H2><A NAME="ss9.140">9.140 show/newconfiguration/node (0)</A>
2294 <P><CODE><B>show/newconfiguration/node</B> Show all the nodes connected locally</CODE>
2296 <P>Show all the nodes connected to this node in the new format.
2298 <H2><A NAME="ss9.141">9.141 show/node (1)</A>
2301 <P><CODE><B>show/node [<node_call> ...]</B> Show the type and version
2302 number of nodes</CODE>
2304 <P>Show the type and version (if connected) of the nodes specified on the
2305 command line. If no callsigns are specified then a sorted list of all
2306 the non-user callsigns known to the system will be displayed.
2308 <H2><A NAME="ss9.142">9.142 show/prefix (0)</A>
2311 <P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE>
2313 <P>This command takes the <callsign> (which can be a full or partial
2314 callsign or a prefix), looks up which internal country number
2315 it is and then displays all the relevant prefixes for that country
2316 together with the internal country no, the CQ and ITU regions.
2317 <P>See also SHOW/DXCC
2320 <H2><A NAME="ss9.143">9.143 show/program (5)</A>
2323 <P><CODE><B>show/program</B> Show the locations of all the included program modules</CODE>
2325 <P>Show the name and location where every program module was load from. This
2326 is useful for checking where you think you have loaded a .pm file from.
2328 <H2><A NAME="ss9.144">9.144 show/qra (0)</A>
2331 <P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
2332 between locators<BR>
2333 <B>show/qra <lat> <long></B> Convert latitude and longitude to a locator</CODE>
2335 <P>This is a multipurpose command that allows you either to calculate the
2336 distance and bearing between two locators or (if only one locator is
2337 given on the command line) the distance and beraing from your station
2338 to the locator. For example:-
2345 </CODE></BLOCKQUOTE>
2346 <P>The first example will show the distance and bearing to the locator from
2347 yourself, the second example will calculate the distance and bearing from
2348 the first locator to the second. You can use 4 or 6 character locators.
2349 <P>It is also possible to convert a latitude and longitude to a locator by
2350 using this command with a latitude and longitude as an argument, for
2355 SH/QRA 52 41 N 0 58 E
2357 </CODE></BLOCKQUOTE>
2359 <H2><A NAME="ss9.145">9.145 show/qrz (0)</A>
2362 <P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE>
2364 <P>This command queries the QRZ callbook server on the internet
2365 and returns any information available for that callsign. This service
2366 is provided for users of this software by http://www.qrz.com
2368 <H2><A NAME="ss9.146">9.146 show/registered (9)</A>
2371 <P><CODE><B>show/registered [<prefix>[</B> Show the registered users</CODE>
2373 <H2><A NAME="ss9.147">9.147 show/route (0)</A>
2376 <P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE>
2378 <P>This command allows you to see to which node the callsigns specified are
2379 connected. It is a sort of inverse sh/config.
2385 </CODE></BLOCKQUOTE>
2387 <H2><A NAME="ss9.148">9.148 show/satellite (0)</A>
2390 <P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
2391 Show satellite tracking data</CODE>
2393 <P>Show the tracking data from your location to the satellite of your choice
2394 from now on for the next few hours.
2395 <P>If you use this command without a satellite name it will display a list
2396 of all the satellites known currently to the system.
2397 <P>If you give a name then you can obtain tracking data of all the passes
2398 that start and finish 5 degrees below the horizon. As default it will
2399 give information for the next three hours for every five minute period.
2400 <P>You can alter the number of hours and the step size, within certain
2402 <P>Each pass in a period is separated with a row of '-----' characters
2408 SH/SAT FENGYUN1 12 2
2410 </CODE></BLOCKQUOTE>
2412 <H2><A NAME="ss9.149">9.149 show/sun (0)</A>
2415 <P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
2416 sun rise and set times</CODE>
2418 <P>Show the sun rise and set times for a (list of) prefixes or callsigns,
2419 together with the azimuth and elevation of the sun currently at those
2421 <P>If you don't specify any prefixes or callsigns, it will show the times for
2422 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2423 together with the current azimuth and elevation.
2424 <P>If all else fails it will show the sunrise and set times for the node
2425 that you are connected to.
2431 SH/SUN G1TLH K9CW ZS
2433 </CODE></BLOCKQUOTE>
2435 <H2><A NAME="ss9.150">9.150 show/time (0)</A>
2438 <P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
2439 the local time</CODE>
2441 <P>If no prefixes or callsigns are given then this command returns the local
2442 time and UTC as the computer has it right now. If you give some prefixes
2443 then it will show UTC and UTC + the local offset (not including DST) at
2444 the prefixes or callsigns that you specify.
2446 <H2><A NAME="ss9.151">9.151 show/vhfstats (0)</A>
2449 <P><CODE><B>show/vhfstats</B> Show the VHF DX Statistics for last 31 days</CODE>
2451 <P>Show the VHF DX spots breakdown by band for the last 31 days
2453 <H2><A NAME="ss9.152">9.152 show/vhftable (0)</A>
2456 <P><CODE><B>show/vhftable</B> Show the VHF DX Spotter Table for your country</CODE>
2458 <P>Show the VHF DX Spotter table for your country for the last 31 days
2460 <H2><A NAME="ss9.153">9.153 show/wcy (0)</A>
2463 <P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
2464 <B>show/wcy <n></B> Show the last <n> WCY broadcasts</CODE>
2466 <P>Display the most recent WCY information that has been received by the system
2468 <H2><A NAME="ss9.154">9.154 show/wwv (0)</A>
2471 <P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
2472 <B>show/wwv <n></B> Show the last <n> WWV broadcasts</CODE>
2474 <P>Display the most recent WWV information that has been received by the system
2477 <H2><A NAME="ss9.155">9.155 shutdown (5)</A>
2480 <P><CODE><B>shutdown</B> Shutdown the cluster</CODE>
2482 <P>Shutdown the cluster and disconnect all the users. If you have Spider
2483 set to respawn in /etc/inittab it will of course restart.
2485 <H2><A NAME="ss9.156">9.156 spoof (9)</A>
2488 <P><CODE><B>spoof <callsign> <command></B> Run commands as another user</CODE>
2490 <P>This is a very simple yet powerful command for the sysop. It allows you to
2491 issue commands as if you were a different user. This is very useful for the
2492 kind of things that users seem to always get wrong.. like home_node for
2495 <H2><A NAME="ss9.157">9.157 stat/db (5)</A>
2498 <P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE>
2500 <P>Show the internal status of a database descriptor.
2501 <P>Depending on your privilege level you will see more or less information.
2502 This command is unlikely to be of much use to anyone other than a sysop.
2504 <H2><A NAME="ss9.158">9.158 stat/channel (5)</A>
2507 <P><CODE><B>stat/channel <callsign></B> Show the status of a channel on the cluster</CODE>
2509 <P>Show the internal status of the channel object either for the channel that
2510 you are on or else for the callsign that you asked for.
2511 <P>Only the fields that are defined (in perl term) will be displayed.
2513 <H2><A NAME="ss9.159">9.159 stat/msg (5)</A>
2516 <P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE>
2518 <P>This command shows the internal status of a message and includes information
2519 such as to whom it has been forwarded, its size, origin etc etc.
2521 <P>If no message number is given then the status of the message system is
2524 <H2><A NAME="ss9.160">9.160 stat/route_node (5)</A>
2527 <P><CODE><B>stat/route_node <callsign></B> Show the data in a Route::Node object</CODE>
2529 <H2><A NAME="ss9.161">9.161 stat/route_user (5)</A>
2532 <P><CODE><B>stat/route_user <callsign></B> Show the data in a Route::User object</CODE>
2534 <H2><A NAME="ss9.162">9.162 stat/user (5)</A>
2537 <P><CODE><B>stat/user <callsign></B> Show the full status of a user</CODE>
2539 <P>Shows the full contents of a user record including all the secret flags
2541 <P>Only the fields that are defined (in perl term) will be displayed.
2543 <H2><A NAME="ss9.163">9.163 sysop (0)</A>
2546 <P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE>
2548 <P>The system automatically reduces your privilege level to that of a
2549 normal user if you login in remotely. This command allows you to
2550 regain your normal privilege level. It uses the normal system: five
2551 numbers are returned that are indexes into the character array that is
2552 your assigned password (see SET/PASSWORD). The indexes start from
2554 <P>You are expected to return a string which contains the characters
2555 required in the correct order. You may intersperse those characters
2556 with others to obscure your reply for any watchers. For example (and
2557 these values are for explanation :-):
2561 password = 012345678901234567890123456789
2565 </CODE></BLOCKQUOTE>
2570 aa2bbbb0ccc5ddd7xxx3n
2574 </CODE></BLOCKQUOTE>
2575 <P>They will all match. If there is no password you will still be offered
2576 numbers but nothing will happen when you input a string. Any match is
2579 <H2><A NAME="ss9.164">9.164 talk (0)</A>
2582 <P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
2583 <B>talk <callsign> <text></B> Send a text message to <callsign><BR>
2584 <B>talk <callsign> > <node_call> [<text>]</B>
2585 Send a text message to <callsign> via <node_call></CODE>
2587 <P>Send a short message to any other station that is visible on the cluster
2588 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2589 command, they don't have to be connected locally.
2590 <P>The second form of TALK is used when other cluster nodes are connected
2591 with restricted information. This usually means that they don't send
2592 the user information usually associated with logging on and off the cluster.
2593 <P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
2594 see GB7TLH in the SH/C list but with no users, then you would use the
2595 second form of the talk message.
2596 <P>If you want to have a ragchew with someone you can leave the text message
2597 out and the system will go into 'Talk' mode. What this means is that a
2598 short message is sent to the recipient telling them that you are in a 'Talking'
2599 frame of mind and then you just type - everything you send will go to the
2600 station that you asked for.
2601 <P>All the usual announcements, spots and so on will still come out on your
2603 <P>If you want to do something (such as send a spot) you precede the normal
2604 command with a '/' character, eg:-
2608 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2611 </CODE></BLOCKQUOTE>
2612 <P>To leave talk mode type:
2618 </CODE></BLOCKQUOTE>
2620 <H2><A NAME="ss9.165">9.165 type (0)</A>
2623 <P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE>
2625 <P>Type out the contents of a file in a filearea. So, for example, in
2626 filearea 'bulletins' you want to look at file 'arld051' you would
2631 TYPE bulletins/arld051
2633 </CODE></BLOCKQUOTE>
2634 <P>See also SHOW/FILES to see what fileareas are available and a
2637 <H2><A NAME="ss9.166">9.166 who (0)</A>
2640 <P><CODE><B>who</B> Show who is physically connected locally</CODE>
2642 <P>This is a quick listing that shows which callsigns are connected and
2643 what sort of connection they have
2645 <H2><A NAME="ss9.167">9.167 wx (0)</A>
2648 <P><CODE><B>wx <text></B> Send a weather message to local users<BR>
2649 <B>wx full <text> </B> Send a weather message to all cluster users</CODE>
2651 <P>Weather messages can sometimes be useful if you are experiencing an extreme
2652 that may indicate enhanced conditions
2654 <H2><A NAME="ss9.168">9.168 wx (enhanced for sysops) (5)</A>
2657 <P><CODE><B>wx sysop <text></B> Send a weather message to other clusters only</CODE>
2659 <P>Send a weather message only to other cluster nodes and not to general users.
2665 <A HREF="adminmanual-8.html">Previous</A>
2666 <A HREF="adminmanual.html#toc9">Contents</A>
projects / spider.git / blob