2 # please put your help in in alphabetical order
4 # a string search is done in the command field (case is ignored)
5 # and all commands matching the asked for command are printed out
7 # the order of the fields in each header is
8 # privilege, command, Description
9 # if the command ends in a - then that line isn't printed, but any
10 # subsequent lines are
12 # Comment lines are indented before printing
14 === 0^ACCEPT^Set a filter to accept something
15 Create a filter to accept something
17 There are 2 types of filter, accept and reject. See HELP FILTERING for more
20 === 0^ACCEPT/ANNOUNCE [0-9] <pattern>^Set an 'accept' filter line for announce
21 Create an 'accept this announce' line for a filter.
23 An accept filter line means that if the announce matches this filter it is
24 passed onto the user. See HELP FILTERING for more info. Please read this
25 to understand how filters work - it will save a lot of grief later on.
27 You can use any of the following things in this line:-
29 info <string> eg: iota or qsl
30 by <prefixes> eg: G,M,2
32 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
33 origin_itu <prefixes or numbers> or: G,GM,GW
34 origin_zone <prefixes or numbers>
35 origin_state <states> eg: VA,NH,RI,NH
36 by_dxcc <prefixes or numbers>
37 by_itu <prefixes or numbers>
38 by_zone <prefixes or numbers>
41 wx 1 filter WX announces
42 dest <prefixes> eg: 6MUK,WDX (distros)
47 acc/ann 2 by_zone 14,15,16
48 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
54 acc/ann by_state va,nh,ri,nh
56 You can use the tag 'all' to accept everything eg:
60 but this probably for advanced users...
62 === 8^ACCEPT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
63 This version allows a sysop to set a filter for a callsign as well as the
64 default for nodes and users eg:-
67 accept/ann input node_default by G,M,2
68 accept/ann user_default by G,M,2
70 === 8^ACCEPT/ROUTE <call> [0-9] <pattern>^Set an 'accept' filter line for routing
71 Create an 'accept this routing PC Protocol' line for a filter.
73 An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
74 it is passed thru that interface. See HELP FILTERING for more info. Please read this
75 to understand how filters work - it will save a lot of grief later on.
77 You can use any of the following things in this line:-
79 call <prefixes> the callsign of the thingy
80 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
81 call_itu <prefixes or numbers> or: G,GM,GW
82 call_zone <prefixes or numbers>
83 call_state <states> eg: VA,NH,RI,NH
84 origin <prefixes> really the interface it came in on
85 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
86 origin_itu <prefixes or numbers> or: G,GM,GW
87 origin_zone <prefixes or numbers>
88 origin_state <states> eg: VA,NH,RI,NH
92 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
93 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
95 you can now use 'by' as a synonym for 'call' so:
102 You can use the tag 'all' to accept everything eg:
107 === 0^ACCEPT/SPOTS [0-9] <pattern>^Set an 'accept' filter line for spots
108 Create an 'accept this spot' line for a filter.
110 An accept filter line means that if the spot matches this filter it is
111 passed onto the user. See HELP FILTERING for more info. Please read this
112 to understand how filters work - it will save a lot of grief later on.
114 You can use any of the following things in this line:-
116 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
117 on <range> same as 'freq'
118 call <prefixes> eg: G,PA,HB9
119 info <string> eg: iota or qsl
121 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
122 call_itu <prefixes or numbers> or: G,GM,GW
123 call_zone <prefixes or numbers>
124 call_state <states> eg: VA,NH,RI,ME
125 by_dxcc <prefixes or numbers>
126 by_itu <prefixes or numbers>
127 by_zone <prefixes or numbers>
128 by_state <states> eg: VA,NH,RI,ME
132 'call' means the callsign that has spotted 'by' whoever.
134 For frequencies, you can use any of the band names defined in
135 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
136 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
137 this is more efficient than saying simply: freq HF (but don't get
138 too hung up about that)
143 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
145 You can use the tag 'all' to accept everything, eg:
151 acc/spots by_state VA,NH,RI,MA,ME
153 but this probably for advanced users...
156 === 8^ACCEPT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
157 This version allows a sysop to set a filter for a callsign as well as the
158 default for nodes and users eg:-
160 accept/spot db0sue-7 1 by_zone 14,15,16
161 accept/spot node_default all
162 set/hops node_default 10
164 accept/spot user_default by G,M,2
166 === 0^ACCEPT/WCY [0-9] <pattern>^set an 'accept' WCY filter
167 It is unlikely that you will want to do this, but if you do then you can
168 filter on the following fields:-
170 by <prefixes> eg: G,M,2
172 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
173 origin_itu <prefixes or numbers> or: G,GM,GW
174 origin_zone <prefixes or numbers>
175 by_dxcc <prefixes or numbers>
176 by_itu <prefixes or numbers>
177 by_zone <prefixes or numbers>
180 There are no examples because WCY Broadcasts only come from one place and
181 you either want them or not (see UNSET/WCY if you don't want them).
183 This command is really provided for future use.
185 See HELP FILTER for information.
187 === 8^ACCEPT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
188 This version allows a sysop to set a filter for a callsign as well as the
189 default for nodes and users eg:-
191 accept/wcy node_default all
192 set/hops node_default 10
194 === 0^ACCEPT/WWV [0-9] <pattern>^set an 'accept' WWV filter
195 It is unlikely that you will want to do this, but if you do then you can
196 filter on the following fields:-
198 by <prefixes> eg: G,M,2
200 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
201 origin_itu <prefixes or numbers> or: G,GM,GW
202 origin_zone <prefixes or numbers>
203 by_dxcc <prefixes or numbers>
204 by_itu <prefixes or numbers>
205 by_zone <prefixes or numbers>
212 is probably the only useful thing to do (which will only show WWV broadcasts
213 by stations in the US).
215 See HELP FILTER for information.
217 === 8^ACCEPT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
218 This version allows a sysop to set a filter for a callsign as well as the
219 default for nodes and users eg:-
221 accept/wwv db0sue-7 1 by_zone 4
222 accept/wwv node_default all
223 set/hops node_default 10
225 accept/wwv user_default by W,K
227 === 0^ANNOUNCE <text>^Send an announcement to LOCAL users only
228 <text> is the text of the announcement you wish to broadcast
230 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
231 This will send your announcement cluster wide
233 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
235 === 0^APROPOS <string>^Search help database for <string>
236 Search the help database for <string> (it isn't case sensitive), and print
237 the names of all the commands that may be relevant.
239 === 0^BLANK [<string>] [<nn>]^Print nn (default 1) blank lines (or strings)
240 In its basic form this command prints one or more blank lines. However if
241 you pass it a string it will replicate the string for the width of the
242 screen (default 80) and then print that one or more times, so:
246 prints two blank lines
250 prints a row of - characters once.
254 prints 'abcabcabcabcabcabc....'
256 This is really only of any use in a script file and you can print a maximum
259 === 0^BYE^Exit from the cluster
260 This will disconnect you from the cluster
262 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
263 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
264 When you send messages the fact that you have forwarded it to another node
265 is remembered so that it isn't sent again. When you have a new partner
266 node and you add their callsign to your /spider/msg/forward.pl file, all
267 outstanding non-private messages will be forwarded to them. This may well
268 be ALL the non-private messages. You can prevent this by using these
272 catchup GB7DJK 300 301 302 303 500-510
274 and to undo what you have just done:-
277 uncatchup GB7DJK 300 301 302 303 500-510
279 which will arrange for them to be forward candidates again.
281 Order is not important.
283 === 0^CLEAR/ANNOUNCE [1|all]^Clear a announce filter line
284 This command allows you to clear (remove) a line in a annouce filter or to
285 remove the whole filter.
287 see CLEAR/SPOTS for a more detailed explanation.
289 === 8^CLEAR/ANNOUNCE [input] <callsign> [0-9|all]^Clear a announce filter line
290 A sysop can clear an input or normal output filter for a user or the
291 node_default or user_default.
293 === 0^CLEAR/ROUTE [1|all]^Clear a route filter line
294 This command allows you to clear (remove) a line in a route filter or to
295 remove the whole filter.
297 see CLEAR/SPOTS for a more detailed explanation.
299 === 8^CLEAR/ROUTE [input] <callsign> [0-9|all]^Clear a route filter line
300 A sysop can clear an input or normal output filter for a user or the
301 node_default or user_default.
303 === 0^CLEAR/SPOTS [0-9|all]^Clear a spot filter line
304 This command allows you to clear (remove) a line in a spot filter or to
305 remove the whole filter.
307 If you have a filter:-
310 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
316 you will be left with:-
318 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
324 the filter will be completely removed.
326 === 8^CLEAR/SPOTS [input] <callsign> [0-9|all]^Clear a spot filter line
327 A sysop can clear an input or normal output filter for a user or the
328 node_default or user_default.
330 === 0^CLEAR/WCY [1|all]^Clear a WCY filter line
331 This command allows you to clear (remove) a line in a WCY filter or to
332 remove the whole filter.
334 see CLEAR/SPOTS for a more detailed explanation.
336 === 8^CLEAR/WCY [input] <callsign> [0-9|all]^Clear a WCY filter line
337 A sysop can clear an input or normal output filter for a user or the
338 node_default or user_default.
340 === 0^CLEAR/WWV [1|all]^Clear a WWV filter line
341 This command allows you to clear (remove) a line in a WWV filter or to
342 remove the whole filter.
344 see CLEAR/SPOTS for a more detailed explanation.
346 === 8^CLEAR/WWV [input] <callsign> [0-9|all]^Clear a WWV filter line
347 A sysop can clear an input or normal output filter for a user or the
348 node_default or user_default.
350 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
351 Start a connection process that will culminate in a new connection to the
352 DX cluster <callsign>. This process creates a new 'client' process which will
353 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
354 necessary to traverse the network(s) to logon to the cluster <callsign>.
356 === 9^DELETE/USER <callsign> ...^Delete this user from the User Database
357 This command will completely remove a one or more users from the database.
359 There is NO SECOND CHANCE.
361 It goes without saying that you should use this command CAREFULLY!
363 === 0^DBAVAIL^Show a list of all the Databases in the system
364 Title says it all really, this command lists all the databases defined
365 in the system. It is also aliased to SHOW/COMMAND.
367 === 9^DBCREATE <name>^Create a database entry
368 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
369 === 9^DBCREATE <name> remote <node>^Create a remote database entry
370 DBCREATE allows you to define a database in the system. It doesn't actually
371 create anything, just defines it.
373 The databases that are created are simple DB_File hash databases, they are
374 therefore already 'indexed'.
376 You can define a local database with the first form of the command eg:
380 You can also chain databases with the addition of the 'chain' keyword.
381 This will search each database one after the other. A typical example
384 DBCREATE sdx_qsl chain sql_ad
386 No checking is done to see if the any of the chained databases exist, in
387 fact it is usually better to do the above staement first then do each of
388 the chained databases.
390 Databases can exist offsite. To define a database that lives on another
393 DBCREATE buckmaster remote gb7dxc
395 Remote databases cannot be chained; however, the last database in a
396 a chain can be a remote database eg:
398 DBCREATE qsl chain gb7dxc
400 To see what databases have been defined do:
402 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
404 It would be normal for you to add an entry into your local Aliases file
405 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
406 need to add a line like:-
411 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
420 to work as they may be used to.
422 See DBIMPORT for the importing of existing AK1A format data to databases.
423 See DBSHOW for generic database enquiry
425 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
426 If you want to import or update data in bulk to a database you can use
427 this command. It will either create or update entries into an existing
428 database. For example:-
430 DBIMPORT oblast /tmp/OBLAST.FUL
432 will import the standard OBLAST database that comes with AK1A into the
433 oblast database held locally.
435 === 9^DBREMOVE <dbname>^Delete a database
436 DBREMOVE will completely remove a database entry and also delete any data
437 file that is associated with it.
439 There is no warning, no comeback, no safety net.
445 will remove the oblast database from the system and it will also remove
446 the associated datafile.
450 There is no warning, no comeback, no safety net.
452 You have been warned.
454 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
455 This is the generic user interface to the database to the database system.
456 It is expected that the sysop will add an entry to the local Aliases file
457 so that users can use the more familiar AK1A style of enquiry such as:
461 but if he hasn't and the database really does exist (use DBAVAIL or
462 SHOW/COMMAND to find out) you can do the same thing with:
466 === 9^DEBUG^Set the cluster program into debug mode
467 Executing this command will only have an effect if you are running the cluster
472 It will interrupt the cluster just after the debug command has finished.
474 === 0^DIRECTORY^List messages
475 === 0^DIRECTORY ALL^List all messages
476 === 0^DIRECTORY OWN^List your own messages
477 === 0^DIRECTORY NEW^List all new messages
478 === 0^DIRECTORY TO <call>^List all messages to <call>
479 === 0^DIRECTORY FROM <call>^List all messages from <call>
480 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
481 === 0^DIRECTORY <nn>^List last <nn> messages
482 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
483 List the messages in the messages directory.
485 If there is a 'p' one space after the message number then it is a
486 personal message. If there is a '-' between the message number and the
487 'p' then this indicates that the message has been read.
489 You can use shell escape characters such as '*' and '?' in the <call>
492 You can combine some of the various directory commands together eg:-
496 DIR SUBJECT IOTA 200-250
498 You can abbreviate all the commands to one letter and use ak1a syntax:-
504 Sysops can see all users' messages.
506 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
507 Disconnect any <call> connected locally
509 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
510 This is how you send a DX Spot to other users. You can, in fact, now
511 enter the <freq> and the <call> either way round.
517 will all give the same result. You can add some remarks to the end
518 of the command and they will be added to the spot.
520 DX FR0G 144600 this is a test
522 You can credit someone else by saying:-
524 DX by G1TLH FR0G 144.600 he isn't on the cluster
526 The <freq> is compared against the available bands set up in the
527 cluster. See SHOW/BANDS for more information.
529 === 0^ECHO <line>^Echo the line to the output
530 This command is useful in scripts and so forth for printing the
531 line that you give to the command to the output. You can use this
532 in user_default scripts and the SAVE command for titling and so forth
534 The script will interpret certain standard "escape" sequences as follows:-
536 \t - becomes a TAB character (0x09 in ascii)
537 \a - becomes a BEEP character (0x07 in ascii)
538 \n - prints a new line
540 So the following example:-
542 echo GB7DJK is a dxcluster
546 GB7DJK is a dxcluster
548 on the output. You don't need a \n on the end of the line you want to send.
550 A more complex example:-
552 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
562 === 9^EXPORT <msgno> <filename>^Export a message to a file
563 Export a message to a file. This command can only be executed on a local
564 console with a fully privileged user. The file produced will be in a form
565 ready to be imported back into the cluster by placing it in the import
566 directory (/spider/msg/import).
568 This command cannot overwrite an existing file. This is to provide some
569 measure of security. Any files written will owned by the same user as the
570 main cluster, otherwise you can put the new files anywhere the cluster can
571 access. For example:-
575 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
576 Export the users database to a file in ascii format. If no filename
577 is given then it will export the file to /spider/data/user_asc.
579 If the file already exists it will be renamed to <filename>.o. In fact
580 up to 5 generations of the file can be kept each one with an extra 'o' on the
583 BE WARNED: this will write to any file you have write access to. No check is
584 made on the filename (if any) that you specify.
586 === 0^FILTERING...^Filtering things in DXSpider
587 There are a number of things you can filter in the DXSpider system. They
588 all use the same general mechanism.
590 In general terms you can create a 'reject' or an 'accept' filter which
591 can have up to 10 lines in it. You do this using, for example:-
596 where ..... are the specific commands for that type of filter. There
597 are filters for spots, wwv, announce, wcy and (for sysops)
598 connects. See each different accept or reject command reference for
601 There is also a command to clear out one or more lines in a filter and
602 one to show you what you have set. They are:-
611 There is clear/xxxx command for each type of filter.
613 For now we are going to use spots for the examples, but you can apply
614 the principles to all types of filter.
616 There are two main types of filter 'accept' or 'reject'; which you use
617 depends entirely on how you look at the world and what is least
618 writing to achieve what you want. Each filter has 10 lines (of any
619 length) which are tried in order. If a line matches then the action
620 you have specified is taken (ie reject means ignore it and accept
623 The important thing to remember is that if you specify a 'reject'
624 filter (all the lines in it say 'reject/spots' (for instance)) then if
625 a spot comes in that doesn't match any of the lines then you will get
626 it BUT if you specify an 'accept' filter then any spots that don't
627 match are dumped. For example if I have a one line accept filter:-
629 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
631 then automatically you will ONLY get VHF spots from or to CQ zones 14
632 15 and 16. If you set a reject filter like:
634 reject/spots on hf/cw
636 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
637 and will work it even on CW then you could say:-
639 reject/spots on hf/cw and not info iota
641 But in that case you might only be interested in iota and say:-
643 accept/spots not on hf/cw or info iota
645 which is exactly the same. You should choose one or the other until
646 you are confortable with the way it works. Yes, you can mix them
647 (actually you can have an accept AND a reject on the same line) but
648 don't try this at home until you can analyse the results that you get
649 without ringing up the sysop for help.
651 Another useful addition now is filtering by US state
653 accept/spots by_state VA,NH,RI,ME
655 You can arrange your filter lines into logical units, either for your
656 own understanding or simply convenience. I have one set frequently:-
658 reject/spots 1 on hf/cw
659 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
661 What this does is to ignore all HF CW spots (being a class B I can't
662 read any CW and couldn't possibly be interested in HF :-) and also
663 rejects any spots on VHF which don't either originate or spot someone
666 This is an exmaple where you would use the line number (1 and 2 in
667 this case), if you leave the digit out, the system assumes '1'. Digits
668 '0'-'9' are available.
670 You can leave the word 'and' out if you want, it is implied. You can
671 use any number of brackets to make the 'expression' as you want
672 it. There are things called precedence rules working here which mean
673 that you will NEED brackets in a situation like line 2 because,
674 without it, will assume:-
676 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
678 annoying, but that is the way it is. If you use OR - use
679 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
682 If you want to alter your filter you can just redefine one or more
683 lines of it or clear out one line. For example:-
685 reject/spots 1 on hf/ssb
691 To remove the filter in its entirty:-
695 There are similar CLEAR commands for the other filters:-
703 Once you are happy with the results you get, you may like to experiment.
705 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
706 can be written with a mixed filter, eg:
710 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
712 each filter slot actually has a 'reject' slot and an 'accept'
713 slot. The reject slot is executed BEFORE the accept slot.
715 It was mentioned earlier that after a reject test that doesn't match,
716 the default for following tests is 'accept', the reverse is true for
717 'accept'. In the example what happens is that the reject is executed
718 first, any non hf/cw spot is passed to the accept line, which lets
719 thru everything else on HF.
721 The next filter line lets through just VHF/UHF spots from EU.
723 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
724 This command sends all the latitude and longitude information that your
725 cluster is holding against callsigns. One advantage of recieving this
726 information is that more locator information is held by you. This
727 means that more locators are given on the DX line assuming you have
728 SET/DXGRID enabled. This could be a LOT of information though, so
729 it is not recommended on slow links.
731 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
732 This command sends out any information held in the user file which can
733 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
734 and Homenode. PC41s are only sent for the information that is available.
736 === 0^HELP^The HELP Command
737 HELP is available for a number of commands. The syntax is:-
741 Where <cmd> is the name of the command you want help on.
743 All commands can be abbreviated, so SHOW/DX can be abbreviated
744 to SH/DX, ANNOUNCE can be shortened to AN and so on.
746 Look at the APROPOS <string> command which will search the help database
747 for the <string> you specify and give you a list of likely commands
748 to look at with HELP.
750 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
751 This command attempts to re-initialise a link to a (usually) AK1A node
752 that has got confused, usually by a protocol loop of some kind. It may
753 work - but you usually will be better off simply disconnecting it (or
754 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
757 Best of luck - you will need it.
759 === 9^DEMONSTRATE <call> <command>^Demonstrate a command to another user
760 This command is provided so that sysops can demonstrate commands to
761 other users. It runs a command as though that user had typed it in and
762 then sends the output to that user, together with the command that
765 DEMO g7brn sh/dx iota oc209
768 Note that this command is similar to SPOOF and will have the same side
769 effects. Commands are run at the privilege of the user which is being
772 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
773 === 0^KILL <from msgno>-<to msgno>^Delete a range of messages
774 === 0^KILL from <regex>^Delete messages FROM a callsign or pattern
775 === 0^KILL to <regex>^Delete messages TO a callsign or pattern
776 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
777 Delete a message from the local system. You will only be able to
778 delete messages that you have originated or been sent (unless you are
783 Will delete all the messages that you own between msgnos 1234 and 1255.
787 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
791 will delete all messages to g1tlh.
795 will delete a message (usually a 'bulletin') from the whole cluster system.
797 This uses the subject field, so any messages that have exactly the
798 same subject will be deleted. Beware!
800 === 6^KILL EXPunge <msgno> [<msgno..]^Expunge a message
801 Deleting a message using the normal KILL commands only marks that message
802 for deletion. The actual deletion only happens later (usually two days later).
804 The KILL EXPUNGE command causes the message to be truly deleted more or less
807 It otherwise is used in the same way as the KILL command.
809 === 0^LINKS^Show which nodes is physically connected
810 This is a quick listing that shows which links are connected and
811 some information about them. See WHO for a list of all connections.
813 === 9^LOAD/ALIASES^Reload the command alias table
814 Reload the /spider/cmd/Aliases file after you have editted it. You
815 will need to do this if you change this file whilst the cluster is
816 running in order for the changes to take effect.
818 === 9^LOAD/BANDS^Reload the band limits table
819 Reload the /spider/data/bands.pl file if you have changed it manually whilst
820 the cluster is running.
822 === 9^LOAD/BADMSG^Reload the bad msg table
823 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
824 the cluster is running. This table contains a number of perl regular
825 expressions which are searched for in the fields targetted of each message.
826 If any of them match then that message is immediately deleted on receipt.
828 === 9^LOAD/BADWORDS^Reload the bad words table
829 Reload the /spider/data/badwords file if you have changed it manually whilst
830 the cluster is running. This file contains a list of words which, if found
831 on certain text portions of PC protocol, will cause those protocol frames
832 to be rejected. It will all put out a message if any of these words are
833 used on the announce, dx and talk commands. The words can be one or
834 more on a line, lines starting with '#' are ignored.
836 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
837 Normally, if you change a command file in the cmd or local_cmd tree it
838 will automatially be picked up by the cluster program. Sometimes it
839 can get confused if you are doing a lot of moving commands about or
840 delete a command in the local_cmd tree and want to use the normal one
841 again. Execute this command to reset everything back to the state it
842 was just after a cluster restart.
844 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
845 Reload the /spider/msg/forward.pl file if you have changed it
846 manually whilst the cluster is running.
848 === 5^LOAD/KEPS^Load new keps data
849 === 5^LOAD/KEPS [nn]^Load new keps data from message
850 If there is no message number then reload the current Keps data from
851 the Keps.pm data file. You create this file by running
853 /spider/perl/convkeps.pl <filename>
855 on a file containing NASA 2 line keps as a message issued by AMSAT.
857 If there is a message number, then it will take the message, run
858 convkeps.pl on it and then load the data, all in one step.
860 These messages are sent to ALL by GB7DJK (and others) from time to time.
862 === 9^LOAD/MESSAGES^Reload the system messages file
863 If you change the /spider/perl/Messages file (usually whilst
864 fiddling/writing new commands) you can have them take effect during a
865 cluster session by executing this command. You need to do this if get
868 unknown message 'xxxx' in lang 'en'
870 === 9^LOAD/PREFIXES^Reload the prefix table
871 Reload the /spider/data/prefix_data.pl file if you have changed it
872 manually whilst the cluster is running.
874 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
875 MERGE allows you to bring your spot and wwv database up to date. By default
876 it will request the last 10 spots and 5 WWVs from the node you select. The
877 node must be connected locally.
879 You can request any number of spots or wwv and although they will be appended
880 to your databases they will not duplicate any that have recently been added
881 (the last 2 days for spots and last month for WWV data).
883 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
884 Alter message parameters like To, From, Subject, whether private or bulletin
885 or return receipt (RR) is required or whether to keep this message from timing
888 MSG TO <msgno> <call> - change TO callsign to <call>
889 MSG FRom <msgno> <call> - change FROM callsign to <call>
890 MSG PRrivate <msgno> - set private flag
891 MSG NOPRrivate <msgno> - unset private flag
892 MSG RR <msgno> - set RR flag
893 MSG NORR <msgno> - unset RR flag
894 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
895 MSG NOKEep <msgno> - unset the keep flag
896 MSG SUbject <msgno> <new> - change the subject to <new>
897 MSG WAittime <msgno> - remove any waitting time for this message
898 MSG NOREad <msgno> - mark message as unread
899 MSG REad <msgno> - mark message as read
900 MSG QUeue - queue any outstanding bulletins
901 MSG QUeue 1 - queue any outstanding private messages
903 You can look at the status of a message by using:-
907 This will display more information on the message than DIR does.
909 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
910 Send some arbitrary text to a locally connected callsign. No
911 processing is done on the text. This command allows you to send PC
912 Protocol to unstick things if problems arise (messages get stuck
915 pc gb7djk PC33^GB7TLH^GB7DJK^400^
917 pc G1TLH Try doing that properly!!!
919 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
920 You can get rid of any message to or originating from your callsign using
921 this command. You can remove more than one message at a time.
923 === 5^KILL <from>-<to>^Remove a range of messages from the system
924 === 5^KILL FROM <call>^Remove all messages from a callsign
925 === 5^KILL TO <call>^Remove all messages to a callsign
926 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
927 Remove this message from the entire cluster system as well as your node.
930 As a sysop you can kill any message on the system.
932 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
933 Send any text you like to the callsign requested. This is used mainly to send
934 PC protocol to connected nodes either for testing or to unstick things.
936 You can also use in the same way as a talk command to a connected user but
937 without any processing, added of "from <blah> to <blah" or whatever.
939 === 1^PING <node call>^Check the link quality between nodes
940 This command allows you to send a frame to another cluster node on
941 the network and get a return frame. The time it takes to do this
942 is a good indication of the quality of the link. The actual time
943 it takes is output to the console in seconds.
944 Any visible cluster node can be PINGed.
946 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
947 This command allows you to send nearly any command to another DX Cluster
948 node that is connected to the system.
950 Whether you get any output is dependant on a) whether the other system knows
951 that the node callsign of this cluster is in fact a node b) whether the
952 other system is allowing RCMDs from this node and c) whether you have
953 permission to send this command at all.
955 === 0^READ^Read the next unread personal message addressed to you
956 === 0^READ <msgno>^Read the specified message
957 You can read any messages that are sent as 'non-personal' and also any
958 message either sent by or sent to your callsign.
961 As a sysop you may read any message on the system
963 === 0^REJECT^Set a filter to reject something
964 Create a filter to reject something
966 There are 2 types of filter, accept and reject. See HELP FILTERING for more
969 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
970 Create an 'reject this announce' line for a filter.
972 A reject filter line means that if the announce matches this filter it is
973 passed onto the user. See HELP FILTERING for more info. Please read this
974 to understand how filters work - it will save a lot of grief later on.
976 You can use any of the following things in this line:-
978 info <string> eg: iota or qsl
979 by <prefixes> eg: G,M,2
981 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
982 origin_itu <prefixes or numbers> or: G,GM,GW
983 origin_zone <prefixes or numbers>
984 origin_state <states> eg: VA,NH,RI,ME
985 by_dxcc <prefixes or numbers>
986 by_itu <prefixes or numbers>
987 by_zone <prefixes or numbers>
988 by_state <states> eg: VA,NH,RI,ME
990 wx 1 filter WX announces
991 dest <prefixes> eg: 6MUK,WDX (distros)
995 rej/ann by_zone 14,15,16 and not by G,M,2
997 You can use the tag 'all' to reject everything eg:
1001 but this probably for advanced users...
1003 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
1004 This version allows a sysop to set a filter for a callsign as well as the
1005 default for nodes and users eg:-
1008 reject/ann input node_default by G,M,2
1009 reject/ann user_default by G,M,2
1011 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
1012 Create a 'reject this spot' line for a filter.
1014 A reject filter line means that if the spot matches this filter it is
1015 dumped (not passed on). See HELP FILTERING for more info. Please read this
1016 to understand how filters work - it will save a lot of grief later on.
1018 You can use any of the following things in this line:-
1020 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1021 on <range> same as 'freq'
1022 call <prefixes> eg: G,PA,HB9
1023 info <string> eg: iota or qsl
1025 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1026 call_itu <prefixes or numbers> or: G,GM,GW
1027 call_zone <prefixes or numbers>
1028 call_state <states> eg: VA,NH,RI,ME
1029 by_dxcc <prefixes or numbers>
1030 by_itu <prefixes or numbers>
1031 by_zone <prefixes or numbers>
1032 by_state <states> eg: VA,NH,RI,ME
1036 'call' means the callsign that has spotted 'by' whoever.
1038 For frequencies, you can use any of the band names defined in
1039 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1040 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1041 this is more efficient than saying simply: on HF (but don't get
1042 too hung up about that)
1047 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1049 You can use the tag 'all' to reject everything eg:
1053 but this probably for advanced users...
1055 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
1056 Create an 'reject this routing PC Protocol' line for a filter.
1058 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1059 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
1060 read this to understand how filters work - it will save a lot of grief later on.
1062 You can use any of the following things in this line:-
1064 call <prefixes> the callsign of the thingy
1065 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1066 call_itu <prefixes or numbers> or: G,GM,GW
1067 call_zone <prefixes or numbers>
1068 call_state <states> eg: VA,NH,RI,ME
1069 origin <prefixes> really the interface it came in on
1070 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1071 origin_itu <prefixes or numbers> or: G,GM,GW
1072 origin_zone <prefixes or numbers>
1073 origin_state <states> eg: VA,NH,RI,ME
1077 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
1079 You can use the tag 'all' to reject everything eg:
1081 rej/route all (equiv to [very] restricted mode)
1083 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
1085 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
1086 This version allows a sysop to set a filter for a callsign as well as the
1087 default for nodes and users eg:-
1089 reject/spot db0sue-7 1 by_zone 14,15,16
1090 reject/spot node_default all
1091 set/hops node_default 10
1093 reject/spot user_default by G,M,2
1095 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
1096 It is unlikely that you will want to do this, but if you do then you can
1097 filter on the following fields:-
1099 by <prefixes> eg: G,M,2
1101 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1102 origin_itu <prefixes or numbers> or: G,GM,GW
1103 origin_zone <prefixes or numbers>
1104 by_dxcc <prefixes or numbers>
1105 by_itu <prefixes or numbers>
1106 by_zone <prefixes or numbers>
1109 There are no examples because WCY Broadcasts only come from one place and
1110 you either want them or not (see UNSET/WCY if you don't want them).
1112 This command is really provided for future use.
1114 See HELP FILTER for information.
1116 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
1117 This version allows a sysop to set a filter for a callsign as well as the
1118 default for nodes and users eg:-
1120 reject/wcy gb7djk all
1122 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
1123 It is unlikely that you will want to do this, but if you do then you can
1124 filter on the following fields:-
1126 by <prefixes> eg: G,M,2
1128 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1129 origin_itu <prefixes or numbers> or: G,GM,GW
1130 origin_zone <prefixes or numbers>
1131 by_dxcc <prefixes or numbers>
1132 by_itu <prefixes or numbers>
1133 by_zone <prefixes or numbers>
1138 reject/wwv by_zone 14,15,16
1140 is probably the only useful thing to do (which will only show WWV broadcasts
1141 by stations in the US).
1143 See HELP FILTER for information.
1145 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
1146 This version allows a sysop to set a filter for a callsign as well as the
1147 default for nodes and users eg:-
1149 reject/wwv db0sue-7 1 by_zone 4
1150 reject/wwv node_default all
1152 reject/wwv user_default by W
1154 === 0^REPLY^Reply (privately) to the last message that you have read
1155 === 0^REPLY <msgno>^Reply (privately) to the specified message
1156 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
1157 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
1158 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
1159 You can reply to a message and the subject will automatically have
1160 "Re:" inserted in front of it, if it isn't already present.
1162 You can also use all the extra qualifiers such as RR, PRIVATE,
1163 NOPRIVATE, B that you can use with the SEND command (see SEND
1164 for further details)
1166 === 9^SAVE [-d -t -a] <filename> "<cmd>" [...]^Save command output to a file
1167 This sysop only cammand allows you to save the output of one or more
1168 commands to a file. For example:-
1170 save /spider/packclus/dxstats show/dxstat
1172 will save the output of the normal command "show/dxstat" to the file
1173 "dxstats" in the files area.
1175 You can have some extra flags to the save which will either
1176 date stamp or time stamp or both the filename so:-
1178 save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
1179 save -t /tmp/a <cmd> creates /tmp/a_2301Z
1180 save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
1182 The -a flag means append to the file instead of overwriting it.
1184 You can have more than one command on the line, to do this you MUST
1185 enclose each command in double quotes (") eg:-
1187 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
1191 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
1193 You can only write into places that the cluster has permission for (which
1194 is that of the "sysop" user [which had BETTER NOT BE "root"]), you will
1195 need to create any directories you want to put stuff in beforehand as well.
1197 It is likely that you will want to run these commands in a crontab type
1198 situation. You would do that something like:-
1200 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
1202 Note that you still enclose each command with (") characters but you must
1203 enclose the entire save command in (') characters.
1205 Now in fact, this can be varied if you know what you are doing. See the
1206 admin manual for more details.
1208 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
1209 === 0^SEND RR <call>^Send a message and ask for a read receipt
1210 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
1211 === 0^SEND PRIVATE <call>^Send a personal message
1212 === 0^SEND NOPRIVATE <call>^Send a message to all stations
1213 All the SEND commands will create a message which will be sent either to
1214 an individual callsign or to one of the 'bulletin' addresses.
1216 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1217 it will mark the message as personal and send it to the cluster node that
1218 that callsign is connected to. If the <call> you have specified is in fact
1219 a known bulletin category on your node (eg: ALL) then the message should
1220 automatically become a bulletin.
1222 You can have more than one callsign in all of the SEND commands.
1224 You can have multiple qualifiers so that you can have for example:-
1226 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1228 which should send a copy of message 123 to G1TLH and G0RDI and you will
1229 receive a read receipt when they have read the message.
1231 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1232 SP is an alias for SEND PRIVATE
1234 The system will ask you for a subject. Conventionally this should be
1235 no longer than 29 characters for compatibility. Most modern cluster
1236 software should accept more.
1238 You will now be prompted to start entering your text.
1240 You finish the message by entering '/EX' on a new line. For instance:
1247 If you have started a message and you don't want to keep it then you
1248 can abandon the message with '/ABORT' on a new line, like:-
1252 oh I just can't be bothered with this
1255 If you abort the message it will NOT be sent.
1257 When you are entering the text of your message, most normal output (such
1258 as DX announcements and so on are suppressed and stored for latter display
1259 (upto 20 such lines are stored, as new ones come along, so the oldest
1262 Also, you can enter normal commands commands (and get the output
1263 immediately) whilst in the middle of a message. You do this by typing
1264 the command preceeded by a '/' character on a new line, so:-
1266 /dx g1tlh 144010 strong signal
1268 Will issue a dx annoucement to the rest of the cluster.
1270 Also, you can add the output of a command to your message by preceeding
1271 the command with '//', thus :-
1275 This will show YOU the output from SH/VHFTABLE and also store it in the
1278 You can carry on with the message until you are ready to send it.
1279 === 0^SET/ADDRESS <your address>^Record your postal address
1281 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
1282 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
1284 === 0^SET/ANNTALK^Allow talk like announce messages on your terminal
1285 === 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal
1286 The announce system on legacy cluster nodes is used as a talk
1287 substitute because the network is so poorly connected. If you:
1291 you will suppress several of these announces, you may miss the odd
1292 useful one as well, but you would probably miss them anyway in the
1293 welter of useless ones.
1297 allows you to see them again. This is the default.
1299 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
1301 === 8^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
1302 === 8^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
1303 Setting a word as 'baddx' will prevent spots with that word in the
1304 'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
1305 further. They will not be displayed and they will not be sent onto
1308 The word must be written in full, no wild cards are allowed eg:-
1310 set/baddx FORSALE VIDEO FR0G
1312 To allow a word again, use the following command ...
1316 === 8^SET/BADNODE <call>..^Stop spots from this node being propagated
1317 === 8^UNSET/BADNODE <call>..^Allow spots from this node again
1318 Setting a callsign as a 'badnode' will prevent spots from that node
1319 going any further. They will not be displayed and they will not be
1320 sent onto other nodes.
1322 The call must be a full eg:-
1326 will stop anything from K1TTT. If you want SSIDs as well then you must
1327 enter them specifically.
1331 will allow spots from him again.
1333 Use with extreme care. This command may well be superceeded by FILTERing.
1335 === 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1336 === 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1337 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1338 going any further. They will not be displayed and they will not be
1339 sent onto other nodes.
1341 The call must be written in full, no wild cards are allowed eg:-
1343 set/badspotter VE2STN
1345 will stop anything from VE2STN. This command will automatically
1346 stop spots from this user, regardless of whether or which SSID
1347 he uses. DO NOT USE SSIDs in the callsign, just use the callsign
1350 unset/badspotter VE2STN
1352 will allow spots from him again.
1354 Use with extreme care. This command may well be superceded by FILTERing.
1356 === 8^SET/BADWORD <word>..^Stop things with this word being propagated
1357 === 8^UNSET/BADWORD <word>..^Propagate things with this word again
1358 Setting a word as a 'badword' will prevent things like spots,
1359 announces or talks with this word in the the text part from going any
1360 further. They will not be displayed and they will not be sent onto
1363 The word must be written in full, no wild cards are allowed eg:-
1365 set/badword annihilate annihilated annihilation
1367 will stop anything with these words in the text.
1369 unset/badword annihilated
1371 will allow text with this word again.
1373 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1374 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1376 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1378 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1380 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1381 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1382 You can choose to log several different levels. The levels are
1390 You can show what levels you are logging with SHOW/DEBUG
1392 === 0^SET/DX^Allow DX messages to come out on your terminal
1393 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1395 === 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements
1396 === 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements
1397 A standard feature which is enabled in version 1.43 and above is
1398 that if the spotter's grid square is known it is output on the end
1399 of a DX announcement (there is just enough room). Some user programs
1400 cannot cope with this. You can use this command to reset (or set)
1403 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1405 === 0^SET/ECHO^Make the cluster echo your input
1406 === 0^UNSET/ECHO^Stop the cluster echoing your input
1407 If you are connected via a telnet session, different implimentations
1408 of telnet handle echo differently depending on whether you are
1409 connected via port 23 or some other port. You can use this command
1410 to change the setting appropriately.
1412 The setting is stored in your user profile.
1414 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1416 === 0^SET/EMAIL <email> ...^Set email address(es) and forward your personals
1417 === 0^UNSET/EMAIL^Stop personal msgs being forwarded by email
1418 If any personal messages come in for your callsign then you can use
1419 these commands to control whether they are forwarded onto your email
1420 address. To enable the forwarding do something like:-
1422 SET/EMAIL mike.tubby@somewhere.com
1424 You can have more than one email address (each one separated by a space).
1425 Emails are forwarded to all the email addresses you specify.
1427 You can disable forwarding by:-
1431 === 0^SET/HERE^Tell the system you are present at your terminal
1432 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1434 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1435 Tell the cluster system where you normally connect to. Any Messages sent
1436 to you will normally find their way there should you not be connected.
1440 === 8^SET/HOPS <call> ann|spots|route|wwv|wcy <n>^Set hop count
1441 === 8^UNSET/HOPS <call> ann|spots|route|wwv|wcy^Unset hop count
1442 Set the hop count for a particular type of broadcast for a node.
1444 This command allows you to set up special hop counts for a node
1445 for currently: announce, spots, wwv and wcy broadcasts.
1448 set/hops gb7djk ann 10
1449 set/hops gb7mbc spots 20
1451 Set SHOW/HOPS for information on what is already set. This command
1452 creates a filter and works in conjunction with the filter system.
1454 You can unset the hops with command UNSET/HOPS. For example:-
1456 unset/hops gb7djk ann
1457 unset/hops gb7mbc spots
1460 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1461 Connect a node to your system in such a way that you are a full protocol
1462 member of its network and can see all spots on it, but nothing either leaks
1463 out from it nor goes back into from the rest of the nodes connected to you.
1465 You can potentially connect several nodes in this way.
1467 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1468 Remove isolation from a node - SET/ISOLATE
1470 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1471 You can select the language that you want the cluster to use. Currently
1472 the languages available are en (English), de (German), es (Spanish)
1475 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1476 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1477 In order to get accurate headings and such like you must tell the system
1478 what your latitude and longitude is. If you have not yet done a SET/QRA
1479 then this command will set your QRA locator for you. For example:-
1480 SET/LOCATION 52 22 N 0 57 E
1482 === 0^SET/LOGININFO^Inform when a station logs in locally
1483 === 0^UNSET/LOGININFO^Inform when a station logs out locally
1485 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1486 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1488 === 0^SET/NAME <your name>^Set your name
1489 Tell the system what your name is eg:-
1492 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1493 Tell the system that the call(s) are to be treated as AK1A cluster and
1494 fed PC Protocol rather normal user commands.
1496 === 8^SET/OBSCOUNT <count> <nodecall>^Set the 'pump-up' obscelence counter
1497 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1498 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1499 counter which is decremented on every outgoing ping and then reset to
1500 the 'obscount' value on every incoming ping. The default value of this
1503 What this means is that a neighbouring node will be pinged twice at
1504 (default) 300 second intervals and if no reply has been heard just before
1505 what would be the third attempt, that node is disconnected.
1507 If a ping is heard then the obscount is reset to the full value. Using
1508 default values, if a node has not responded to a ping within 15 minutes,
1511 You can set this parameter between 1 and 9.
1513 It is STRONGLY recommended that you don't change the default.
1515 === 0^SET/PAGE <lines per page>^Set the lines per page
1516 Tell the system how many lines you wish on a page when the number of line
1517 of output from a command is more than this. The default is 20. Setting it
1518 explicitly to 0 will disable paging.
1522 The setting is stored in your user profile.
1524 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1525 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1526 in order to determine the rolling quality of the link and, in future, to
1527 affect routing decisions. The default interval is 300 secs or 5 minutes.
1529 You can use this command to set a different interval. Please don't.
1531 But if you do the value you enter is treated as minutes up 30 and seconds
1532 for numbers greater than that.
1534 This is used also to help determine when a link is down at the far end
1535 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1536 for more information.
1538 If you must change it (and it may be useful for internet connected nodes
1539 on dynamic IP addresses that go away after a set time of usage) the time
1540 can be specified as:-
1542 5 which if less than 30 is converted to minutes otherwise is
1543 taken as the no of seconds between pings.
1548 Please be aware that this causes traffic to occur on the link, setting
1549 this value too low may annoy your neighbours beyond the point of
1552 You can switch this off by setting it to 0.
1554 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1555 Set the privilege level on a callsign. The privilege levels that pertain
1556 to commands are as default:-
1558 1 - allow remote nodes normal user RCMDs
1559 5 - various privileged commands (including shutdown, but not disc-
1560 connect), the normal level for another node.
1561 8 - more privileged commands (including disconnect)
1562 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1564 If you are a sysop and you come in as a normal user on a remote connection
1565 your privilege will automatically be set to 0.
1567 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1568 You can use this command to 'protect' this session from unauthorised
1569 use. If you want to get your normal privilege back you will need to
1570 either logout and login again (if you are on a console) or use the
1573 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1574 The password for a user can only be set by a full sysop. The string
1575 can contain any characters.
1577 The way this field is used depends on context. If it is being used in
1578 the SYSOP command context then you are offered 5 random numbers and you
1579 have to supply the corresponding letters. This is now mainly for ax25
1582 If it is being used on incoming telnet connections then, if a password
1585 set/var $main::passwdreq = 1
1587 command is executed in the startup script, then a password prompt is
1588 given after the normal 'login: ' prompt.
1590 === 0^SET/PASSWORD^Set your own password
1591 This command only works for a 'telnet' user (currently). It will
1592 only work if you have a password already set. This initial password
1593 can only be set by the sysop.
1595 When you execute this command it will ask you for your old password,
1596 then ask you to type in your new password twice (to make sure you
1597 get it right). You may or may not see the data echoed on the screen
1598 as you type, depending on the type of telnet client you have.
1600 === 9^UNSET/PASSWORD <call> ...^Delete (remove) a user's password
1601 This command allows the sysop to completely delete and remove a
1602 password for a user.
1604 === 0^SET/PROMPT <string>^Set your prompt to <string>
1605 === 0^UNSET/PROMPT^Set your prompt back to default
1606 This command will set your user prompt to exactly the string that you
1607 say. The point of this command to enable a user to interface to programs
1608 that are looking for a specific prompt (or else you just want a different
1613 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to
1616 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1617 Tell the system that the call(s) are to be treated as DXSpider node and
1618 fed new style DX Protocol rather normal user commands.
1620 === 9^SET/SYS_QRA <locator>^Set your cluster QRA Grid locator
1621 === 0^SET/QRA <locator>^Set your QRA Grid locator
1622 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1623 done a SET/LOCATION then your latitude and longitude will be set roughly
1624 correctly (assuming your locator is correct ;-). For example:-
1627 === 0^SET/QTH <your qth>^Set your QTH
1628 Tell the system where you are. For example:-
1629 SET/QTH East Dereham, Norfolk
1631 === 9^SET/REGISTER <call> ...^Mark a user as registered
1632 === 9^UNSET/REGISTER <call> ...^Mark a user as not registered
1633 Registration is a concept that you can switch on by executing the
1635 set/var $main::regreq = 1
1637 command (usually in your startup file)
1639 If a user is NOT registered then, firstly, instead of the normal
1640 motd file (/spider/data/motd) being sent to the user at startup, the
1641 user is sent the motd_nor file instead. Secondly, the non registered
1642 user only has READ-ONLY access to the node. The non-registered user
1643 cannot use DX, ANN etc.
1645 The only exception to this is that a non-registered user can TALK or
1646 SEND messages to the sysop.
1648 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1649 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1651 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1652 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1654 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1655 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1657 === 0^SET/WX^Allow WX messages to come out on your terminal
1658 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1660 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1661 Display all the bad dx callsigns in the system, see SET/BADDX
1662 for more information.
1664 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1665 Display all the bad node callsigns in the system, see SET/BADNODE
1666 for more information.
1668 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1669 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1670 for more information.
1672 === 1^SHOW/BADWORD^Show all the bad words in the system
1673 Display all the bad words in the system, see SET/BADWORD
1674 for more information.
1676 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
1677 This command allows you to see all the users that can be seen
1678 and the nodes to which they are connected.
1680 This command is normally abbreviated to: sh/c
1682 BE WARNED: the list that is returned can be VERY long
1684 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
1685 Show all the nodes connected to this node.
1687 === 1^SHOW/CONNECT^Show all the active connections
1688 This command shows information on all the active connections known to
1689 the node. This command gives slightly more information than WHO.
1691 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
1692 This is very nearly the same as SHOW/TIME, the only difference the format
1693 of the date string if no arguments are given.
1695 If no prefixes or callsigns are given then this command returns the local
1696 time and UTC as the computer has it right now. If you give some prefixes
1697 then it will show UTC and UTC + the local offset (not including DST) at
1698 the prefixes or callsigns that you specify.
1700 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
1702 === 0^SHOW/DX^Interrogate the spot database
1703 If you just type SHOW/DX you will get the last so many spots
1704 (sysop configurable, but usually 10).
1706 In addition you can add any number of these commands in very nearly
1707 any order to the basic SHOW/DX command, they are:-
1709 on <band> - eg 160m 20m 2m 23cm 6mm
1710 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1711 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
1714 <number> - the number of spots you want
1715 <from>-<to> - <from> spot no <to> spot no in the selected list
1718 <prefix> - for a spotted callsign beginning with <prefix>
1719 *<suffix> - for a spotted callsign ending in <suffix>
1720 *<string>* - for a spotted callsign containing <string>
1722 day <number> - starting <number> days ago
1723 day <from>-<to> - <from> days <to> days ago
1726 info <text> - any spots containing <text> in the info or remarks
1728 by <call> - any spots spotted by <call> (spotter <call> is the
1731 qsl - this automatically looks for any qsl info on the call
1732 held in the spot database.
1734 iota [<iota>] - If the iota island number is missing it will look for
1735 the string iota and anything which looks like an iota
1736 island number. If you specify then it will look for
1739 qra [<locator>] - this will look for the specific locator if you specify
1740 one or else anything that looks like a locator.
1742 dxcc - treat the prefix as a 'country' and look for spots
1743 from that country regardless of actual prefix.
1746 You can also use this with the 'by' keyword so
1752 SH/DX on 20m info iota
1753 SH/DX 9a on vhf day 30
1759 SH/DX dxcc oq2 by w dxcc
1761 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
1762 This command takes the <prefix> (which can be a full or partial
1763 callsign if desired), looks up which internal country number it is
1764 and then displays all the spots as per SH/DX for that country.
1766 This is now an alias for 'SHOW/DX DXCC'
1768 The options for SHOW/DX also apply to this command.
1772 SH/DXCC W on 20m iota
1774 This can be done with the SHOW/DX command like this:-
1777 SH/DX dxcc w on 20m iota
1779 === 0^SHOW/DXSTATS^Show the DX Statistics for last 31 days
1780 Show the total DX spots for the last 31 days
1782 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
1783 SHOW/FILES on its own will show you a list of the various fileareas
1784 available on the system. To see the contents of a particular file
1787 where <filearea> is the name of the filearea you want to see the
1790 You can also use shell globbing characters like '*' and '?' in a
1791 string to see a selection of files in a filearea eg:-
1792 SH/FILES bulletins arld*
1794 See also TYPE - to see the contents of a file.
1796 === 0^SHOW/FILTER^Show the contents of all the filters you have set
1797 Show the contents of all the filters that are set. This command displays
1798 all the filters set - for all the various categories.
1800 === 0^SHOW/HFSTATS^Show the HF DX Statistics for last 31 days
1801 Show the HF DX spots breakdown by band for the last 31 days
1803 === 0^SHOW/HFTABLE [prefix ...]^Show the HF DX Spotter Table
1804 Show the HF DX Spotter table for the list of prefixes for the last 31 days,
1805 if there are no prefixes then it will show the table for your country.
1807 Remember that some countries have more than one "DXCC country" in them
1808 (eg G :-), to show them (assuming you are not in G already which is
1809 specially treated in the code) you must list all the relevant prefixes
1811 sh/hftable g gm gd gi gj gw gu
1813 Note that the prefixes are converted into country codes so you don't have
1814 to list all possible prefixes for each country.
1816 === 8^SHOW/HOPS <call> [ann|spots|route|wcy|wwv]^Show the hop counts for a node
1817 This command shows the hop counts set up for a node. You can specify
1818 which category you want to see. If you leave the category out then
1819 all the categories will be listed.
1821 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
1823 === 9^SHOW/LOCKOUT <prefix>|ALL^Show the list of locked out or excluded callsigns
1825 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
1826 This command outputs a short section of the system log. On its own
1827 it will output a general logfile. With the optional callsign it will
1828 show output from the log associated with that callsign.
1830 === 0^SHOW/MOON [ndays] [<prefix>|<callsign>]^Show Moon rise and set times
1831 Show the Moon rise and set times for a (list of) prefixes or callsigns,
1832 together with the azimuth and elevation of the sun currently at those
1835 If you don't specify any prefixes or callsigns, it will show the times for
1836 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1837 together with the current azimuth and elevation.
1839 In addition, it will show the illuminated fraction of the moons disk.
1841 If all else fails it will show the Moonrise and set times for the node
1842 that you are connected to.
1849 You can also use this command to see into the past or the future, so
1850 if you want to see yesterday's times then do:-
1854 or in three days time:-
1858 Upto 366 days can be checked both in the past and in the future.
1860 Please note that the rise and set times are given as the UT times of rise and
1861 set on the requested UT day.
1863 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
1864 This command allow you to estimate the likelihood of you contacting
1865 a station with the prefix you have specified. The output assumes a modest
1866 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
1868 The result predicts the most likely operating frequencies and signal
1869 levels for high frequency (shortwave) radio propagation paths on
1870 specified days of the year and hours of the day. It is most useful for
1871 paths between 250 km and 6000 km, but can be used with reduced accuracy
1872 for paths shorter or longer than this.
1874 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1875 used to predict the MUF given the predicted flux, day of the year,
1876 hour of the day and geographic coordinates of the transmitter and
1877 receiver. This routine is reasonably accurate for the purposes here,
1878 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1879 than the programs used by major shortwave broadcasting organizations,
1880 such as the Voice of America.
1882 The command will display some header information detailing its
1883 assumptions, together with the locations, latitude and longitudes and
1884 bearings. It will then show UTC (UT), local time at the other end
1885 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1886 (Zen) and the likely signal strengths. Then for each frequency for which
1887 the system thinks there is a likelihood of a circuit it prints a value.
1889 The value is currently a likely S meter reading based on the conventional
1890 6dB / S point scale. If the value has a '+' appended it means that it is
1891 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1892 there is likely to be much fading and by an 's' that the signal is likely
1895 By default SHOW/MUF will show the next two hours worth of data. You
1896 can specify anything up to 24 hours worth of data by appending the no of
1897 hours required after the prefix. For example:-
1903 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1904 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1905 Location Lat / Long Azim
1906 East Dereham, Norfolk 52 41 N 0 57 E 47
1907 United-States-W 43 0 N 87 54 W 299
1908 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1909 18 23 11.5 -35 mS0+ mS2 S3
1910 19 0 11.2 -41 mS0+ mS2 S3
1912 indicating that you will have weak, fading circuits on top band and
1913 80m but usable signals on 40m (about S3).
1919 will get you the above display, but with the next 24 hours worth of
1925 Gives you an estimate of the long path propagation characterics. It
1926 should be noted that the figures will probably not be very useful, nor
1927 terrible accurate, but it is included for completeness.
1929 === 0^SHOW/NEWCONFIGURATION [<node>]^Show all the nodes and users visible
1930 This command allows you to see all the users that can be seen
1931 and the nodes to which they are connected.
1933 This command produces essentially the same information as
1934 SHOW/CONFIGURATION except that it shows all the duplication of
1935 any routes that might be present It also uses a different format
1936 which may not take up quite as much space if you don't have any
1939 BE WARNED: the list that is returned can be VERY long
1941 === 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally
1942 Show all the nodes connected to this node in the new format.
1944 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
1945 Show the type and version (if connected) of the nodes specified on the
1946 command line. If no callsigns are specified then a sorted list of all
1947 the non-user callsigns known to the system will be displayed.
1949 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
1950 This command takes the <callsign> (which can be a full or partial
1951 callsign or a prefix), looks up which internal country number
1952 it is and then displays all the relevant prefixes for that country
1953 together with the internal country no, the CQ and ITU regions.
1957 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
1958 Show the name and location where every program module was load from. This
1959 is useful for checking where you think you have loaded a .pm file from.
1961 === 0^SHOW/QRA <locator> [<locator>]^Show distance between QRA Grid locators
1962 === 0^SHOW/QRA <lat> <long>^Convert lat/long to a QRA Grid locator
1963 This is a multipurpose command that allows you either to calculate the
1964 distance and bearing between two locators or (if only one locator is
1965 given on the command line) the distance and beraing from your station
1966 to the locator. For example:-
1971 The first example will show the distance and bearing to the locator from
1972 yourself, the second example will calculate the distance and bearing from
1973 the first locator to the second. You can use 4 or 6 character locators.
1975 It is also possible to convert a latitude and longitude to a locator by
1976 using this command with a latitude and longitude as an argument, for
1979 SH/QRA 52 41 N 0 58 E
1981 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
1982 This command queries the QRZ callbook server on the internet
1983 and returns any information available for that callsign. This service
1984 is provided for users of this software by http://www.qrz.com
1986 === 9^SHOW/REGISTERED [<prefix>]^Show the registered users
1988 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
1989 This command allows you to see to which node the callsigns specified are
1990 connected. It is a sort of inverse sh/config.
1994 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
1995 Show the tracking data from your location to the satellite of your choice
1996 from now on for the next few hours.
1998 If you use this command without a satellite name it will display a list
1999 of all the satellites known currently to the system.
2001 If you give a name then you can obtain tracking data of all the passes
2002 that start and finish 5 degrees below the horizon. As default it will
2003 give information for the next three hours for every five minute period.
2005 You can alter the number of hours and the step size, within certain
2008 Each pass in a period is separated with a row of '-----' characters
2013 SH/SAT FENGYUN1 12 2
2015 === 6^SHOW/STATION ALL [<regex>]^Show list of users in the system
2016 === 0^SHOW/STATION [<callsign> ..]^Show information about a callsign
2017 Show the information known about a callsign and whether (and where)
2018 that callsign is connected to the cluster.
2022 If no callsign is given then show the information for yourself.
2024 === 0^SHOW/SUN [ndays] [<prefix>|<callsign>]^Show sun rise and set times
2025 Show the sun rise and set times for a (list of) prefixes or callsigns,
2026 together with the azimuth and elevation of the sun currently at those
2029 If you don't specify any prefixes or callsigns, it will show the times for
2030 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2031 together with the current azimuth and elevation.
2033 If all else fails it will show the sunrise and set times for the node
2034 that you are connected to.
2039 SH/SUN G1TLH K9CW ZS
2041 You can also use this command to see into the past or the future, so
2042 if you want to see yesterday's times then do:-
2046 or in three days time:-
2050 Upto 366 days can be checked both in the past and in the future.
2052 Please note that the rise and set times are given as the UT times of rise
2053 and set on the requested UT day.
2055 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
2056 If no prefixes or callsigns are given then this command returns the local
2057 time and UTC as the computer has it right now. If you give some prefixes
2058 then it will show UTC and UTC + the local offset (not including DST) at
2059 the prefixes or callsigns that you specify.
2061 === 0^SHOW/VHFSTATS^Show the VHF DX Statistics for last 31 days
2062 Show the VHF DX spots breakdown by band for the last 31 days
2064 === 0^SHOW/VHFTABLE [prefix ...]^Show the VHF DX Spotter Table
2065 Show the VHF DX Spotter table for the list of prefixes for the last 31 days,
2066 if there are no prefixes then it will show the table for your country.
2068 Remember that some countries have more than one "DXCC country" in them
2069 (eg G :-), to show them (assuming you are not in G already which is
2070 specially treated in the code) you must list all the relevant prefixes
2072 sh/vhftable g gm gd gi gj gw gu
2074 Note that the prefixes are converted into country codes so you don't have
2075 to list all possible prefixes for each country.
2077 === 0^SHOW/WCY^Show last 10 WCY broadcasts
2078 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
2079 Display the most recent WCY information that has been received by the system
2081 === 0^SHOW/WWV^Show last 10 WWV broadcasts
2082 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
2083 Display the most recent WWV information that has been received by the system
2085 === 5^SHUTDOWN^Shutdown the cluster
2086 Shutdown the cluster and disconnect all the users
2088 === 9^SPOOF <call> <command>^Do a command as though you are another user
2089 This command is provided so that sysops can set a user's parameters without
2090 me having to write a special 'sysop' version for every user command. It
2091 allows you to pretend that you are doing the command as the user you specify.
2095 SPOOF G1TLH set/name Dirk
2096 SPOOF G1TLH set/qra JO02LQ
2098 === 5^STAT/DB <dbname>^Show the status of a database
2099 Show the internal status of a database descriptor.
2101 Depending on your privilege level you will see more or less information.
2102 This command is unlikely to be of much use to anyone other than a sysop.
2104 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
2105 Show the internal status of the channel object either for the channel that
2106 you are on or else for the callsign that you asked for.
2108 Only the fields that are defined (in perl term) will be displayed.
2110 === 1^STAT/MSG^Show the status of the message system
2111 === 1^STAT/MSG <msgno>^Show the status of a message
2112 This command shows the internal status of a message and includes information
2113 such as to whom it has been forwarded, its size, origin etc etc.
2115 If no message number is given then the status of the message system is
2118 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
2119 === 5^STAT/ROUTE_NODE all^Show list of all Route::Node objects
2121 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
2122 === 5^STAT/ROUTE_USER all^Show list of all Route::User objects
2124 === 5^STAT/USER [<callsign>]^Show the full status of a user
2125 Shows the full contents of a user record including all the secret flags
2128 Only the fields that are defined (in perl term) will be displayed.
2130 === 0^SYSOP^Regain your privileges if you login remotely
2131 The system automatically reduces your privilege level to that of a
2132 normal user if you login in remotely. This command allows you to
2133 regain your normal privilege level. It uses the normal system: five
2134 numbers are returned that are indexes into the character array that is
2135 your assigned password (see SET/PASSWORD). The indexes start from
2138 You are expected to return a string which contains the characters
2139 required in the correct order. You may intersperse those characters
2140 with others to obscure your reply for any watchers. For example (and
2141 these values are for explanation :-):
2143 password = 012345678901234567890123456789
2147 aa2bbbb0ccc5ddd7xxx3n
2151 They will all match. If there is no password you will still be offered
2152 numbers but nothing will happen when you input a string. Any match is
2155 === 0^TALK <call> [<text>]^Send a text message to another station
2156 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
2157 Send a short message to any other station that is visible on the cluster
2158 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2159 command, they don't have to be connected locally.
2161 The second form of TALK is used when other cluster nodes are connected
2162 with restricted information. This usually means that they don't send
2163 the user information usually associated with logging on and off the cluster.
2165 If you know that G3JNB is likely to be present on GB7TLH, but you can only
2166 see GB7TLH in the SH/C list but with no users, then you would use the
2167 second form of the talk message.
2169 If you want to have a ragchew with someone you can leave the text message
2170 out and the system will go into 'Talk' mode. What this means is that a
2171 short message is sent to the recipient telling them that you are in a
2172 'Talking' frame of mind and then you just type - everything you send will
2173 go to the station that you asked for.
2175 All the usual announcements, spots and so on will still come out on your
2178 If you want to do something (such as send a spot) you preceed the normal
2179 command with a '/' character, eg:-
2181 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2184 To leave talk mode type:
2188 If you are in 'Talk' mode, there is an extention to the '/' command which
2189 allows you to send the output to all the people you are talking to. You do
2190 with the '//' command. For example:-
2194 will send the hftable as you have it to all the people you are currently
2197 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
2198 Type out the contents of a file in a filearea. So, for example, in
2199 filearea 'bulletins' you want to look at file 'arld051' you would
2201 TYPE bulletins/arld051
2203 See also SHOW/FILES to see what fileareas are available and a
2206 === 0^WHO^Show who is physically connected
2207 This is a quick listing that shows which callsigns are connected and
2208 what sort of connection they have
2210 === 0^WX <text>^Send a weather message to local users
2211 === 0^WX FULL <text>^Send a weather message to all cluster users
2212 === 5^WX SYSOP <text>^Send a weather message to other clusters only
2213 Weather messages can sometimes be useful if you are experiencing an extreme
2214 that may indicate enhanced conditions