1 <!doctype linuxdoc system>
5 <!-- Title information -->
7 <title>The DXSpider Administration Manual v1.48</title>
8 <author>Ian Maude, G0VGS, (ianmaude@btinternet.com)</author>
9 <date>Version 1.48 August 2001 revision 1.1</date>
12 A reference for SysOps of the DXSpider DXCluster program.
15 <!-- Table of contents -->
18 <!-- Begin the document -->
20 <sect>Routing and Filtering
25 From DXSpider version 1.48, major changes were introduced to the way
26 node connections are treated. This is part of an ongoing process to
27 remove problems with loops and to enable talk and other functions to
28 propagate across the whole of the worldwide cluster network. In fact,
29 in a Spider network, it would be useful, perhaps even necessary to
30 have loops. This would give real resilience to the network, meaning
31 that if a link dropped, the information flow would simply come in and
32 go out via a different route. Of course, we do not have a complete
33 network of Spider nodes, there are other programs out there. Some of
34 these do not have any protection from loops. Certainly AK1A does not
35 handle loops well at all. It is therefore necessary to have some form
36 of protection for these nodes.
39 This is achieved by using filtering on a route basis. There is a
40 default setting to help to protect the network, especially useful for new
41 and inexperienced SysOps. The idea is simple. When Spider is started
42 for the first time and a connection is made to or from another node,
43 the default is to only send the nodes you already have that are in your
44 own zone. For example, in the UK the default setting would be to send
45 only UK nodes to any connection. This can be filtered further (down to
46 a single node if needed) or expanded as required.
52 As mentioned in the introduction, a default setting exists. If this is
53 all you want to use then that is fine, you have nothing else to do.
54 However, if you want to make any alterations then you need to know
58 It is possible to reset the default setting for node connections should
59 you wish to do so, however this can be dangerous to the network unless
60 you have some experience in how all this works.... be careful! It is
61 also possible to change settings for one connection only. You can,
62 therefore, have many different filters set dependent on the amount of
66 I should at this stage give a little bit of background on filters. All
67 the filters in Spider work in basically the same way. You can either
68 accept or reject various options in order to create the filter rules
69 you wish to achieve. Some filters are user settable, others can only
70 be altered by the sysop. Route filtering can only be done by the sysop.
72 <sect1>The default_node filter
75 As discussed previously, a default setting exists that only sends nodes
76 from your own zone. This can be overridden by using the default_node
77 filter option like this ...
80 reject/route default_node <filter_option>
84 accept/route default_node <filter_option>
88 where filter_option is one of the following ...
92 call_dxcc <numbers>
93 call_itu <numbers>
94 call_zone <numbers>
95 origin <prefixes>
96 origin_dxcc <numbers>
97 origin_itu <numbers>
98 origin_zone <numbers>
102 Please be careful if you alter this setting, it will affect
103 <bf><it>ALL</it></bf> your links!
105 <sect1>General route filtering
108 Exactly the same rules apply for general route filtering. You would
109 use either an accept filter or a reject filter like this ...
112 reject/route <node_call> <filter_option>
116 accept/route <node_call> <filter_option>
120 where filter_option is one of the following ...
123 call <prefixes>
124 call_dxcc <numbers>
125 call_itu <numbers>
126 call_zone <numbers>
127 origin <prefixes>
128 origin_dxcc <numbers>
129 origin_itu <numbers>
130 origin_zone <numbers>
134 Here are some examples of route filters ...
137 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
138 rej/route all (equiv to [very] restricted mode)
139 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
140 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
143 <sect1>General filter rules
146 Upto v1.44 it was not possible for the user to set their own filters. From
147 v1.45 though that has all changed. It is now possible to set filters for just
148 about anything you wish. If you have just updated from an older version of
149 DXSpider you will need to update your new filters. You do not need to do
150 anything with your old filters, they will be renamed as you update.
153 There are 3 basic commands involved in setting and manipulating filters. These
154 are <em>accept</em>, <em>reject</em> and <em>clear</em>. First we will look
155 generally at filtering. There are a number of things you can filter in the
156 DXSpider system. They all use the same general mechanism.
159 In general terms you can create a 'reject' or an 'accept' filter which can have
160 up to 10 lines in it. You do this using, for example ...
167 where ..... are the specific commands for that type of filter. There are filters
168 for spots, wwv, announce, wcy and (for sysops) connects. See each different
169 accept or reject command reference for more details.
171 There is also a command to clear out one or more lines in a filter. They are ...
178 There is clear/xxxx command for each type of filter.
181 and you can check that your filters have worked by the command ...
188 For now we are going to use spots for the examples, but you can apply the same
189 principles to all types of filter.
191 <sect1>Types of filter
194 There are two main types of filter, <em>accept</em> or <em>reject</em>. You
195 can use either to achieve the result you want dependent on your own preference
196 and which is more simple to do. It is pointless writing 8 lines of reject
197 filters when 1 accept filter would do the same thing! Each filter has 10
198 lines (of any length) which are tried in order. If a line matches then the
199 action you have specified is taken (ie reject means ignore it and accept
203 If you specify reject filters, then any lines that arrive that match the filter
204 will be dumped but all else will be accepted. If you use an accept filter,
205 then ONLY the lines in the filter will be accepted and all else will be dumped.
206 For example if you have a single line <em>accept</em> filter ...
209 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
212 then you will <em>ONLY</em> get VHF spots <em>from</em> or <em>to</em> CQ zones
216 If you set a reject filter like this ...
219 reject/spots on hf/cw
222 Then you will get everything <em>EXCEPT</em> HF CW spots. You could make this
223 single filter even more flexible. For example, if you are interested in IOTA
224 and will work it even on CW even though normally you are not interested in
225 CW, then you could say ...
228 reject/spots on hf/cw and not info iota
231 But in that case you might only be interested in iota and say:-
234 accept/spots not on hf/cw or info iota
237 which achieves exactly the same thing. You should choose one or the other
238 until you are comfortable with the way it works. You can mix them if you
239 wish (actually you can have an accept AND a reject on the same line) but
240 don't attempt this until you are sure you know what you are doing!
243 You can arrange your filter lines into logical units, either for your own
244 understanding or simply convenience. Here is an example ...
247 reject/spots 1 on hf/cw
248 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
251 What this does is to ignore all HF CW spots and also rejects any spots on VHF
252 which don't either originate or spot someone in Europe.
255 This is an example where you would use a line number (1 and 2 in this case), if
256 you leave the digit out, the system assumes '1'. Digits '0'-'9' are available.
257 This make it easier to see just what filters you have set. It also makes it
258 more simple to remove individual filters, during a contest for example.
261 You will notice in the above example that the second line has brackets. Look
262 at the line logically. You can see there are 2 separate sections to it. We
263 are saying reject spots that are VHF or above <em>APART</em> from those in
264 zones 14, 15 and 16 (either spotted there or originated there). If you did
265 not have the brackets to separate the 2 sections, then Spider would read it
266 logically from the front and see a different expression entirely ...
269 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
272 The simple way to remember this is, if you use OR - use brackets. Whilst we are
273 here CASE is not important. 'And BY_Zone' is just the same as 'and by_zone'.
275 As mentioned earlier, setting several filters can be more flexible than
276 simply setting one complex one. Doing it in this way means that if you want
277 to alter your filter you can just redefine or remove one or more lines of it or
278 one line. For example ...
281 reject/spots 1 on hf/ssb
284 would redefine our earlier example, or
290 To remove all the filter lines in the spot filter ...
296 <sect1>Filter options
299 You can filter in several different ways. The options are listed in the
300 various helpfiles for accept, reject and filter.
302 <sect1>Default filters
305 Sometimes all that is needed is a general rule for node connects. This can
306 be done with a node_default filter. This rule will always be followed, even
307 if the link is isolated, unless another filter is set specifically. Default
308 rules can be set for nodes and users. They can be set for spots, announces,
309 WWV and WCY. They can also be used for hops. An example might look like
313 accept/spot node_default by_zone 14,15,16,20,33
314 set/hops node_default spot 50
317 This filter is for spots only, you could set others for announce, WWV and WCY.
318 This filter would work for ALL nodes unless a specific filter is written to
319 override it for a particular node. You can also set a user_default should
320 you require. It is important to note that default filters should be
321 considered to be "connected". By this I mean that should you override the
322 default filter for spots, you need to add a rule for the hops for spots also.
324 <sect1>Advanced filtering
327 Once you are happy with the results you get, you may like to experiment.
330 The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU
331 can be written with a mixed filter, for example ...
336 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
339 Note that the first filter has not been specified with a number. This will
340 automatically be assumed to be number 1. In this case, we have said <em>reject all
341 HF spots in the CW section of the bands but accept all others at HF. Also
342 accept anything in VHF and above spotted in or by operators in the zones
343 14, 15 and 16</em>. Each filter slot actually has a 'reject' slot and
344 an 'accept' slot. The reject slot is executed BEFORE the accept slot.
347 It was mentioned earlier that after a reject test that doesn't match, the default
348 for following tests is 'accept', the reverse is true for 'accept'. In the example
349 what happens is that the reject is executed first, any non hf/cw spot is passed
350 to the accept line, which lets through everything else on HF. The next filter line
351 lets through just VHF/UHF spots from EU.
353 <sect1>Basic hop control
356 In /spider/data you will find a file called hop_table.pl. This is the file
357 that controls your hop count settings. It has a set of default hops on the
358 various PC frames and also a set for each node you want to alter the hops for.
359 You may be happy with the default settings of course, but this powerful tool
360 can help to protect and improve the network. The file will look something
365 # hop table construction
370 # default hopcount to use
373 # some variable hop counts based on message type
384 # the per node hop control thingy
416 Each set of hops is contained within a pair of curly braces and contains a
417 series of PC frame types. PC11 for example is a DX spot. The figures here
418 are not exhaustive but should give you a good idea of how the file works.
421 You can alter this file at any time, including whilst the cluster is running.
422 If you alter the file during runtime, the command <em>load/hops</em> will
423 bring your changes into effect.
425 <sect1>Isolating networks
428 It is possible to isolate networks from each other on a "gateway" node using the
429 <em>set/isolate <node_call></em> command.
432 The effect of this is to partition an isolated network completely from another
433 node connected to your node. Your node will appear on and otherwise behave
434 normally on every network to which you are connected, but data from an isolated
435 network will not cross onto any other network or vice versa. However all the
436 spot, announce and WWV traffic and personal messages will still be handled
437 locally (because you are a real node on all connected networks), that is locally
438 connected users will appear on all networks and will be able to access and
439 receive information from all networks transparently. All routed messages will
440 be sent as normal, so if a user on one network knows that you are a gateway for
441 another network, he can still still send a talk/announce etc message via your
442 node and it will be routed across.
445 The only limitation currently is that non-private messages cannot be passed down
446 isolated links regardless of whether they are generated locally. This will change
447 when the bulletin routing facility is added.
450 If you use isolate on a node connection you will continue to receive all
451 information from the isolated partner, however you will not pass any information
452 back to the isolated node. There are times when you would like to forward only
453 spots across a link (maybe during a contest for example). To do this, isolate
454 the node in the normal way and put in a filter in the /spider/filter/spots
455 directory to override the isolate. This filter can be very simple and consists
456 of just one line ....
460 [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count
466 <sect1>Filtering Mail
469 In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename
470 this to badmsg.pl and edit the file. The original looks something like this ....
474 # the list of regexes for messages that we won't store having
475 # received them (bear in mind that we must receive them fully before
479 # The format of each line is as follows
481 # type source pattern
482 # P/B/F T/F/O/S regex
484 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
485 # source: T - to field, F - from field, O - origin, S - subject
486 # pattern: a perl regex on the field requested
488 # Currently only type B and P msgs are affected by this code.
490 # The list is read from the top down, the first pattern that matches
491 # causes the action to be taken.
493 # The pattern can be undef or 0 in which case it will always be selected
494 # for the action specified
512 I think this is fairly self explanatory. It is simply a list of subject
513 headers that we do not want to pass on to either the users of the cluster or
514 the other cluster nodes that we are linked to. This is usually because of
515 rules and regulations pertaining to items for sale etc in a particular country.
517 <sect1>Filtering DX callouts (Depricated)
520 <bf><it>From version 1.47, this method is replaced by the command set/baddx</it></bf>
523 In the same way as mail, there are some types of spot we do not wish to pass on
524 to users or linked cluster nodes. In the /spider/data directory you will find
525 a file called baddx.pl.issue. Rename this to baddx.pl and edit the file. The
526 original looks like this ....
530 # the list of dx spot addresses that we don't store and don't pass on
551 Again, this is simply a list of names we do not want to see in the spotted
552 field of a DX callout.
555 <sect1>Filtering words from text fields in Announce, Talk and DX spots
558 Create a file in /spider/data called <em>badwords</em>. The format is quite
559 simple. Lines beginning with # are ignored so comments can be added. An
560 example file is below ...
563 # Below is a list of words we do not wish to see on the cluster
564 grunge grunged grunging
565 splodge splodger splodging
570 Multiple words can be used on the same line as shown. Obviously these
571 are just examples :-)
574 You can reload the file from the cluster prompt as sysop with load/badwords.
579 DXSpider deals seamlessly with standard AK1A type mail. It supports both
580 personal and bulletin mail and the sysop has additional commands to ensure
581 that mail gets to where it is meant. DXSpider will send mail almost
582 immediately, assuming that the target is on line. However, only one
583 mail message is dealt with at any one time. If a mail message is already
584 being sent or recieved, then the new message will be queued until it has
587 The cluster mail is automatically deleted after 30 days unless the sysop
588 sets the "keep" flag using the <em>msg</em> command.
593 Personal mail is sent using the <em>sp</em> command. This is actually the
594 default method of sending mail and so a simple <em>s</em> for send will do.
595 A full list of the send commands and options is in the <em>command set</em>
596 section, so I will not duplicate them here.
601 Bulletin mail is sent by using the <em>sb</em> command. This is one of the
602 most common mistakes users make when sending mail. They send a bulletin
603 mail with <em>s</em> or <em>sp</em> instead of <em>sb</em> and of course
604 the message never leaves the cluster. This can be rectified by the sysop
605 by using the <em>msg</em> command.
607 <P>Bulletin addresses can be set using the Forward.pl file.
612 DXSpider receives all and any mail sent to it without any alterations needed
613 in files. Because personal and bulletin mail are treated differently, there
614 is no need for a list of accepted bulletin addresses. It is necessary, however,
615 to tell the program which links accept which bulletins. For example, it is
616 pointless sending bulletins addresses to "UK" to any links other than UK
617 ones. The file that does this is called forward.pl and lives in /spider/msg.
618 At default, like other spider files it is named forward.pl.issue. Rename it
619 to forward.pl and edit the file to match your requirements.
620 The format is below ...
624 # this is an example message forwarding file for the system
626 # The format of each line is as follows
628 # type to/from/at pattern action destinations
629 # P/B/F T/F/A regex I/F [ call [, call ...] ]
631 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
632 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
633 # pattern: a perl regex on the field requested
634 # action: I - ignore, F - forward
635 # destinations: a reference to an array containing node callsigns
637 # if it is non-private and isn't in here then it won't get forwarded
639 # Currently only type B msgs are affected by this code.
641 # The list is read from the top down, the first pattern that matches
642 # causes the action to be taken.
644 # The pattern can be undef or 0 in which case it will always be selected
645 # for the action specified
647 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
648 # pattern) then it will always be forwarded to every node that doesn't have
649 # it (I strongly recommend you don't use this unless you REALLY mean it, if
650 # you allow a new link with this on EVERY bull will be forwarded immediately
651 # on first connection)
657 'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ],
658 'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
659 'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ],
660 'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
661 'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
662 'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
663 'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
664 'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
665 'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
666 'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ],
667 'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
671 Simply insert a bulletin address and state in the brackets where you wish
672 that mail to go. For example, you can see here that mail sent to "UK" will
673 only be sent to the UK links and not to PA4AB-14.
676 To force the cluster to reread the file use load/forward
679 <sect1>The msg command
682 The <em>msg</em> command is a very powerful and flexible tool for the
683 sysop. It allows the sysop to alter to and from fields and make other
684 changes to manage the cluster mail.
686 Here is a full list of the various options ...
689 MSG TO <msgno> <call> - change TO callsign to <call>
690 MSG FRom <msgno> <call> - change FROM callsign to <call>
691 MSG PRrivate <msgno> - set private flag
692 MSG NOPRrivate <msgno> - unset private flag
693 MSG RR <msgno> - set RR flag
694 MSG NORR <msgno> - unset RR flag
695 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
696 MSG NOKEep <msgno> - unset the keep flag
697 MSG SUbject <msgno> <new> - change the subject to <new>
698 MSG WAittime <msgno> - remove any waiting time for this message
699 MSG NOREad <msgno> - mark message as unread
700 MSG REad <msgno> - mark message as read
701 MSG QUeue - queue any outstanding bulletins
702 MSG QUeue 1 - queue any outstanding private messages
705 These commands are simply typed from within the cluster as the sysop user.
707 <sect1>Message status
710 You can check on a message from within the cluster by using the command
711 <em>stat/msg</em>. This will give you additional information on the
712 message number including which nodes have received it, which node it
713 was received from and when etc. Here is an example of the output of
717 G0VGS de GB7MBC 28-Jan-2001 1308Z >
720 Msg Time: 26-Jan-2001 1302Z
724 Subject: AMSAT 2line KEPS 01025.AMSAT
726 Got it Nodes: GB7BAA, GB7ADX
730 G0VGS de GB7MBC 28-Jan-2001 1308Z >
733 <sect1>Filtering mail
736 This is described in the section on <em>Other filters</em> so I will not
739 <sect1>Distribution lists
742 Distribution lists are simply a list of users to send certain types of
743 mail to. An example of this is mail you only wish to send to other
744 sysops. In /spider/msg there is a directory called <em>distro</em>. You
745 put any distibution lists in here. For example, here is a file called
746 SYSOP.pl that caters for the UK sysops.
749 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
750 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
751 GB7DXK GB7DXI GB7DXS)
754 Any mail sent to "sysop" would only be sent to the callsigns in this list.
759 Spider provides a simple BBS interface. No input is required from the sysop
760 of the cluster at all. The BBS simply sets the cluster as a BBS and pushes
761 any required mail to the cluster. No mail can flow from Spider to the BBS,
762 the interface is one-way.
765 Please be careful not to flood the cluster network with unnecessary mail.
766 Make sure you only send mail to the clusters that want it by using the
767 Forward.pl file very carefully.
772 Spider allows the creation of local or remote databases. It supports
773 chained databases, allowing several different databases to be scanned
774 with one simple command. Importing of databases is limited at present
775 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
776 database but will expand with time.
778 <sect1>Creating databases
781 Creating a database could not be more simple. All the commands are
782 sent from the cluster prompt as the <em>sysop</em> user.
784 To create a database you use the command <em>dbcreate</em>. It can
785 be used in 3 different ways like so ..
791 To simply create a database locally, you just tell the command the
792 name of the database. This does not create the actual database, it
793 simply defines it to say that it exists.
796 dbcreate <name> chain <name> [<name>...]
799 This creates a chained database entry. The first database will be
800 scanned, then the second, the third etc...
803 dbcreate <name> remote <name>
806 This creates a remote entry. the first name field is the database
807 name at the remote node, then the remote switch, then the actual
808 node_call of the remote node, for example...
811 dbcreate buckmaster remote gb7dxc
814 Remote databases cannot be chained, however, the last database in a
815 chain can be a remote database.
817 <sect1>Importing databases
820 The only databases that Spider can currently import are the standard
821 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
822 This will be added to with time.
824 To import such a database, first put the file somewhere useful like /tmp
825 and then issue the following command ...
828 dbimport oblast /tmp/OBLAST.FUL
831 This will update the existing local oblast database or create it if
834 <sect1>Checking available databases
837 Once a database is created, you will want to check that it has been
838 added. To do this use the <em>dbavail</em> command. This will
839 output the available databases. For example ...
843 DB Name Location Chain
847 G0VGS de GB7MBC 3-Feb-2001 1925Z >
850 <sect1>Looking up databases
853 To look for information in a defined database, simply use the <em>dbshow</em>
854 command, for example ...
857 dbshow buckmaster G0YLM
860 will show the information for the callsign G0YLM from the buckmaster
861 database if it exists. To make things more standard for the users
862 you can add an entry in the Aliases file so that it looks like a standard
863 <em>show</em> command like this ...
866 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
869 Now you can simply use show/buckmaster or an abreviation.
871 <sect1>Removing databases
874 To delete an existing database you use the <em>dbremove</em> command.
881 would remove the oblast database and its associated datafile from the
882 system. There are no warnings or recovery possible from this command.
883 If you remove a database it ceases to exist and would have to be created
884 from scratch if you still required it.
886 <sect>Information, files and useful programs
891 One of the more important things a cluster sysop needs to do is to get
892 information to his users. The simplest way to do this is to have a banner
893 that is sent to the user on login. This is know as a "message of the day"
894 or "motd". To set this up, simply create a file in /spider/data called motd
895 and edit it to say whatever you want. It is purely a text file and will be
896 sent automatically to anyone logging in to the cluster.
898 <sect1>Downtime message
901 If for any reason the cluster is down, maybe for upgrade or maintenance but
902 the machine is still running, a message can be sent to the user advising them
903 of the fact. This message lives in the /spider/data directory and is called
904 "offline". Simply create the file and edit it to say whatever you wish.
905 This file will be sent to a user attempting to log into the cluster when
906 DXSpider is not actually running.
908 <sect1>Other text messages
911 You can set other text messages to be read by the user if they input the file
912 name. This could be for news items or maybe information for new users.
913 To set this up, make a directory under /spider called <em>packclus</em>.
914 Under this directory you can create files called <em>news</em> or <em>newuser</em>
915 for example. In fact you can create files with any names you like. These can
916 be listed by the user with the command ....
922 They can be read by the user by typing the command ....
928 If the file they want to read is called <em>news</em>. You could also set
929 an alias for this in the Alias file to allow them just to type <em>news</em>
932 You can also store other information in this directory, either directly or
933 nested under directories. One use for this would be to store DX bulletins
934 such as the OPDX bulletins. These can be listed and read by the user.
935 To keep things tidy, make a directory under /spider/packclus called
936 <em>bulletin</em>. Now copy any OPDX or similar bulletins into it. These
937 can be listed by the user in the same way as above using the <em>show/files</em>
938 command with an extension for the bulletin directory you have just created,
946 An example would look like this ....
950 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
953 You can see that in the files area (basically the packclus directory) there is a
954 file called <em>news</em> and a directory called <em>bulletin</em>. You can
955 also see that dates they were created. In the case of the file <em>news</em>,
956 you can also see the time it was last modified, a good clue as to whether the
957 file has been updated since you last read it. To read the file called
958 <em>news</em> you would simply issue the command ....
964 To look what is in the bulletin directory you issue the command ....
968 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
969 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
970 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
971 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
972 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
973 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
974 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
975 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
976 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
977 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
978 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
979 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
980 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
981 Press Enter to continue, A to abort (16 lines) >
984 You can now read any file in this directory using the type command, like this ....
987 type bulletin/opdx391
988 Ohio/Penn DX Bulletin No. 391
989 The Ohio/Penn Dx PacketCluster
993 Editor Tedd Mirgliotta, KB8NW
994 Provided by BARF-80 BBS Cleveland, Ohio
995 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
996 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
997 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
998 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
999 Press Enter to continue, A to abort (508 lines) >
1002 The page length will of course depend on what you have it set to!
1004 <sect1>The Aliases file
1007 You will find a file in /spider/cmd/ called Aliases. First, copy this file to
1008 /spider/local_cmd/Aliases and edit this file. You will see something like this ...
1014 # provide some standard aliases for commands for terminally
1015 # helpless ak1a user (helpless in the sense that they never
1016 # read nor understand help files)
1018 # This file is automagically reloaded if its modification time is
1019 # later than the one stored in CmdAlias.pm
1021 # PLEASE make this file consistant with reality! (the patterns MUST
1022 # match the filenames!)
1024 # Don't alter this file, copy it into the local_cmd tree and modify it.
1025 # This file will be replaced everytime I issue a new release.
1027 # You only need to put aliases in here for commands that don't work as
1028 # you desire naturally, e.g sh/dx on its own just works as you expect
1029 # so you need not add it as an alias.
1037 '^\?', 'apropos', 'apropos',
1040 '^ann.*/full', 'announce full', 'announce',
1041 '^ann.*/sysop', 'announce sysop', 'announce',
1042 '^ann.*/(.*)$', 'announce $1', 'announce',
1049 '^del', 'kill', 'kill',
1050 '^del\w*/fu', 'kill full', 'kill',
1051 '^di\w*/a\w*', 'directory all', 'directory',
1052 '^di\w*/b\w*', 'directory bulletins', 'directory',
1053 '^di\w*/n\w*', 'directory new', 'directory',
1054 '^di\w*/o\w*', 'directory own', 'directory',
1055 '^di\w*/s\w*', 'directory subject', 'directory',
1056 '^di\w*/t\w*', 'directory to', 'directory',
1057 '^di\w*/f\w*', 'directory from', 'directory',
1058 '^di\w*/(\d+)', 'directory $1', 'directory',
1075 '^l$', 'directory', 'directory',
1076 '^ll$', 'directory', 'directory',
1077 '^ll/(\d+)', 'directory $1', 'directory',
1082 '^news', 'type news', 'type',
1092 '^r$', 'read', 'read',
1093 '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
1096 '^s/p$', 'send', 'send',
1097 '^sb$', 'send noprivate', 'send',
1098 '^set/home$', 'set/homenode', 'set/homenode',
1099 '^set/nobe', 'unset/beep', 'unset/beep',
1100 '^set/nohe', 'unset/here', 'unset/here',
1101 '^set/noan', 'unset/announce', 'unset/announce',
1102 '^set/nodx', 'unset/dx', 'unset/dx',
1103 '^set/nota', 'unset/talk', 'unset/talk',
1104 '^set/noww', 'unset/wwv', 'unset/wwv',
1105 '^set/nowx', 'unset/wx', 'unset/wx',
1106 '^sh$', 'show', 'show',
1107 '^sh\w*/buck', 'dbshow buck', 'dbshow',
1108 '^sh\w*/bu', 'show/files bulletins', 'show/files',
1109 '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
1110 '^sh\w*/c$', 'show/configuration', 'show/configuration',
1111 '^sh\w*/com', 'dbavail', 'dbavail',
1112 '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
1113 '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
1114 '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
1115 '^sh\w*/email', 'dbshow email', 'dbshow',
1116 '^sh\w*/hftest', 'dbshow hftest', 'dbshow',
1117 '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
1118 '^sh\w*/qsl', 'dbshow qsl', 'dbshow',
1119 '^sh\w*/tnc', 'who', 'who',
1120 '^sh\w*/up', 'show/cluster', 'show/cluster',
1121 '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
1122 '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
1123 '^sp$', 'send', 'send',
1127 '^ta$', 'talk', 'talk',
1128 '^t$', 'talk', 'talk',
1135 '^wx/full', 'wx full', 'wx',
1136 '^wx/sysop', 'wx sysop', 'wx',
1147 You can create aliases for commands at will. Beware though, these may not
1148 always turn out as you think. Care is needed and you need to test the
1149 results once you have set an alias.
1154 In later versions of Spider a simple console program is provided for the sysop.
1155 This has a type ahead buffer with line editing facilities and colour for spots,
1156 announces etc. To use this program, simply use console.pl instead of client.
1159 To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
1160 file with your favourite editor.
1162 <sect1>Updating kepler data
1165 Spider has a powerful and flexible show/satellite command. In order for
1166 this to be accurate, the kepler data has to be updated regularly. In
1167 general, this data is available as an email or via cluster mail.
1168 Updating it is simple. First you need to export the mail message as a
1169 file. You do this with the <em>export</em> command from the cluster prompt
1170 as the sysop. For example ...
1173 export 5467 /spider/perl/keps.in
1176 would export message number 5467 as a file called keps.in in the
1177 /spider/perl directory.
1179 Now login to a VT as sysop and cd /spider/perl. There is a command in
1180 the perl directory called <em>convkeps.pl</em>. All we need to do now is
1181 convert the file like so ...
1184 ./convkeps.pl keps.in
1187 Now go back to the cluster and issue the command ...
1193 That is it! the kepler data has been updated.
1195 <sect1>The QRZ callbook
1198 The command <em>sh/qrz</em> will only work once you have followed a few
1199 simple steps. First you need to get a user ID and password from qrz.com.
1200 Simply go to the site and create one. Secondly you need to copy the file
1201 /spider/perl/Internet.pm to /spider/local and alter it to match your user
1202 ID and password. You also at this point need to set $allow=1 to complete
1203 the setup. Many thanks to Fred Lloyd, the proprieter of
1204 <htmlurl url="http://www.qrz.com" name="qrz.com"> for allowing this access.
1209 CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held
1210 at <htmlurl url="http://www.sourceforge.net" name="Sourceforge">. This means
1211 that it is possible to update your DXSpider installation to the latest
1212 sources by using a few simple commands.
1215 THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST
1216 INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!!
1217 THIS MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!!
1218 YOU HAVE BEEN WARNED!!!
1221 DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE
1225 I am of course assuming that you have a machine with both DXSpider and
1226 Internet access running.
1229 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
1230 ENTIRE SPIDER TREE!!
1233 Assuming you are connected to the Internet, you need to login to the
1234 CVS repository and then update your Spider source. There are several
1235 steps which are listed below ...
1238 First login as the user <em>sysop</em>. Next you need to connect to the CVS
1239 repository. You do this with the command below ...
1242 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
1245 You will get a password prompt. Simply hit return here and your machine should
1246 return to a normal linux prompt.
1249 What happens next depends on whether you have an existing installation that
1250 you want to update with the latest and greatest or whether you just want
1251 to see what is there and/or run it on a new machine for testing.
1253 If you are installing Spider from CVS then change directory to /home/sysop
1255 If you are wanting to update Spider then cd to /tmp
1258 The next step will create a brand new 'spider' directory in your current
1262 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
1265 This command is all on one line.
1268 Hopefully your screen should show you downloading files. The -z3 simply compresses
1269 the download to improve speed.
1270 When this has finished, you will have exactly the same as if you had untarred a full
1271 tarball PLUS some extra directories and files that CVS needs to do the magic that
1275 Now if you are doing a new installation, that's it. Carry on as if you have
1276 just downloaded and untarred the lastest tarball.
1279 If you want to upgrade your current installation then do this ...
1282 tar cvfz /tmp/s.tgz spider
1284 tar xvfzp /tmp/s.tgz
1287 This is assuming you downloaded to the /tmp directory of course.
1290 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions
1291 correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????
1293 Remember to recompile the C client (cd /spider/src; make)
1296 At this point the files have been upgraded. You can (usually) restart the cluster
1297 in your own time. However, if you attempt to use any new commands or features
1298 expect it to be fatal! At least your cluster will have been restarted then so it
1299 will be too late to worry about it!
1302 Now the magic part! From now on when you want to update, simply connect to the
1303 Internet and then, as the user <em>sysop</em> ...
1310 and your files will be updated. As above, remember to recompile the "C" client
1311 if it has been updated (CVS will tell you) and restart if any of the perl scripts
1312 have been altered or added, again, CVS will tell you.
1315 You will find any changes documented in the /spider/Changes file.
1317 <sect>The DXSpider command set
1320 Below is a complete list of commands available from the cluster prompt.
1321 Most maintenance tasks are automatic but there are some commands that are useful
1322 for a sysop. These are listed below in alphabetical order. The number in
1323 brackets following the command name is the permissions level needed to use
1326 <sect1>accept/announce (0)
1330 <bf>accept/announce [0-9] <pattern></bf> Set an accept filter
1335 Create an 'accept this announce' line for a filter.
1337 An accept filter line means that if the announce matches this filter it is
1338 passed onto the user. See HELP FILTERS for more info. Please read this
1339 to understand how filters work - it will save a lot of grief later on.
1341 You can use any of the following things in this line:-
1344 info <string> eg: iota or qsl
1345 by <prefixes> eg: G,M,2
1347 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1348 origin_itu <numbers>
1349 origin_zone <numbers>
1354 wx 1 filter WX announces
1355 dest <prefixes> eg: 6MUK,WDX (distros)
1362 acc/ann 2 by_zone 14,15,16
1363 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
1372 This filter would only allow announces that were posted buy UK stations.
1373 You can use the tag 'all' to accept everything eg:
1379 but this probably for advanced users...
1381 <sect1>accept/announce (extended for sysops) (8)
1385 <bf>accept/announce <call> [input] [0-9]<pattern></bf> Announce filter sysop version
1389 This version allows a sysop to set a filter for a callsign as well as the
1390 default for nodes and users eg:-
1394 accept/ann input node_default by G,M,2
1395 accept/ann user_default by G,M,2
1398 <sect1>accept/route (8)
1402 <bf>accept/route <call> [0-9] <pattern></bf> Set an 'accept' filter line for routing
1406 Create an 'accept this routing PC Protocol' line for a filter.
1409 An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1410 it is passed thru that interface. See HELP FILTERING for more info. Please read this
1411 to understand how filters work - it will save a lot of grief later on.
1414 You can use any of the following things in this line:-
1417 call <prefixes> the callsign of the thingy
1418 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1421 origin <prefixes> really the interface it came in on
1422 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1423 origin_itu <numbers>
1424 origin_zone <numbers>
1431 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
1432 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
1436 You can use the tag 'all' to accept everything eg:
1442 <sect1>accept/spots (0)
1446 <bf>accept/announce [0-9] <pattern></bf> Set an accept filter
1451 Create an 'accept this spot' line for a filter.
1454 An accept filter line means that if the spot matches this filter it is
1455 passed onto the user. See HELP FILTERS for more info. Please read this
1456 to understand how filters work - it will save a lot of grief later on.
1458 You can use any of the following things in this line:-
1461 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1462 on <range> same as 'freq'
1463 call <prefixes> eg: G,PA,HB9
1464 info <string> eg: iota or qsl
1466 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1477 For frequencies, you can use any of the band names defined in
1478 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1479 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1480 this is more efficient than saying simply: freq HF (but don't get
1481 too hung up about that)
1487 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1490 You can use the tag 'all' to accept everything, eg:
1496 but this probably for advanced users...
1498 <sect1>accept/spots (extended for sysops) (8)
1502 <bf>accept/spots <call> [input] [0-9] <pattern></bf> Spot filter sysop version
1506 This version allows a sysop to set a filter for a callsign as well as the
1507 default for nodes and users eg:-
1510 accept/spot db0sue-7 1 by_zone 14,15,16
1511 accept/spot node_default all
1512 set/hops node_default 10
1514 accept/spot user_default by G,M,2
1517 <sect1>accept/wcy (0)
1521 <bf>accept/wcy [0-9] <pattern></bf> set an accept WCY filter
1525 It is unlikely that you will want to do this, but if you do then you can
1526 filter on the following fields:-
1529 by <prefixes> eg: G,M,2
1531 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1532 origin_itu <numbers>
1533 origin_zone <numbers>
1541 There are no examples because WCY Broadcasts only come from one place and
1542 you either want them or not (see UNSET/WCY if you don't want them).
1544 This command is really provided for future use.
1546 See HELP FILTER for information.
1548 <sect1>accept/wcy (extended for sysops) (8)
1552 <bf>accept/wcy <call> [input] [0-9] <pattern></bf>
1553 WCY filter sysop version
1557 This version allows a sysop to set a filter for a callsign as well as the
1558 default for nodes and users eg:-
1561 accept/wcy node_default all
1562 set/hops node_default 10
1565 <sect1>accept/wwv (0)
1569 <bf>accept/wwv [0-9] <pattern></bf> Set an accept WWV filter
1573 It is unlikely that you will want to do this, but if you do then you can
1574 filter on the following fields:-
1577 by <prefixes> eg: G,M,2
1579 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1580 origin_itu <numbers>
1581 origin_zone <numbers>
1591 accept/wwv by_zone 4
1594 is probably the only useful thing to do (which will only show WWV broadcasts
1595 by stations in the US).
1597 See HELP FILTER for information.
1599 <sect1>accept/wwv (extended for sysops) (8)
1603 <bf>accept/wwv <call> [input] [0-9] <pattern></bf>
1604 WWV filter sysop version
1608 This version allows a sysop to set a filter for a callsign as well as the
1609 default for nodes and users eg:-
1612 accept/wwv db0sue-7 1 by_zone 4
1613 accept/wwv node_default all
1614 set/hops node_default 10
1616 accept/wwv user_default by W,K
1623 <bf>announce <text></bf> Send an announcement to local users
1627 Send an announcement to LOCAL users only, where <text> is the text
1628 of the announcement you wish to broadcast. If you do not wish to receive
1629 announces, use the <em>set/noannounce</em> command. Any announces made by
1630 a sysop will override set/noannounce.
1632 <sect1>announce full (0)
1636 <bf>announce full <text></bf> Send an announcement cluster wide
1640 This command will send your announcement across the whole cluster
1644 <sect1>announce sysop (5)
1648 <bf>announce sysop <text></bf>
1652 Send an announcement to Sysops only
1658 <bf>apropos <string></bf> Search the help database
1662 Search the help database for <string> (it isn't case sensitive),
1663 and print the names of all the commands that may be relevant.
1669 <bf>bye</bf> Exit from the cluster
1673 This will disconnect you from the cluster
1679 <bf>catchup <node_call> All|[<msgno> ...]</bf>
1680 Mark a message as sent
1684 When you send messages the fact that you have forwarded it to another node
1685 is remembered so that it isn't sent again. When you have a new partner
1686 node and you add their callsign to your /spider/msg/forward.pl file, all
1687 outstanding non-private messages will be forwarded to them. This may well
1688 be ALL the non-private messages. You can prevent this by using these
1693 catchup GB7DJK 300 301 302 303 500-510
1696 and to undo what you have just done:-
1699 uncatchup GB7DJK all
1700 uncatchup GB7DJK 300 301 302 303 500-510
1703 which will arrange for them to be forward candidates again.
1705 Order is not important.
1707 <sect1>clear/spots (0)
1711 <bf>clear/spots [1|all]</bf> Clear a spot filter line
1715 This command allows you to clear (remove) a line in a spot filter or to
1716 remove the whole filter.
1718 If you have a filter:-
1722 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1731 you will be left with:-
1734 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1743 the filter will be completely removed.
1750 <bf>connect <callsign></bf> Start a connection to another DX Cluster
1754 Start a connection process that will culminate in a new connection to the
1755 DX cluster <callsign>. This process creates a new 'client' process which will
1756 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
1757 necessary to traverse the network(s) to logon to the cluster <callsign>.
1763 <bf>dbavail</bf> Show a list of all the databases in the system
1767 The title says it all really, this command lists all the databases defined
1768 in the system. It is also aliased to SHOW/COMMAND.
1774 <bf>dbcreate <name></bf> Create a database entry<newline>
1775 <bf>dbcreate <name> chain <name> [<name>..]</bf> Create a
1776 chained database entry<newline>
1777 <bf>dbcreate <name> remote <node></bf> Create a remote database
1782 DBCREATE allows you to define a database in the system. It doesn't actually
1783 create anything, just defines it.
1785 The databases that are created are simple DB_File hash databases, they are
1786 therefore already 'indexed'.
1788 You can define a local database with the first form of the command eg:
1792 You can also chain databases with the addition of the 'chain' keyword.
1793 This will search each database one after the other. A typical example
1796 DBCREATE sdx_qsl chain sql_ad
1798 No checking is done to see if the any of the chained databases exist, in
1799 fact it is usually better to do the above statement first then do each of
1800 the chained databases.
1802 Databases can exist offsite. To define a database that lives on another
1805 DBCREATE buckmaster remote gb7dxc
1807 Remote databases cannot be chained; however, the last database in a
1808 a chain can be a remote database eg:
1810 DBCREATE qsl chain gb7dxc
1812 To see what databases have been defined do:
1814 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
1816 It would be normal for you to add an entry into your local Aliases file
1817 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
1818 need to add a line like:-
1824 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
1834 to work as they may be used to.
1836 See DBIMPORT for the importing of existing AK1A format data to databases.
1837 See DBSHOW for generic database enquiry
1843 <bf>dbimport <dbname></bf> Import AK1A data into a database
1847 If you want to import or update data in bulk to a database you can use
1848 this command. It will either create or update entries into an existing
1849 database. For example:-
1851 DBIMPORT oblast /tmp/OBLAST.FUL
1853 will import the standard OBLAST database that comes with AK1A into the
1854 oblast database held locally.
1860 <bf>dbremove <dbname></bf> Delete a database
1864 DBREMOVE will completely remove a database entry and also delete any data
1865 file that is associated with it.
1867 There is no warning, no comeback, no safety net.
1873 will remove the oblast database from the system and it will also remove
1874 the associated datafile.
1878 There is no warning, no comeback, no safety net.
1880 You have been warned.
1886 <bf>dbshow <dbname> <key></bf> Display an entry, if it exists,
1891 This is the generic user interface to the database to the database system.
1892 It is expected that the sysop will add an entry to the local Aliases file
1893 so that users can use the more familiar AK1A style of enquiry such as:
1899 but if he hasn't and the database really does exist (use DBAVAIL or
1900 SHOW/COMMAND to find out) you can do the same thing with:
1911 <bf>debug</bf> Set the cluster program into debug mode
1915 Executing this command will only have an effect if you are running the cluster
1922 It will interrupt the cluster just after the debug command has finished.
1924 <sect1>directory (0)
1928 <bf>directory</bf> List messages<newline>
1929 <bf>directory all</bf> List all messages<newline>
1930 <bf>directory own</bf> List your own messages<newline>
1931 <bf>directory new</bf> List all new messages<newline>
1932 <bf>directory to <call></bf> List all messages to <call><newline>
1933 <bf>directory from <call></bf> List all messages from <call><newline>
1934 <bf>directory subject <string></bf> List all messages with <string>
1936 <bf>directory <nn></bf> List last <nn> messages<newline>
1937 <bf>directory <from>-<to></bf> List messages <from> message <to> message <newline>
1941 List the messages in the messages directory.
1943 If there is a 'p' one space after the message number then it is a
1944 personal message. If there is a '-' between the message number and the
1945 'p' then this indicates that the message has been read.
1947 You can use shell escape characters such as '*' and '?' in the <call>
1950 You can combine some of the various directory commands together eg:-
1955 DIR SUBJECT IOTA 200-250
1958 You can abbreviate all the commands to one letter and use ak1a syntax:-
1966 <sect1>directory (extended for sysops) (5)
1969 Works just like the user command except that sysops can see ALL messages.
1971 <sect1>disconnect (8)
1975 <bf>disconnect <call> [<call> ...]</bf> Disconnect a user or node
1979 Disconnect any <call> connected locally
1985 <bf>dx [by <call>] <freq> <call> <remarks></bf> Send a DX spot
1989 This is how you send a DX Spot to other users. You can, in fact, now
1990 enter the <freq> and the <call> either way round.
1998 will all give the same result. You can add some remarks to the end
1999 of the command and they will be added to the spot.
2002 DX FR0G 144600 this is a test
2005 You can credit someone else by saying:-
2008 DX by G1TLH FR0G 144.600 he isn't on the cluster
2011 The <freq> is compared against the available bands set up in the
2012 cluster. See SHOW/BANDS for more information.
2018 <bf>export <msgno> <filename></bf> Export a message to a file
2022 Export a message to a file. This command can only be executed on a local
2023 console with a fully privileged user. The file produced will be in a form
2024 ready to be imported back into the cluster by placing it in the import
2025 directory (/spider/msg/import).
2027 This command cannot overwrite an existing file. This is to provide some
2028 measure of security. Any files written will owned by the same user as the
2029 main cluster, otherwise you can put the new files anywhere the cluster can
2030 access. For example:-
2034 <sect1>export_users (9)
2038 <bf>export_users [<filename>]</bf> Export the users database to ascii
2042 Export the users database to a file in ascii format. If no filename
2043 is given then it will export the file to /spider/data/user_asc.
2045 If the file already exists it will be renamed to <filename>.o. In fact
2046 up to 5 generations of the file can be kept each one with an extra 'o' on the
2049 BE WARNED: this will write to any file you have write access to. No check is
2050 made on the filename (if any) that you specify.
2052 <sect1>forward/latlong (8)
2056 <bf>forward/latlong <node_call></bf> Send latitude and longitude
2057 information to another cluster
2061 This command sends all the latitude and longitude information that your
2062 cluster is holding against callsigns. One advantage of recieving this
2063 information is that more locator information is held by you. This
2064 means that more locators are given on the DX line assuming you have
2065 <em>set/dxgrid</em> enabled. This could be a LOT of information though, so
2066 it is not recommended on slow links.
2068 <sect1>forward/opername (1)
2072 <bf>forward/opername <call></bf> Send out information on this <call>
2077 This command sends out any information held in the user file which can
2078 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
2079 and Homenode. PC41s are only sent for the information that is available.
2085 <bf>help <cmd></bf> Get help on a command
2089 All commands can be abbreviated, so SHOW/DX can be abbreviated
2090 to SH/DX, ANNOUNCE can be shortened to AN and so on.
2092 Look at the APROPOS <string> command which will search the help database
2093 for the <string> you specify and give you a list of likely commands
2094 to look at with HELP.
2100 <bf>init <node call></bf> Re-initialise a link to an AK1A compatible node
2104 This command attempts to re-initialise a link to a (usually) AK1A node
2105 that has got confused, usually by a protocol loop of some kind. It may
2106 work - but you usually will be better off simply disconnecting it (or
2107 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
2110 Best of luck - you will need it.
2116 <bf>kill <msgno> [<msgno> ..]</bf> Delete a message
2117 from the local system
2121 Delete a message from the local system. You will only be able to
2122 delete messages that you have originated or been sent (unless you are
2129 <bf>kill <msgno> [<msgno> ...]</bf> Remove or erase a message from
2131 <bf>kill from <call></bf> Remove all messages from a callsign<newline>
2132 <bf>kill to <call></bf> Remove all messages to a callsign<newline>
2136 You can get rid of any message to or originating from your callsign using
2137 this command. You can remove more than one message at a time.
2139 As a sysop you can kill any message on the system.
2141 <sect1>kill full (5)
2145 <bf>kill full <msgno> [<msgno>]</bf> Delete a message from the
2150 Delete a message (usually a 'bulletin') from the whole cluster system.
2152 This uses the subject field, so any messages that have exactly the same subject
2153 will be deleted. Beware!
2159 <bf>links</bf> Show which nodes are physically connected
2163 This is a quick listing that shows which links are connected and
2164 some information about them. See WHO for a list of all connections.
2167 <sect1>load/aliases (9)
2171 <bf>load/aliases</bf> Reload the command alias table
2175 Reload the /spider/cmd/Aliases file after you have editted it. You will need to
2176 do this if you change this file whilst the cluster is running in order for the
2177 changes to take effect.
2180 <sect1>load/baddx (9)
2184 <bf>load/baddx</bf> Reload the bad DX table
2188 Reload the /spider/data/baddx.pl file if you have changed it manually whilst
2189 the cluster is running. This table contains the DX Calls that, if spotted,
2190 will not be passed on. FR0G and TEST are classic examples.
2192 <sect1>load/badmsg (9)
2196 <bf>load/badmsg</bf> Reload the bad message table
2200 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
2201 the cluster is running. This table contains a number of perl regular
2202 expressions which are searched for in the fields targetted of each message.
2203 If any of them match then that message is immediately deleted on receipt.
2205 <sect1>load/badwords (9)
2209 <bf>load/badwords</bf> Reload the badwords file
2213 Reload the /spider/data/badwords file if you have changed it manually whilst
2214 the cluster is running. This file contains a list of words which, if found
2215 on certain text portions of PC protocol, will cause those protocol frames
2216 to be rejected. It will all put out a message if any of these words are
2217 used on the announce, dx and talk commands. The words can be one or
2218 more on a line, lines starting with '#' are ignored.
2220 <sect1>load/bands (9)
2224 <bf>load/bands</bf> Reload the band limits table
2228 Reload the /spider/data/bands.pl file if you have changed it manually whilst
2229 the cluster is running.
2231 <sect1>load/cmd_cache (9)
2235 <bf>load/cmd_cache</bf> Reload the automatic command cache
2239 Normally, if you change a command file in the cmd or local_cmd tree it will
2240 automatially be picked up by the cluster program. Sometimes it can get confused
2241 if you are doing a lot of moving commands about or delete a command in the
2242 local_cmd tree and want to use the normal one again. Execute this command to
2243 reset everything back to the state it was just after a cluster restart.
2245 <sect1>load/forward (9)
2249 <bf>load/forward</bf> Reload the msg forwarding routing table
2252 Reload the /spider/msg/forward.pl file if you have changed it
2253 manually whilst the cluster is running.
2255 <sect1>load/messages (9)
2259 <bf>load/messages</bf> Reload the system messages file
2263 If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne
2264 commands) you can have them take effect during a cluster session by executing this
2265 command. You need to do this if get something like :-
2267 unknown message 'xxxx' in lang 'en'
2269 <sect1>load/prefixes (9)
2273 <bf>load/prefixes</bf> Reload the prefix table
2277 Reload the /spider/data/prefix_data.pl file if you have changed it manually
2278 whilst the cluster is running.
2284 <bf>merge <node> [<no spots>/<no wwv>]</bf> Ask for the
2285 latest spots and WWV
2289 MERGE allows you to bring your spot and wwv database up to date. By default
2290 it will request the last 10 spots and 5 WWVs from the node you select. The
2291 node must be connected locally.
2293 You can request any number of spots or wwv and although they will be appended
2294 to your databases they will not duplicate any that have recently been added
2295 (the last 2 days for spots and last month for WWV data).
2301 <bf>msg <cmd> <msgno> [data ...]</bf> Alter various message
2306 Alter message parameters like To, From, Subject, whether private or bulletin
2307 or return receipt (RR) is required or whether to keep this message from timing
2311 MSG TO <msgno> <call> - change TO callsign to <call>
2312 MSG FRom <msgno> <call> - change FROM callsign to <call>
2313 MSG PRrivate <msgno> - set private flag
2314 MSG NOPRrivate <msgno> - unset private flag
2315 MSG RR <msgno> - set RR flag
2316 MSG NORR <msgno> - unset RR flag
2317 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
2318 MSG NOKEep <msgno> - unset the keep flag
2319 MSG SUbject <msgno> <new> - change the subject to <new>
2320 MSG WAittime <msgno> - remove any waitting time for this message
2321 MSG NOREad <msgno> - mark message as unread
2322 MSG REad <msgno> - mark message as read
2323 MSG QUeue - queue any outstanding bulletins
2324 MSG QUeue 1 - queue any outstanding private messages
2327 You can look at the status of a message by using:-
2329 STAT/MSG <msgno>
2331 This will display more information on the message than DIR does.
2337 <bf>pc <call> <text></bf> Send text (eg PC Protocol) to <call>
2341 Send some arbitrary text to a locally connected callsign. No processing is done on
2342 the text. This command allows you to send PC Protocol to unstick things if problems
2343 arise (messages get stuck etc). eg:-
2345 pc gb7djk PC33^GB7TLH^GB7DJK^400^
2347 You can also use in the same way as a talk command to a connected user but
2348 without any processing, added of "from <blah> to <blah>" or whatever.
2350 pc G1TLH Try doing that properly!!!
2356 <bf>ping <node></bf> Check the link quality between nodes
2360 his command allows you to send a frame to another cluster node on
2361 the network and get a return frame. The time it takes to do this
2362 is a good indication of the quality of the link. The actual time
2363 it takes is output to the console in seconds.
2364 Any visible cluster node can be PINGed.
2371 <bf>rcmd <node call> <cmd></bf> Send a command to another DX cluster
2375 This command allows you to send nearly any command to another DX Cluster
2376 node that is connected to the system.
2378 Whether you get any output is dependant on a) whether the other system knows
2379 that the node callsign of this cluster is in fact a node b) whether the
2380 other system is allowing RCMDs from this node and c) whether you have
2381 permission to send this command at all.
2387 <bf>read</bf> Read the next unread personal message addressed to you<newline>
2388 <bf>read <msgno></bf> Read the specified message<newline>
2392 You can read any messages that are sent as 'non-personal' and also any
2393 message either sent by or sent to your callsign.
2396 <sect1>read (extended for sysops) (5)
2400 <bf>read <msgno></bf> Read a message on the system
2404 As a sysop you may read any message on the system
2406 <sect1>reject/announce
2410 <bf>reject/announce [0-9] <pattern></bf> Set a reject filter
2415 Create an 'reject this announce' line for a filter.
2417 An reject filter line means that if the announce matches this filter it is
2418 passed onto the user. See HELP FILTERS for more info. Please read this
2419 to understand how filters work - it will save a lot of grief later on.
2421 You can use any of the following things in this line:-
2424 info <string> eg: iota or qsl
2425 by <prefixes> eg: G,M,2
2427 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2428 origin_itu <numbers>
2429 origin_zone <numbers>
2434 wx 1 filter WX announces
2435 dest <prefixes> eg: 6MUK,WDX (distros)
2441 rej/ann by_zone 14,15,16 and not by G,M,2
2444 You can use the tag 'all' to reject everything eg:
2450 but this probably for advanced users...
2452 <sect1>reject/announce (extended for sysops) (8)
2456 <bf>reject/announce <call> [input] [0-9] <pattern></bf> Announce filter sysop version
2460 This version allows a sysop to set a filter for a callsign as well as the
2461 default for nodes and users eg:-
2465 reject/ann input node_default by G,M,2
2466 reject/ann user_default by G,M,2
2469 <sect1>reject/route (8)
2473 <bf>reject/route <call> [0-9] <pattern></bf> Set an 'reject' filter line for routing
2477 Create an 'reject this routing PC Protocol' line for a filter.
2480 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
2481 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
2482 read this to understand how filters work - it will save a lot of grief later on.
2483 You can use any of the following things in this line:-
2486 call <prefixes> the callsign of the thingy
2487 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2490 origin <prefixes> really the interface it came in on
2491 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2492 origin_itu <numbers>
2493 origin_zone <numbers>
2500 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
2504 You can use the tag 'all' to reject everything eg:
2507 rej/route all (equiv to [very] restricted mode)
2510 <sect1>reject/spots (0)
2514 <bf>reject/spots [0-9] <pattern></bf> Set a reject filter
2519 Create a 'reject this spot' line for a filter.
2521 A reject filter line means that if the spot matches this filter it is
2522 dumped (not passed on). See HELP FILTERS for more info. Please read this
2523 to understand how filters work - it will save a lot of grief later on.
2525 You can use any of the following things in this line:-
2528 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
2529 on <range> same as 'freq'
2530 call <prefixes> eg: G,PA,HB9
2531 info <string> eg: iota or qsl
2533 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2543 For frequencies, you can use any of the band names defined in
2544 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
2545 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
2546 this is more efficient than saying simply: on HF (but don't get
2547 too hung up about that)
2553 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
2556 You can use the tag 'all' to reject everything eg:
2562 but this probably for advanced users...
2564 <sect1>reject/spots (extended for sysops) (8)
2568 <bf>reject/spots <call> [input] [0-9] <pattern></bf>
2569 Reject spot filter sysop version
2573 This version allows a sysop to set a filter for a callsign as well as the
2574 default for nodes and users eg:-
2577 reject/spot db0sue-7 1 by_zone 14,15,16
2578 reject/spot node_default all
2579 set/hops node_default 10
2581 reject/spot user_default by G,M,2
2584 <sect1>reject/wcy (0)
2588 <bf>reject/wcy [0-9] <pattern></bf> Set a reject WCY filter
2592 It is unlikely that you will want to do this, but if you do then you can
2593 filter on the following fields:-
2596 by <prefixes> eg: G,M,2
2598 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2599 origin_itu <numbers>
2600 origin_zone <numbers>
2607 There are no examples because WCY Broadcasts only come from one place and
2608 you either want them or not (see UNSET/WCY if you don't want them).
2610 This command is really provided for future use.
2612 See HELP FILTER for information.
2614 <sect1>reject/wcy (extended for sysops) (8)
2618 <bf>reject/wcy <call> [input] [0-9] <pattern></bf>
2619 WCY reject filter sysop version
2623 This version allows a sysop to set a filter for a callsign as well as the
2624 default for nodes and users eg:-
2626 reject/wcy gb7djk all
2628 <sect1>reject/wwv (0)
2632 <bf>reject/wwv [0-9] <pattern></bf> Set a reject WWV filter
2636 It is unlikely that you will want to do this, but if you do then you can
2637 filter on the following fields:-
2640 by <prefixes> eg: G,M,2
2642 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2643 origin_itu <numbers>
2644 origin_zone <numbers>
2654 reject/wwv by_zone 14,15,16
2657 is probably the only useful thing to do (which will only show WWV broadcasts
2658 by stations in the US).
2660 See HELP FILTER for information.
2662 <sect1>reject/wwv (extended for sysops) (8)
2666 <bf>reject/wwv <call> [input] [0-9] <pattern></bf>
2667 WWV reject filter sysop version
2670 <P>This version allows a sysop to set a filter for a callsign as well as the
2671 default for nodes and users eg:-
2674 reject/wwv db0sue-7 1 by_zone 4
2675 reject/wwv node_default all
2677 reject/wwv user_default by W
2684 <bf>reply</bf> Reply (privately) to the last message that you have read<newline>
2685 <bf>reply <msgno></bf> Reply (privately) to the specified message<newline>
2686 <bf>reply B <msgno></bf> Reply as a Bulletin to the specified message<newline>
2687 <bf>reply NOPrivate <msgno></bf> Reply as a Bulletin to the specified
2689 <bf>reply RR <msgno></bf> Reply to the specified message with read
2694 You can reply to a message and the subject will automatically have
2695 "Re:" inserted in front of it, if it isn't already present.
2697 You can also use all the extra qualifiers such as RR, PRIVATE,
2698 NOPRIVATE, B that you can use with the SEND command (see SEND
2699 for further details)
2705 <bf>send <call> [<call> ...]</bf> Send a message to
2706 one or more callsigns<newline>
2707 <bf>send RR <call></bf> Send a message and ask for a read receipt<newline>
2708 <bf>send COPY <msgno> <call></bf> Send a copy of a message
2710 <bf>send PRIVATE <call></bf> Send a personal message<newline>
2711 <bf>send NOPRIVATE <call></bf> Send a message to all stations<newline>
2715 All the SEND commands will create a message which will be sent either to
2716 an individual callsign or to one of the 'bulletin' addresses.
2718 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
2719 it will mark the message as personal and send it to the cluster node that
2720 that callsign is connected to.
2722 You can have more than one callsign in all of the SEND commands.
2724 You can have multiple qualifiers so that you can have for example:-
2727 SEND RR COPY 123 PRIVATE G1TLH G0RDI
2730 which should send a copy of message 123 to G1TLH and G0RDI and you will
2731 receive a read receipt when they have read the message.
2733 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
2734 SP is an alias for SEND PRIVATE
2736 <sect1>set/address (0)
2740 <bf>set/address <your_address></bf> Record your postal address
2744 Literally, record your address details on the cluster.
2746 <sect1>set/announce (0)
2750 <bf>set/announce</bf> Allow announce messages
2754 Allow announce messages to arrive at your terminal.
2756 <sect1>set/arcluster (5)
2760 <bf>set/arcluster <node_call> [<node_call> ...]</bf> Make
2761 the node_call an AR-Cluster type node
2765 Set the node_call as an AR-Cluster type node
2767 <sect1>set/baddx (8)
2771 <bf>set/baddx <call></bf> Stop words we do not wish to see in the callsign field
2772 of a dx spot being propagated
2776 Setting a word as 'baddx' will prevent spots with that word in the callsign
2777 field of a DX spot from going any further. They will not be displayed and they
2778 will not be sent onto other nodes.
2780 The word must be wriiten in full, no wild cards are allowed eg:-
2783 set/baddx FORSALE VIDEO FR0G
2786 To allow a word again, use the following command ...
2792 <sect1>set/badnode (6)
2796 <bf>set/badnode <node_call></bf> Stop spots from this node_call
2801 Setting a callsign as a 'badnode' will prevent spots from that node
2802 going any further. They will not be displayed and they will not be
2803 sent onto other nodes.
2805 The call can be a full or partial call (or a prefix), eg:-
2811 will stop anything from K1TTT (including any SSID's)
2817 will allow spots from him again.
2819 Use with extreme care. This command may well be superceded by FILTERing.
2821 <sect1>set/badspotter (8)
2825 <bf>set/badspotter <call></bf> Stop spots from this callsign being propagated
2829 Setting a callsign as a 'badspotter' will prevent spots from this callsign
2830 going any further. They will not be displayed and they will not be
2831 sent onto other nodes.
2833 The call must be written in full, no wild cards are allowed eg:-
2836 set/badspotter VE2STN
2839 will stop anything from VE2STN. If you want SSIDs as well then you must
2840 enter them specifically.
2843 unset/badspotter VE2STN
2846 will allow spots from him again.
2848 Use with extreme care. This command may well be superceded by FILTERing.
2854 <bf>set/beep</bf> Add beeps to terminal messages
2858 Add a beep to DX and other terminal messages.
2864 <bf>set/bbs <call> [<call>..]</bf>Make <call> a BBS
2871 <bf>set/clx <node_call> [<node_call> ...]</bf> Make
2872 the node_call a CLX type node
2876 Set the node_call as a CLX type node
2878 <sect1>set/debug (9)
2882 <bf>set/debug <name></bf> Add a debug level to the debug set
2886 You can choose to log several different levels. The levels are
2894 You can show what levels you are logging with the <em>show/debug</em>
2897 You can remove a debug level with unset/debug <name>
2903 <bf>set/dx</bf>Allow DX messages to arrive at your terminal
2907 You can stop DX messages with the <em>unset/dx</em> command
2909 <sect1>set/dxgrid (0)
2913 <bf>set/dxgrid</bf>Allow grid squares on the end of DX messages
2917 Some logging programs do not like the additional information at
2918 the end of a DX spot. If this is the case, use the <em>unset/dxgrid</em>
2919 command to remove the grid squares.
2921 <sect1>set/dxnet (5)
2925 <bf>set/dxnet <node_call> [<node_call> ...]</bf> Make
2926 the node_call a DXNet type node
2930 Set the node_call as a DXNet type node
2936 <bf>set/echo</bf> Make the cluster echo your input
2940 If you are connected via a telnet session, different implimentations
2941 of telnet handle echo differently depending on whether you are
2942 connected via port 23 or some other port. You can use this command
2943 to change the setting appropriately.
2945 You can remove the echo with the <em>unset/echo</em> command
2947 The setting is stored in your user profile.
2949 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
2955 <bf>set/here</bf> Set the here flag
2959 Let others on the cluster know you are here by only displaying your
2960 callsign. If you are away from your terminal you can use the <em>unset/here</em>
2961 command to let people know you are away. This simply puts brackets
2962 around your callsign to indicate you are not available.
2964 <sect1>set/homenode (0)
2968 <bf>set/homenode <node_call></bf> Set your home cluster
2972 Tell the cluster system where you normally connect to. Any Messages sent
2973 to you will normally find their way there should you not be connected.
2984 <bf>set/hops <node_call> ann|spots|wwv|wcy <n></bf>
2989 Set the hop count for a particular type of broadcast for a node.
2991 This command allows you to set up special hop counts for a node
2992 for currently: announce, spots, wwv and wcy broadcasts.
2996 set/hops gb7djk ann 10
2997 set/hops gb7mbc spots 20
3000 Set SHOW/HOPS for information on what is already set. This command
3001 creates a filter and works in conjunction with the filter system.
3003 <sect1>set/isolate (9)
3007 <bf>set/isolate <node call></bf> Isolate a node from the rest of the network
3011 Connect a node to your system in such a way that you are a full protocol
3012 member of its network and can see all spots on it, but nothing either leaks
3013 out from it nor goes back into from the rest of the nodes connected to you.
3015 You can potentially connect several nodes in this way.
3017 You can see which nodes are isolated with the show/isolate (1) command.
3019 You can remove the isolation with the command unset/isolate.
3021 <sect1>set/language (0)
3025 <bf>set/language <language></bf> Set the language you wish to use
3029 You can select the language that you want the cluster to use. Currently
3030 the languages available are <em>en</em> (English) and <em>nl</em> (Dutch).
3032 <sect1>set/location (0)
3036 <bf>set/location <lat and long></bf> Set your latitude and longitude
3040 You can set your latitude and longitude manually or alternatively use the
3041 <em>set/qra</em> command which will do the conversion for you.
3044 set/location 54 04 N 2 02 E
3048 <sect1>set/sys_location (9)
3052 <bf>set/sys_location <lat & long></bf> Set your cluster latitude and longitude
3056 In order to get accurate headings and such like you must tell the system
3057 what your latitude and longitude is. If you have not yet done a SET/QRA
3058 then this command will set your QRA locator for you. For example:-
3061 SET/LOCATION 52 22 N 0 57 E
3064 <sect1>set/logininfo (0)
3068 <bf>set/logininfo</bf> Show logins and logouts of nodes and users
3072 Show users and nodes when they log in and out of the local cluster. You
3073 can stop these messages by using the <em>unset/logininfo</em> command.
3076 <sect1>set/lockout (9)
3080 <bf>set/lockout <call></bf> Stop a callsign connecting to the cluster
3084 You can show who is locked out with the <em>show/lockout</em> command.
3085 To allow the user to connect again, use the <em>unset/lockout</em> command.
3091 <bf>set/name <your_name></bf> Set your name
3095 Tell the cluster what your name is, eg:-
3105 <bf>set/node <call> [<call> ...]</bf> Make the callsign an AK1A cluster
3109 Tell the system that the call(s) are to be treated as AK1A cluster and
3110 fed PC Protocol rather normal user commands.
3112 From version 1.41 you can also set the following types of cluster
3121 To see what your nodes are set to, use the <em>show/nodes</em> command.
3123 <sect1>set/obscount (9)
3127 <bf>set/obscount <count> <node call></bf> Set the 'pump-up'
3128 obsolescence counter
3132 From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see
3133 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
3134 counter which is decremented on every outgoing ping and then reset to
3135 the 'obscount' value on every incoming ping. The default value of this
3138 What this means is that a neighbouring node will be pinged twice at
3139 (default) 300 second intervals and if no reply has been heard just before
3140 what would be the third attempt, that node is disconnected.
3142 If a ping is heard then the obscount is reset to the full value. Using
3143 default values, if a node has not responded to a ping within 15 minutes,
3150 <bf>set/page <n></bf> Set the number of lines per page
3154 Tell the system how many lines you wish on a page when the number of lines
3155 of output from a command is more than this. The default is 20. Setting it
3156 explicitly to 0 will disable paging.
3163 The setting is stored in your user profile.
3166 <sect1>set/password (9)
3170 <bf>set/password <callsign> <string></bf> Set a users password
3174 The password for a user can only be set by a full sysop. The string
3175 can contain any characters but any spaces are removed (you can type in
3176 spaces - but they won't appear in the password). You can see the
3177 result with STAT/USER. The password is the usual 30 character baycom
3180 <sect1>set/pinginterval (9)
3184 <bf>set/pinginterval <time> <node call></bf> Set the ping time
3185 to neighbouring nodes
3189 As from version 1.35 all neighbouring nodes are pinged at regular intervals
3190 in order to determine the rolling quality of the link and, in future, to
3191 affect routing decisions. The default interval is 300 secs or 5 minutes.
3193 You can use this command to set a different interval. Please don't.
3195 But if you do the value you enter is treated as minutes up 60 and seconds
3196 for numbers greater than that.
3198 This is used also to help determine when a link is down at the far end
3199 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
3200 for more information.
3202 <sect1>set/privilege (9)
3206 <bf>set/privilege <n> <call> [<call> ...]</bf> Set the
3207 privilege level on a call
3211 Set the privilege level on a callsign. The privilege levels that pertain
3212 to commands are as default:-
3216 1 - allow remote nodes normal user RCMDs
3217 5 - various privileged commands (including shutdown, but not disc-
3218 connect), the normal level for another node.
3219 8 - more privileged commands (including disconnect)
3220 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
3224 If you are a sysop and you come in as a normal user on a remote connection
3225 your privilege will automatically be set to 0.
3227 <sect1>set/spider (5)
3231 <bf>set/spider <node_call> [<node_call> ...]</bf> Make
3232 the node_call a DXSpider type node
3236 Set the node_call as a DXSpider type node
3238 <sect1>set/sys_qra (9)
3242 <bf>set/sys_qra <locator></bf> Set your cluster QRA locator
3249 <bf>set/qra <locator></bf> Set your QRA locator
3253 Tell the system what your QRA (or Maidenhead) locator is. If you have not
3254 done a SET/LOCATION then your latitude and longitude will be set roughly
3255 correctly (assuming your locator is correct ;-). For example:-
3265 <bf>set/qth <your QTH></bf> Set your QTH
3269 Tell the system where your are. For example:-
3272 set/qth East Dereham, Norfolk
3279 <bf>set/talk</bf> Allow talk messages to be seen at your console
3283 Allow talk messages to arrive at your console. You can switch off
3284 talks with the <em>unset/talk</em> command.
3290 <bf>set/wcy</bf> Allow WCY messages to be seen at your console
3294 Allow WCY information to be seen at your console. You can switch off
3295 WCY messages with the <em>unset/wcy</em> command.
3301 <bf>set/wwv</bf> Allow WWV messages to be seen at your console
3305 Allow WWV information to be seen at your console. You can switch off
3306 WWV messages with the <em>unset/wwv</em> command.
3312 <bf>set/wx</bf> Allow WX messages to be seen at your console
3316 Allow WX information to be seen at your console. You can switch off
3317 WX messages with the <em>unset/wx</em> command.
3319 <sect1>show/baddx (1)
3323 <bf>show/baddx</bf>Show all the bad dx calls in the system
3327 Display all the bad dx callsigns in the system, see SET/BADDX
3328 for more information.
3330 <sect1>show/badnode (6)
3334 <bf>show/badnode</bf> Show all the bad nodes in the system
3338 Display all the bad node callsigns in the system, see SET/BADNODE
3339 for more information.
3341 <sect1>show/badspotter (1)
3345 <bf>show/badspotter</bf> Show all the bad spotters in the system
3349 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
3350 for more information.
3352 <sect1>show/configuration (0)
3356 <bf>show/configuration [<node>]</bf> Show all visible nodes and their users
3360 This command allows you to see all the users that can be seen
3361 and the nodes to which they are connected. With the optional <em>node</em>,
3362 you can specify a particular node to look at.
3364 This command is normally abbreviated to: sh/c
3366 BE WARNED: the list that is returned can be VERY long
3368 <sect1>show/configuration/node (0)
3372 <bf>show/configuration/node</bf> Show all the nodes connected
3376 Show all the nodes connected locally and the nodes they have connected.
3378 <sect1>show/connect (1)
3382 <bf>show/connect</bf> Show all the active connections
3386 This command shows information on all the active connections known to
3387 the node. This command gives slightly more information than WHO.
3389 <sect1>show/date (0)
3393 <bf>show/date [<prefix>|<callsign>]</bf> Show
3398 This is very nearly the same as SHOW/TIME, the only difference the format
3399 of the date string if no arguments are given.
3401 If no prefixes or callsigns are given then this command returns the local
3402 time and UTC as the computer has it right now. If you give some prefixes
3403 then it will show UTC and UTC + the local offset (not including DST) at
3404 the prefixes or callsigns that you specify.
3406 <sect1>show/debug (9)
3410 <bf>show/debug</bf> Show what levels of debug you are logging
3414 The levels can be set with <em>set/debug</em>
3420 <bf>show/dx [options]</bf> interrogate the spot database
3424 If you just type SHOW/DX you will get the last so many spots
3425 (sysop configurable, but usually 10).
3427 In addition you can add any number of these options in very nearly
3428 any order to the basic SHOW/DX command, they are:-
3431 on <band> - eg 160m 20m 2m 23cm 6mm
3432 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
3434 <number> - the number of spots you want
3435 <from>-<to> - <from> spot no <to> spot no in
3438 <prefix> - for a spotted callsign beginning with <prefix>
3439 *<suffix> - for a spotted callsign ending in <suffix>
3440 *<string>* - for a spotted callsign containing <string>
3442 day <number> - starting <number> days ago
3443 day <from>-<to> - <from> days <to> days ago
3445 info <text> - any spots containing <text> in the info or remarks
3447 by <call> - any spots spotted by <call> (spotter <call>
3450 qsl - this automatically looks for any qsl info on the call
3451 held in the spot database.
3453 iota [<iota>] - If the iota island number is missing it will
3454 look for the string iota and anything which looks like
3455 an iota island number. If you specify then it will look
3458 qra [<locator>] - this will look for the specific locator if
3459 you specify one or else anything that looks like a locator.
3466 SH/DX on 20m info iota
3467 SH/DX 9a on vhf day 30
3474 <sect1>show/dxcc (0)
3478 <bf>show/dxcc <prefix></bf> Interrogate the spot database by country
3482 This command takes the <prefix> (which can be a full or partial
3483 callsign if desired), looks up which internal country number it is
3484 and then displays all the spots as per SH/DX for that country.
3486 The options for SHOW/DX also apply to this command.
3491 SH/DXCC W on 20m info iota
3494 <sect1>show/files (0)
3498 <bf>show/files [<filearea> [<string>]]</bf> List
3499 the contents of a filearea
3503 SHOW/FILES on its own will show you a list of the various fileareas
3504 available on the system. To see the contents of a particular file
3508 SH/FILES <filearea>
3511 where <filearea> is the name of the filearea you want to see the
3514 You can also use shell globbing characters like '*' and '?' in a
3515 string to see a selection of files in a filearea eg:-
3518 SH/FILES bulletins arld*
3521 See also TYPE - to see the contents of a file.
3523 <sect1>show/filter (0)
3527 <bf>show/filter</bf> Show the filters you have set
3531 Show the contents of all the filters that are set by you. This command
3532 displays all the filters set - for all the various categories.
3534 <sect1>show/filter (extended for sysops) (5)
3538 <bf>show/filter <callsign></bf> Show the filters set by <callsign>
3542 A sysop can look at any filters that have been set.
3544 <sect1>show/hops (8)
3548 <bf>show/hops <node_call> [ann|spots|wcy|wwv|]</bf> Show the hop
3553 This command shows the hop counts set up for a node. You can specify
3554 which category you want to see. If you leave the category out then
3555 all the categories will be listed.
3557 <sect1>show/isolate (1)
3561 <bf>show/isolate</bf> Show a list of isolated nodes
3565 Show which nodes are currently set to be isolated.
3567 <sect1>show/lockout (9)
3571 <bf>show/lockout</bf> Show a list of excluded callsigns
3575 Show a list of callsigns that have been excluded (locked out) of the
3576 cluster locally with the <em>set/lockout</em> command
3582 <bf>show/log [<callsign>]</bf> Show excerpts from the system log
3586 This command outputs a short section of the system log. On its own
3587 it will output a general logfile. With the optional callsign it will
3588 show output from the log associated with that callsign.
3590 <sect1>show/moon (0)
3594 <bf>show/moon [<prefix>|<callsign>]</bf> Show moon
3599 Show the Moon rise and set times for a (list of) prefixes or callsigns,
3600 together with the azimuth and elevation of the sun currently at those
3603 If you don't specify any prefixes or callsigns, it will show the times for
3604 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
3605 together with the current azimuth and elevation.
3607 In addition, it will show the gain or loss dB relative to the nominal
3608 distance of 385,000Km due to the ellipsoidal nature of the orbit.
3610 If all else fails it will show the Moonrise and set times for the node
3611 that you are connected to.
3624 <bf>show/muf <prefix> [<hours>][long]</bf> Show
3625 the likely propagation to <prefix>
3629 This command allow you to estimate the likelihood of you contacting
3630 a station with the prefix you have specified. The output assumes a modest
3631 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
3633 The result predicts the most likely operating frequencies and signal
3634 levels for high frequency (shortwave) radio propagation paths on
3635 specified days of the year and hours of the day. It is most useful for
3636 paths between 250 km and 6000 km, but can be used with reduced accuracy
3637 for paths shorter or longer than this.
3639 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
3640 used to predict the MUF given the predicted flux, day of the year,
3641 hour of the day and geographic coordinates of the transmitter and
3642 receiver. This routine is reasonably accurate for the purposes here,
3643 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
3644 than the programs used by major shortwave broadcasting organizations,
3645 such as the Voice of America.
3647 The command will display some header information detailing its
3648 assumptions, together with the locations, latitude and longitudes and
3649 bearings. It will then show UTC (UT), local time at the other end
3650 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
3651 (Zen) and the likely signal strengths. Then for each frequency for which
3652 the system thinks there is a likelihood of a circuit it prints a value.
3654 The value is currently a likely S meter reading based on the conventional
3655 6dB / S point scale. If the value has a '+' appended it means that it is
3656 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
3657 there is likely to be much fading and by an 's' that the signal is likely
3660 By default SHOW/MUF will show the next two hours worth of data. You
3661 can specify anything up to 24 hours worth of data by appending the no of
3662 hours required after the prefix. For example:-
3671 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
3672 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
3673 Location Lat / Long Azim
3674 East Dereham, Norfolk 52 41 N 0 57 E 47
3675 United-States-W 43 0 N 87 54 W 299
3676 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
3677 18 23 11.5 -35 mS0+ mS2 S3
3678 19 0 11.2 -41 mS0+ mS2 S3
3681 indicating that you will have weak, fading circuits on top band and
3682 80m but usable signals on 40m (about S3).
3690 will get you the above display, but with the next 24 hours worth of
3698 Gives you an estimate of the long path propagation characterics. It
3699 should be noted that the figures will probably not be very useful, nor
3700 terrible accurate, but it is included for completeness.
3702 <sect1>show/node (1)
3706 <bf>show/node [<node_call> ...]</bf> Show the type and version
3711 Show the type and version (if connected) of the nodes specified on the
3712 command line. If no callsigns are specified then a sorted list of all
3713 the non-user callsigns known to the system will be displayed.
3715 <sect1>show/prefix (0)
3719 <bf>show/prefix <callsign></bf> Interrogate the prefix database
3723 This command takes the <callsign> (which can be a full or partial
3724 callsign or a prefix), looks up which internal country number
3725 it is and then displays all the relevant prefixes for that country
3726 together with the internal country no, the CQ and ITU regions.
3731 <sect1>show/program (5)
3735 <bf>show/program</bf> Show the locations of all the included program modules
3739 Show the name and location where every program module was load from. This
3740 is useful for checking where you think you have loaded a .pm file from.
3746 <bf>show/qra <locator> [<locator>]</bf> Show the distance
3747 between locators<newline>
3748 <bf>show/qra <lat> <long></bf> Convert latitude and longitude to
3753 This is a multipurpose command that allows you either to calculate the
3754 distance and bearing between two locators or (if only one locator is
3755 given on the command line) the distance and beraing from your station
3756 to the locator. For example:-
3763 The first example will show the distance and bearing to the locator from
3764 yourself, the second example will calculate the distance and bearing from
3765 the first locator to the second. You can use 4 or 6 character locators.
3767 It is also possible to convert a latitude and longitude to a locator by
3768 using this command with a latitude and longitude as an argument, for
3772 SH/QRA 52 41 N 0 58 E
3779 <bf>show/qrz <callsign></bf> Show any callbook details on a callsign
3783 This command queries the QRZ callbook server on the internet
3784 and returns any information available for that callsign. This service
3785 is provided for users of this software by http://www.qrz.com
3787 <sect1>show/route (0)
3791 <bf>show/route <callsign></bf> Show the route to <callsign>
3795 This command allows you to see to which node the callsigns specified are
3796 connected. It is a sort of inverse sh/config.
3802 <sect1>show/satellite (0)
3806 <bf>show/satellite <name> [<hours> <interval>]</bf>
3807 Show satellite tracking data
3811 Show the tracking data from your location to the satellite of your choice
3812 from now on for the next few hours.
3814 If you use this command without a satellite name it will display a list
3815 of all the satellites known currently to the system.
3817 If you give a name then you can obtain tracking data of all the passes
3818 that start and finish 5 degrees below the horizon. As default it will
3819 give information for the next three hours for every five minute period.
3821 You can alter the number of hours and the step size, within certain
3824 Each pass in a period is separated with a row of '-----' characters
3830 SH/SAT FENGYUN1 12 2
3837 <bf>show/sun [<prefix>|<callsign>]</bf> Show
3838 sun rise and set times
3842 Show the sun rise and set times for a (list of) prefixes or callsigns,
3843 together with the azimuth and elevation of the sun currently at those
3846 If you don't specify any prefixes or callsigns, it will show the times for
3847 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
3848 together with the current azimuth and elevation.
3850 If all else fails it will show the sunrise and set times for the node
3851 that you are connected to.
3857 SH/SUN G1TLH K9CW ZS
3860 <sect1>show/time (0)
3864 <bf>show/time [<prefix>|<callsign>]</bf> Show
3869 If no prefixes or callsigns are given then this command returns the local
3870 time and UTC as the computer has it right now. If you give some prefixes
3871 then it will show UTC and UTC + the local offset (not including DST) at
3872 the prefixes or callsigns that you specify.
3878 <bf>show/wcy</bf> Show the last 10 WCY broadcasts<newline>
3879 <bf>show/wcy <n></bf> Show the last <n> WCY broadcasts
3883 Display the most recent WCY information that has been received by the system
3889 <bf>show/wwv</bf> Show the last 10 WWV broadcasts<newline>
3890 <bf>show/wwv <n></bf> Show the last <n> WWV broadcasts
3894 Display the most recent WWV information that has been received by the system
3901 <bf>shutdown</bf> Shutdown the cluster
3905 Shutdown the cluster and disconnect all the users. If you have Spider
3906 set to respawn in /etc/inittab it will of course restart.
3912 <bf>spoof <callsign> <command></bf> Run commands as another user
3916 This is a very simple yet powerful command for the sysop. It allows you to
3917 issue commands as if you were a different user. This is very useful for the
3918 kind of things that users seem to always get wrong.. like home_node for
3925 <bf>stat/db <dbname></bf> Show the status of a database
3929 Show the internal status of a database descriptor.
3931 Depending on your privilege level you will see more or less information.
3932 This command is unlikely to be of much use to anyone other than a sysop.
3934 <sect1>stat/channel (5)
3938 <bf>stat/channel <callsign></bf> Show the status of a channel on the cluster
3942 Show the internal status of the channel object either for the channel that
3943 you are on or else for the callsign that you asked for.
3945 Only the fields that are defined (in perl term) will be displayed.
3951 <bf>stat/msg <msgno></bf> Show the status of a message
3955 This command shows the internal status of a message and includes information
3956 such as to whom it has been forwarded, its size, origin etc etc.
3959 If no message number is given then the status of the message system is
3962 <sect1>stat/route_node (5)
3966 <bf>stat/route_node <callsign></bf> Show the data in a Route::Node object
3969 <sect1>stat/route_user (5)
3973 <bf>stat/route_user <callsign></bf> Show the data in a Route::User object
3976 <sect1>stat/user (5)
3980 <bf>stat/user <callsign></bf> Show the full status of a user
3984 Shows the full contents of a user record including all the secret flags
3987 Only the fields that are defined (in perl term) will be displayed.
3993 <bf>sysop</bf> Regain your privileges if you login remotely
3997 The system automatically reduces your privilege level to that of a
3998 normal user if you login in remotely. This command allows you to
3999 regain your normal privilege level. It uses the normal system: five
4000 numbers are returned that are indexes into the character array that is
4001 your assigned password (see SET/PASSWORD). The indexes start from
4004 You are expected to return a string which contains the characters
4005 required in the correct order. You may intersperse those characters
4006 with others to obscure your reply for any watchers. For example (and
4007 these values are for explanation :-):
4010 password = 012345678901234567890123456789
4018 aa2bbbb0ccc5ddd7xxx3n
4023 They will all match. If there is no password you will still be offered
4024 numbers but nothing will happen when you input a string. Any match is
4031 <bf>talk <callsign></bf> Enter talk mode with <callsign><newline>
4032 <bf>talk <callsign> <text></bf> Send a text message to <callsign><newline>
4033 <bf>talk <callsign> > <node_call> [<text>]</bf>
4034 Send a text message to <callsign> via <node_call>
4038 Send a short message to any other station that is visible on the cluster
4039 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
4040 command, they don't have to be connected locally.
4042 The second form of TALK is used when other cluster nodes are connected
4043 with restricted information. This usually means that they don't send
4044 the user information usually associated with logging on and off the cluster.
4046 If you know that G3JNB is likely to be present on GB7TLH, but you can only
4047 see GB7TLH in the SH/C list but with no users, then you would use the
4048 second form of the talk message.
4050 If you want to have a ragchew with someone you can leave the text message
4051 out and the system will go into 'Talk' mode. What this means is that a
4052 short message is sent to the recipient telling them that you are in a 'Talking'
4053 frame of mind and then you just type - everything you send will go to the
4054 station that you asked for.
4056 All the usual announcements, spots and so on will still come out on your
4059 If you want to do something (such as send a spot) you precede the normal
4060 command with a '/' character, eg:-
4063 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
4067 To leave talk mode type:
4077 <bf>type <filearea>/<name></bf> Look at a file in one of the fileareas
4081 Type out the contents of a file in a filearea. So, for example, in
4082 filearea 'bulletins' you want to look at file 'arld051' you would
4086 TYPE bulletins/arld051
4089 See also SHOW/FILES to see what fileareas are available and a
4096 <bf>who</bf> Show who is physically connected locally
4100 This is a quick listing that shows which callsigns are connected and
4101 what sort of connection they have
4107 <bf>wx <text></bf> Send a weather message to local users<newline>
4108 <bf>wx full <text> </bf> Send a weather message to all cluster users
4112 Weather messages can sometimes be useful if you are experiencing an extreme
4113 that may indicate enhanced conditions
4115 <sect1>wx (enhanced for sysops) (5)
4119 <bf>wx sysop <text></bf> Send a weather message to other clusters only
4123 Send a weather message only to other cluster nodes and not to general users.
projects / spider.git / blob