+19Jul01=======================================================================
+1. changes to Admin Manual to reflect route filtering. Some alterations to
+the help files (g0vgs)
06Jul01=======================================================================
1. fix talk and routing problems to mycall
2. add unset/privilege command to relinquish any sysop privileges you might
accept/ann input node_default by G,M,2
accept/ann user_default by G,M,2
+=== 8^ACCEPT/ROUTE <call> [0-9] <pattern>^Set an 'accept' filter line for routing
+Create an 'accept this routing PC Protocol' line for a filter.
+
+An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
+it is passed thru that interface. See HELP FILTERING for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+
+You can use any of the following things in this line:-
+
+ call <prefixes> the callsign of the thingy
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes> really the interface it came in on
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+
+some examples:-
+
+ acc/route gb7djk call_zone 61,38 (send only UK+EIRE nodes)
+ acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
+
+You can use the tag 'all' to accept everything eg:
+
+ acc/route all
+
+
=== 0^ACCEPT/SPOTS [0-9] <pattern>^Set an 'accept' filter line for spots
Create an 'accept this spot' line for a filter.
but this probably for advanced users...
-=== 8^ACCEPT/route <call> [0-9] <pattern>^Set an 'accept' filter line for routing
-Create an 'accept this routing PC Protocol' line for a filter.
-
-An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
-it is passed thru that interface. See HELP FILTERING for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.
-
-You can use any of the following things in this line:-
-
- call <prefixes> the callsign of the thingy
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- origin <prefixes> really the interface it came in on
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
-
-some examples:-
-
- acc/route gb7djk call_zone 61,38 (send only UK+EIRE nodes)
- acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
-
-You can use the tag 'all' to accept everything eg:
-
- acc/route all
-
=== 8^ACCEPT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
This version allows a sysop to set a filter for a callsign as well as the
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.47: Hop control</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.47: Routing and Filtering</TITLE>
<LINK HREF="adminmanual-2.html" REL=next>
<LINK HREF="adminmanual.html#toc1" REL=contents>
Previous
<A HREF="adminmanual.html#toc1">Contents</A>
<HR>
-<H2><A NAME="s1">1. Hop control</A></H2>
+<H2><A NAME="s1">1. Routing and Filtering</A></H2>
-<P>Starting with version 1.13 there is simple hop control available on a per
-node basis. Also it is possible to isolate a network completely so that you
-get all the benefits of being on that network, but can't pass on information
-from it to any other networks you may be connected to (or vice versa).
+<H2><A NAME="ss1.1">1.1 Introduction</A>
+</H2>
+
+<P>From DXSpider version 1.48, major changes were introduced to the way
+node connections are treated. This is part of an ongoing process to
+remove problems with loops and to enable talk and other functions to
+propagate across the whole of the worldwide cluster network. In fact,
+in a Spider network, it would be useful, perhaps even necessary to
+have loops. This would give real resilience to the network, meaning
+that if a link dropped, the information flow would simply come in and
+go out via a different route. Of course, we do not have a complete
+network of Spider nodes, there are other programs out there. Some of
+these do not have any protection from loops. Certainly AK1A does not
+handle loops well at all. It is therefore necessary to have some form
+of protection for these nodes.
+<P>
+<P>This is achieved by using filtering on a route basis. There is a
+default setting to help to protect the network, especially useful for new
+and inexperienced SysOps. The idea is simple. When Spider is started
+for the first time and a connection is made to or from another node,
+the default is to only send the nodes you already have that are in your
+own zone. For example, in the UK the default setting would be to send
+only UK nodes to any connection. This can be filtered further (down to
+a single node if needed) or expanded as required.
+<P>
+<P>
+<H2><A NAME="ss1.2">1.2 Route Filters</A>
+</H2>
+
+<P>As mentioned in the introduction, a default setting exists. If this is
+all you want to use then that is fine, you have nothing else to do.
+However, if you want to make any alterations then you need to know
+a bit about filters.
+<P>
+<P>It is possible to reset the default setting for node connections should
+you wish to do so, however this can be dangerous to the network unless
+you have some experience in how all this works.... be careful! It is
+also possible to change settings for one connection only. You can,
+therefore, have many different filters set dependent on the amount of
+node links you have.
<P>
-<H2><A NAME="ss1.1">1.1 Basic hop control</A>
+<P>I should at this stage give a little bit of background on filters. All
+the filters in Spider work in basically the same way. You can either
+accept or reject various options in order to create the filter rules
+you wish to achieve. Some filters are user settable, others can only
+be altered by the sysop. Route filtering can only be done by the sysop.
+<P>
+<H2><A NAME="ss1.3">1.3 The default_node filter</A>
+</H2>
+
+<P>As discussed previously, a default setting exists that only sends nodes
+from your own zone. This can be overridden by using the default_node
+filter option like this ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+reject/route default_node <filter_option>
+
+or
+
+accept/route default_node <filter_option>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>where filter_option is one of the following ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+call <prefixes>
+call_dxcc <numbers>
+call_itu <numbers>
+call_zone <numbers>
+origin <prefixes>
+origin_dxcc <numbers>
+origin_itu <numbers>
+origin_zone <numbers>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>Please be careful if you alter this setting, it will affect
+<B><I>ALL</I></B> your links!
+<P>
+<H2><A NAME="ss1.4">1.4 General route filtering</A>
+</H2>
+
+<P>Exactly the same rules apply for general route filtering. You would
+use either an accept filter or a reject filter like this ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+reject/route <node_call> <filter_option>
+
+or
+
+accept/route <node_call> <filter_option>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>where filter_option is one of the following ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+call <prefixes>
+call_dxcc <numbers>
+call_itu <numbers>
+call_zone <numbers>
+origin <prefixes>
+origin_dxcc <numbers>
+origin_itu <numbers>
+origin_zone <numbers>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>Here are some examples of route filters ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+rej/route gb7djk call_zone 61,38 (everything except UK+EIRE nodes)
+rej/route all (equiv to [very] restricted mode)
+acc/route gb7djk call_zone 61,38 (send only UK+EIRE nodes)
+acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss1.5">1.5 General filter rules</A>
+</H2>
+
+<P>Upto v1.44 it was not possible for the user to set their own filters. From
+v1.45 though that has all changed. It is now possible to set filters for just
+about anything you wish. If you have just updated from an older version of
+DXSpider you will need to update your new filters. You do not need to do
+anything with your old filters, they will be renamed as you update.
+<P>
+<P>There are 3 basic commands involved in setting and manipulating filters. These
+are <EM>accept</EM>, <EM>reject</EM> and <EM>clear</EM>. First we will look
+generally at filtering. There are a number of things you can filter in the
+DXSpider system. They all use the same general mechanism.
+<P>
+<P>In general terms you can create a 'reject' or an 'accept' filter which can have
+up to 10 lines in it. You do this using, for example ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+accept/spots .....
+reject/spots .....
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>where ..... are the specific commands for that type of filter. There are filters
+for spots, wwv, announce, wcy and (for sysops) connects. See each different
+accept or reject command reference for more details.
+<P>There is also a command to clear out one or more lines in a filter. They are ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+clear/spots 1
+clear/spots all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>There is clear/xxxx command for each type of filter.
+<P>
+<P>and you can check that your filters have worked by the command ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+show/filter
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>For now we are going to use spots for the examples, but you can apply the same
+principles to all types of filter.
+<P>
+<H2><A NAME="ss1.6">1.6 Types of filter</A>
+</H2>
+
+<P>There are two main types of filter, <EM>accept</EM> or <EM>reject</EM>. You
+can use either to achieve the result you want dependent on your own preference
+and which is more simple to do. It is pointless writing 8 lines of reject
+filters when 1 accept filter would do the same thing! Each filter has 10
+lines (of any length) which are tried in order. If a line matches then the
+action you have specified is taken (ie reject means ignore it and accept
+means take it)
+<P>
+<P>If you specify reject filters, then any lines that arrive that match the filter
+will be dumped but all else will be accepted. If you use an accept filter,
+then ONLY the lines in the filter will be accepted and all else will be dumped.
+For example if you have a single line <EM>accept</EM> filter ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>then you will <EM>ONLY</EM> get VHF spots <EM>from</EM> or <EM>to</EM> CQ zones
+14, 15 and 16.
+<P>
+<P>If you set a reject filter like this ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+reject/spots on hf/cw
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Then you will get everything <EM>EXCEPT</EM> HF CW spots. You could make this
+single filter even more flexible. For example, if you are interested in IOTA
+and will work it even on CW even though normally you are not interested in
+CW, then you could say ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+reject/spots on hf/cw and not info iota
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>But in that case you might only be interested in iota and say:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+accept/spots not on hf/cw or info iota
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>which achieves exactly the same thing. You should choose one or the other
+until you are comfortable with the way it works. You can mix them if you
+wish (actually you can have an accept AND a reject on the same line) but
+don't attempt this until you are sure you know what you are doing!
+<P>
+<P>You can arrange your filter lines into logical units, either for your own
+understanding or simply convenience. Here is an example ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+reject/spots 1 on hf/cw
+reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>What this does is to ignore all HF CW spots and also rejects any spots on VHF
+which don't either originate or spot someone in Europe.
+<P>
+<P>This is an example where you would use a line number (1 and 2 in this case), if
+you leave the digit out, the system assumes '1'. Digits '0'-'9' are available.
+This make it easier to see just what filters you have set. It also makes it
+more simple to remove individual filters, during a contest for example.
+<P>
+<P>You will notice in the above example that the second line has brackets. Look
+at the line logically. You can see there are 2 separate sections to it. We
+are saying reject spots that are VHF or above <EM>APART</EM> from those in
+zones 14, 15 and 16 (either spotted there or originated there). If you did
+not have the brackets to separate the 2 sections, then Spider would read it
+logically from the front and see a different expression entirely ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The simple way to remember this is, if you use OR - use brackets. Whilst we are
+here CASE is not important. 'And BY_Zone' is just the same as 'and by_zone'.
+<P>As mentioned earlier, setting several filters can be more flexible than
+simply setting one complex one. Doing it in this way means that if you want
+to alter your filter you can just redefine or remove one or more lines of it or
+one line. For example ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+reject/spots 1 on hf/ssb
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>would redefine our earlier example, or
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+clear/spots 1
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To remove all the filter lines in the spot filter ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+clear/spots all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss1.7">1.7 Filter options</A>
+</H2>
+
+<P>You can filter in several different ways. The options are listed in the
+various helpfiles for accept, reject and filter.
+<P>
+<H2><A NAME="ss1.8">1.8 Default filters</A>
+</H2>
+
+<P>Sometimes all that is needed is a general rule for node connects. This can
+be done with a node_default filter. This rule will always be followed, even
+if the link is isolated, unless another filter is set specifically. Default
+rules can be set for nodes and users. They can be set for spots, announces,
+WWV and WCY. They can also be used for hops. An example might look like
+this ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+accept/spot node_default by_zone 14,15,16,20,33
+set/hops node_default spot 50
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This filter is for spots only, you could set others for announce, WWV and WCY.
+This filter would work for ALL nodes unless a specific filter is written to
+override it for a particular node. You can also set a user_default should
+you require. It is important to note that default filters should be
+considered to be "connected". By this I mean that should you override the
+default filter for spots, you need to add a rule for the hops for spots also.
+<P>
+<H2><A NAME="ss1.9">1.9 Advanced filtering</A>
+</H2>
+
+<P>Once you are happy with the results you get, you may like to experiment.
+<P>
+<P>The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU
+can be written with a mixed filter, for example ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+rej/spot on hf/cw
+acc/spot on 0/30000
+acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Note that the first filter has not been specified with a number. This will
+automatically be assumed to be number 1. In this case, we have said <EM>reject all
+HF spots in the CW section of the bands but accept all others at HF. Also
+accept anything in VHF and above spotted in or by operators in the zones
+14, 15 and 16</EM>. Each filter slot actually has a 'reject' slot and
+an 'accept' slot. The reject slot is executed BEFORE the accept slot.
+<P>
+<P>It was mentioned earlier that after a reject test that doesn't match, the default
+for following tests is 'accept', the reverse is true for 'accept'. In the example
+what happens is that the reject is executed first, any non hf/cw spot is passed
+to the accept line, which lets through everything else on HF. The next filter line
+lets through just VHF/UHF spots from EU.
+<P>
+<H2><A NAME="ss1.10">1.10 Basic hop control</A>
</H2>
<P>In /spider/data you will find a file called hop_table.pl. This is the file
If you alter the file during runtime, the command <EM>load/hops</EM> will
bring your changes into effect.
<P>
-<H2><A NAME="ss1.2">1.2 Isolating networks</A>
+<H2><A NAME="ss1.11">1.11 Isolating networks</A>
</H2>
<P>It is possible to isolate networks from each other on a "gateway" node using the
<EM>set/isolate <node_call></EM> command.
<P>
<P>The effect of this is to partition an isolated network completely from another
-nodes connected to your node. Your node will appear on and otherwise behave
+node connected to your node. Your node will appear on and otherwise behave
normally on every network to which you are connected, but data from an isolated
network will not cross onto any other network or vice versa. However all the
spot, announce and WWV traffic and personal messages will still be handled
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>There is a lot more on filtering in the next section.
-<P>
<HR>
<A HREF="adminmanual-2.html">Next</A>
Previous
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.47: Filtering (Old Style upto v1.44)</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.47: Other filters</TITLE>
<LINK HREF="adminmanual-3.html" REL=next>
<LINK HREF="adminmanual-1.html" REL=previous>
<LINK HREF="adminmanual.html#toc2" REL=contents>
<A HREF="adminmanual-1.html">Previous</A>
<A HREF="adminmanual.html#toc2">Contents</A>
<HR>
-<H2><A NAME="s2">2. Filtering (Old Style upto v1.44)</A></H2>
-
-<P>Filters can be set for spots, announcements and WWV. You will find the
-directories for these under /spider/filter. You will find some examples in
-the directories with the suffix <EM>.issue</EM>. There are two types of
-filter, one for incoming information and one for outgoing information.
-Outgoing filters are in the form <EM>CALLSIGN.pl</EM> and incoming filters
-are in the form <EM>in_CALLSIGN.pl</EM>. Filters can be set for both nodes
-and users.
-<P>
-<P>All filters work in basically the same way. There are several elements
-delimited by commas. There can be many lines in the filter and they are
-read from the top by the program. When writing a filter you need to think
-carefully about just what you want to achieve. You are either going to write
-a filter to <EM>accept</EM> or to <EM>reject</EM>. Think of a filter as
-having 2 main elements. For a reject filter, you would have a line or multiple
-lines rejecting the things you do not wish to receive and then a default line
-accepting everything else that is not included in the filter. Likewise, for an
-accept filter, you would have a line or multiple lines accepting the things you
-wish to receive and a default line rejecting everthing else.
-<P>
-<P>In the example below, a user requires a filter that would only return SSB spots
-posted in Europe on the HF bands. This is achieved by first rejecting the CW
-section of each HF band and rejecting all of VHF, UHF etc based on frequency.
-Secondly, a filter rule is set based on CQ zones to only accept spots posted in
-Europe. Lastly, a default filter rule is set to reject anything outside the filter.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$in = [
- [ 0, 0, 'r', # reject all CW spots
- [
- 1800.0, 1850.0,
- 3500.0, 3600.0,
- 7000.0, 7040.0,
- 14000.0, 14100.0,
- 18068.0, 18110.0,
- 21000.0, 21150.0,
- 24890.0, 24930.0,
- 28000.0, 28180.0,
- 30000.0, 49000000000.0,
- ] ,1 ],
- [ 1, 11, 'n', [ 14, 15, 16, 20, 33, ], 15 ], #accept EU
- [ 0, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
-];
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>The actual elements of each filter are described more fully in the following
-sections.
-<P>
-<H2><A NAME="ss2.1">2.1 Spots</A>
+<H2><A NAME="s2">2. Other filters</A></H2>
+
+<H2><A NAME="ss2.1">2.1 Filtering Mail</A>
</H2>
-<P>The elements of the Spot filter are ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-[action, field_no, sort, possible_values, hops]
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>There are 3 elements here to look at. Firstly, the action element. This is
-very simple and only 2 possible states exist, accept (1) or drop (0).
-<P>
-<P>The second element is the field_no. There are 13 possiblities to choose from
-here ....
+<P>In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename
+this to badmsg.pl and edit the file. The original looks something like this ....
<P>
<BLOCKQUOTE><CODE>
<PRE>
- 0 = frequency
- 1 = call
- 2 = date in unix format
- 3 = comment
- 4 = spotter
- 5 = spotted dxcc country
- 6 = spotter's dxcc country
- 7 = origin
- 8 = spotted itu
- 9 = spotted cq
- 10 = spotter's itu
- 11 = spotter's cq
- 12 = callsign of the channel on which the spot has appeared
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>The third element tells us what to expect in the fourth element. There are
-4 possibilities ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- n - numeric list of numbers e.g. [ 1,2,3 ]
- r - ranges of pairs of numbers e.g. between 2 and 4 or 10 to 17 - [ 2,4, 10,17 ]
- a - an alphanumeric regex
- d - the default rule
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>The fifth element is simply the hops to set in this filter. This would only
-be used if the filter was for a node of course and overrides the hop count in
-hop_table.pl.
-<P>
-<P>So, let's look at an example spot filter. It does not matter in the example
-who the filter is to be used for. So, what do we need in the filter? We need
-to filter the spots the user/node requires and also set a default rule for
-anything else outside the filter. Below is a simple filter that stops spots
-arriving from outside Europe.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$in = [
- [ 0, 4, 'a', '^(K|N|A|W|VE|VA|J)'], # 0 = drop, 'a' = alphanumeric
- [ 1, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
- ];
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>So the filter is wrapped in between a pair of square brackets. This tells
-Spider to look in between these limits. Then each line is contained within
-its own square brackets and ends with a comma. Lets look carefully at the first
-line. The first element is 0 (drop). Therefore anything we put on this line
-will not be accepted. The next element is 4. This means we are filtering by
-the spotter. The third element is the letter "a" which tells the program to
-expect an alphanumeric expression in the fourth element. The fourth element
-is a list of letters separated by the pipe symbol.
-<P>
-<P>What this line does is tell the program to drop any spots posted by anyone in
-the USA, Canada or Japan.
-<P>
-<P>The second line is the default rule for anything else. The "d" tells us this
-and the line simply reads... accept anything else.
-<P>
-<P>You can add as many lines as you need to complete the filter but if there are
-several lines of the same type it is neater to enclose them all as one line.
-An example of this is where specific bands are set. We could write this like
-this ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-[ 0,0,'r',[1800.0, 2000.0], 1],
-[ 0,0,'r',[10100.0, 10150.0], 1],
-[ 0,0,'r',[14000.0, 14350.0], 1],
-[ 0,0,'r',[18000.0, 18200.0], 1],
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>But the line below achieves the same thing and is more efficient ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- [ 0, 0, 'r',
- [
- 1800.0, 2000.0, # top band
- 10100.0, 10150.0, # WARC
- 14000.0, 14350.0, # 20m
- 18000.0, 18200.0, # WARC
- [ ,1 ],
+
+# the list of regexes for messages that we won't store having
+# received them (bear in mind that we must receive them fully before
+# we can bin them)
+
+
+# The format of each line is as follows
+
+# type source pattern
+# P/B/F T/F/O/S regex
+
+# type: P - private, B - bulletin (msg), F - file (ak1a bull)
+# source: T - to field, F - from field, O - origin, S - subject
+# pattern: a perl regex on the field requested
+
+# Currently only type B and P msgs are affected by this code.
+#
+# The list is read from the top down, the first pattern that matches
+# causes the action to be taken.
+
+# The pattern can be undef or 0 in which case it will always be selected
+# for the action specified
+
+
+
+package DXMsg;
+
+@badmsg = (
+'B', 'T', 'SALE',
+'B', 'T', 'WANTED',
+'B', 'S', 'WANTED',
+'B', 'S', 'SALE',
+'B', 'S', 'WTB',
+'B', 'S', 'WTS',
+'B', 'T', 'FS',
+);
</PRE>
</CODE></BLOCKQUOTE>
<P>
+<P>I think this is fairly self explanatory. It is simply a list of subject
+headers that we do not want to pass on to either the users of the cluster or
+the other cluster nodes that we are linked to. This is usually because of
+rules and regulations pertaining to items for sale etc in a particular country.
<P>
-<H2><A NAME="ss2.2">2.2 Announcements</A>
+<H2><A NAME="ss2.2">2.2 Filtering DX callouts (Depricated)</A>
</H2>
+<P><B><I>From version 1.47, this method is replaced by the command set/baddx</I></B>
+<P>
+<P>In the same way as mail, there are some types of spot we do not wish to pass on
+to users or linked cluster nodes. In the /spider/data directory you will find
+a file called baddx.pl.issue. Rename this to baddx.pl and edit the file. The
+original looks like this ....
<P>
<BLOCKQUOTE><CODE>
<PRE>
-# This is an example announce or filter allowing only West EU announces
-#
-# The element list is:-
-# 0 - callsign of announcer
-# 1 - destination * = all, <callsign> = routed to the node
-# 2 - text
-# 3 - * - sysop, <some text> - special list eg 6MUK, ' ', normal announce
-# 4 - origin
-# 5 - 0 - announce, 1 - wx
-# 6 - channel callsign (the interface from which this spot came)
-
-$in = [
- [ 1, 0, 'a', '^(P[ABCDE]|DK0WCY|G|M|2|EI|F|ON)' ],
- [ 0, 0, 'd', 0 ]
-];
+# the list of dx spot addresses that we don't store and don't pass on
+
+
+package DXProt;
+
+@baddx = qw
+
+ FROG
+ SALE
+ FORSALE
+ WANTED
+ P1RATE
+ PIRATE
+ TEST
+ DXTEST
+ NIL
+ NOCALL
+);
</PRE>
</CODE></BLOCKQUOTE>
-<P>In this example, only the prefixes listed will be allowed. It is possible to
-be quite specific. The Dutch prefix "P" is followed by several secondary
-identifiers which are allowed. So, in the example, "PA" or "PE" would be ok
-but not "PG". It is even possible to allow information from a single callsign.
-In the example this is DK0WCY, to allow the posting of his Aurora Beacon.
<P>
-<H2><A NAME="ss2.3">2.3 WWV</A>
+<P>Again, this is simply a list of names we do not want to see in the spotted
+field of a DX callout.
+<P>
+<P>
+<H2><A NAME="ss2.3">2.3 Filtering words from text fields in Announce, Talk and DX spots</A>
</H2>
+<P>Create a file in /spider/data called <EM>badwords</EM>. The format is quite
+simple. Lines beginning with # are ignored so comments can be added. An
+example file is below ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-
-# This is an example WWV filter
-#
-# The element list is:-
-# 0 - nominal unix date of spot (ie the day + hour:13)
-# 1 - the hour
-# 2 - SFI
-# 3 - K
-# 4 - I
-# 5 - text
-# 6 - spotter
-# 7 - origin
-# 8 - incoming interface callsign
-
-# this one doesn't filter, it just sets the hop count to 6 and is
-# used mainly just to override any isolation from WWV coming from
-# the internet.
-
-$in = [
- [ 1, 0, 'd', 0, 6 ]
-];
+# Below is a list of words we do not wish to see on the cluster
+grunge grunged grunging
+splodge splodger splodging
+grince
+fluffle
</PRE>
</CODE></BLOCKQUOTE>
+<P>Multiple words can be used on the same line as shown. Obviously these
+are just examples :-)
<P>
-<P>It should be noted that the filter will start to be used only once a user/node
-has logged out and back in again.
-<P>I am not going to spend any more time on these filters now as they will become
-more "comprehensive" in the near future.
+<P>You can reload the file from the cluster prompt as sysop with load/badwords.
<P>
<HR>
<A HREF="adminmanual-3.html">Next</A>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.47: Filtering (New Style v1.45 and later)</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.47: Mail</TITLE>
<LINK HREF="adminmanual-4.html" REL=next>
<LINK HREF="adminmanual-2.html" REL=previous>
<LINK HREF="adminmanual.html#toc3" REL=contents>
<A HREF="adminmanual-2.html">Previous</A>
<A HREF="adminmanual.html#toc3">Contents</A>
<HR>
-<H2><A NAME="s3">3. Filtering (New Style v1.45 and later)</A></H2>
+<H2><A NAME="s3">3. Mail</A></H2>
-<H2><A NAME="ss3.1">3.1 General filter rules</A>
+<P>DXSpider deals seamlessly with standard AK1A type mail. It supports both
+personal and bulletin mail and the sysop has additional commands to ensure
+that mail gets to where it is meant. DXSpider will send mail almost
+immediately, assuming that the target is on line. However, only one
+mail message is dealt with at any one time. If a mail message is already
+being sent or recieved, then the new message will be queued until it has
+finished.
+<P>The cluster mail is automatically deleted after 30 days unless the sysop
+sets the "keep" flag using the <EM>msg</EM> command.
+<P>
+<H2><A NAME="ss3.1">3.1 Personal mail</A>
</H2>
-<P>Upto v1.44 it was not possible for the user to set their own filters. From
-v1.45 though that has all changed. It is now possible to set filters for just
-about anything you wish. If you have just updated from an older version of
-DXSpider you will need to update your new filters. You do not need to do
-anything with your old filters, they will be renamed as you update.
+<P>Personal mail is sent using the <EM>sp</EM> command. This is actually the
+default method of sending mail and so a simple <EM>s</EM> for send will do.
+A full list of the send commands and options is in the <EM>command set</EM>
+section, so I will not duplicate them here.
<P>
-<P>There are 3 basic commands involved in setting and manipulating filters. These
-are <EM>accept</EM>, <EM>reject</EM> and <EM>clear</EM>. First we will look
-generally at filtering. There are a number of things you can filter in the
-DXSpider system. They all use the same general mechanism.
-<P>
-<P>In general terms you can create a 'reject' or an 'accept' filter which can have
-up to 10 lines in it. You do this using, for example ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-accept/spots .....
-reject/spots .....
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>where ..... are the specific commands for that type of filter. There are filters
-for spots, wwv, announce, wcy and (for sysops) connects. See each different
-accept or reject command reference for more details.
-<P>There is also a command to clear out one or more lines in a filter. They are ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-clear/spots 1
-clear/spots all
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>There is clear/xxxx command for each type of filter.
-<P>
-<P>and you can check that your filters have worked by the command ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-show/filter
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>For now we are going to use spots for the examples, but you can apply the same
-principles to all types of filter.
-<P>
-<H2><A NAME="ss3.2">3.2 Types of filter</A>
+<H2><A NAME="ss3.2">3.2 Bulletin mail</A>
</H2>
-<P>There are two main types of filter, <EM>accept</EM> or <EM>reject</EM>. You
-can use either to achieve the result you want dependent on your own preference
-and which is more simple to do. It is pointless writing 8 lines of reject
-filters when 1 accept filter would do the same thing! Each filter has 10
-lines (of any length) which are tried in order. If a line matches then the
-action you have specified is taken (ie reject means ignore it and accept
-means take it)
-<P>
-<P>If you specify reject filters, then any lines that arrive that match the filter
-will be dumped but all else will be accepted. If you use an accept filter,
-then ONLY the lines in the filter will be accepted and all else will be dumped.
-For example if you have a single line <EM>accept</EM> filter ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>then you will <EM>ONLY</EM> get VHF spots <EM>from</EM> or <EM>to</EM> CQ zones
-14, 15 and 16.
+<P>Bulletin mail is sent by using the <EM>sb</EM> command. This is one of the
+most common mistakes users make when sending mail. They send a bulletin
+mail with <EM>s</EM> or <EM>sp</EM> instead of <EM>sb</EM> and of course
+the message never leaves the cluster. This can be rectified by the sysop
+by using the <EM>msg</EM> command.
<P>
-<P>If you set a reject filter like this ...
+<P>Bulletin addresses can be set using the Forward.pl file.
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots on hf/cw
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Then you will get everything <EM>EXCEPT</EM> HF CW spots. You could make this
-single filter even more flexible. For example, if you are interested in IOTA
-and will work it even on CW even though normally you are not interested in
-CW, then you could say ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots on hf/cw and not info iota
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>But in that case you might only be interested in iota and say:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-accept/spots not on hf/cw or info iota
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>which achieves exactly the same thing. You should choose one or the other
-until you are comfortable with the way it works. You can mix them if you
-wish (actually you can have an accept AND a reject on the same line) but
-don't attempt this until you are sure you know what you are doing!
-<P>
-<P>You can arrange your filter lines into logical units, either for your own
-understanding or simply convenience. Here is an example ...
+<H2><A NAME="ss3.3">3.3 Forward.pl</A>
+</H2>
+
+<P>DXSpider receives all and any mail sent to it without any alterations needed
+in files. Because personal and bulletin mail are treated differently, there
+is no need for a list of accepted bulletin addresses. It is necessary, however,
+to tell the program which links accept which bulletins. For example, it is
+pointless sending bulletins addresses to "UK" to any links other than UK
+ones. The file that does this is called forward.pl and lives in /spider/msg.
+At default, like other spider files it is named forward.pl.issue. Rename it
+to forward.pl and edit the file to match your requirements.
+The format is below ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-reject/spots 1 on hf/cw
-reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
+#
+# this is an example message forwarding file for the system
+#
+# The format of each line is as follows
+#
+# type to/from/at pattern action destinations
+# P/B/F T/F/A regex I/F [ call [, call ...] ]
+#
+# type: P - private, B - bulletin (msg), F - file (ak1a bull)
+# to/from/at: T - to field, F - from field, A - home bbs, O - origin
+# pattern: a perl regex on the field requested
+# action: I - ignore, F - forward
+# destinations: a reference to an array containing node callsigns
+#
+# if it is non-private and isn't in here then it won't get forwarded
+#
+# Currently only type B msgs are affected by this code.
+#
+# The list is read from the top down, the first pattern that matches
+# causes the action to be taken.
+#
+# The pattern can be undef or 0 in which case it will always be selected
+# for the action specified
+#
+# If the BBS list is undef or 0 and the action is 'F' (and it matches the
+# pattern) then it will always be forwarded to every node that doesn't have
+# it (I strongly recommend you don't use this unless you REALLY mean it, if
+# you allow a new link with this on EVERY bull will be forwarded immediately
+# on first connection)
+#
+
+package DXMsg;
+
+@forward = (
+'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ],
+'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ],
+'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ],
+'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
+);
</PRE>
</CODE></BLOCKQUOTE>
-<P>What this does is to ignore all HF CW spots and also rejects any spots on VHF
-which don't either originate or spot someone in Europe.
+<P>Simply insert a bulletin address and state in the brackets where you wish
+that mail to go. For example, you can see here that mail sent to "UK" will
+only be sent to the UK links and not to PA4AB-14.
<P>
-<P>This is an example where you would use a line number (1 and 2 in this case), if
-you leave the digit out, the system assumes '1'. Digits '0'-'9' are available.
-This make it easier to see just what filters you have set. It also makes it
-more simple to remove individual filters, during a contest for example.
+<P>To force the cluster to reread the file use load/forward
<P>
-<P>You will notice in the above example that the second line has brackets. Look
-at the line logically. You can see there are 2 separate sections to it. We
-are saying reject spots that are VHF or above <EM>APART</EM> from those in
-zones 14, 15 and 16 (either spotted there or originated there). If you did
-not have the brackets to separate the 2 sections, then Spider would read it
-logically from the front and see a different expression entirely ...
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>The simple way to remember this is, if you use OR - use brackets. Whilst we are
-here CASE is not important. 'And BY_Zone' is just the same as 'and by_zone'.
-<P>As mentioned earlier, setting several filters can be more flexible than
-simply setting one complex one. Doing it in this way means that if you want
-to alter your filter you can just redefine or remove one or more lines of it or
-one line. For example ...
+<H2><A NAME="ss3.4">3.4 The msg command</A>
+</H2>
+
+<P>The <EM>msg</EM> command is a very powerful and flexible tool for the
+sysop. It allows the sysop to alter to and from fields and make other
+changes to manage the cluster mail.
+<P>Here is a full list of the various options ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-reject/spots 1 on hf/ssb
+ MSG TO <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - remove any waiting time for this message
+ MSG NOREad <msgno> - mark message as unread
+ MSG REad <msgno> - mark message as read
+ MSG QUeue - queue any outstanding bulletins
+ MSG QUeue 1 - queue any outstanding private messages
</PRE>
</CODE></BLOCKQUOTE>
-<P>would redefine our earlier example, or
+<P>These commands are simply typed from within the cluster as the sysop user.
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-clear/spots 1
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>To remove all the filter lines in the spot filter ...
+<H2><A NAME="ss3.5">3.5 Message status</A>
+</H2>
+
+<P>You can check on a message from within the cluster by using the command
+<EM>stat/msg</EM>. This will give you additional information on the
+message number including which nodes have received it, which node it
+was received from and when etc. Here is an example of the output of
+the command ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-clear/spots all
+G0VGS de GB7MBC 28-Jan-2001 1308Z >
+stat/msg 6869
+ From: GB7DJK
+ Msg Time: 26-Jan-2001 1302Z
+ Msgno: 6869
+ Origin: GB7DJK
+ Size: 8012
+ Subject: AMSAT 2line KEPS 01025.AMSAT
+ To: UK
+Got it Nodes: GB7BAA, GB7ADX
+ Private: 0
+Read Confirm: 0
+ Times read: 0
+G0VGS de GB7MBC 28-Jan-2001 1308Z >
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss3.3">3.3 Filter options</A>
+<H2><A NAME="ss3.6">3.6 Filtering mail</A>
</H2>
-<P>You can filter in several different ways. The options are listed in the
-various helpfiles for accept, reject and filter.
+<P>This is described in the section on <EM>Other filters</EM> so I will not
+duplicate it here.
<P>
-<H2><A NAME="ss3.4">3.4 Default filters</A>
+<H2><A NAME="ss3.7">3.7 Distribution lists</A>
</H2>
-<P>Sometimes all that is needed is a general rule for node connects. This can
-be done with a node_default filter. This rule will always be followed, even
-if the link is isolated, unless another filter is set specifically. Default
-rules can be set for nodes and users. They can be set for spots, announces,
-WWV and WCY. They can also be used for hops. An example might look like
-this ...
+<P>Distribution lists are simply a list of users to send certain types of
+mail to. An example of this is mail you only wish to send to other
+sysops. In /spider/msg there is a directory called <EM>distro</EM>. You
+put any distibution lists in here. For example, here is a file called
+SYSOP.pl that caters for the UK sysops.
<P>
<BLOCKQUOTE><CODE>
<PRE>
-accept/spot node_default by_zone 14,15,16,20,33
-set/hops node_default spot 50
+qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
+ GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
+ GB7DXK GB7DXI GB7DXS)
</PRE>
</CODE></BLOCKQUOTE>
-<P>This filter is for spots only, you could set others for announce, WWV and WCY.
-This filter would work for ALL nodes unless a specific filter is written to
-override it for a particular node. You can also set a user_default should
-you require. It is important to note that default filters should be
-considered to be "connected". By this I mean that should you override the
-default filter for spots, you need to add a rule for the hops for spots also.
-<P>
-<H2><A NAME="ss3.5">3.5 Advanced filtering</A>
+<P>Any mail sent to "sysop" would only be sent to the callsigns in this list.
+<P>
+<H2><A NAME="ss3.8">3.8 BBS interface</A>
</H2>
-<P>Once you are happy with the results you get, you may like to experiment.
-<P>
-<P>The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU
-can be written with a mixed filter, for example ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-rej/spot on hf/cw
-acc/spot on 0/30000
-acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Note that the first filter has not been specified with a number. This will
-automatically be assumed to be number 1. In this case, we have said <EM>reject all
-HF spots in the CW section of the bands but accept all others at HF. Also
-accept anything in VHF and above spotted in or by operators in the zones
-14, 15 and 16</EM>. Each filter slot actually has a 'reject' slot and
-an 'accept' slot. The reject slot is executed BEFORE the accept slot.
-<P>
-<P>It was mentioned earlier that after a reject test that doesn't match, the default
-for following tests is 'accept', the reverse is true for 'accept'. In the example
-what happens is that the reject is executed first, any non hf/cw spot is passed
-to the accept line, which lets through everything else on HF. The next filter line
-lets through just VHF/UHF spots from EU.
-<P>
+<P>Spider provides a simple BBS interface. No input is required from the sysop
+of the cluster at all. The BBS simply sets the cluster as a BBS and pushes
+any required mail to the cluster. No mail can flow from Spider to the BBS,
+the interface is one-way.
+<P>
+<P>Please be careful not to flood the cluster network with unnecessary mail.
+Make sure you only send mail to the clusters that want it by using the
+Forward.pl file very carefully.
<P>
<HR>
<A HREF="adminmanual-4.html">Next</A>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.47: Other filters</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.47: Databases</TITLE>
<LINK HREF="adminmanual-5.html" REL=next>
<LINK HREF="adminmanual-3.html" REL=previous>
<LINK HREF="adminmanual.html#toc4" REL=contents>
<A HREF="adminmanual-3.html">Previous</A>
<A HREF="adminmanual.html#toc4">Contents</A>
<HR>
-<H2><A NAME="s4">4. Other filters</A></H2>
+<H2><A NAME="s4">4. Databases</A></H2>
-<H2><A NAME="ss4.1">4.1 Filtering Mail</A>
+<P>Spider allows the creation of local or remote databases. It supports
+chained databases, allowing several different databases to be scanned
+with one simple command. Importing of databases is limited at present
+to the standard AK1A databases such as OBLAST and the DB0SDX QSL
+database but will expand with time.
+<P>
+<H2><A NAME="ss4.1">4.1 Creating databases</A>
</H2>
-<P>In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename
-this to badmsg.pl and edit the file. The original looks something like this ....
+<P>Creating a database could not be more simple. All the commands are
+sent from the cluster prompt as the <EM>sysop</EM> user.
+<P>To create a database you use the command <EM>dbcreate</EM>. It can
+be used in 3 different ways like so ..
<P>
<BLOCKQUOTE><CODE>
<PRE>
-
-# the list of regexes for messages that we won't store having
-# received them (bear in mind that we must receive them fully before
-# we can bin them)
-
-
-# The format of each line is as follows
-
-# type source pattern
-# P/B/F T/F/O/S regex
-
-# type: P - private, B - bulletin (msg), F - file (ak1a bull)
-# source: T - to field, F - from field, O - origin, S - subject
-# pattern: a perl regex on the field requested
-
-# Currently only type B and P msgs are affected by this code.
-#
-# The list is read from the top down, the first pattern that matches
-# causes the action to be taken.
-
-# The pattern can be undef or 0 in which case it will always be selected
-# for the action specified
-
-
-
-package DXMsg;
-
-@badmsg = (
-'B', 'T', 'SALE',
-'B', 'T', 'WANTED',
-'B', 'S', 'WANTED',
-'B', 'S', 'SALE',
-'B', 'S', 'WTB',
-'B', 'S', 'WTS',
-'B', 'T', 'FS',
-);
+dbcreate <name>
</PRE>
</CODE></BLOCKQUOTE>
+<P>To simply create a database locally, you just tell the command the
+name of the database. This does not create the actual database, it
+simply defines it to say that it exists.
<P>
-<P>I think this is fairly self explanatory. It is simply a list of subject
-headers that we do not want to pass on to either the users of the cluster or
-the other cluster nodes that we are linked to. This is usually because of
-rules and regulations pertaining to items for sale etc in a particular country.
+<BLOCKQUOTE><CODE>
+<PRE>
+dbcreate <name> chain <name> [<name>...]
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This creates a chained database entry. The first database will be
+scanned, then the second, the third etc...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dbcreate <name> remote <name>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This creates a remote entry. the first name field is the database
+name at the remote node, then the remote switch, then the actual
+node_call of the remote node, for example...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dbcreate buckmaster remote gb7dxc
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Remote databases cannot be chained, however, the last database in a
+chain can be a remote database.
<P>
-<H2><A NAME="ss4.2">4.2 Filtering DX callouts (Depricated)</A>
+<H2><A NAME="ss4.2">4.2 Importing databases</A>
</H2>
-<P><B><I>From version 1.47, this method is replaced by the command set/baddx</I></B>
-<P>
-<P>In the same way as mail, there are some types of spot we do not wish to pass on
-to users or linked cluster nodes. In the /spider/data directory you will find
-a file called baddx.pl.issue. Rename this to baddx.pl and edit the file. The
-original looks like this ....
+<P>The only databases that Spider can currently import are the standard
+AK1A databases such as OBLAST or the DB0SDX qsl and address database.
+This will be added to with time.
+<P>To import such a database, first put the file somewhere useful like /tmp
+and then issue the following command ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-
-# the list of dx spot addresses that we don't store and don't pass on
-
-
-package DXProt;
-
-@baddx = qw
-
- FROG
- SALE
- FORSALE
- WANTED
- P1RATE
- PIRATE
- TEST
- DXTEST
- NIL
- NOCALL
-);
+dbimport oblast /tmp/OBLAST.FUL
</PRE>
</CODE></BLOCKQUOTE>
+<P>This will update the existing local oblast database or create it if
+it does not exist.
<P>
-<P>Again, this is simply a list of names we do not want to see in the spotted
-field of a DX callout.
+<H2><A NAME="ss4.3">4.3 Checking available databases</A>
+</H2>
+
+<P>Once a database is created, you will want to check that it has been
+added. To do this use the <EM>dbavail</EM> command. This will
+output the available databases. For example ...
<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dbavail
+DB Name Location Chain
+qsl Local
+buck GB7ADX
+hftest GB7DXM
+G0VGS de GB7MBC 3-Feb-2001 1925Z >
+</PRE>
+</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss4.3">4.3 Filtering words from text fields in Announce, Talk and DX spots</A>
+<H2><A NAME="ss4.4">4.4 Looking up databases</A>
</H2>
-<P>Create a file in /spider/data called <EM>badwords</EM>. The format is quite
-simple. Lines beginning with # are ignored so comments can be added. An
-example file is below ...
+<P>To look for information in a defined database, simply use the <EM>dbshow</EM>
+command, for example ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-# Below is a list of words we do not wish to see on the cluster
-grunge grunged grunging
-splodge splodger splodging
-grince
-fluffle
+dbshow buckmaster G0YLM
</PRE>
</CODE></BLOCKQUOTE>
-<P>Multiple words can be used on the same line as shown. Obviously these
-are just examples :-)
+<P>will show the information for the callsign G0YLM from the buckmaster
+database if it exists. To make things more standard for the users
+you can add an entry in the Aliases file so that it looks like a standard
+<EM>show</EM> command like this ...
<P>
-<P>You can reload the file from the cluster prompt as sysop with load/badwords.
+<BLOCKQUOTE><CODE>
+<PRE>
+'^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Now you can simply use show/buckmaster or an abreviation.
+<P>
+<H2><A NAME="ss4.5">4.5 Removing databases</A>
+</H2>
+
+<P>To delete an existing database you use the <EM>dbremove</EM> command.
+For example ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dbremove oblast
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>would remove the oblast database and its associated datafile from the
+system. There are no warnings or recovery possible from this command.
+If you remove a database it ceases to exist and would have to be created
+from scratch if you still required it.
<P>
<HR>
<A HREF="adminmanual-5.html">Next</A>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.47: Mail</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.47: Information, files and useful programs</TITLE>
<LINK HREF="adminmanual-6.html" REL=next>
<LINK HREF="adminmanual-4.html" REL=previous>
<LINK HREF="adminmanual.html#toc5" REL=contents>
<A HREF="adminmanual-4.html">Previous</A>
<A HREF="adminmanual.html#toc5">Contents</A>
<HR>
-<H2><A NAME="s5">5. Mail</A></H2>
-
-<P>DXSpider deals seamlessly with standard AK1A type mail. It supports both
-personal and bulletin mail and the sysop has additional commands to ensure
-that mail gets to where it is meant. DXSpider will send mail almost
-immediately, assuming that the target is on line. However, only one
-mail message is dealt with at any one time. If a mail message is already
-being sent or recieved, then the new message will be queued until it has
-finished.
-<P>The cluster mail is automatically deleted after 30 days unless the sysop
-sets the "keep" flag using the <EM>msg</EM> command.
-<P>
-<H2><A NAME="ss5.1">5.1 Personal mail</A>
+<H2><A NAME="s5">5. Information, files and useful programs</A></H2>
+
+<H2><A NAME="ss5.1">5.1 MOTD</A>
</H2>
-<P>Personal mail is sent using the <EM>sp</EM> command. This is actually the
-default method of sending mail and so a simple <EM>s</EM> for send will do.
-A full list of the send commands and options is in the <EM>command set</EM>
-section, so I will not duplicate them here.
+<P>One of the more important things a cluster sysop needs to do is to get
+information to his users. The simplest way to do this is to have a banner
+that is sent to the user on login. This is know as a "message of the day"
+or "motd". To set this up, simply create a file in /spider/data called motd
+and edit it to say whatever you want. It is purely a text file and will be
+sent automatically to anyone logging in to the cluster.
<P>
-<H2><A NAME="ss5.2">5.2 Bulletin mail</A>
+<H2><A NAME="ss5.2">5.2 Downtime message</A>
</H2>
-<P>Bulletin mail is sent by using the <EM>sb</EM> command. This is one of the
-most common mistakes users make when sending mail. They send a bulletin
-mail with <EM>s</EM> or <EM>sp</EM> instead of <EM>sb</EM> and of course
-the message never leaves the cluster. This can be rectified by the sysop
-by using the <EM>msg</EM> command.
-<P>
-<P>Bulletin addresses can be set using the Forward.pl file.
+<P>If for any reason the cluster is down, maybe for upgrade or maintenance but
+the machine is still running, a message can be sent to the user advising them
+of the fact. This message lives in the /spider/data directory and is called
+"offline". Simply create the file and edit it to say whatever you wish.
+This file will be sent to a user attempting to log into the cluster when
+DXSpider is not actually running.
<P>
-<H2><A NAME="ss5.3">5.3 Forward.pl</A>
+<H2><A NAME="ss5.3">5.3 Other text messages</A>
</H2>
-<P>DXSpider receives all and any mail sent to it without any alterations needed
-in files. Because personal and bulletin mail are treated differently, there
-is no need for a list of accepted bulletin addresses. It is necessary, however,
-to tell the program which links accept which bulletins. For example, it is
-pointless sending bulletins addresses to "UK" to any links other than UK
-ones. The file that does this is called forward.pl and lives in /spider/msg.
-At default, like other spider files it is named forward.pl.issue. Rename it
-to forward.pl and edit the file to match your requirements.
-The format is below ...
+<P>You can set other text messages to be read by the user if they input the file
+name. This could be for news items or maybe information for new users.
+To set this up, make a directory under /spider called <EM>packclus</EM>.
+Under this directory you can create files called <EM>news</EM> or <EM>newuser</EM>
+for example. In fact you can create files with any names you like. These can
+be listed by the user with the command ....
<P>
<BLOCKQUOTE><CODE>
<PRE>
-#
-# this is an example message forwarding file for the system
-#
-# The format of each line is as follows
-#
-# type to/from/at pattern action destinations
-# P/B/F T/F/A regex I/F [ call [, call ...] ]
-#
-# type: P - private, B - bulletin (msg), F - file (ak1a bull)
-# to/from/at: T - to field, F - from field, A - home bbs, O - origin
-# pattern: a perl regex on the field requested
-# action: I - ignore, F - forward
-# destinations: a reference to an array containing node callsigns
-#
-# if it is non-private and isn't in here then it won't get forwarded
-#
-# Currently only type B msgs are affected by this code.
-#
-# The list is read from the top down, the first pattern that matches
-# causes the action to be taken.
-#
-# The pattern can be undef or 0 in which case it will always be selected
-# for the action specified
-#
-# If the BBS list is undef or 0 and the action is 'F' (and it matches the
-# pattern) then it will always be forwarded to every node that doesn't have
-# it (I strongly recommend you don't use this unless you REALLY mean it, if
-# you allow a new link with this on EVERY bull will be forwarded immediately
-# on first connection)
-#
-
-package DXMsg;
-
-@forward = (
-'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ],
-'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ],
-'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ],
-'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-);
+show/files
</PRE>
</CODE></BLOCKQUOTE>
-<P>Simply insert a bulletin address and state in the brackets where you wish
-that mail to go. For example, you can see here that mail sent to "UK" will
-only be sent to the UK links and not to PA4AB-14.
+<P>They can be read by the user by typing the command ....
<P>
-<P>To force the cluster to reread the file use load/forward
+<BLOCKQUOTE><CODE>
+<PRE>
+type news
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>If the file they want to read is called <EM>news</EM>. You could also set
+an alias for this in the Alias file to allow them just to type <EM>news</EM>
<P>
+<P>You can also store other information in this directory, either directly or
+nested under directories. One use for this would be to store DX bulletins
+such as the OPDX bulletins. These can be listed and read by the user.
+To keep things tidy, make a directory under /spider/packclus called
+<EM>bulletin</EM>. Now copy any OPDX or similar bulletins into it. These
+can be listed by the user in the same way as above using the <EM>show/files</EM>
+command with an extension for the bulletin directory you have just created,
+like this ....
<P>
-<H2><A NAME="ss5.4">5.4 The msg command</A>
-</H2>
-
-<P>The <EM>msg</EM> command is a very powerful and flexible tool for the
-sysop. It allows the sysop to alter to and from fields and make other
-changes to manage the cluster mail.
-<P>Here is a full list of the various options ...
+<BLOCKQUOTE><CODE>
+<PRE>
+show/files bulletin
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>An example would look like this ....
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+sh/files
+bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can see that in the files area (basically the packclus directory) there is a
+file called <EM>news</EM> and a directory called <EM>bulletin</EM>. You can
+also see that dates they were created. In the case of the file <EM>news</EM>,
+you can also see the time it was last modified, a good clue as to whether the
+file has been updated since you last read it. To read the file called
+<EM>news</EM> you would simply issue the command ....
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+type news
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To look what is in the bulletin directory you issue the command ....
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+show/files bulletin
+opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
+opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
+opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
+opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
+opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
+opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
+opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
+opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
+opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
+opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
+opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
+opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
+opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
+Press Enter to continue, A to abort (16 lines) >
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can now read any file in this directory using the type command, like this ....
<P>
<BLOCKQUOTE><CODE>
<PRE>
- MSG TO <msgno> <call> - change TO callsign to <call>
- MSG FRom <msgno> <call> - change FROM callsign to <call>
- MSG PRrivate <msgno> - set private flag
- MSG NOPRrivate <msgno> - unset private flag
- MSG RR <msgno> - set RR flag
- MSG NORR <msgno> - unset RR flag
- MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
- MSG NOKEep <msgno> - unset the keep flag
- MSG SUbject <msgno> <new> - change the subject to <new>
- MSG WAittime <msgno> - remove any waiting time for this message
- MSG NOREad <msgno> - mark message as unread
- MSG REad <msgno> - mark message as read
- MSG QUeue - queue any outstanding bulletins
- MSG QUeue 1 - queue any outstanding private messages
+type bulletin/opdx391
+Ohio/Penn DX Bulletin No. 391
+The Ohio/Penn Dx PacketCluster
+DX Bulletin No. 391
+BID: $OPDX.391
+January 11, 1999
+Editor Tedd Mirgliotta, KB8NW
+Provided by BARF-80 BBS Cleveland, Ohio
+Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
+Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
+Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
+& The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
+Press Enter to continue, A to abort (508 lines) >
</PRE>
</CODE></BLOCKQUOTE>
-<P>These commands are simply typed from within the cluster as the sysop user.
+<P>The page length will of course depend on what you have it set to!
<P>
-<H2><A NAME="ss5.5">5.5 Message status</A>
+<H2><A NAME="ss5.4">5.4 The Aliases file</A>
</H2>
-<P>You can check on a message from within the cluster by using the command
-<EM>stat/msg</EM>. This will give you additional information on the
-message number including which nodes have received it, which node it
-was received from and when etc. Here is an example of the output of
-the command ...
+<P>You will find a file in /spider/cmd/ called Aliases. First, copy this file to
+/spider/local_cmd/Aliases and edit this file. You will see something like this ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-G0VGS de GB7MBC 28-Jan-2001 1308Z >
-stat/msg 6869
- From: GB7DJK
- Msg Time: 26-Jan-2001 1302Z
- Msgno: 6869
- Origin: GB7DJK
- Size: 8012
- Subject: AMSAT 2line KEPS 01025.AMSAT
- To: UK
-Got it Nodes: GB7BAA, GB7ADX
- Private: 0
-Read Confirm: 0
- Times read: 0
-G0VGS de GB7MBC 28-Jan-2001 1308Z >
+
+#!/usr/bin/perl
+
+# provide some standard aliases for commands for terminally
+# helpless ak1a user (helpless in the sense that they never
+# read nor understand help files)
+
+# This file is automagically reloaded if its modification time is
+# later than the one stored in CmdAlias.pm
+
+# PLEASE make this file consistant with reality! (the patterns MUST
+# match the filenames!)
+
+# Don't alter this file, copy it into the local_cmd tree and modify it.
+# This file will be replaced everytime I issue a new release.
+
+# You only need to put aliases in here for commands that don't work as
+# you desire naturally, e.g sh/dx on its own just works as you expect
+# so you need not add it as an alias.
+
+
+
+package CmdAlias;
+
+%alias = (
+ '?' => [
+ '^\?', 'apropos', 'apropos',
+ ],
+ 'a' => [
+ '^ann.*/full', 'announce full', 'announce',
+ '^ann.*/sysop', 'announce sysop', 'announce',
+ '^ann.*/(.*)$', 'announce $1', 'announce',
+ ],
+ 'b' => [
+ ],
+ 'c' => [
+ ],
+ 'd' => [
+ '^del', 'kill', 'kill',
+ '^del\w*/fu', 'kill full', 'kill',
+ '^di\w*/a\w*', 'directory all', 'directory',
+ '^di\w*/b\w*', 'directory bulletins', 'directory',
+ '^di\w*/n\w*', 'directory new', 'directory',
+ '^di\w*/o\w*', 'directory own', 'directory',
+ '^di\w*/s\w*', 'directory subject', 'directory',
+ '^di\w*/t\w*', 'directory to', 'directory',
+ '^di\w*/f\w*', 'directory from', 'directory',
+ '^di\w*/(\d+)', 'directory $1', 'directory',
+ ],
+ 'e' => [
+ ],
+ 'f' => [
+ ],
+ 'g' => [
+ ],
+ 'h' => [
+ ],
+ 'i' => [
+ ],
+ 'j' => [
+ ],
+ 'k' => [
+ ],
+ 'l' => [
+ '^l$', 'directory', 'directory',
+ '^ll$', 'directory', 'directory',
+ '^ll/(\d+)', 'directory $1', 'directory',
+ ],
+ 'm' => [
+ ],
+ 'n' => [
+ '^news', 'type news', 'type',
+ ],
+ 'o' => [
+ ],
+ 'p' => [
+ ],
+ 'q' => [
+ '^q', 'bye', 'bye',
+ ],
+ 'r' => [
+ '^r$', 'read', 'read',
+ '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
+ ],
+ 's' => [
+ '^s/p$', 'send', 'send',
+ '^sb$', 'send noprivate', 'send',
+ '^set/home$', 'set/homenode', 'set/homenode',
+ '^set/nobe', 'unset/beep', 'unset/beep',
+ '^set/nohe', 'unset/here', 'unset/here',
+ '^set/noan', 'unset/announce', 'unset/announce',
+ '^set/nodx', 'unset/dx', 'unset/dx',
+ '^set/nota', 'unset/talk', 'unset/talk',
+ '^set/noww', 'unset/wwv', 'unset/wwv',
+ '^set/nowx', 'unset/wx', 'unset/wx',
+ '^sh$', 'show', 'show',
+ '^sh\w*/buck', 'dbshow buck', 'dbshow',
+ '^sh\w*/bu', 'show/files bulletins', 'show/files',
+ '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
+ '^sh\w*/c$', 'show/configuration', 'show/configuration',
+ '^sh\w*/com', 'dbavail', 'dbavail',
+ '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
+ '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
+ '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
+ '^sh\w*/email', 'dbshow email', 'dbshow',
+ '^sh\w*/hftest', 'dbshow hftest', 'dbshow',
+ '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
+ '^sh\w*/qsl', 'dbshow qsl', 'dbshow',
+ '^sh\w*/tnc', 'who', 'who',
+ '^sh\w*/up', 'show/cluster', 'show/cluster',
+ '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
+ '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
+ '^sp$', 'send', 'send',
+
+ ],
+ 't' => [
+ '^ta$', 'talk', 'talk',
+ '^t$', 'talk', 'talk',
+ ],
+ 'u' => [
+ ],
+ 'v' => [
+ ],
+ 'w' => [
+ '^wx/full', 'wx full', 'wx',
+ '^wx/sysop', 'wx sysop', 'wx',
+ ],
+ 'x' => [
+ ],
+ 'y' => [
+ ],
+ 'z' => [
+ ],
+)
</PRE>
</CODE></BLOCKQUOTE>
+<P>You can create aliases for commands at will. Beware though, these may not
+always turn out as you think. Care is needed and you need to test the
+results once you have set an alias.
<P>
-<H2><A NAME="ss5.6">5.6 Filtering mail</A>
+<H2><A NAME="ss5.5">5.5 Console.pl</A>
</H2>
-<P>This is described in the section on <EM>Other filters</EM> so I will not
-duplicate it here.
+<P>In later versions of Spider a simple console program is provided for the sysop.
+This has a type ahead buffer with line editing facilities and colour for spots,
+announces etc. To use this program, simply use console.pl instead of client.
<P>
-<H2><A NAME="ss5.7">5.7 Distribution lists</A>
+<P>To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
+file with your favourite editor.
+<P>
+<H2><A NAME="ss5.6">5.6 Updating kepler data</A>
</H2>
-<P>Distribution lists are simply a list of users to send certain types of
-mail to. An example of this is mail you only wish to send to other
-sysops. In /spider/msg there is a directory called <EM>distro</EM>. You
-put any distibution lists in here. For example, here is a file called
-SYSOP.pl that caters for the UK sysops.
+<P>Spider has a powerful and flexible show/satellite command. In order for
+this to be accurate, the kepler data has to be updated regularly. In
+general, this data is available as an email or via cluster mail.
+Updating it is simple. First you need to export the mail message as a
+file. You do this with the <EM>export</EM> command from the cluster prompt
+as the sysop. For example ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+export 5467 /spider/perl/keps.in
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>would export message number 5467 as a file called keps.in in the
+/spider/perl directory.
+<P>Now login to a VT as sysop and cd /spider/perl. There is a command in
+the perl directory called <EM>convkeps.pl</EM>. All we need to do now is
+convert the file like so ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
- GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
- GB7DXK GB7DXI GB7DXS)
+./convkeps.pl keps.in
</PRE>
</CODE></BLOCKQUOTE>
-<P>Any mail sent to "sysop" would only be sent to the callsigns in this list.
+<P>Now go back to the cluster and issue the command ...
<P>
-<H2><A NAME="ss5.8">5.8 BBS interface</A>
+<BLOCKQUOTE><CODE>
+<PRE>
+load/keps
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>That is it! the kepler data has been updated.
+<P>
+<H2><A NAME="ss5.7">5.7 The QRZ callbook</A>
</H2>
-<P>Spider provides a simple BBS interface. No input is required from the sysop
-of the cluster at all. The BBS simply sets the cluster as a BBS and pushes
-any required mail to the cluster. No mail can flow from Spider to the BBS,
-the interface is one-way.
-<P>
-<P>Please be careful not to flood the cluster network with unnecessary mail.
-Make sure you only send mail to the clusters that want it by using the
-Forward.pl file very carefully.
+<P>The command <EM>sh/qrz</EM> will only work once you have followed a few
+simple steps. First you need to get a user ID and password from qrz.com.
+Simply go to the site and create one. Secondly you need to copy the file
+/spider/perl/Internet.pm to /spider/local and alter it to match your user
+ID and password. You also at this point need to set $allow=1 to complete
+the setup. Many thanks to Fred Lloyd, the proprieter of
+<A HREF="http://www.qrz.com">qrz.com</A> for allowing this access.
<P>
<HR>
<A HREF="adminmanual-6.html">Next</A>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.47: Databases</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.47: CVS</TITLE>
<LINK HREF="adminmanual-7.html" REL=next>
<LINK HREF="adminmanual-5.html" REL=previous>
<LINK HREF="adminmanual.html#toc6" REL=contents>
<A HREF="adminmanual-5.html">Previous</A>
<A HREF="adminmanual.html#toc6">Contents</A>
<HR>
-<H2><A NAME="s6">6. Databases</A></H2>
+<H2><A NAME="s6">6. CVS</A></H2>
-<P>Spider allows the creation of local or remote databases. It supports
-chained databases, allowing several different databases to be scanned
-with one simple command. Importing of databases is limited at present
-to the standard AK1A databases such as OBLAST and the DB0SDX QSL
-database but will expand with time.
-<P>
-<H2><A NAME="ss6.1">6.1 Creating databases</A>
-</H2>
-
-<P>Creating a database could not be more simple. All the commands are
-sent from the cluster prompt as the <EM>sysop</EM> user.
-<P>To create a database you use the command <EM>dbcreate</EM>. It can
-be used in 3 different ways like so ..
+<P>CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held
+at
+<A HREF="http://www.sourceforge.net">Sourceforge</A>. This means
+that it is possible to update your DXSpider installation to the latest
+sources by using a few simple commands.
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbcreate <name>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>To simply create a database locally, you just tell the command the
-name of the database. This does not create the actual database, it
-simply defines it to say that it exists.
+<P>THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST
+INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!!
+THIS MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!!
+YOU HAVE BEEN WARNED!!!
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbcreate <name> chain <name> [<name>...]
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>This creates a chained database entry. The first database will be
-scanned, then the second, the third etc...
+<P>DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE
+CONSEQUENCES!!!
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbcreate <name> remote <name>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>This creates a remote entry. the first name field is the database
-name at the remote node, then the remote switch, then the actual
-node_call of the remote node, for example...
+<P>I am of course assuming that you have a machine with both DXSpider and
+Internet access running.
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbcreate buckmaster remote gb7dxc
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Remote databases cannot be chained, however, the last database in a
-chain can be a remote database.
+<P>BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
+ENTIRE SPIDER TREE!!
<P>
-<H2><A NAME="ss6.2">6.2 Importing databases</A>
-</H2>
-
-<P>The only databases that Spider can currently import are the standard
-AK1A databases such as OBLAST or the DB0SDX qsl and address database.
-This will be added to with time.
-<P>To import such a database, first put the file somewhere useful like /tmp
-and then issue the following command ...
+<P>Assuming you are connected to the Internet, you need to login to the
+CVS repository and then update your Spider source. There are several
+steps which are listed below ...
+<P>
+<P>First login as the user <EM>sysop</EM>. Next you need to connect to the CVS
+repository. You do this with the command below ...
<P>
-<BLOCKQUOTE><CODE>
<PRE>
-dbimport oblast /tmp/OBLAST.FUL
+cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
</PRE>
-</CODE></BLOCKQUOTE>
-<P>This will update the existing local oblast database or create it if
-it does not exist.
+<P>You will get a password prompt. Simply hit return here and your machine should
+return to a normal linux prompt.
<P>
-<H2><A NAME="ss6.3">6.3 Checking available databases</A>
-</H2>
-
-<P>Once a database is created, you will want to check that it has been
-added. To do this use the <EM>dbavail</EM> command. This will
-output the available databases. For example ...
+<P>What happens next depends on whether you have an existing installation that
+you want to update with the latest and greatest or whether you just want
+to see what is there and/or run it on a new machine for testing.
+<P>If you are installing Spider from CVS then change directory to /home/sysop
+<P>If you are wanting to update Spider then cd to /tmp
+<P>
+<P>The next step will create a brand new 'spider' directory in your current
+directory.
<P>
-<BLOCKQUOTE><CODE>
<PRE>
-dbavail
-DB Name Location Chain
-qsl Local
-buck GB7ADX
-hftest GB7DXM
-G0VGS de GB7MBC 3-Feb-2001 1925Z >
+cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
</PRE>
-</CODE></BLOCKQUOTE>
+<P>This command is all on one line.
<P>
-<H2><A NAME="ss6.4">6.4 Looking up databases</A>
-</H2>
-
-<P>To look for information in a defined database, simply use the <EM>dbshow</EM>
-command, for example ...
+<P>Hopefully your screen should show you downloading files. The -z3 simply compresses
+the download to improve speed.
+When this has finished, you will have exactly the same as if you had untarred a full
+tarball PLUS some extra directories and files that CVS needs to do the magic that
+it does.
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbshow buckmaster G0YLM
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>will show the information for the callsign G0YLM from the buckmaster
-database if it exists. To make things more standard for the users
-you can add an entry in the Aliases file so that it looks like a standard
-<EM>show</EM> command like this ...
+<P>Now if you are doing a new installation, that's it. Carry on as if you have
+just downloaded and untarred the lastest tarball.
+<P>
+<P>If you want to upgrade your current installation then do this ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-'^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
+tar cvfz /tmp/s.tgz spider
+cd /
+tar xvfzp /tmp/s.tgz
</PRE>
</CODE></BLOCKQUOTE>
-<P>Now you can simply use show/buckmaster or an abreviation.
+<P>This is assuming you downloaded to the /tmp directory of course.
<P>
-<H2><A NAME="ss6.5">6.5 Removing databases</A>
-</H2>
-
-<P>To delete an existing database you use the <EM>dbremove</EM> command.
-For example ...
+<P>NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions
+correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????
+<P>Remember to recompile the C client (cd /spider/src; make)
+<P>
+<P>At this point the files have been upgraded. You can (usually) restart the cluster
+in your own time. However, if you attempt to use any new commands or features
+expect it to be fatal! At least your cluster will have been restarted then so it
+will be too late to worry about it!
+<P>
+<P>Now the magic part! From now on when you want to update, simply connect to the
+Internet and then, as the user <EM>sysop</EM> ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-dbremove oblast
+cd /spider
+cvs -z3 update -d
</PRE>
</CODE></BLOCKQUOTE>
-<P>would remove the oblast database and its associated datafile from the
-system. There are no warnings or recovery possible from this command.
-If you remove a database it ceases to exist and would have to be created
-from scratch if you still required it.
+<P>and your files will be updated. As above, remember to recompile the "C" client
+if it has been updated (CVS will tell you) and restart if any of the perl scripts
+have been altered or added, again, CVS will tell you.
+<P>
+<P>You will find any changes documented in the /spider/Changes file.
<P>
<HR>
<A HREF="adminmanual-7.html">Next</A>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.47: Information, files and useful programs</TITLE>
- <LINK HREF="adminmanual-8.html" REL=next>
+ <TITLE>The DXSpider Administration Manual v1.47: The DXSpider command set</TITLE>
<LINK HREF="adminmanual-6.html" REL=previous>
<LINK HREF="adminmanual.html#toc7" REL=contents>
<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
</HEAD>
<BODY>
-<A HREF="adminmanual-8.html">Next</A>
+Next
<A HREF="adminmanual-6.html">Previous</A>
<A HREF="adminmanual.html#toc7">Contents</A>
<HR>
-<H2><A NAME="s7">7. Information, files and useful programs</A></H2>
+<H2><A NAME="s7">7. The DXSpider command set</A></H2>
-<H2><A NAME="ss7.1">7.1 MOTD</A>
+<P>Below is a complete list of commands available from the cluster prompt.
+Most maintenance tasks are automatic but there are some commands that are useful
+for a sysop. These are listed below in alphabetical order. The number in
+brackets following the command name is the permissions level needed to use
+the command.
+<P>
+<H2><A NAME="ss7.1">7.1 accept/announce (0)</A>
+</H2>
+
+<P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter
+line for announce</CODE>
+<P>
+<P>Create an 'accept this announce' line for a filter.
+<P>An accept filter line means that if the announce matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/ann dest 6MUK
+ acc/ann 2 by_zone 14,15,16
+ (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>or
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/ann by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This filter would only allow announces that were posted buy UK stations.
+You can use the tag 'all' to accept everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/ann all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss7.2">7.2 accept/announce (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>accept/announce <call> [input] [0-9]<pattern></B> Announce filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/ann by G,M,2
+ accept/ann input node_default by G,M,2
+ accept/ann user_default by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.3">7.3 accept/route (8)</A>
+</H2>
+
+<P><CODE><B>accept/route <call> [0-9] <pattern></B> Set an 'accept' filter line for routing</CODE>
+<P>
+<P>Create an 'accept this routing PC Protocol' line for a filter.
+<P>
+<P>An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
+it is passed thru that interface. See HELP FILTERING for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ call <prefixes> the callsign of the thingy
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes> really the interface it came in on
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/route gb7djk call_zone 61,38 (send only UK+EIRE nodes)
+ acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>You can use the tag 'all' to accept everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/route all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.4">7.4 accept/spots (0)</A>
+</H2>
+
+<P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter line for spots</CODE>
+<P>
+<P>Create an 'accept this spot' line for a filter.
+<P>
+<P>An accept filter line means that if the spot matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>For frequencies, you can use any of the band names defined in
+SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+this is more efficient than saying simply: freq HF (but don't get
+too hung up about that)
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can use the tag 'all' to accept everything, eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 3 all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss7.5">7.5 accept/spots (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>accept/spots <call> [input] [0-9] <pattern></B> Spot filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/spot db0sue-7 1 by_zone 14,15,16
+ accept/spot node_default all
+ set/hops node_default 10
+
+ accept/spot user_default by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.6">7.6 accept/wcy (0)</A>
+</H2>
+
+<P><CODE><B>accept/wcy [0-9] <pattern></B> set an accept WCY filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>There are no examples because WCY Broadcasts only come from one place and
+you either want them or not (see UNSET/WCY if you don't want them).
+<P>This command is really provided for future use.
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss7.7">7.7 accept/wcy (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>accept/wcy <call> [input] [0-9] <pattern></B>
+WCY filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/wcy node_default all
+ set/hops node_default 10
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.8">7.8 accept/wwv (0)</A>
+</H2>
+
+<P><CODE><B>accept/wwv [0-9] <pattern></B> Set an accept WWV filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>for example
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/wwv by_zone 4
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>is probably the only useful thing to do (which will only show WWV broadcasts
+by stations in the US).
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss7.9">7.9 accept/wwv (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>accept/wwv <call> [input] [0-9] <pattern></B>
+WWV filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/wwv db0sue-7 1 by_zone 4
+ accept/wwv node_default all
+ set/hops node_default 10
+
+ accept/wwv user_default by W,K
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.10">7.10 announce (0)</A>
+</H2>
+
+<P><CODE><B>announce <text></B> Send an announcement to local users</CODE>
+<P>
+<P>Send an announcement to LOCAL users only, where <text> is the text
+of the announcement you wish to broadcast. If you do not wish to receive
+announces, use the <EM>set/noannounce</EM> command. Any announces made by
+a sysop will override set/noannounce.
+<P>
+<H2><A NAME="ss7.11">7.11 announce full (0)</A>
+</H2>
+
+<P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE>
+<P>
+<P>This command will send your announcement across the whole cluster
+network.
+<P>
+<P>
+<H2><A NAME="ss7.12">7.12 announce sysop (5)</A>
+</H2>
+
+<P><CODE><B>announce sysop <text></B></CODE>
+<P>
+<P>Send an announcement to Sysops only
+<P>
+<H2><A NAME="ss7.13">7.13 apropos (0)</A>
+</H2>
+
+<P><CODE><B>apropos <string></B> Search the help database</CODE>
+<P>
+<P>Search the help database for <string> (it isn't case sensitive),
+and print the names of all the commands that may be relevant.
+<P>
+<H2><A NAME="ss7.14">7.14 bye (0)</A>
+</H2>
+
+<P><CODE><B>bye</B> Exit from the cluster</CODE>
+<P>
+<P>This will disconnect you from the cluster
+<P>
+<H2><A NAME="ss7.15">7.15 catchup (5)</A>
+</H2>
+
+<P><CODE><B>catchup <node_call> All|[<msgno> ...]</B> Mark a message as sent</CODE>
+<P>
+<P>When you send messages the fact that you have forwarded it to another node
+is remembered so that it isn't sent again. When you have a new partner
+node and you add their callsign to your /spider/msg/forward.pl file, all
+outstanding non-private messages will be forwarded to them. This may well
+be ALL the non-private messages. You can prevent this by using these
+commmands:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ catchup GB7DJK all
+ catchup GB7DJK 300 301 302 303 500-510
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>and to undo what you have just done:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ uncatchup GB7DJK all
+ uncatchup GB7DJK 300 301 302 303 500-510
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>which will arrange for them to be forward candidates again.
+<P>Order is not important.
+<P>
+<H2><A NAME="ss7.16">7.16 clear/spots (0)</A>
+</H2>
+
+<P><CODE><B>clear/spots [1|all]</B> Clear a spot filter line</CODE>
+<P>
+<P>This command allows you to clear (remove) a line in a spot filter or to
+remove the whole filter.
+<P>If you have a filter:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>and you say:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ clear/spot 1
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>you will be left with:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>If you do:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ clear/spot all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>the filter will be completely removed.
+<P>
+<P>
+<H2><A NAME="ss7.17">7.17 connect (5) </A>
+</H2>
+
+<P><CODE><B>connect <callsign></B> Start a connection to another DX Cluster</CODE>
+<P>
+<P>Start a connection process that will culminate in a new connection to the
+DX cluster <callsign>. This process creates a new 'client' process which will
+use the script in /spider/connect/<callsign> to effect the 'chat' exchange
+necessary to traverse the network(s) to logon to the cluster <callsign>.
+<P>
+<H2><A NAME="ss7.18">7.18 dbavail (0)</A>
+</H2>
+
+<P><CODE><B>dbavail</B> Show a list of all the databases in the system</CODE>
+<P>
+<P>The title says it all really, this command lists all the databases defined
+in the system. It is also aliased to SHOW/COMMAND.
+<P>
+<H2><A NAME="ss7.19">7.19 dbcreate (9)</A>
+</H2>
+
+<P><CODE><B>dbcreate <name></B> Create a database entry<BR>
+<B>dbcreate <name> chain <name> [<name>..]</B> Create a chained database entry<BR>
+<B>dbcreate <name> remote <node></B> Create a remote database
+entry<BR></CODE>
+<P>
+<P>DBCREATE allows you to define a database in the system. It doesn't actually
+create anything, just defines it.
+<P>The databases that are created are simple DB_File hash databases, they are
+therefore already 'indexed'.
+<P>You can define a local database with the first form of the command eg:
+<P>DBCREATE oblast
+<P>You can also chain databases with the addition of the 'chain' keyword.
+This will search each database one after the other. A typical example
+is:
+<P>DBCREATE sdx_qsl chain sql_ad
+<P>No checking is done to see if the any of the chained databases exist, in
+fact it is usually better to do the above statement first then do each of
+the chained databases.
+<P>Databases can exist offsite. To define a database that lives on another
+node do:
+<P>DBCREATE buckmaster remote gb7dxc
+<P>Remote databases cannot be chained; however, the last database in a
+a chain can be a remote database eg:
+<P>DBCREATE qsl chain gb7dxc
+<P>To see what databases have been defined do:
+<P>DBAVAIL (or it will have been aliased to SHOW/COMMAND)
+<P>It would be normal for you to add an entry into your local Aliases file
+to allow people to use the 'SHOW/<dbname>' style syntax. So you would
+need to add a line like:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ 's' => [
+ ..
+ ..
+ '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
+ ..
+ ..
+ ],
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>to allow
+<P>SH/BUCK g1tlh
+<P>to work as they may be used to.
+<P>See DBIMPORT for the importing of existing AK1A format data to databases.
+See DBSHOW for generic database enquiry
+<P>
+<H2><A NAME="ss7.20">7.20 dbimport (9)</A>
+</H2>
+
+<P><CODE><B>dbimport <dbname></B> Import AK1A data into a database</CODE>
+<P>
+<P>If you want to import or update data in bulk to a database you can use
+this command. It will either create or update entries into an existing
+database. For example:-
+<P>DBIMPORT oblast /tmp/OBLAST.FUL
+<P>will import the standard OBLAST database that comes with AK1A into the
+oblast database held locally.
+<P>
+<H2><A NAME="ss7.21">7.21 dbremove (9)</A>
+</H2>
+
+<P><CODE><B>dbremove <dbname></B> Delete a database</CODE>
+<P>
+<P>DBREMOVE will completely remove a database entry and also delete any data
+file that is associated with it.
+<P>There is no warning, no comeback, no safety net.
+<P>For example:
+<P>DBREMOVE oblast
+<P>will remove the oblast database from the system and it will also remove
+the associated datafile.
+<P>I repeat:
+<P>There is no warning, no comeback, no safety net.
+<P>You have been warned.
+<P>
+<H2><A NAME="ss7.22">7.22 dbshow (0)</A>
+</H2>
+
+<P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE>
+<P>
+<P>This is the generic user interface to the database to the database system.
+It is expected that the sysop will add an entry to the local Aliases file
+so that users can use the more familiar AK1A style of enquiry such as:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/BUCK G1TLH
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but if he hasn't and the database really does exist (use DBAVAIL or
+SHOW/COMMAND to find out) you can do the same thing with:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBSHOW buck G1TLH
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>
+<H2><A NAME="ss7.23">7.23 debug (9)</A>
+</H2>
+
+<P><CODE><B>debug</B> Set the cluster program into debug mode</CODE>
+<P>
+<P>Executing this command will only have an effect if you are running the cluster
+in debug mode i.e.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ perl -d cluster.pl
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>It will interrupt the cluster just after the debug command has finished.
+<P>
+<H2><A NAME="ss7.24">7.24 directory (0)</A>
+</H2>
+
+<P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
+<B>directory own</B> List your own messages<BR>
+<B>directory new</B> List all new messages<BR>
+<B>directory to <call></B> List all messages to <call><BR>
+<B>directory from <call></B> List all messages from <call><BR>
+<B>directory subject <string></B> List all messages with <string> in subject<BR>
+<B>directory <nn></B> List last <nn> messages<BR>
+<B>directory <from>-<to></B> List messages <from> message <to> message <BR></CODE>
+<P>
+<P>List the messages in the messages directory.
+<P>If there is a 'p' one space after the message number then it is a
+personal message. If there is a '-' between the message number and the
+'p' then this indicates that the message has been read.
+<P>You can use shell escape characters such as '*' and '?' in the <call>
+fields.
+<P>You can combine some of the various directory commands together eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DIR TO G1TLH 5
+or
+ DIR SUBJECT IOTA 200-250
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can abbreviate all the commands to one letter and use ak1a syntax:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DIR/T G1* 10
+ DIR/S QSL 10-100 5
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>
+<H2><A NAME="ss7.25">7.25 directory (extended for sysops) (5)</A>
+</H2>
+
+<P>Works just like the user command except that sysops can see ALL messages.
+<P>
+<H2><A NAME="ss7.26">7.26 disconnect (8)</A>
+</H2>
+
+<P><CODE><B>disconnect <call> [<call> ...]</B> Disconnect a user or node</CODE>
+<P>
+<P>Disconnect any <call> connected locally
+<P>
+<H2><A NAME="ss7.27">7.27 dx (0)</A>
+</H2>
+
+<P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE>
+<P>
+<P>This is how you send a DX Spot to other users. You can, in fact, now
+enter the <freq> and the <call> either way round.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DX FR0G 144.600
+ DX 144.600 FR0G
+ DX 144600 FR0G
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will all give the same result. You can add some remarks to the end
+of the command and they will be added to the spot.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DX FR0G 144600 this is a test
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can credit someone else by saying:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The <freq> is compared against the available bands set up in the
+cluster. See SHOW/BANDS for more information.
+<P>
+<H2><A NAME="ss7.28">7.28 export (9)</A>
+</H2>
+
+<P><CODE><B>export <msgno> <filename></B> Export a message to a file</CODE>
+<P>
+<P>Export a message to a file. This command can only be executed on a local
+console with a fully privileged user. The file produced will be in a form
+ready to be imported back into the cluster by placing it in the import
+directory (/spider/msg/import).
+<P>This command cannot overwrite an existing file. This is to provide some
+measure of security. Any files written will owned by the same user as the
+main cluster, otherwise you can put the new files anywhere the cluster can
+access. For example:-
+<P>EXPORT 2345 /tmp/a
+<P>
+<H2><A NAME="ss7.29">7.29 export_users (9)</A>
+</H2>
+
+<P><CODE><B>export_users [<filename>]</B> Export the users database to ascii</CODE>
+<P>
+<P>Export the users database to a file in ascii format. If no filename
+is given then it will export the file to /spider/data/user_asc.
+<P>If the file already exists it will be renamed to <filename>.o. In fact
+up to 5 generations of the file can be kept each one with an extra 'o' on the
+suffix.
+<P>BE WARNED: this will write to any file you have write access to. No check is
+made on the filename (if any) that you specify.
+<P>
+<H2><A NAME="ss7.30">7.30 forward/latlong (8)</A>
+</H2>
+
+<P><CODE><B>forward/latlong <node_call></B> Send latitude and longitude information to another cluster</CODE>
+<P>
+<P>This command sends all the latitude and longitude information that your
+cluster is holding against callsigns. One advantage of recieving this
+information is that more locator information is held by you. This
+means that more locators are given on the DX line assuming you have
+<EM>set/dxgrid</EM> enabled. This could be a LOT of information though, so
+it is not recommended on slow links.
+<P>
+<H2><A NAME="ss7.31">7.31 forward/opername (1)</A>
+</H2>
+
+<P><CODE><B>forward/opername <call></B> Send out information on this <call> to all clusters</CODE>
+<P>
+<P>This command sends out any information held in the user file which can
+be broadcast in PC41 protocol packets. This information is Name, QTH, Location
+and Homenode. PC41s are only sent for the information that is available.
+<P>
+<H2><A NAME="ss7.32">7.32 help (0)</A>
+</H2>
+
+<P><CODE><B>help <cmd></B> Get help on a command</CODE>
+<P>
+<P>All commands can be abbreviated, so SHOW/DX can be abbreviated
+to SH/DX, ANNOUNCE can be shortened to AN and so on.
+<P>Look at the APROPOS <string> command which will search the help database
+for the <string> you specify and give you a list of likely commands
+to look at with HELP.
+<P>
+<H2><A NAME="ss7.33">7.33 init (5)</A>
+</H2>
+
+<P><CODE><B>init <node call></B> Re-initialise a link to an AK1A compatible node</CODE>
+<P>
+<P>This command attempts to re-initialise a link to a (usually) AK1A node
+that has got confused, usually by a protocol loop of some kind. It may
+work - but you usually will be better off simply disconnecting it (or
+better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
+node>).
+<P>Best of luck - you will need it.
+<P>
+<H2><A NAME="ss7.34">7.34 kill (0)</A>
+</H2>
+
+<P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE>
+<P>
+<P>Delete a message from the local system. You will only be able to
+delete messages that you have originated or been sent (unless you are
+the sysop).
+<P>
+<H2><A NAME="ss7.35">7.35 kill (5)</A>
+</H2>
+
+<P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system<BR>
+<B>kill from <call></B> Remove all messages from a callsign<BR>
+<B>kill to <call></B> Remove all messages to a callsign<BR></CODE>
+<P>
+<P>You can get rid of any message to or originating from your callsign using
+this command. You can remove more than one message at a time.
+<P>As a sysop you can kill any message on the system.
+<P>
+<H2><A NAME="ss7.36">7.36 kill full (5)</A>
+</H2>
+
+<P><CODE><B>kill full <msgno> [<msgno>]</B> Delete a message from the whole cluster</CODE>
+<P>
+<P>Delete a message (usually a 'bulletin') from the whole cluster system.
+<P>This uses the subject field, so any messages that have exactly the same subject
+will be deleted. Beware!
+<P>
+<H2><A NAME="ss7.37">7.37 links (0)</A>
+</H2>
+
+<P><CODE><B>links</B> Show which nodes are physically connected</CODE>
+<P>
+<P>This is a quick listing that shows which links are connected and
+some information about them. See WHO for a list of all connections.
+<P>
+<P>
+<H2><A NAME="ss7.38">7.38 load/aliases (9)</A>
+</H2>
+
+<P><CODE><B>load/aliases</B> Reload the command alias table</CODE>
+<P>
+<P>Reload the /spider/cmd/Aliases file after you have editted it. You will need to
+do this if you change this file whilst the cluster is running in order for the
+changes to take effect.
+<P>
+<P>
+<H2><A NAME="ss7.39">7.39 load/baddx (9)</A>
+</H2>
+
+<P><CODE><B>load/baddx</B> Reload the bad DX table</CODE>
+<P>
+<P>Reload the /spider/data/baddx.pl file if you have changed it manually whilst
+the cluster is running. This table contains the DX Calls that, if spotted,
+will not be passed on. FR0G and TEST are classic examples.
+<P>
+<H2><A NAME="ss7.40">7.40 load/badmsg (9)</A>
+</H2>
+
+<P><CODE><B>load/badmsg</B> Reload the bad message table</CODE>
+<P>
+<P>Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
+the cluster is running. This table contains a number of perl regular
+expressions which are searched for in the fields targetted of each message.
+If any of them match then that message is immediately deleted on receipt.
+<P>
+<H2><A NAME="ss7.41">7.41 load/badwords (9)</A>
+</H2>
+
+<P><CODE><B>load/badwords</B> Reload the badwords file</CODE>
+<P>
+<P>Reload the /spider/data/badwords file if you have changed it manually whilst
+the cluster is running. This file contains a list of words which, if found
+on certain text portions of PC protocol, will cause those protocol frames
+to be rejected. It will all put out a message if any of these words are
+used on the announce, dx and talk commands. The words can be one or
+more on a line, lines starting with '#' are ignored.
+<P>
+<H2><A NAME="ss7.42">7.42 load/bands (9)</A>
+</H2>
+
+<P><CODE><B>load/bands</B> Reload the band limits table</CODE>
+<P>
+<P>Reload the /spider/data/bands.pl file if you have changed it manually whilst
+the cluster is running.
+<P>
+<H2><A NAME="ss7.43">7.43 load/cmd_cache (9)</A>
+</H2>
+
+<P><CODE><B>load/cmd_cache</B> Reload the automatic command cache</CODE>
+<P>
+<P>Normally, if you change a command file in the cmd or local_cmd tree it will
+automatially be picked up by the cluster program. Sometimes it can get confused
+if you are doing a lot of moving commands about or delete a command in the
+local_cmd tree and want to use the normal one again. Execute this command to
+reset everything back to the state it was just after a cluster restart.
+<P>
+<H2><A NAME="ss7.44">7.44 load/forward (9)</A>
+</H2>
+
+<P><CODE><B>load/forward</B> Reload the msg forwarding routing table</CODE>
+<P>Reload the /spider/msg/forward.pl file if you have changed it
+manually whilst the cluster is running.
+<P>
+<H2><A NAME="ss7.45">7.45 load/messages (9)</A>
+</H2>
+
+<P><CODE><B>load/messages</B> Reload the system messages file</CODE>
+<P>
+<P>If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne
+commands) you can have them take effect during a cluster session by executing this
+command. You need to do this if get something like :-
+<P>unknown message 'xxxx' in lang 'en'
+<P>
+<H2><A NAME="ss7.46">7.46 load/prefixes (9)</A>
+</H2>
+
+<P><CODE><B>load/prefixes</B> Reload the prefix table</CODE>
+<P>
+<P>Reload the /spider/data/prefix_data.pl file if you have changed it manually
+whilst the cluster is running.
+<P>
+<H2><A NAME="ss7.47">7.47 merge (5)</A>
+</H2>
+
+<P><CODE><B>merge <node> [<no spots>/<no wwv>]</B> Ask for the latest spots and WWV</CODE>
+<P>
+<P>MERGE allows you to bring your spot and wwv database up to date. By default
+it will request the last 10 spots and 5 WWVs from the node you select. The
+node must be connected locally.
+<P>You can request any number of spots or wwv and although they will be appended
+to your databases they will not duplicate any that have recently been added
+(the last 2 days for spots and last month for WWV data).
+<P>
+<H2><A NAME="ss7.48">7.48 msg (9)</A>
+</H2>
+
+<P><CODE><B>msg <cmd> <msgno> [data ...]</B> Alter various message parameters</CODE>
+<P>
+<P>Alter message parameters like To, From, Subject, whether private or bulletin
+or return receipt (RR) is required or whether to keep this message from timing
+out.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ MSG TO <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - remove any waitting time for this message
+ MSG NOREad <msgno> - mark message as unread
+ MSG REad <msgno> - mark message as read
+ MSG QUeue - queue any outstanding bulletins
+ MSG QUeue 1 - queue any outstanding private messages
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can look at the status of a message by using:-
+<P>STAT/MSG <msgno>
+<P>This will display more information on the message than DIR does.
+<P>
+<H2><A NAME="ss7.49">7.49 pc (8)</A>
+</H2>
+
+<P><CODE><B>pc <call> <text></B> Send text (eg PC Protocol) to <call></CODE>
+<P>
+<P>Send some arbitrary text to a locally connected callsign. No processing is done on
+the text. This command allows you to send PC Protocol to unstick things if problems
+arise (messages get stuck etc). eg:-
+<P>pc gb7djk PC33^GB7TLH^GB7DJK^400^
+<P>You can also use in the same way as a talk command to a connected user but
+without any processing, added of "from <blah> to <blah>" or whatever.
+<P>pc G1TLH Try doing that properly!!!
+<P>
+<H2><A NAME="ss7.50">7.50 ping (1)</A>
+</H2>
+
+<P><CODE><B>ping <node></B> Check the link quality between nodes</CODE>
+<P>
+<P>his command allows you to send a frame to another cluster node on
+the network and get a return frame. The time it takes to do this
+is a good indication of the quality of the link. The actual time
+it takes is output to the console in seconds.
+Any visible cluster node can be PINGed.
+<P>
+<P>
+<H2><A NAME="ss7.51">7.51 rcmd (1)</A>
+</H2>
+
+<P><CODE><B>rcmd <node call> <cmd></B> Send a command to another DX cluster</CODE>
+<P>
+<P>This command allows you to send nearly any command to another DX Cluster
+node that is connected to the system.
+<P>Whether you get any output is dependant on a) whether the other system knows
+that the node callsign of this cluster is in fact a node b) whether the
+other system is allowing RCMDs from this node and c) whether you have
+permission to send this command at all.
+<P>
+<H2><A NAME="ss7.52">7.52 read (0)</A>
+</H2>
+
+<P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
+<B>read <msgno></B> Read the specified message<BR></CODE>
+<P>
+<P>You can read any messages that are sent as 'non-personal' and also any
+message either sent by or sent to your callsign.
+<P>
+<P>
+<H2><A NAME="ss7.53">7.53 read (extended for sysops) (5) </A>
+</H2>
+
+<P><CODE><B>read <msgno></B> Read a message on the system</CODE>
+<P>
+<P>As a sysop you may read any message on the system
+<P>
+<H2><A NAME="ss7.54">7.54 reject/announce</A>
+</H2>
+
+<P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
+for announce</CODE>
+<P>
+<P>Create an 'reject this announce' line for a filter.
+<P>An reject filter line means that if the announce matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/ann by_zone 14,15,16 and not by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can use the tag 'all' to reject everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/ann all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss7.55">7.55 reject/announce (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>reject/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ reject/ann by G,M,2
+ reject/ann input node_default by G,M,2
+ reject/ann user_default by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.56">7.56 reject/route (8)</A>
+</H2>
+
+<P><CODE><B>reject/route <call> [0-9] <pattern></B> Set an 'reject' filter line for routing</CODE>
+<P>
+<P>Create an 'reject this routing PC Protocol' line for a filter.
+<P>
+<P>An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
+it is NOT passed thru that interface. See HELP FILTERING for more info. Please
+read this to understand how filters work - it will save a lot of grief later on.
+You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ call <prefixes> the callsign of the thingy
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes> really the interface it came in on
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/route gb7djk call_zone 61,38 (everything except UK+EIRE nodes)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>You can use the tag 'all' to reject everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/route all (equiv to [very] restricted mode)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.57">7.57 reject/spots (0)</A>
+</H2>
+
+<P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE>
+<P>
+<P>Create a 'reject this spot' line for a filter.
+<P>A reject filter line means that if the spot matches this filter it is
+dumped (not passed on). See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>For frequencies, you can use any of the band names defined in
+SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+this is more efficient than saying simply: on HF (but don't get
+too hung up about that)
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/spot 1 on hf
+ rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can use the tag 'all' to reject everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/spot 3 all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss7.58">7.58 reject/spots (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>reject/spots <call> [input] [0-9] <pattern></B>
+Reject spot filter sysop version </CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ reject/spot db0sue-7 1 by_zone 14,15,16
+ reject/spot node_default all
+ set/hops node_default 10
+
+ reject/spot user_default by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.59">7.59 reject/wcy (0)</A>
+</H2>
+
+<P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>There are no examples because WCY Broadcasts only come from one place and
+you either want them or not (see UNSET/WCY if you don't want them).
+<P>This command is really provided for future use.
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss7.60">7.60 reject/wcy (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>reject/wcy <call> [input] [0-9] <pattern></B>
+WCY reject filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>reject/wcy gb7djk all
+<P>
+<H2><A NAME="ss7.61">7.61 reject/wwv (0)</A>
+</H2>
+
+<P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>for example
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ reject/wwv by_zone 14,15,16
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>is probably the only useful thing to do (which will only show WWV broadcasts
+by stations in the US).
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss7.62">7.62 reject/wwv (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>reject/wwv <call> [input] [0-9] <pattern></B>
+WWV reject filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ reject/wwv db0sue-7 1 by_zone 4
+ reject/wwv node_default all
+
+ reject/wwv user_default by W
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.63">7.63 reply (0)</A>
+</H2>
+
+<P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
+<B>reply <msgno></B> Reply (privately) to the specified message<BR>
+<B>reply B <msgno></B> Reply as a Bulletin to the specified message<BR>
+<B>reply NOPrivate <msgno></B> Reply as a Bulletin to the specified
+message<BR>
+<B>reply RR <msgno></B> Reply to the specified message with read receipt<BR></CODE>
+<P>
+<P>You can reply to a message and the subject will automatically have
+"Re:" inserted in front of it, if it isn't already present.
+<P>You can also use all the extra qualifiers such as RR, PRIVATE,
+NOPRIVATE, B that you can use with the SEND command (see SEND
+for further details)
+<P>
+<H2><A NAME="ss7.64">7.64 send (0)</A>
+</H2>
+
+<P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
+<B>send RR <call></B> Send a message and ask for a read receipt<BR>
+<B>send COPY <msgno> <call></B> Send a copy of a message to someone<BR>
+<B>send PRIVATE <call></B> Send a personal message<BR>
+<B>send NOPRIVATE <call></B> Send a message to all stations<BR></CODE>
+<P>
+<P>All the SEND commands will create a message which will be sent either to
+an individual callsign or to one of the 'bulletin' addresses.
+<P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
+it will mark the message as personal and send it to the cluster node that
+that callsign is connected to.
+<P>You can have more than one callsign in all of the SEND commands.
+<P>You can have multiple qualifiers so that you can have for example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SEND RR COPY 123 PRIVATE G1TLH G0RDI
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>which should send a copy of message 123 to G1TLH and G0RDI and you will
+receive a read receipt when they have read the message.
+<P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
+SP is an alias for SEND PRIVATE
+<P>
+<H2><A NAME="ss7.65">7.65 set/address (0)</A>
+</H2>
+
+<P><CODE><B>set/address <your_address></B> Record your postal address</CODE>
+<P>
+<P>Literally, record your address details on the cluster.
+<P>
+<H2><A NAME="ss7.66">7.66 set/announce (0)</A>
+</H2>
+
+<P><CODE><B>set/announce</B> Allow announce messages</CODE>
+<P>
+<P>Allow announce messages to arrive at your terminal.
+<P>
+<H2><A NAME="ss7.67">7.67 set/arcluster (5)</A>
+</H2>
+
+<P><CODE><B>set/arcluster <node_call> [<node_call> ...]</B> Make
+the node_call an AR-Cluster type node</CODE>
+<P>
+<P>Set the node_call as an AR-Cluster type node
+<P>
+<H2><A NAME="ss7.68">7.68 set/baddx (8)</A>
+</H2>
+
+<P><CODE><B>set/baddx <call></B> Stop words we do not wish to see in the callsign field
+of a dx spot being propagated</CODE>
+<P>
+<P>Setting a word as 'baddx' will prevent spots with that word in the callsign
+field of a DX spot from going any further. They will not be displayed and they
+will not be sent onto other nodes.
+<P>The word must be wriiten in full, no wild cards are allowed eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/baddx FORSALE VIDEO FR0G
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To allow a word again, use the following command ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ unset/baddx VIDEO
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.69">7.69 set/badnode (6)</A>
+</H2>
+
+<P><CODE><B>set/badnode <node_call></B> Stop spots from this node_call
+being propagated</CODE>
+<P>
+<P>Setting a callsign as a 'badnode' will prevent spots from that node
+going any further. They will not be displayed and they will not be
+sent onto other nodes.
+<P>The call can be a full or partial call (or a prefix), eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/badnode K1TTT
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will stop anything from K1TTT (including any SSID's)
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ unset/badnode K1TTT
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will allow spots from him again.
+<P>Use with extreme care. This command may well be superceded by FILTERing.
+<P>
+<H2><A NAME="ss7.70">7.70 set/badspotter (8)</A>
+</H2>
+
+<P><CODE><B>set/badspotter <call></B> Stop spots from this callsign being propagated</CODE>
+<P>
+<P>Setting a callsign as a 'badspotter' will prevent spots from this callsign
+going any further. They will not be displayed and they will not be
+sent onto other nodes.
+<P>The call must be written in full, no wild cards are allowed eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/badspotter VE2STN
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will stop anything from VE2STN. If you want SSIDs as well then you must
+enter them specifically.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ unset/badspotter VE2STN
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will allow spots from him again.
+<P>Use with extreme care. This command may well be superceded by FILTERing.
+<P>
+<H2><A NAME="ss7.71">7.71 set/beep (0)</A>
+</H2>
+
+<P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE>
+<P>
+<P>Add a beep to DX and other terminal messages.
+<P>
+<H2><A NAME="ss7.72">7.72 set/bbs (5)</A>
+</H2>
+
+<P><CODE><B>set/bbs <call> [<call>..]</B>Make <call> a BBS</CODE>
+<P>
+<H2><A NAME="ss7.73">7.73 set/clx (5)</A>
+</H2>
+
+<P><CODE><B>set/clx <node_call> [<node_call> ...]</B> Make
+the node_call a CLX type node</CODE>
+<P>
+<P>Set the node_call as a CLX type node
+<P>
+<H2><A NAME="ss7.74">7.74 set/debug (9)</A>
+</H2>
+
+<P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE>
+<P>
+<P>You can choose to log several different levels. The levels are
+<P>chan
+state
+msg
+cron
+connect
+<P>You can show what levels you are logging with the <EM>show/debug</EM>
+command.
+<P>You can remove a debug level with unset/debug <name>
+<P>
+<H2><A NAME="ss7.75">7.75 set/dx (0)</A>
+</H2>
+
+<P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE>
+<P>
+<P>You can stop DX messages with the <EM>unset/dx</EM> command
+<P>
+<H2><A NAME="ss7.76">7.76 set/dxgrid (0)</A>
+</H2>
+
+<P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE>
+<P>
+<P>Some logging programs do not like the additional information at
+the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
+command to remove the grid squares.
+<P>
+<H2><A NAME="ss7.77">7.77 set/dxnet (5)</A>
+</H2>
+
+<P><CODE><B>set/dxnet <node_call> [<node_call> ...]</B> Make
+the node_call a DXNet type node</CODE>
+<P>
+<P>Set the node_call as a DXNet type node
+<P>
+<H2><A NAME="ss7.78">7.78 set/echo (0)</A>
+</H2>
+
+<P><CODE><B>set/echo</B> Make the cluster echo your input</CODE>
+<P>
+<P>If you are connected via a telnet session, different implimentations
+of telnet handle echo differently depending on whether you are
+connected via port 23 or some other port. You can use this command
+to change the setting appropriately.
+<P>You can remove the echo with the <EM>unset/echo</EM> command
+<P>The setting is stored in your user profile.
+<P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
+<P>
+<H2><A NAME="ss7.79">7.79 set/here (0)</A>
+</H2>
+
+<P><CODE><B>set/here</B> Set the here flag</CODE>
+<P>
+<P>Let others on the cluster know you are here by only displaying your
+callsign. If you are away from your terminal you can use the <EM>unset/here</EM>
+command to let people know you are away. This simply puts brackets
+around your callsign to indicate you are not available.
+<P>
+<H2><A NAME="ss7.80">7.80 set/homenode (0)</A>
+</H2>
+
+<P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE>
+<P>
+<P>Tell the cluster system where you normally connect to. Any Messages sent
+to you will normally find their way there should you not be connected.
+eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/HOMENODE gb7djk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.81">7.81 set/hops (8)</A>
+</H2>
+
+<P><CODE><B>set/hops <node_call> ann|spots|wwv|wcy <n></B>
+Set hop count</CODE>
+<P>
+<P>Set the hop count for a particular type of broadcast for a node.
+<P>This command allows you to set up special hop counts for a node
+for currently: announce, spots, wwv and wcy broadcasts.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+eg:
+ set/hops gb7djk ann 10
+ set/hops gb7mbc spots 20
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Set SHOW/HOPS for information on what is already set. This command
+creates a filter and works in conjunction with the filter system.
+<P>
+<H2><A NAME="ss7.82">7.82 set/isolate (9)</A>
+</H2>
+
+<P><CODE><B>set/isolate <node call></B> Isolate a node from the rest of the network</CODE>
+<P>
+<P>Connect a node to your system in such a way that you are a full protocol
+member of its network and can see all spots on it, but nothing either leaks
+out from it nor goes back into from the rest of the nodes connected to you.
+<P>You can potentially connect several nodes in this way.
+<P>You can see which nodes are isolated with the show/isolate (1) command.
+<P>You can remove the isolation with the command unset/isolate.
+<P>
+<H2><A NAME="ss7.83">7.83 set/language (0)</A>
+</H2>
+
+<P><CODE><B>set/language <language></B> Set the language you wish to use</CODE>
+<P>
+<P>You can select the language that you want the cluster to use. Currently
+the languages available are <EM>en</EM> (English) and <EM>nl</EM> (Dutch).
+<P>
+<H2><A NAME="ss7.84">7.84 set/location (0)</A>
+</H2>
+
+<P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE>
+<P>
+<P>You can set your latitude and longitude manually or alternatively use the
+<EM>set/qra</EM> command which will do the conversion for you.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/location 54 04 N 2 02 E
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>
+<H2><A NAME="ss7.85">7.85 set/sys_location (9)</A>
+</H2>
+
+<P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE>
+<P>
+<P>In order to get accurate headings and such like you must tell the system
+what your latitude and longitude is. If you have not yet done a SET/QRA
+then this command will set your QRA locator for you. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/LOCATION 52 22 N 0 57 E
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.86">7.86 set/logininfo (0)</A>
+</H2>
+
+<P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE>
+<P>
+<P>Show users and nodes when they log in and out of the local cluster. You
+can stop these messages by using the <EM>unset/logininfo</EM> command.
+<P>
+<P>
+<H2><A NAME="ss7.87">7.87 set/lockout (9)</A>
+</H2>
+
+<P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE>
+<P>
+<P>You can show who is locked out with the <EM>show/lockout</EM> command.
+To allow the user to connect again, use the <EM>unset/lockout</EM> command.
+<P>
+<H2><A NAME="ss7.88">7.88 set/name (0)</A>
+</H2>
+
+<P><CODE><B>set/name <your_name></B> Set your name</CODE>
+<P>
+<P>Tell the cluster what your name is, eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/name Dirk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.89">7.89 set/node (9)</A>
+</H2>
+
+<P><CODE><B>set/node <call> [<call> ...]</B> Make the callsign an AK1A cluster</CODE>
+<P>
+<P>Tell the system that the call(s) are to be treated as AK1A cluster and
+fed PC Protocol rather normal user commands.
+<P>From version 1.41 you can also set the following types of cluster
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/spider
+ set/dxnet
+ set/clx
+ set/arcluster
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To see what your nodes are set to, use the <EM>show/nodes</EM> command.
+<P>
+<H2><A NAME="ss7.90">7.90 set/obscount (9)</A>
+</H2>
+
+<P><CODE><B>set/obscount <count> <node call></B> Set the 'pump-up' obsolescence counter</CODE>
+<P>
+<P>From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see
+SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
+counter which is decremented on every outgoing ping and then reset to
+the 'obscount' value on every incoming ping. The default value of this
+parameter is 2.
+<P>What this means is that a neighbouring node will be pinged twice at
+(default) 300 second intervals and if no reply has been heard just before
+what would be the third attempt, that node is disconnected.
+<P>If a ping is heard then the obscount is reset to the full value. Using
+default values, if a node has not responded to a ping within 15 minutes,
+it is disconnected.
+<P>
+<H2><A NAME="ss7.91">7.91 set/page (0)</A>
+</H2>
+
+<P><CODE><B>set/page <n></B> Set the number of lines per page</CODE>
+<P>
+<P>Tell the system how many lines you wish on a page when the number of lines
+of output from a command is more than this. The default is 20. Setting it
+explicitly to 0 will disable paging.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/PAGE 30
+ SET/PAGE 0
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The setting is stored in your user profile.
+<P>
+<P>
+<H2><A NAME="ss7.92">7.92 set/password (9)</A>
+</H2>
+
+<P><CODE><B>set/password <callsign> <string></B> Set a users password</CODE>
+<P>
+<P>The password for a user can only be set by a full sysop. The string
+can contain any characters but any spaces are removed (you can type in
+spaces - but they won't appear in the password). You can see the
+result with STAT/USER. The password is the usual 30 character baycom
+type password.
+<P>
+<H2><A NAME="ss7.93">7.93 set/pinginterval (9)</A>
+</H2>
+
+<P><CODE><B>set/pinginterval <time> <node call></B> Set the ping time to neighbouring nodes</CODE>
+<P>
+<P>As from version 1.35 all neighbouring nodes are pinged at regular intervals
+in order to determine the rolling quality of the link and, in future, to
+affect routing decisions. The default interval is 300 secs or 5 minutes.
+<P>You can use this command to set a different interval. Please don't.
+<P>But if you do the value you enter is treated as minutes up 60 and seconds
+for numbers greater than that.
+<P>This is used also to help determine when a link is down at the far end
+(as certain cluster software doesn't always notice), see SET/OBSCOUNT
+for more information.
+<P>
+<H2><A NAME="ss7.94">7.94 set/privilege (9)</A>
+</H2>
+
+<P><CODE><B>set/privilege <n> <call> [<call> ...]</B> Set the privilege level on a call</CODE>
+<P>
+<P>Set the privilege level on a callsign. The privilege levels that pertain
+to commands are as default:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ 0 - normal user
+ 1 - allow remote nodes normal user RCMDs
+ 5 - various privileged commands (including shutdown, but not disc-
+ connect), the normal level for another node.
+ 8 - more privileged commands (including disconnect)
+ 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
+ LEVEL.
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>If you are a sysop and you come in as a normal user on a remote connection
+your privilege will automatically be set to 0.
+<P>
+<H2><A NAME="ss7.95">7.95 set/spider (5)</A>
+</H2>
+
+<P><CODE><B>set/spider <node_call> [<node_call> ...]</B> Make
+the node_call a DXSpider type node</CODE>
+<P>
+<P>Set the node_call as a DXSpider type node
+<P>
+<H2><A NAME="ss7.96">7.96 set/sys_qra (9)</A>
+</H2>
+
+<P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA locator</CODE>
+<P>
+<H2><A NAME="ss7.97">7.97 set/qra (0)</A>
+</H2>
+
+<P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE>
+<P>
+<P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
+done a SET/LOCATION then your latitude and longitude will be set roughly
+correctly (assuming your locator is correct ;-). For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/QRA JO02LQ
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.98">7.98 set/qth (0)</A>
+</H2>
+
+<P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE>
+<P>
+<P>Tell the system where your are. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/qth East Dereham, Norfolk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.99">7.99 set/talk (0)</A>
+</H2>
+
+<P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE>
+<P>
+<P>Allow talk messages to arrive at your console. You can switch off
+talks with the <EM>unset/talk</EM> command.
+<P>
+<H2><A NAME="ss7.100">7.100 set/wcy (0)</A>
+</H2>
+
+<P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE>
+<P>
+<P>Allow WCY information to be seen at your console. You can switch off
+WCY messages with the <EM>unset/wcy</EM> command.
+<P>
+<H2><A NAME="ss7.101">7.101 set/wwv (0)</A>
+</H2>
+
+<P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE>
+<P>
+<P>Allow WWV information to be seen at your console. You can switch off
+WWV messages with the <EM>unset/wwv</EM> command.
+<P>
+<H2><A NAME="ss7.102">7.102 set/wx (0)</A>
+</H2>
+
+<P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE>
+<P>
+<P>Allow WX information to be seen at your console. You can switch off
+WX messages with the <EM>unset/wx</EM> command.
+<P>
+<H2><A NAME="ss7.103">7.103 show/baddx (1)</A>
+</H2>
+
+<P><CODE><B>show/baddx</B>Show all the bad dx calls in the system</CODE>
+<P>
+<P>Display all the bad dx callsigns in the system, see SET/BADDX
+for more information.
+<P>
+<H2><A NAME="ss7.104">7.104 show/badnode (6)</A>
+</H2>
+
+<P><CODE><B>show/badnode</B> Show all the bad nodes in the system</CODE>
+<P>
+<P>Display all the bad node callsigns in the system, see SET/BADNODE
+for more information.
+<P>
+<H2><A NAME="ss7.105">7.105 show/badspotter (1)</A>
+</H2>
+
+<P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE>
+<P>
+<P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
+for more information.
+<P>
+<H2><A NAME="ss7.106">7.106 show/configuration (0)</A>
+</H2>
+
+<P><CODE><B>show/configuration [<node>]</B> Show all visible nodes and their users</CODE>
+<P>
+<P>This command allows you to see all the users that can be seen
+and the nodes to which they are connected. With the optional <EM>node</EM>,
+you can specify a particular node to look at.
+<P>This command is normally abbreviated to: sh/c
+<P>BE WARNED: the list that is returned can be VERY long
+<P>
+<H2><A NAME="ss7.107">7.107 show/configuration/node (0)</A>
+</H2>
+
+<P><CODE><B>show/configuration/node</B> Show all the nodes connected</CODE>
+<P>
+<P>Show all the nodes connected locally and the nodes they have connected.
+<P>
+<H2><A NAME="ss7.108">7.108 show/connect (1)</A>
+</H2>
+
+<P><CODE><B>show/connect</B> Show all the active connections</CODE>
+<P>
+<P>This command shows information on all the active connections known to
+the node. This command gives slightly more information than WHO.
+<P>
+<H2><A NAME="ss7.109">7.109 show/date (0)</A>
+</H2>
+
+<P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
+the local time</CODE>
+<P>
+<P>This is very nearly the same as SHOW/TIME, the only difference the format
+of the date string if no arguments are given.
+<P>If no prefixes or callsigns are given then this command returns the local
+time and UTC as the computer has it right now. If you give some prefixes
+then it will show UTC and UTC + the local offset (not including DST) at
+the prefixes or callsigns that you specify.
+<P>
+<H2><A NAME="ss7.110">7.110 show/debug (9)</A>
+</H2>
+
+<P><CODE><B>show/debug</B> Show what levels of debug you are logging</CODE>
+<P>
+<P>The levels can be set with <EM>set/debug</EM>
+<P>
+<H2><A NAME="ss7.111">7.111 show/dx (0)</A>
+</H2>
+
+<P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE>
+<P>
+<P>If you just type SHOW/DX you will get the last so many spots
+(sysop configurable, but usually 10).
+<P>In addition you can add any number of these options in very nearly
+any order to the basic SHOW/DX command, they are:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+on <band> - eg 160m 20m 2m 23cm 6mm
+on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
+
+<number> - the number of spots you want
+<from>-<to> - <from> spot no <to> spot no in
+ the selected list
+
+<prefix> - for a spotted callsign beginning with <prefix>
+*<suffix> - for a spotted callsign ending in <suffix>
+*<string>* - for a spotted callsign containing <string>
+
+day <number> - starting <number> days ago
+day <from>-<to> - <from> days <to> days ago
+
+info <text> - any spots containing <text> in the info or remarks
+
+by <call> - any spots spotted by <call> (spotter <call>
+ is the same).
+
+qsl - this automatically looks for any qsl info on the call
+ held in the spot database.
+
+iota [<iota>] - If the iota island number is missing it will
+ look for the string iota and anything which looks like
+ an iota island number. If you specify then it will look
+ for that island.
+
+qra [<locator>] - this will look for the specific locator if
+ you specify one or else anything that looks like a locator.
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>e.g.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+ SH/DX 9m0
+ SH/DX on 20m info iota
+ SH/DX 9a on vhf day 30
+ SH/DX rf1p qsl
+ SH/DX iota
+ SH/DX iota eu-064
+ SH/DX qra jn86
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.112">7.112 show/dxcc (0)</A>
+</H2>
+
+<P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE>
+<P>
+<P>This command takes the <prefix> (which can be a full or partial
+callsign if desired), looks up which internal country number it is
+and then displays all the spots as per SH/DX for that country.
+<P>The options for SHOW/DX also apply to this command.
+e.g.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+ SH/DXCC G
+ SH/DXCC W on 20m info iota
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.113">7.113 show/files (0)</A>
+</H2>
+
+<P><CODE><B>show/files [<filearea> [<string>]]</B> List
+the contents of a filearea</CODE>
+<P>
+<P>SHOW/FILES on its own will show you a list of the various fileareas
+available on the system. To see the contents of a particular file
+area type:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/FILES <filearea>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>where <filearea> is the name of the filearea you want to see the
+contents of.
+<P>You can also use shell globbing characters like '*' and '?' in a
+string to see a selection of files in a filearea eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/FILES bulletins arld*
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>See also TYPE - to see the contents of a file.
+<P>
+<H2><A NAME="ss7.114">7.114 show/filter (0)</A>
+</H2>
+
+<P><CODE><B>show/filter</B> Show the filters you have set</CODE>
+<P>
+<P>Show the contents of all the filters that are set by you. This command
+displays all the filters set - for all the various categories.
+<P>
+<H2><A NAME="ss7.115">7.115 show/filter (extended for sysops) (5)</A>
+</H2>
+
+<P><CODE><B>show/filter <callsign></B> Show the filters set by <callsign></CODE>
+<P>
+<P>A sysop can look at any filters that have been set.
+<P>
+<H2><A NAME="ss7.116">7.116 show/hops (8)</A>
+</H2>
+
+<P><CODE><B>show/hops <node_call> [ann|spots|wcy|wwv|]</B> Show the hop counts for a node</CODE>
+<P>
+<P>This command shows the hop counts set up for a node. You can specify
+which category you want to see. If you leave the category out then
+all the categories will be listed.
+<P>
+<H2><A NAME="ss7.117">7.117 show/isolate (1)</A>
+</H2>
+
+<P><CODE><B>show/isolate</B> Show a list of isolated nodes</CODE>
+<P>
+<P>Show which nodes are currently set to be isolated.
+<P>
+<H2><A NAME="ss7.118">7.118 show/lockout (9)</A>
+</H2>
+
+<P><CODE><B>show/lockout</B> Show a list of excluded callsigns</CODE>
+<P>
+<P>Show a list of callsigns that have been excluded (locked out) of the
+cluster locally with the <EM>set/lockout</EM> command
+<P>
+<H2><A NAME="ss7.119">7.119 show/log (8)</A>
</H2>
-<P>One of the more important things a cluster sysop needs to do is to get
-information to his users. The simplest way to do this is to have a banner
-that is sent to the user on login. This is know as a "message of the day"
-or "motd". To set this up, simply create a file in /spider/data called motd
-and edit it to say whatever you want. It is purely a text file and will be
-sent automatically to anyone logging in to the cluster.
+<P><CODE><B>show/log [<callsign>]</B> Show excerpts from the system log</CODE>
+<P>
+<P>This command outputs a short section of the system log. On its own
+it will output a general logfile. With the optional callsign it will
+show output from the log associated with that callsign.
<P>
-<H2><A NAME="ss7.2">7.2 Downtime message</A>
+<H2><A NAME="ss7.120">7.120 show/moon (0)</A>
</H2>
-<P>If for any reason the cluster is down, maybe for upgrade or maintenance but
-the machine is still running, a message can be sent to the user advising them
-of the fact. This message lives in the /spider/data directory and is called
-"offline". Simply create the file and edit it to say whatever you wish.
-This file will be sent to a user attempting to log into the cluster when
-DXSpider is not actually running.
+<P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
+rise and set times</CODE>
+<P>
+<P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
+together with the azimuth and elevation of the sun currently at those
+locations.
+<P>If you don't specify any prefixes or callsigns, it will show the times for
+your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
+together with the current azimuth and elevation.
+<P>In addition, it will show the gain or loss dB relative to the nominal
+distance of 385,000Km due to the ellipsoidal nature of the orbit.
+<P>If all else fails it will show the Moonrise and set times for the node
+that you are connected to.
+<P>For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MOON
+ SH/MOON G1TLH W5UN
+</PRE>
+</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss7.3">7.3 Other text messages</A>
+<H2><A NAME="ss7.121">7.121 show/muf (0)</A>
</H2>
-<P>You can set other text messages to be read by the user if they input the file
-name. This could be for news items or maybe information for new users.
-To set this up, make a directory under /spider called <EM>packclus</EM>.
-Under this directory you can create files called <EM>news</EM> or <EM>newuser</EM>
-for example. In fact you can create files with any names you like. These can
-be listed by the user with the command ....
+<P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
+the likely propagation to <prefix></CODE>
+<P>
+<P>This command allow you to estimate the likelihood of you contacting
+a station with the prefix you have specified. The output assumes a modest
+power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
+<P>The result predicts the most likely operating frequencies and signal
+levels for high frequency (shortwave) radio propagation paths on
+specified days of the year and hours of the day. It is most useful for
+paths between 250 km and 6000 km, but can be used with reduced accuracy
+for paths shorter or longer than this.
+<P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
+used to predict the MUF given the predicted flux, day of the year,
+hour of the day and geographic coordinates of the transmitter and
+receiver. This routine is reasonably accurate for the purposes here,
+with a claimed RMS error of 3.8 MHz, but much smaller and less complex
+than the programs used by major shortwave broadcasting organizations,
+such as the Voice of America.
+<P>The command will display some header information detailing its
+assumptions, together with the locations, latitude and longitudes and
+bearings. It will then show UTC (UT), local time at the other end
+(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
+(Zen) and the likely signal strengths. Then for each frequency for which
+the system thinks there is a likelihood of a circuit it prints a value.
+<P>The value is currently a likely S meter reading based on the conventional
+6dB / S point scale. If the value has a '+' appended it means that it is
+1/2 an S point stronger. If the value is preceeded by an 'm' it means that
+there is likely to be much fading and by an 's' that the signal is likely
+to be noisy.
+<P>By default SHOW/MUF will show the next two hours worth of data. You
+can specify anything up to 24 hours worth of data by appending the no of
+hours required after the prefix. For example:-
<P>
<BLOCKQUOTE><CODE>
<PRE>
-show/files
+ SH/MUF W
</PRE>
</CODE></BLOCKQUOTE>
-<P>They can be read by the user by typing the command ....
+<P>produces:
<P>
<BLOCKQUOTE><CODE>
<PRE>
-type news
+ RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
+ Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
+ Location Lat / Long Azim
+ East Dereham, Norfolk 52 41 N 0 57 E 47
+ United-States-W 43 0 N 87 54 W 299
+ UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
+ 18 23 11.5 -35 mS0+ mS2 S3
+ 19 0 11.2 -41 mS0+ mS2 S3
</PRE>
</CODE></BLOCKQUOTE>
-<P>If the file they want to read is called <EM>news</EM>. You could also set
-an alias for this in the Alias file to allow them just to type <EM>news</EM>
+<P>indicating that you will have weak, fading circuits on top band and
+80m but usable signals on 40m (about S3).
+<P>inputing:-
<P>
-<P>You can also store other information in this directory, either directly or
-nested under directories. One use for this would be to store DX bulletins
-such as the OPDX bulletins. These can be listed and read by the user.
-To keep things tidy, make a directory under /spider/packclus called
-<EM>bulletin</EM>. Now copy any OPDX or similar bulletins into it. These
-can be listed by the user in the same way as above using the <EM>show/files</EM>
-command with an extension for the bulletin directory you have just created,
-like this ....
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MUF W 24
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will get you the above display, but with the next 24 hours worth of
+propagation data.
<P>
<BLOCKQUOTE><CODE>
<PRE>
-show/files bulletin
+ SH/MUF W L 24
+ SH/MUF W 24 Long
</PRE>
</CODE></BLOCKQUOTE>
+<P>Gives you an estimate of the long path propagation characterics. It
+should be noted that the figures will probably not be very useful, nor
+terrible accurate, but it is included for completeness.
+<P>
+<H2><A NAME="ss7.122">7.122 show/node (1)</A>
+</H2>
+
+<P><CODE><B>show/node [<node_call> ...]</B> Show the type and version
+number of nodes</CODE>
+<P>
+<P>Show the type and version (if connected) of the nodes specified on the
+command line. If no callsigns are specified then a sorted list of all
+the non-user callsigns known to the system will be displayed.
+<P>
+<H2><A NAME="ss7.123">7.123 show/prefix (0)</A>
+</H2>
+
+<P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE>
<P>
-<P>An example would look like this ....
+<P>This command takes the <callsign> (which can be a full or partial
+callsign or a prefix), looks up which internal country number
+it is and then displays all the relevant prefixes for that country
+together with the internal country no, the CQ and ITU regions.
+<P>See also SHOW/DXCC
+<P>
+<P>
+<H2><A NAME="ss7.124">7.124 show/program (5)</A>
+</H2>
+
+<P><CODE><B>show/program</B> Show the locations of all the included program modules</CODE>
+<P>
+<P>Show the name and location where every program module was load from. This
+is useful for checking where you think you have loaded a .pm file from.
+<P>
+<H2><A NAME="ss7.125">7.125 show/qra (0)</A>
+</H2>
+
+<P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
+between locators<BR>
+<B>show/qra <lat> <long></B> Convert latitude and longitude to a locator</CODE>
+<P>
+<P>This is a multipurpose command that allows you either to calculate the
+distance and bearing between two locators or (if only one locator is
+given on the command line) the distance and beraing from your station
+to the locator. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+SH/QRA IO92QL
+SH/QRA JN06 IN73
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The first example will show the distance and bearing to the locator from
+yourself, the second example will calculate the distance and bearing from
+the first locator to the second. You can use 4 or 6 character locators.
+<P>It is also possible to convert a latitude and longitude to a locator by
+using this command with a latitude and longitude as an argument, for
+example:-
<P>
<BLOCKQUOTE><CODE>
<PRE>
-sh/files
-bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
+SH/QRA 52 41 N 0 58 E
</PRE>
</CODE></BLOCKQUOTE>
-<P>You can see that in the files area (basically the packclus directory) there is a
-file called <EM>news</EM> and a directory called <EM>bulletin</EM>. You can
-also see that dates they were created. In the case of the file <EM>news</EM>,
-you can also see the time it was last modified, a good clue as to whether the
-file has been updated since you last read it. To read the file called
-<EM>news</EM> you would simply issue the command ....
+<P>
+<H2><A NAME="ss7.126">7.126 show/qrz (0)</A>
+</H2>
+
+<P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE>
+<P>
+<P>This command queries the QRZ callbook server on the internet
+and returns any information available for that callsign. This service
+is provided for users of this software by http://www.qrz.com
+<P>
+<H2><A NAME="ss7.127">7.127 show/route (0)</A>
+</H2>
+
+<P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE>
+<P>
+<P>This command allows you to see to which node the callsigns specified are
+connected. It is a sort of inverse sh/config.
<P>
<BLOCKQUOTE><CODE>
<PRE>
-type news
+ sh/route n2tly
</PRE>
</CODE></BLOCKQUOTE>
-<P>To look what is in the bulletin directory you issue the command ....
+<P>
+<H2><A NAME="ss7.128">7.128 show/satellite (0)</A>
+</H2>
+
+<P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
+Show satellite tracking data</CODE>
+<P>
+<P>Show the tracking data from your location to the satellite of your choice
+from now on for the next few hours.
+<P>If you use this command without a satellite name it will display a list
+of all the satellites known currently to the system.
+<P>If you give a name then you can obtain tracking data of all the passes
+that start and finish 5 degrees below the horizon. As default it will
+give information for the next three hours for every five minute period.
+<P>You can alter the number of hours and the step size, within certain
+limits.
+<P>Each pass in a period is separated with a row of '-----' characters
+<P>So for example:-
<P>
<BLOCKQUOTE><CODE>
<PRE>
-show/files bulletin
-opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
-opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
-opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
-opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
-opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
-opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
-opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
-opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
-opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
-opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
-opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
-opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
-opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
-Press Enter to continue, A to abort (16 lines) >
+SH/SAT AO-10
+SH/SAT FENGYUN1 12 2
</PRE>
</CODE></BLOCKQUOTE>
-<P>You can now read any file in this directory using the type command, like this ....
+<P>
+<H2><A NAME="ss7.129">7.129 show/sun (0)</A>
+</H2>
+
+<P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
+sun rise and set times</CODE>
+<P>
+<P>Show the sun rise and set times for a (list of) prefixes or callsigns,
+together with the azimuth and elevation of the sun currently at those
+locations.
+<P>If you don't specify any prefixes or callsigns, it will show the times for
+your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
+together with the current azimuth and elevation.
+<P>If all else fails it will show the sunrise and set times for the node
+that you are connected to.
+<P>For example:-
<P>
<BLOCKQUOTE><CODE>
<PRE>
-type bulletin/opdx391
-Ohio/Penn DX Bulletin No. 391
-The Ohio/Penn Dx PacketCluster
-DX Bulletin No. 391
-BID: $OPDX.391
-January 11, 1999
-Editor Tedd Mirgliotta, KB8NW
-Provided by BARF-80 BBS Cleveland, Ohio
-Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
-Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
-Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
-& The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
-Press Enter to continue, A to abort (508 lines) >
+ SH/SUN
+ SH/SUN G1TLH K9CW ZS
</PRE>
</CODE></BLOCKQUOTE>
-<P>The page length will of course depend on what you have it set to!
<P>
-<H2><A NAME="ss7.4">7.4 The Aliases file</A>
+<H2><A NAME="ss7.130">7.130 show/time (0)</A>
+</H2>
+
+<P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
+the local time</CODE>
+<P>
+<P>If no prefixes or callsigns are given then this command returns the local
+time and UTC as the computer has it right now. If you give some prefixes
+then it will show UTC and UTC + the local offset (not including DST) at
+the prefixes or callsigns that you specify.
+<P>
+<H2><A NAME="ss7.131">7.131 show/wcy (0)</A>
+</H2>
+
+<P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
+<B>show/wcy <n></B> Show the last <n> WCY broadcasts</CODE>
+<P>
+<P>Display the most recent WCY information that has been received by the system
+<P>
+<H2><A NAME="ss7.132">7.132 show/wwv (0)</A>
+</H2>
+
+<P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
+<B>show/wwv <n></B> Show the last <n> WWV broadcasts</CODE>
+<P>
+<P>Display the most recent WWV information that has been received by the system
+<P>
+<P>
+<H2><A NAME="ss7.133">7.133 shutdown (5)</A>
+</H2>
+
+<P><CODE><B>shutdown</B> Shutdown the cluster</CODE>
+<P>
+<P>Shutdown the cluster and disconnect all the users. If you have Spider
+set to respawn in /etc/inittab it will of course restart.
+<P>
+<H2><A NAME="ss7.134">7.134 spoof (9)</A>
+</H2>
+
+<P><CODE><B>spoof <callsign> <command></B> Run commands as another user</CODE>
+<P>
+<P>This is a very simple yet powerful command for the sysop. It allows you to
+issue commands as if you were a different user. This is very useful for the
+kind of things that users seem to always get wrong.. like home_node for
+example.
+<P>
+<H2><A NAME="ss7.135">7.135 stat/db (5)</A>
+</H2>
+
+<P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE>
+<P>
+<P>Show the internal status of a database descriptor.
+<P>Depending on your privilege level you will see more or less information.
+This command is unlikely to be of much use to anyone other than a sysop.
+<P>
+<H2><A NAME="ss7.136">7.136 stat/channel (5)</A>
+</H2>
+
+<P><CODE><B>stat/channel <callsign></B> Show the status of a channel on the cluster</CODE>
+<P>
+<P>Show the internal status of the channel object either for the channel that
+you are on or else for the callsign that you asked for.
+<P>Only the fields that are defined (in perl term) will be displayed.
+<P>
+<H2><A NAME="ss7.137">7.137 stat/msg (5)</A>
+</H2>
+
+<P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE>
+<P>
+<P>This command shows the internal status of a message and includes information
+such as to whom it has been forwarded, its size, origin etc etc.
+<P>
+<P>If no message number is given then the status of the message system is
+displayed.
+<P>
+<H2><A NAME="ss7.138">7.138 stat/route_node (5)</A>
</H2>
-<P>You will find a file in /spider/cmd/ called Aliases. First, copy this file to
-/spider/local_cmd/Aliases and edit this file. You will see something like this ...
+<P><CODE><B>stat/route_node <callsign></B> Show the data in a Route::Node object</CODE>
+<P>
+<H2><A NAME="ss7.139">7.139 stat/route_user (5)</A>
+</H2>
+
+<P><CODE><B>stat/route_user <callsign></B> Show the data in a Route::User object</CODE>
+<P>
+<H2><A NAME="ss7.140">7.140 stat/user (5)</A>
+</H2>
+
+<P><CODE><B>stat/user <callsign></B> Show the full status of a user</CODE>
+<P>
+<P>Shows the full contents of a user record including all the secret flags
+and stuff.
+<P>Only the fields that are defined (in perl term) will be displayed.
+<P>
+<H2><A NAME="ss7.141">7.141 sysop (0)</A>
+</H2>
+
+<P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE>
+<P>
+<P>The system automatically reduces your privilege level to that of a
+normal user if you login in remotely. This command allows you to
+regain your normal privilege level. It uses the normal system: five
+numbers are returned that are indexes into the character array that is
+your assigned password (see SET/PASSWORD). The indexes start from
+zero.
+<P>You are expected to return a string which contains the characters
+required in the correct order. You may intersperse those characters
+with others to obscure your reply for any watchers. For example (and
+these values are for explanation :-):
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ password = 012345678901234567890123456789
+ > sysop
+ 22 10 15 17 3
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>you type:-
<P>
<BLOCKQUOTE><CODE>
<PRE>
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>They will all match. If there is no password you will still be offered
+numbers but nothing will happen when you input a string. Any match is
+case sensitive.
+<P>
+<H2><A NAME="ss7.142">7.142 talk (0)</A>
+</H2>
-#!/usr/bin/perl
+<P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
+<B>talk <callsign> <text></B> Send a text message to <callsign><BR>
+<B>talk <callsign> > <node_call> [<text>]</B>
+Send a text message to <callsign> via <node_call></CODE>
+<P>
+<P>Send a short message to any other station that is visible on the cluster
+system. You can send it to anyone you can see with a SHOW/CONFIGURATION
+command, they don't have to be connected locally.
+<P>The second form of TALK is used when other cluster nodes are connected
+with restricted information. This usually means that they don't send
+the user information usually associated with logging on and off the cluster.
+<P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
+see GB7TLH in the SH/C list but with no users, then you would use the
+second form of the talk message.
+<P>If you want to have a ragchew with someone you can leave the text message
+out and the system will go into 'Talk' mode. What this means is that a
+short message is sent to the recipient telling them that you are in a 'Talking'
+frame of mind and then you just type - everything you send will go to the
+station that you asked for.
+<P>All the usual announcements, spots and so on will still come out on your
+terminal.
+<P>If you want to do something (such as send a spot) you precede the normal
+command with a '/' character, eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
+ /HELP talk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To leave talk mode type:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ /EX
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss7.143">7.143 type (0)</A>
+</H2>
-# provide some standard aliases for commands for terminally
-# helpless ak1a user (helpless in the sense that they never
-# read nor understand help files)
-
-# This file is automagically reloaded if its modification time is
-# later than the one stored in CmdAlias.pm
-
-# PLEASE make this file consistant with reality! (the patterns MUST
-# match the filenames!)
-
-# Don't alter this file, copy it into the local_cmd tree and modify it.
-# This file will be replaced everytime I issue a new release.
-
-# You only need to put aliases in here for commands that don't work as
-# you desire naturally, e.g sh/dx on its own just works as you expect
-# so you need not add it as an alias.
-
-
-
-package CmdAlias;
-
-%alias = (
- '?' => [
- '^\?', 'apropos', 'apropos',
- ],
- 'a' => [
- '^ann.*/full', 'announce full', 'announce',
- '^ann.*/sysop', 'announce sysop', 'announce',
- '^ann.*/(.*)$', 'announce $1', 'announce',
- ],
- 'b' => [
- ],
- 'c' => [
- ],
- 'd' => [
- '^del', 'kill', 'kill',
- '^del\w*/fu', 'kill full', 'kill',
- '^di\w*/a\w*', 'directory all', 'directory',
- '^di\w*/b\w*', 'directory bulletins', 'directory',
- '^di\w*/n\w*', 'directory new', 'directory',
- '^di\w*/o\w*', 'directory own', 'directory',
- '^di\w*/s\w*', 'directory subject', 'directory',
- '^di\w*/t\w*', 'directory to', 'directory',
- '^di\w*/f\w*', 'directory from', 'directory',
- '^di\w*/(\d+)', 'directory $1', 'directory',
- ],
- 'e' => [
- ],
- 'f' => [
- ],
- 'g' => [
- ],
- 'h' => [
- ],
- 'i' => [
- ],
- 'j' => [
- ],
- 'k' => [
- ],
- 'l' => [
- '^l$', 'directory', 'directory',
- '^ll$', 'directory', 'directory',
- '^ll/(\d+)', 'directory $1', 'directory',
- ],
- 'm' => [
- ],
- 'n' => [
- '^news', 'type news', 'type',
- ],
- 'o' => [
- ],
- 'p' => [
- ],
- 'q' => [
- '^q', 'bye', 'bye',
- ],
- 'r' => [
- '^r$', 'read', 'read',
- '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
- ],
- 's' => [
- '^s/p$', 'send', 'send',
- '^sb$', 'send noprivate', 'send',
- '^set/home$', 'set/homenode', 'set/homenode',
- '^set/nobe', 'unset/beep', 'unset/beep',
- '^set/nohe', 'unset/here', 'unset/here',
- '^set/noan', 'unset/announce', 'unset/announce',
- '^set/nodx', 'unset/dx', 'unset/dx',
- '^set/nota', 'unset/talk', 'unset/talk',
- '^set/noww', 'unset/wwv', 'unset/wwv',
- '^set/nowx', 'unset/wx', 'unset/wx',
- '^sh$', 'show', 'show',
- '^sh\w*/buck', 'dbshow buck', 'dbshow',
- '^sh\w*/bu', 'show/files bulletins', 'show/files',
- '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
- '^sh\w*/c$', 'show/configuration', 'show/configuration',
- '^sh\w*/com', 'dbavail', 'dbavail',
- '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
- '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
- '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
- '^sh\w*/email', 'dbshow email', 'dbshow',
- '^sh\w*/hftest', 'dbshow hftest', 'dbshow',
- '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
- '^sh\w*/qsl', 'dbshow qsl', 'dbshow',
- '^sh\w*/tnc', 'who', 'who',
- '^sh\w*/up', 'show/cluster', 'show/cluster',
- '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
- '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
- '^sp$', 'send', 'send',
-
- ],
- 't' => [
- '^ta$', 'talk', 'talk',
- '^t$', 'talk', 'talk',
- ],
- 'u' => [
- ],
- 'v' => [
- ],
- 'w' => [
- '^wx/full', 'wx full', 'wx',
- '^wx/sysop', 'wx sysop', 'wx',
- ],
- 'x' => [
- ],
- 'y' => [
- ],
- 'z' => [
- ],
-)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>You can create aliases for commands at will. Beware though, these may not
-always turn out as you think. Care is needed and you need to test the
-results once you have set an alias.
-<P>
-<H2><A NAME="ss7.5">7.5 Console.pl</A>
-</H2>
-
-<P>In later versions of Spider a simple console program is provided for the sysop.
-This has a type ahead buffer with line editing facilities and colour for spots,
-announces etc. To use this program, simply use console.pl instead of client.
-<P>
-<P>To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
-file with your favourite editor.
-<P>
-<H2><A NAME="ss7.6">7.6 Updating kepler data</A>
-</H2>
-
-<P>Spider has a powerful and flexible show/satellite command. In order for
-this to be accurate, the kepler data has to be updated regularly. In
-general, this data is available as an email or via cluster mail.
-Updating it is simple. First you need to export the mail message as a
-file. You do this with the <EM>export</EM> command from the cluster prompt
-as the sysop. For example ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-export 5467 /spider/perl/keps.in
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>would export message number 5467 as a file called keps.in in the
-/spider/perl directory.
-<P>Now login to a VT as sysop and cd /spider/perl. There is a command in
-the perl directory called <EM>convkeps.pl</EM>. All we need to do now is
-convert the file like so ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-./convkeps.pl keps.in
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Now go back to the cluster and issue the command ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-load/keps
+<P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE>
+<P>
+<P>Type out the contents of a file in a filearea. So, for example, in
+filearea 'bulletins' you want to look at file 'arld051' you would
+enter:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ TYPE bulletins/arld051
</PRE>
</CODE></BLOCKQUOTE>
-<P>That is it! the kepler data has been updated.
+<P>See also SHOW/FILES to see what fileareas are available and a
+list of content.
+<P>
+<H2><A NAME="ss7.144">7.144 who (0)</A>
+</H2>
+
+<P><CODE><B>who</B> Show who is physically connected locally</CODE>
<P>
-<H2><A NAME="ss7.7">7.7 The QRZ callbook</A>
+<P>This is a quick listing that shows which callsigns are connected and
+what sort of connection they have
+<P>
+<H2><A NAME="ss7.145">7.145 wx (0)</A>
+</H2>
+
+<P><CODE><B>wx <text></B> Send a weather message to local users<BR>
+<B>wx full <text> </B> Send a weather message to all cluster users</CODE>
+<P>
+<P>Weather messages can sometimes be useful if you are experiencing an extreme
+that may indicate enhanced conditions
+<P>
+<H2><A NAME="ss7.146">7.146 wx (enhanced for sysops) (5)</A>
</H2>
-<P>The command <EM>sh/qrz</EM> will only work once you have followed a few
-simple steps. First you need to get a user ID and password from qrz.com.
-Simply go to the site and create one. Secondly you need to copy the file
-/spider/perl/Internet.pm to /spider/local and alter it to match your user
-ID and password. You also at this point need to set $allow=1 to complete
-the setup. Many thanks to Fred Lloyd, the proprieter of
-<A HREF="http://www.qrz.com">qrz.com</A> for allowing this access.
+<P><CODE><B>wx sysop <text></B> Send a weather message to other clusters only</CODE>
+<P>
+<P>Send a weather message only to other cluster nodes and not to general users.
+<P>
+<P>
<P>
<HR>
-<A HREF="adminmanual-8.html">Next</A>
+Next
<A HREF="adminmanual-6.html">Previous</A>
<A HREF="adminmanual.html#toc7">Contents</A>
</BODY>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.47: CVS</TITLE>
- <LINK HREF="adminmanual-9.html" REL=next>
+ <TITLE>The DXSpider Administration Manual v1.47: The DXSpider command set</TITLE>
<LINK HREF="adminmanual-7.html" REL=previous>
<LINK HREF="adminmanual.html#toc8" REL=contents>
<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
</HEAD>
<BODY>
-<A HREF="adminmanual-9.html">Next</A>
+Next
<A HREF="adminmanual-7.html">Previous</A>
<A HREF="adminmanual.html#toc8">Contents</A>
<HR>
-<H2><A NAME="s8">8. CVS</A></H2>
+<H2><A NAME="s8">8. The DXSpider command set</A></H2>
-<P>CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held
-at
-<A HREF="http://www.sourceforge.net">Sourceforge</A>. This means
-that it is possible to update your DXSpider installation to the latest
-sources by using a few simple commands.
+<P>Below is a complete list of commands available from the cluster prompt.
+Most maintenance tasks are automatic but there are some commands that are useful
+for a sysop. These are listed below in alphabetical order. The number in
+brackets following the command name is the permissions level needed to use
+the command.
<P>
-<P>THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST
-INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!!
-THIS MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!!
-YOU HAVE BEEN WARNED!!!
+<H2><A NAME="ss8.1">8.1 accept/announce (0)</A>
+</H2>
+
+<P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter
+line for announce</CODE>
+<P>
+<P>Create an 'accept this announce' line for a filter.
+<P>An accept filter line means that if the announce matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/ann dest 6MUK
+ acc/ann 2 by_zone 14,15,16
+ (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>or
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/ann by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This filter would only allow announces that were posted buy UK stations.
+You can use the tag 'all' to accept everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/ann all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss8.2">8.2 accept/announce (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>accept/announce <call> [input] [0-9]<pattern></B> Announce filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/ann by G,M,2
+ accept/ann input node_default by G,M,2
+ accept/ann user_default by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.3">8.3 accept/spots (0)</A>
+</H2>
+
+<P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter line for spots</CODE>
+<P>
+<P>Create an 'accept this spot' line for a filter.
+<P>
+<P>An accept filter line means that if the spot matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>For frequencies, you can use any of the band names defined in
+SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+this is more efficient than saying simply: freq HF (but don't get
+too hung up about that)
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can use the tag 'all' to accept everything, eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 3 all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss8.4">8.4 accept/spots (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>accept/spots <call> [input] [0-9] <pattern></B> Spot filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/spot db0sue-7 1 by_zone 14,15,16
+ accept/spot node_default all
+ set/hops node_default 10
+
+ accept/spot user_default by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.5">8.5 accept/wcy (0)</A>
+</H2>
+
+<P><CODE><B>accept/wcy [0-9] <pattern></B> set an accept WCY filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>There are no examples because WCY Broadcasts only come from one place and
+you either want them or not (see UNSET/WCY if you don't want them).
+<P>This command is really provided for future use.
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss8.6">8.6 accept/wcy (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>accept/wcy <call> [input] [0-9] <pattern></B>
+WCY filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/wcy node_default all
+ set/hops node_default 10
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.7">8.7 accept/wwv (0)</A>
+</H2>
+
+<P><CODE><B>accept/wwv [0-9] <pattern></B> Set an accept WWV filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>for example
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/wwv by_zone 4
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>is probably the only useful thing to do (which will only show WWV broadcasts
+by stations in the US).
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss8.8">8.8 accept/wwv (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>accept/wwv <call> [input] [0-9] <pattern></B>
+WWV filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/wwv db0sue-7 1 by_zone 4
+ accept/wwv node_default all
+ set/hops node_default 10
+
+ accept/wwv user_default by W,K
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.9">8.9 announce (0)</A>
+</H2>
+
+<P><CODE><B>announce <text></B> Send an announcement to local users</CODE>
+<P>
+<P>Send an announcement to LOCAL users only, where <text> is the text
+of the announcement you wish to broadcast
+<P>
+<H2><A NAME="ss8.10">8.10 announce full (0)</A>
+</H2>
+
+<P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE>
+<P>
+<P>This command will send your announcement across the whole cluster
+network.
+<P>
+<P>
+<H2><A NAME="ss8.11">8.11 announce sysop (5)</A>
+</H2>
+
+<P><CODE><B>announce sysop <text></B></CODE>
+<P>
+<P>Send an announcement to Sysops only
+<P>
+<H2><A NAME="ss8.12">8.12 apropos (0)</A>
+</H2>
+
+<P><CODE><B>apropos <string></B> Search the help database</CODE>
+<P>
+<P>Search the help database for <string> (it isn't case sensitive),
+and print the names of all the commands that may be relevant.
+<P>
+<H2><A NAME="ss8.13">8.13 bye (0)</A>
+</H2>
+
+<P><CODE><B>bye</B> Exit from the cluster</CODE>
+<P>
+<P>This will disconnect you from the cluster
+<P>
+<H2><A NAME="ss8.14">8.14 catchup (5)</A>
+</H2>
+
+<P><CODE><B>catchup <node_call> All|[<msgno> ...]</B> Mark a message as sent</CODE>
+<P>
+<P>When you send messages the fact that you have forwarded it to another node
+is remembered so that it isn't sent again. When you have a new partner
+node and you add their callsign to your /spider/msg/forward.pl file, all
+outstanding non-private messages will be forwarded to them. This may well
+be ALL the non-private messages. You can prevent this by using these
+commmands:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ catchup GB7DJK all
+ catchup GB7DJK 300 301 302 303 500-510
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>and to undo what you have just done:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ uncatchup GB7DJK all
+ uncatchup GB7DJK 300 301 302 303 500-510
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>which will arrange for them to be forward candidates again.
+<P>Order is not important.
+<P>
+<H2><A NAME="ss8.15">8.15 clear/spots (0)</A>
+</H2>
+
+<P><CODE><B>clear/spots [1|all]</B> Clear a spot filter line</CODE>
+<P>
+<P>This command allows you to clear (remove) a line in a spot filter or to
+remove the whole filter.
+<P>If you have a filter:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>and you say:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ clear/spot 1
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>you will be left with:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>If you do:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ clear/spot all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>the filter will be completely removed.
+<P>
+<P>
+<H2><A NAME="ss8.16">8.16 connect (5) </A>
+</H2>
+
+<P><CODE><B>connect <callsign></B> Start a connection to another DX Cluster</CODE>
+<P>
+<P>Start a connection process that will culminate in a new connection to the
+DX cluster <callsign>. This process creates a new 'client' process which will
+use the script in /spider/connect/<callsign> to effect the 'chat' exchange
+necessary to traverse the network(s) to logon to the cluster <callsign>.
+<P>
+<H2><A NAME="ss8.17">8.17 dbavail (0)</A>
+</H2>
+
+<P><CODE><B>dbavail</B> Show a list of all the databases in the system</CODE>
+<P>
+<P>The title says it all really, this command lists all the databases defined
+in the system. It is also aliased to SHOW/COMMAND.
+<P>
+<H2><A NAME="ss8.18">8.18 dbcreate (9)</A>
+</H2>
+
+<P><CODE><B>dbcreate <name></B> Create a database entry<BR>
+<B>dbcreate <name> chain <name> [<name>..]</B> Create a chained database entry<BR>
+<B>dbcreate <name> remote <node></B> Create a remote database
+entry<BR></CODE>
+<P>
+<P>DBCREATE allows you to define a database in the system. It doesn't actually
+create anything, just defines it.
+<P>The databases that are created are simple DB_File hash databases, they are
+therefore already 'indexed'.
+<P>You can define a local database with the first form of the command eg:
+<P>DBCREATE oblast
+<P>You can also chain databases with the addition of the 'chain' keyword.
+This will search each database one after the other. A typical example
+is:
+<P>DBCREATE sdx_qsl chain sql_ad
+<P>No checking is done to see if the any of the chained databases exist, in
+fact it is usually better to do the above statement first then do each of
+the chained databases.
+<P>Databases can exist offsite. To define a database that lives on another
+node do:
+<P>DBCREATE buckmaster remote gb7dxc
+<P>Remote databases cannot be chained; however, the last database in a
+a chain can be a remote database eg:
+<P>DBCREATE qsl chain gb7dxc
+<P>To see what databases have been defined do:
+<P>DBAVAIL (or it will have been aliased to SHOW/COMMAND)
+<P>It would be normal for you to add an entry into your local Aliases file
+to allow people to use the 'SHOW/<dbname>' style syntax. So you would
+need to add a line like:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ 's' => [
+ ..
+ ..
+ '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
+ ..
+ ..
+ ],
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>to allow
+<P>SH/BUCK g1tlh
+<P>to work as they may be used to.
+<P>See DBIMPORT for the importing of existing AK1A format data to databases.
+See DBSHOW for generic database enquiry
+<P>
+<H2><A NAME="ss8.19">8.19 dbimport (9)</A>
+</H2>
+
+<P><CODE><B>dbimport <dbname></B> Import AK1A data into a database</CODE>
+<P>
+<P>If you want to import or update data in bulk to a database you can use
+this command. It will either create or update entries into an existing
+database. For example:-
+<P>DBIMPORT oblast /tmp/OBLAST.FUL
+<P>will import the standard OBLAST database that comes with AK1A into the
+oblast database held locally.
+<P>
+<H2><A NAME="ss8.20">8.20 dbremove (9)</A>
+</H2>
+
+<P><CODE><B>dbremove <dbname></B> Delete a database</CODE>
+<P>
+<P>DBREMOVE will completely remove a database entry and also delete any data
+file that is associated with it.
+<P>There is no warning, no comeback, no safety net.
+<P>For example:
+<P>DBREMOVE oblast
+<P>will remove the oblast database from the system and it will also remove
+the associated datafile.
+<P>I repeat:
+<P>There is no warning, no comeback, no safety net.
+<P>You have been warned.
+<P>
+<H2><A NAME="ss8.21">8.21 dbshow (0)</A>
+</H2>
+
+<P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE>
+<P>
+<P>This is the generic user interface to the database to the database system.
+It is expected that the sysop will add an entry to the local Aliases file
+so that users can use the more familiar AK1A style of enquiry such as:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/BUCK G1TLH
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but if he hasn't and the database really does exist (use DBAVAIL or
+SHOW/COMMAND to find out) you can do the same thing with:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBSHOW buck G1TLH
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>
+<H2><A NAME="ss8.22">8.22 debug (9)</A>
+</H2>
+
+<P><CODE><B>debug</B> Set the cluster program into debug mode</CODE>
+<P>
+<P>Executing this command will only have an effect if you are running the cluster
+in debug mode i.e.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ perl -d cluster.pl
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>It will interrupt the cluster just after the debug command has finished.
+<P>
+<H2><A NAME="ss8.23">8.23 directory (0)</A>
+</H2>
+
+<P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
+<B>directory own</B> List your own messages<BR>
+<B>directory new</B> List all new messages<BR>
+<B>directory to <call></B> List all messages to <call><BR>
+<B>directory from <call></B> List all messages from <call><BR>
+<B>directory subject <string></B> List all messages with <string> in subject<BR>
+<B>directory <nn></B> List last <nn> messages<BR>
+<B>directory <from>-<to></B> List messages <from> message <to> message <BR></CODE>
+<P>
+<P>List the messages in the messages directory.
+<P>If there is a 'p' one space after the message number then it is a
+personal message. If there is a '-' between the message number and the
+'p' then this indicates that the message has been read.
+<P>You can use shell escape characters such as '*' and '?' in the <call>
+fields.
+<P>You can combine some of the various directory commands together eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DIR TO G1TLH 5
+or
+ DIR SUBJECT IOTA 200-250
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can abbreviate all the commands to one letter and use ak1a syntax:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DIR/T G1* 10
+ DIR/S QSL 10-100 5
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>
+<H2><A NAME="ss8.24">8.24 directory (extended for sysops) (5)</A>
+</H2>
+
+<P>Works just like the user command except that sysops can see ALL messages.
+<P>
+<H2><A NAME="ss8.25">8.25 disconnect (8)</A>
+</H2>
+
+<P><CODE><B>disconnect <call> [<call> ...]</B> Disconnect a user or node</CODE>
+<P>
+<P>Disconnect any <call> connected locally
+<P>
+<H2><A NAME="ss8.26">8.26 dx (0)</A>
+</H2>
+
+<P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE>
+<P>
+<P>This is how you send a DX Spot to other users. You can, in fact, now
+enter the <freq> and the <call> either way round.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DX FR0G 144.600
+ DX 144.600 FR0G
+ DX 144600 FR0G
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will all give the same result. You can add some remarks to the end
+of the command and they will be added to the spot.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DX FR0G 144600 this is a test
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can credit someone else by saying:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The <freq> is compared against the available bands set up in the
+cluster. See SHOW/BANDS for more information.
+<P>
+<H2><A NAME="ss8.27">8.27 export (9)</A>
+</H2>
+
+<P><CODE><B>export <msgno> <filename></B> Export a message to a file</CODE>
+<P>
+<P>Export a message to a file. This command can only be executed on a local
+console with a fully privileged user. The file produced will be in a form
+ready to be imported back into the cluster by placing it in the import
+directory (/spider/msg/import).
+<P>This command cannot overwrite an existing file. This is to provide some
+measure of security. Any files written will owned by the same user as the
+main cluster, otherwise you can put the new files anywhere the cluster can
+access. For example:-
+<P>EXPORT 2345 /tmp/a
+<P>
+<H2><A NAME="ss8.28">8.28 export_users (9)</A>
+</H2>
+
+<P><CODE><B>export_users [<filename>]</B> Export the users database to ascii</CODE>
+<P>
+<P>Export the users database to a file in ascii format. If no filename
+is given then it will export the file to /spider/data/user_asc.
+<P>If the file already exists it will be renamed to <filename>.o. In fact
+up to 5 generations of the file can be kept each one with an extra 'o' on the
+suffix.
+<P>BE WARNED: this will write to any file you have write access to. No check is
+made on the filename (if any) that you specify.
+<P>
+<H2><A NAME="ss8.29">8.29 forward/latlong (8)</A>
+</H2>
+
+<P><CODE><B>forward/latlong <node_call></B> Send latitude and longitude information to another cluster</CODE>
+<P>
+<P>This command sends all the latitude and longitude information that your
+cluster is holding against callsigns. One advantage of recieving this
+information is that more locator information is held by you. This
+means that more locators are given on the DX line assuming you have
+<EM>set/dxgrid</EM> enabled. This could be a LOT of information though, so
+it is not recommended on slow links.
+<P>
+<H2><A NAME="ss8.30">8.30 forward/opername (1)</A>
+</H2>
+
+<P><CODE><B>forward/opername <call></B> Send out information on this <call> to all clusters</CODE>
+<P>
+<P>This command sends out any information held in the user file which can
+be broadcast in PC41 protocol packets. This information is Name, QTH, Location
+and Homenode. PC41s are only sent for the information that is available.
+<P>
+<H2><A NAME="ss8.31">8.31 help (0)</A>
+</H2>
+
+<P><CODE><B>help <cmd></B> Get help on a command</CODE>
+<P>
+<P>All commands can be abbreviated, so SHOW/DX can be abbreviated
+to SH/DX, ANNOUNCE can be shortened to AN and so on.
+<P>Look at the APROPOS <string> command which will search the help database
+for the <string> you specify and give you a list of likely commands
+to look at with HELP.
+<P>
+<H2><A NAME="ss8.32">8.32 init (5)</A>
+</H2>
+
+<P><CODE><B>init <node call></B> Re-initialise a link to an AK1A compatible node</CODE>
+<P>
+<P>This command attempts to re-initialise a link to a (usually) AK1A node
+that has got confused, usually by a protocol loop of some kind. It may
+work - but you usually will be better off simply disconnecting it (or
+better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
+node>).
+<P>Best of luck - you will need it.
+<P>
+<H2><A NAME="ss8.33">8.33 kill (0)</A>
+</H2>
+
+<P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE>
+<P>
+<P>Delete a message from the local system. You will only be able to
+delete messages that you have originated or been sent (unless you are
+the sysop).
+<P>
+<H2><A NAME="ss8.34">8.34 kill (5)</A>
+</H2>
+
+<P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system<BR>
+<B>kill from <call></B> Remove all messages from a callsign<BR>
+<B>kill to <call></B> Remove all messages to a callsign<BR></CODE>
+<P>
+<P>You can get rid of any message to or originating from your callsign using
+this command. You can remove more than one message at a time.
+<P>As a sysop you can kill any message on the system.
+<P>
+<H2><A NAME="ss8.35">8.35 kill full (5)</A>
+</H2>
+
+<P><CODE><B>kill full <msgno> [<msgno>]</B> Delete a message from the whole cluster</CODE>
+<P>
+<P>Delete a message (usually a 'bulletin') from the whole cluster system.
+<P>This uses the subject field, so any messages that have exactly the same subject
+will be deleted. Beware!
+<P>
+<H2><A NAME="ss8.36">8.36 links (0)</A>
+</H2>
+
+<P><CODE><B>links</B> Show which nodes are physically connected</CODE>
+<P>
+<P>This is a quick listing that shows which links are connected and
+some information about them. See WHO for a list of all connections.
+<P>
+<P>
+<H2><A NAME="ss8.37">8.37 load/aliases (9)</A>
+</H2>
+
+<P><CODE><B>load/aliases</B> Reload the command alias table</CODE>
+<P>
+<P>Reload the /spider/cmd/Aliases file after you have editted it. You will need to
+do this if you change this file whilst the cluster is running in order for the
+changes to take effect.
+<P>
+<P>
+<H2><A NAME="ss8.38">8.38 load/baddx (9)</A>
+</H2>
+
+<P><CODE><B>load/baddx</B> Reload the bad DX table</CODE>
+<P>
+<P>Reload the /spider/data/baddx.pl file if you have changed it manually whilst
+the cluster is running. This table contains the DX Calls that, if spotted,
+will not be passed on. FR0G and TEST are classic examples.
+<P>
+<H2><A NAME="ss8.39">8.39 load/badmsg (9)</A>
+</H2>
+
+<P><CODE><B>load/badmsg</B> Reload the bad message table</CODE>
+<P>
+<P>Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
+the cluster is running. This table contains a number of perl regular
+expressions which are searched for in the fields targetted of each message.
+If any of them match then that message is immediately deleted on receipt.
+<P>
+<H2><A NAME="ss8.40">8.40 load/badwords (9)</A>
+</H2>
+
+<P><CODE><B>load/badwords</B> Reload the badwords file</CODE>
+<P>
+<P>Reload the /spider/data/badwords file if you have changed it manually whilst
+the cluster is running. This file contains a list of words which, if found
+on certain text portions of PC protocol, will cause those protocol frames
+to be rejected. It will all put out a message if any of these words are
+used on the announce, dx and talk commands. The words can be one or
+more on a line, lines starting with '#' are ignored.
+<P>
+<H2><A NAME="ss8.41">8.41 load/bands (9)</A>
+</H2>
+
+<P><CODE><B>load/bands</B> Reload the band limits table</CODE>
+<P>
+<P>Reload the /spider/data/bands.pl file if you have changed it manually whilst
+the cluster is running.
+<P>
+<H2><A NAME="ss8.42">8.42 load/cmd_cache (9)</A>
+</H2>
+
+<P><CODE><B>load/cmd_cache</B> Reload the automatic command cache</CODE>
+<P>
+<P>Normally, if you change a command file in the cmd or local_cmd tree it will
+automatially be picked up by the cluster program. Sometimes it can get confused
+if you are doing a lot of moving commands about or delete a command in the
+local_cmd tree and want to use the normal one again. Execute this command to
+reset everything back to the state it was just after a cluster restart.
+<P>
+<H2><A NAME="ss8.43">8.43 load/forward (9)</A>
+</H2>
+
+<P><CODE><B>load/forward</B> Reload the msg forwarding routing table</CODE>
+<P>Reload the /spider/msg/forward.pl file if you have changed it
+manually whilst the cluster is running.
+<P>
+<H2><A NAME="ss8.44">8.44 load/messages (9)</A>
+</H2>
+
+<P><CODE><B>load/messages</B> Reload the system messages file</CODE>
+<P>
+<P>If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne
+commands) you can have them take effect during a cluster session by executing this
+command. You need to do this if get something like :-
+<P>unknown message 'xxxx' in lang 'en'
+<P>
+<H2><A NAME="ss8.45">8.45 load/prefixes (9)</A>
+</H2>
+
+<P><CODE><B>load/prefixes</B> Reload the prefix table</CODE>
+<P>
+<P>Reload the /spider/data/prefix_data.pl file if you have changed it manually
+whilst the cluster is running.
+<P>
+<H2><A NAME="ss8.46">8.46 merge (5)</A>
+</H2>
+
+<P><CODE><B>merge <node> [<no spots>/<no wwv>]</B> Ask for the latest spots and WWV</CODE>
+<P>
+<P>MERGE allows you to bring your spot and wwv database up to date. By default
+it will request the last 10 spots and 5 WWVs from the node you select. The
+node must be connected locally.
+<P>You can request any number of spots or wwv and although they will be appended
+to your databases they will not duplicate any that have recently been added
+(the last 2 days for spots and last month for WWV data).
+<P>
+<H2><A NAME="ss8.47">8.47 msg (9)</A>
+</H2>
+
+<P><CODE><B>msg <cmd> <msgno> [data ...]</B> Alter various message parameters</CODE>
+<P>
+<P>Alter message parameters like To, From, Subject, whether private or bulletin
+or return receipt (RR) is required or whether to keep this message from timing
+out.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ MSG TO <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - remove any waitting time for this message
+ MSG NOREad <msgno> - mark message as unread
+ MSG REad <msgno> - mark message as read
+ MSG QUeue - queue any outstanding bulletins
+ MSG QUeue 1 - queue any outstanding private messages
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can look at the status of a message by using:-
+<P>STAT/MSG <msgno>
+<P>This will display more information on the message than DIR does.
+<P>
+<H2><A NAME="ss8.48">8.48 pc (8)</A>
+</H2>
+
+<P><CODE><B>pc <call> <text></B> Send text (eg PC Protocol) to <call></CODE>
+<P>
+<P>Send some arbitrary text to a locally connected callsign. No processing is done on
+the text. This command allows you to send PC Protocol to unstick things if problems
+arise (messages get stuck etc). eg:-
+<P>pc gb7djk PC33^GB7TLH^GB7DJK^400^
+<P>You can also use in the same way as a talk command to a connected user but
+without any processing, added of "from <blah> to <blah>" or whatever.
+<P>pc G1TLH Try doing that properly!!!
+<P>
+<H2><A NAME="ss8.49">8.49 ping (1)</A>
+</H2>
+
+<P><CODE><B>ping <node></B> Check the link quality between nodes</CODE>
+<P>
+<P>his command allows you to send a frame to another cluster node on
+the network and get a return frame. The time it takes to do this
+is a good indication of the quality of the link. The actual time
+it takes is output to the console in seconds.
+Any visible cluster node can be PINGed.
+<P>
+<P>
+<H2><A NAME="ss8.50">8.50 rcmd (1)</A>
+</H2>
+
+<P><CODE><B>rcmd <node call> <cmd></B> Send a command to another DX cluster</CODE>
+<P>
+<P>This command allows you to send nearly any command to another DX Cluster
+node that is connected to the system.
+<P>Whether you get any output is dependant on a) whether the other system knows
+that the node callsign of this cluster is in fact a node b) whether the
+other system is allowing RCMDs from this node and c) whether you have
+permission to send this command at all.
+<P>
+<H2><A NAME="ss8.51">8.51 read (0)</A>
+</H2>
+
+<P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
+<B>read <msgno></B> Read the specified message<BR></CODE>
+<P>
+<P>You can read any messages that are sent as 'non-personal' and also any
+message either sent by or sent to your callsign.
+<P>
+<P>
+<H2><A NAME="ss8.52">8.52 read (extended for sysops) (5) </A>
+</H2>
+
+<P><CODE><B>read <msgno></B> Read a message on the system</CODE>
+<P>
+<P>As a sysop you may read any message on the system
+<P>
+<H2><A NAME="ss8.53">8.53 reject/announce</A>
+</H2>
+
+<P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
+for announce</CODE>
+<P>
+<P>Create an 'reject this announce' line for a filter.
+<P>An reject filter line means that if the announce matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/ann by_zone 14,15,16 and not by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can use the tag 'all' to reject everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/ann all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss8.54">8.54 reject/announce (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>reject/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ reject/ann by G,M,2
+ reject/ann input node_default by G,M,2
+ reject/ann user_default by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.55">8.55 reject/spots (0)</A>
+</H2>
+
+<P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE>
+<P>
+<P>Create a 'reject this spot' line for a filter.
+<P>A reject filter line means that if the spot matches this filter it is
+dumped (not passed on). See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>For frequencies, you can use any of the band names defined in
+SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+this is more efficient than saying simply: on HF (but don't get
+too hung up about that)
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/spot 1 on hf
+ rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can use the tag 'all' to reject everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/spot 3 all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss8.56">8.56 reject/spots (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>reject/spots <call> [input] [0-9] <pattern></B>
+Reject spot filter sysop version </CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ reject/spot db0sue-7 1 by_zone 14,15,16
+ reject/spot node_default all
+ set/hops node_default 10
+
+ reject/spot user_default by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.57">8.57 reject/wcy (0)</A>
+</H2>
+
+<P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>There are no examples because WCY Broadcasts only come from one place and
+you either want them or not (see UNSET/WCY if you don't want them).
+<P>This command is really provided for future use.
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss8.58">8.58 reject/wcy (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>reject/wcy <call> [input] [0-9] <pattern></B>
+WCY reject filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>reject/wcy gb7djk all
+<P>
+<H2><A NAME="ss8.59">8.59 reject/wwv (0)</A>
+</H2>
+
+<P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>for example
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ reject/wwv by_zone 14,15,16
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>is probably the only useful thing to do (which will only show WWV broadcasts
+by stations in the US).
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss8.60">8.60 reject/wwv (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>reject/wwv <call> [input] [0-9] <pattern></B>
+WWV reject filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ reject/wwv db0sue-7 1 by_zone 4
+ reject/wwv node_default all
+
+ reject/wwv user_default by W
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.61">8.61 reply (0)</A>
+</H2>
+
+<P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
+<B>reply <msgno></B> Reply (privately) to the specified message<BR>
+<B>reply B <msgno></B> Reply as a Bulletin to the specified message<BR>
+<B>reply NOPrivate <msgno></B> Reply as a Bulletin to the specified
+message<BR>
+<B>reply RR <msgno></B> Reply to the specified message with read receipt<BR></CODE>
+<P>
+<P>You can reply to a message and the subject will automatically have
+"Re:" inserted in front of it, if it isn't already present.
+<P>You can also use all the extra qualifiers such as RR, PRIVATE,
+NOPRIVATE, B that you can use with the SEND command (see SEND
+for further details)
+<P>
+<H2><A NAME="ss8.62">8.62 send (0)</A>
+</H2>
+
+<P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
+<B>send RR <call></B> Send a message and ask for a read receipt<BR>
+<B>send COPY <msgno> <call></B> Send a copy of a message to someone<BR>
+<B>send PRIVATE <call></B> Send a personal message<BR>
+<B>send NOPRIVATE <call></B> Send a message to all stations<BR></CODE>
+<P>
+<P>All the SEND commands will create a message which will be sent either to
+an individual callsign or to one of the 'bulletin' addresses.
+<P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
+it will mark the message as personal and send it to the cluster node that
+that callsign is connected to.
+<P>You can have more than one callsign in all of the SEND commands.
+<P>You can have multiple qualifiers so that you can have for example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SEND RR COPY 123 PRIVATE G1TLH G0RDI
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>which should send a copy of message 123 to G1TLH and G0RDI and you will
+receive a read receipt when they have read the message.
+<P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
+SP is an alias for SEND PRIVATE
+<P>
+<H2><A NAME="ss8.63">8.63 set/address (0)</A>
+</H2>
+
+<P><CODE><B>set/address <your_address></B> Record your postal address</CODE>
+<P>
+<P>Literally, record your address details on the cluster.
+<P>
+<H2><A NAME="ss8.64">8.64 set/announce (0)</A>
+</H2>
+
+<P><CODE><B>set/announce</B> Allow announce messages</CODE>
+<P>
+<P>Allow announce messages to arrive at your terminal.
+<P>
+<H2><A NAME="ss8.65">8.65 set/arcluster (5)</A>
+</H2>
+
+<P><CODE><B>set/arcluster <node_call> [<node_call> ...]</B> Make
+the node_call an AR-Cluster type node</CODE>
+<P>
+<P>Set the node_call as an AR-Cluster type node
+<P>
+<H2><A NAME="ss8.66">8.66 set/baddx (8)</A>
+</H2>
+
+<P><CODE><B>set/baddx <call></B> Stop words we do not wish to see in the callsign field
+of a dx spot being propagated</CODE>
+<P>
+<P>Setting a word as 'baddx' will prevent spots with that word in the callsign
+field of a DX spot from going any further. They will not be displayed and they
+will not be sent onto other nodes.
+<P>The word must be wriiten in full, no wild cards are allowed eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/baddx FORSALE VIDEO FR0G
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To allow a word again, use the following command ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ unset/baddx VIDEO
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.67">8.67 set/badnode (6)</A>
+</H2>
+
+<P><CODE><B>set/badnode <node_call></B> Stop spots from this node_call
+being propagated</CODE>
+<P>
+<P>Setting a callsign as a 'badnode' will prevent spots from that node
+going any further. They will not be displayed and they will not be
+sent onto other nodes.
+<P>The call can be a full or partial call (or a prefix), eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/badnode K1TTT
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will stop anything from K1TTT (including any SSID's)
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ unset/badnode K1TTT
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will allow spots from him again.
+<P>Use with extreme care. This command may well be superceded by FILTERing.
+<P>
+<H2><A NAME="ss8.68">8.68 set/badspotter (8)</A>
+</H2>
+
+<P><CODE><B>set/badspotter <call></B> Stop spots from this callsign being propagated</CODE>
+<P>
+<P>Setting a callsign as a 'badspotter' will prevent spots from this callsign
+going any further. They will not be displayed and they will not be
+sent onto other nodes.
+<P>The call must be written in full, no wild cards are allowed eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/badspotter VE2STN
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will stop anything from VE2STN. If you want SSIDs as well then you must
+enter them specifically.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ unset/badspotter VE2STN
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will allow spots from him again.
+<P>Use with extreme care. This command may well be superceded by FILTERing.
+<P>
+<H2><A NAME="ss8.69">8.69 set/beep (0)</A>
+</H2>
+
+<P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE>
+<P>
+<P>Add a beep to DX and other terminal messages.
+<P>
+<H2><A NAME="ss8.70">8.70 set/clx (5)</A>
+</H2>
+
+<P><CODE><B>set/clx <node_call> [<node_call> ...]</B> Make
+the node_call a CLX type node</CODE>
+<P>
+<P>Set the node_call as a CLX type node
+<P>
+<H2><A NAME="ss8.71">8.71 set/debug (9)</A>
+</H2>
+
+<P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE>
+<P>
+<P>You can choose to log several different levels. The levels are
+<P>chan
+state
+msg
+cron
+connect
+<P>You can show what levels you are logging with the <EM>show/debug</EM>
+command.
+<P>You can remove a debug level with unset/debug <name>
+<P>
+<H2><A NAME="ss8.72">8.72 set/dx (0)</A>
+</H2>
+
+<P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE>
+<P>
+<P>You can stop DX messages with the <EM>unset/dx</EM> command
+<P>
+<H2><A NAME="ss8.73">8.73 set/dxgrid (0)</A>
+</H2>
+
+<P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE>
+<P>
+<P>Some logging programs do not like the additional information at
+the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
+command to remove the grid squares.
+<P>
+<H2><A NAME="ss8.74">8.74 set/dxnet (5)</A>
+</H2>
+
+<P><CODE><B>set/dxnet <node_call> [<node_call> ...]</B> Make
+the node_call a DXNet type node</CODE>
+<P>
+<P>Set the node_call as a DXNet type node
+<P>
+<H2><A NAME="ss8.75">8.75 set/echo (0)</A>
+</H2>
+
+<P><CODE><B>set/echo</B> Make the cluster echo your input</CODE>
+<P>
+<P>If you are connected via a telnet session, different implimentations
+of telnet handle echo differently depending on whether you are
+connected via port 23 or some other port. You can use this command
+to change the setting appropriately.
+<P>You can remove the echo with the <EM>unset/echo</EM> command
+<P>The setting is stored in your user profile.
+<P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
+<P>
+<H2><A NAME="ss8.76">8.76 set/here (0)</A>
+</H2>
+
+<P><CODE><B>set/here</B> Set the here flag</CODE>
+<P>
+<P>Let others on the cluster know you are here by only displaying your
+callsign. If you are away from your terminal you can use the <EM>unset/here</EM>
+command to let people know you are away. This simply puts brackets
+around your callsign to indicate you are not available.
+<P>
+<H2><A NAME="ss8.77">8.77 set/homenode (0)</A>
+</H2>
+
+<P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE>
+<P>
+<P>Tell the cluster system where you normally connect to. Any Messages sent
+to you will normally find their way there should you not be connected.
+eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/HOMENODE gb7djk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.78">8.78 set/hops (8)</A>
+</H2>
+
+<P><CODE><B>set/hops <node_call> ann|spots|wwv|wcy <n></B>
+Set hop count</CODE>
+<P>
+<P>Set the hop count for a particular type of broadcast for a node.
+<P>This command allows you to set up special hop counts for a node
+for currently: announce, spots, wwv and wcy broadcasts.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+eg:
+ set/hops gb7djk ann 10
+ set/hops gb7mbc spots 20
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Set SHOW/HOPS for information on what is already set. This command
+creates a filter and works in conjunction with the filter system.
+<P>
+<H2><A NAME="ss8.79">8.79 set/isolate (9)</A>
+</H2>
+
+<P><CODE><B>set/isolate <node call></B> Isolate a node from the rest of the network</CODE>
+<P>
+<P>Connect a node to your system in such a way that you are a full protocol
+member of its network and can see all spots on it, but nothing either leaks
+out from it nor goes back into from the rest of the nodes connected to you.
+<P>You can potentially connect several nodes in this way.
+<P>You can see which nodes are isolated with the show/isolate (1) command.
+<P>You can remove the isolation with the command unset/isolate.
+<P>
+<H2><A NAME="ss8.80">8.80 set/language (0)</A>
+</H2>
+
+<P><CODE><B>set/language <language></B> Set the language you wish to use</CODE>
+<P>
+<P>You can select the language that you want the cluster to use. Currently
+the languages available are <EM>en</EM> (English) and <EM>nl</EM> (Dutch).
+<P>
+<H2><A NAME="ss8.81">8.81 set/location (0)</A>
+</H2>
+
+<P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE>
+<P>
+<P>You can set your latitude and longitude manually or alternatively use the
+<EM>set/qra</EM> command which will do the conversion for you.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/location 54 04 N 2 02 E
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>
+<H2><A NAME="ss8.82">8.82 set/sys_location (9)</A>
+</H2>
+
+<P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE>
+<P>
+<P>In order to get accurate headings and such like you must tell the system
+what your latitude and longitude is. If you have not yet done a SET/QRA
+then this command will set your QRA locator for you. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/LOCATION 52 22 N 0 57 E
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.83">8.83 set/logininfo (0)</A>
+</H2>
+
+<P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE>
+<P>
+<P>Show users and nodes when they log in and out of the local cluster. You
+can stop these messages by using the <EM>unset/logininfo</EM> command.
+<P>
+<P>
+<H2><A NAME="ss8.84">8.84 set/lockout (9)</A>
+</H2>
+
+<P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE>
+<P>
+<P>You can show who is locked out with the <EM>show/lockout</EM> command.
+To allow the user to connect again, use the <EM>unset/lockout</EM> command.
+<P>
+<H2><A NAME="ss8.85">8.85 set/name (0)</A>
+</H2>
+
+<P><CODE><B>set/name <your_name></B> Set your name</CODE>
+<P>
+<P>Tell the cluster what your name is, eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/name Dirk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.86">8.86 set/node (9)</A>
+</H2>
+
+<P><CODE><B>set/node <call> [<call> ...]</B> Make the callsign an AK1A cluster</CODE>
+<P>
+<P>Tell the system that the call(s) are to be treated as AK1A cluster and
+fed PC Protocol rather normal user commands.
+<P>From version 1.41 you can also set the following types of cluster
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/spider
+ set/dxnet
+ set/clx
+ set/arcluster
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To see what your nodes are set to, use the <EM>show/nodes</EM> command.
+<P>
+<H2><A NAME="ss8.87">8.87 set/obscount (9)</A>
+</H2>
+
+<P><CODE><B>set/obscount <count> <node call></B> Set the 'pump-up' obsolescence counter</CODE>
+<P>
+<P>From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see
+SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
+counter which is decremented on every outgoing ping and then reset to
+the 'obscount' value on every incoming ping. The default value of this
+parameter is 2.
+<P>What this means is that a neighbouring node will be pinged twice at
+(default) 300 second intervals and if no reply has been heard just before
+what would be the third attempt, that node is disconnected.
+<P>If a ping is heard then the obscount is reset to the full value. Using
+default values, if a node has not responded to a ping within 15 minutes,
+it is disconnected.
+<P>
+<H2><A NAME="ss8.88">8.88 set/page (0)</A>
+</H2>
+
+<P><CODE><B>set/page <n></B> Set the number of lines per page</CODE>
+<P>
+<P>Tell the system how many lines you wish on a page when the number of lines
+of output from a command is more than this. The default is 20. Setting it
+explicitly to 0 will disable paging.
<P>
-<P>DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE
-CONSEQUENCES!!!
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/PAGE 30
+ SET/PAGE 0
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The setting is stored in your user profile.
+<P>
+<P>
+<H2><A NAME="ss8.89">8.89 set/password (9)</A>
+</H2>
+
+<P><CODE><B>set/password <callsign> <string></B> Set a users password</CODE>
+<P>
+<P>The password for a user can only be set by a full sysop. The string
+can contain any characters but any spaces are removed (you can type in
+spaces - but they won't appear in the password). You can see the
+result with STAT/USER. The password is the usual 30 character baycom
+type password.
+<P>
+<H2><A NAME="ss8.90">8.90 set/pinginterval (9)</A>
+</H2>
+
+<P><CODE><B>set/pinginterval <time> <node call></B> Set the ping time to neighbouring nodes</CODE>
+<P>
+<P>As from version 1.35 all neighbouring nodes are pinged at regular intervals
+in order to determine the rolling quality of the link and, in future, to
+affect routing decisions. The default interval is 300 secs or 5 minutes.
+<P>You can use this command to set a different interval. Please don't.
+<P>But if you do the value you enter is treated as minutes up 60 and seconds
+for numbers greater than that.
+<P>This is used also to help determine when a link is down at the far end
+(as certain cluster software doesn't always notice), see SET/OBSCOUNT
+for more information.
+<P>
+<H2><A NAME="ss8.91">8.91 set/privilege (9)</A>
+</H2>
+
+<P><CODE><B>set/privilege <n> <call> [<call> ...]</B> Set the privilege level on a call</CODE>
+<P>
+<P>Set the privilege level on a callsign. The privilege levels that pertain
+to commands are as default:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ 0 - normal user
+ 1 - allow remote nodes normal user RCMDs
+ 5 - various privileged commands (including shutdown, but not disc-
+ connect), the normal level for another node.
+ 8 - more privileged commands (including disconnect)
+ 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
+ LEVEL.
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>If you are a sysop and you come in as a normal user on a remote connection
+your privilege will automatically be set to 0.
+<P>
+<H2><A NAME="ss8.92">8.92 set/spider (5)</A>
+</H2>
+
+<P><CODE><B>set/spider <node_call> [<node_call> ...]</B> Make
+the node_call a DXSpider type node</CODE>
+<P>
+<P>Set the node_call as a DXSpider type node
+<P>
+<H2><A NAME="ss8.93">8.93 set/sys_qra (9)</A>
+</H2>
+
+<P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA locator</CODE>
+<P>
+<H2><A NAME="ss8.94">8.94 set/qra (0)</A>
+</H2>
+
+<P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE>
+<P>
+<P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
+done a SET/LOCATION then your latitude and longitude will be set roughly
+correctly (assuming your locator is correct ;-). For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/QRA JO02LQ
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.95">8.95 set/qth (0)</A>
+</H2>
+
+<P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE>
+<P>
+<P>Tell the system where your are. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/qth East Dereham, Norfolk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.96">8.96 set/talk (0)</A>
+</H2>
+
+<P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE>
+<P>
+<P>Allow talk messages to arrive at your console. You can switch off
+talks with the <EM>unset/talk</EM> command.
+<P>
+<H2><A NAME="ss8.97">8.97 set/wcy (0)</A>
+</H2>
+
+<P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE>
+<P>
+<P>Allow WCY information to be seen at your console. You can switch off
+WCY messages with the <EM>unset/wcy</EM> command.
+<P>
+<H2><A NAME="ss8.98">8.98 set/wwv (0)</A>
+</H2>
+
+<P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE>
+<P>
+<P>Allow WWV information to be seen at your console. You can switch off
+WWV messages with the <EM>unset/wwv</EM> command.
+<P>
+<H2><A NAME="ss8.99">8.99 set/wx (0)</A>
+</H2>
+
+<P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE>
+<P>
+<P>Allow WX information to be seen at your console. You can switch off
+WX messages with the <EM>unset/wx</EM> command.
+<P>
+<H2><A NAME="ss8.100">8.100 show/baddx (1)</A>
+</H2>
+
+<P><CODE><B>show/baddx</B>Show all the bad dx calls in the system</CODE>
+<P>
+<P>Display all the bad dx callsigns in the system, see SET/BADDX
+for more information.
+<P>
+<H2><A NAME="ss8.101">8.101 show/badnode (6)</A>
+</H2>
+
+<P><CODE><B>show/badnode</B> Show all the bad nodes in the system</CODE>
+<P>
+<P>Display all the bad node callsigns in the system, see SET/BADNODE
+for more information.
+<P>
+<H2><A NAME="ss8.102">8.102 show/badspotter (1)</A>
+</H2>
+
+<P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE>
+<P>
+<P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
+for more information.
+<P>
+<H2><A NAME="ss8.103">8.103 show/configuration (0)</A>
+</H2>
+
+<P><CODE><B>show/configuration [<node>]</B> Show all visible nodes and their users</CODE>
+<P>
+<P>This command allows you to see all the users that can be seen
+and the nodes to which they are connected. With the optional <EM>node</EM>,
+you can specify a particular node to look at.
+<P>This command is normally abbreviated to: sh/c
+<P>BE WARNED: the list that is returned can be VERY long
+<P>
+<H2><A NAME="ss8.104">8.104 show/configuration/node (0)</A>
+</H2>
+
+<P><CODE><B>show/configuration/node</B> Show all the nodes connected</CODE>
+<P>
+<P>Show all the nodes connected locally and the nodes they have connected.
+<P>
+<H2><A NAME="ss8.105">8.105 show/connect (1)</A>
+</H2>
+
+<P><CODE><B>show/connect</B> Show all the active connections</CODE>
+<P>
+<P>This command shows information on all the active connections known to
+the node. This command gives slightly more information than WHO.
+<P>
+<H2><A NAME="ss8.106">8.106 show/date (0)</A>
+</H2>
+
+<P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
+the local time</CODE>
+<P>
+<P>This is very nearly the same as SHOW/TIME, the only difference the format
+of the date string if no arguments are given.
+<P>If no prefixes or callsigns are given then this command returns the local
+time and UTC as the computer has it right now. If you give some prefixes
+then it will show UTC and UTC + the local offset (not including DST) at
+the prefixes or callsigns that you specify.
+<P>
+<H2><A NAME="ss8.107">8.107 show/debug (9)</A>
+</H2>
+
+<P><CODE><B>show/debug</B> Show what levels of debug you are logging</CODE>
+<P>
+<P>The levels can be set with <EM>set/debug</EM>
+<P>
+<H2><A NAME="ss8.108">8.108 show/dx (0)</A>
+</H2>
+
+<P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE>
+<P>
+<P>If you just type SHOW/DX you will get the last so many spots
+(sysop configurable, but usually 10).
+<P>In addition you can add any number of these options in very nearly
+any order to the basic SHOW/DX command, they are:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+on <band> - eg 160m 20m 2m 23cm 6mm
+on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
+
+<number> - the number of spots you want
+<from>-<to> - <from> spot no <to> spot no in
+ the selected list
+
+<prefix> - for a spotted callsign beginning with <prefix>
+*<suffix> - for a spotted callsign ending in <suffix>
+*<string>* - for a spotted callsign containing <string>
+
+day <number> - starting <number> days ago
+day <from>-<to> - <from> days <to> days ago
+
+info <text> - any spots containing <text> in the info or remarks
+
+by <call> - any spots spotted by <call> (spotter <call>
+ is the same).
+
+qsl - this automatically looks for any qsl info on the call
+ held in the spot database.
+
+iota [<iota>] - If the iota island number is missing it will
+ look for the string iota and anything which looks like
+ an iota island number. If you specify then it will look
+ for that island.
+
+qra [<locator>] - this will look for the specific locator if
+ you specify one or else anything that looks like a locator.
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>e.g.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+ SH/DX 9m0
+ SH/DX on 20m info iota
+ SH/DX 9a on vhf day 30
+ SH/DX rf1p qsl
+ SH/DX iota
+ SH/DX iota eu-064
+ SH/DX qra jn86
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.109">8.109 show/dxcc (0)</A>
+</H2>
+
+<P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE>
+<P>
+<P>This command takes the <prefix> (which can be a full or partial
+callsign if desired), looks up which internal country number it is
+and then displays all the spots as per SH/DX for that country.
+<P>The options for SHOW/DX also apply to this command.
+e.g.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+ SH/DXCC G
+ SH/DXCC W on 20m info iota
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.110">8.110 show/files (0)</A>
+</H2>
+
+<P><CODE><B>show/files [<filearea> [<string>]]</B> List
+the contents of a filearea</CODE>
+<P>
+<P>SHOW/FILES on its own will show you a list of the various fileareas
+available on the system. To see the contents of a particular file
+area type:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/FILES <filearea>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>where <filearea> is the name of the filearea you want to see the
+contents of.
+<P>You can also use shell globbing characters like '*' and '?' in a
+string to see a selection of files in a filearea eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/FILES bulletins arld*
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>See also TYPE - to see the contents of a file.
+<P>
+<H2><A NAME="ss8.111">8.111 show/filter (0)</A>
+</H2>
+
+<P><CODE><B>show/filter</B> Show the filters you have set</CODE>
+<P>
+<P>Show the contents of all the filters that are set by you. This command
+displays all the filters set - for all the various categories.
+<P>
+<H2><A NAME="ss8.112">8.112 show/filter (extended for sysops) (5)</A>
+</H2>
+
+<P><CODE><B>show/filter <callsign></B> Show the filters set by <callsign></CODE>
+<P>
+<P>A sysop can look at any filters that have been set.
+<P>
+<H2><A NAME="ss8.113">8.113 show/hops (8)</A>
+</H2>
+
+<P><CODE><B>show/hops <node_call> [ann|spots|wcy|wwv|]</B> Show the hop counts for a node</CODE>
+<P>
+<P>This command shows the hop counts set up for a node. You can specify
+which category you want to see. If you leave the category out then
+all the categories will be listed.
+<P>
+<H2><A NAME="ss8.114">8.114 show/isolate (1)</A>
+</H2>
+
+<P><CODE><B>show/isolate</B> Show a list of isolated nodes</CODE>
+<P>
+<P>Show which nodes are currently set to be isolated.
+<P>
+<H2><A NAME="ss8.115">8.115 show/lockout (9)</A>
+</H2>
+
+<P><CODE><B>show/lockout</B> Show a list of excluded callsigns</CODE>
+<P>
+<P>Show a list of callsigns that have been excluded (locked out) of the
+cluster locally with the <EM>set/lockout</EM> command
<P>
-<P>I am of course assuming that you have a machine with both DXSpider and
-Internet access running.
+<H2><A NAME="ss8.116">8.116 show/log (8)</A>
+</H2>
+
+<P><CODE><B>show/log [<callsign>]</B> Show excerpts from the system log</CODE>
+<P>
+<P>This command outputs a short section of the system log. On its own
+it will output a general logfile. With the optional callsign it will
+show output from the log associated with that callsign.
+<P>
+<H2><A NAME="ss8.117">8.117 show/moon (0)</A>
+</H2>
+
+<P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
+rise and set times</CODE>
+<P>
+<P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
+together with the azimuth and elevation of the sun currently at those
+locations.
+<P>If you don't specify any prefixes or callsigns, it will show the times for
+your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
+together with the current azimuth and elevation.
+<P>In addition, it will show the gain or loss dB relative to the nominal
+distance of 385,000Km due to the ellipsoidal nature of the orbit.
+<P>If all else fails it will show the Moonrise and set times for the node
+that you are connected to.
+<P>For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MOON
+ SH/MOON G1TLH W5UN
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.118">8.118 show/muf (0)</A>
+</H2>
+
+<P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
+the likely propagation to <prefix></CODE>
+<P>
+<P>This command allow you to estimate the likelihood of you contacting
+a station with the prefix you have specified. The output assumes a modest
+power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
+<P>The result predicts the most likely operating frequencies and signal
+levels for high frequency (shortwave) radio propagation paths on
+specified days of the year and hours of the day. It is most useful for
+paths between 250 km and 6000 km, but can be used with reduced accuracy
+for paths shorter or longer than this.
+<P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
+used to predict the MUF given the predicted flux, day of the year,
+hour of the day and geographic coordinates of the transmitter and
+receiver. This routine is reasonably accurate for the purposes here,
+with a claimed RMS error of 3.8 MHz, but much smaller and less complex
+than the programs used by major shortwave broadcasting organizations,
+such as the Voice of America.
+<P>The command will display some header information detailing its
+assumptions, together with the locations, latitude and longitudes and
+bearings. It will then show UTC (UT), local time at the other end
+(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
+(Zen) and the likely signal strengths. Then for each frequency for which
+the system thinks there is a likelihood of a circuit it prints a value.
+<P>The value is currently a likely S meter reading based on the conventional
+6dB / S point scale. If the value has a '+' appended it means that it is
+1/2 an S point stronger. If the value is preceeded by an 'm' it means that
+there is likely to be much fading and by an 's' that the signal is likely
+to be noisy.
+<P>By default SHOW/MUF will show the next two hours worth of data. You
+can specify anything up to 24 hours worth of data by appending the no of
+hours required after the prefix. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MUF W
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>produces:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
+ Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
+ Location Lat / Long Azim
+ East Dereham, Norfolk 52 41 N 0 57 E 47
+ United-States-W 43 0 N 87 54 W 299
+ UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
+ 18 23 11.5 -35 mS0+ mS2 S3
+ 19 0 11.2 -41 mS0+ mS2 S3
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>indicating that you will have weak, fading circuits on top band and
+80m but usable signals on 40m (about S3).
+<P>inputing:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MUF W 24
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will get you the above display, but with the next 24 hours worth of
+propagation data.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MUF W L 24
+ SH/MUF W 24 Long
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Gives you an estimate of the long path propagation characterics. It
+should be noted that the figures will probably not be very useful, nor
+terrible accurate, but it is included for completeness.
+<P>
+<H2><A NAME="ss8.119">8.119 show/node (1)</A>
+</H2>
+
+<P><CODE><B>show/node [<node_call> ...]</B> Show the type and version
+number of nodes</CODE>
+<P>
+<P>Show the type and version (if connected) of the nodes specified on the
+command line. If no callsigns are specified then a sorted list of all
+the non-user callsigns known to the system will be displayed.
+<P>
+<H2><A NAME="ss8.120">8.120 show/prefix (0)</A>
+</H2>
+
+<P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE>
+<P>
+<P>This command takes the <callsign> (which can be a full or partial
+callsign or a prefix), looks up which internal country number
+it is and then displays all the relevant prefixes for that country
+together with the internal country no, the CQ and ITU regions.
+<P>See also SHOW/DXCC
+<P>
+<P>
+<H2><A NAME="ss8.121">8.121 show/program (5)</A>
+</H2>
+
+<P><CODE><B>show/program</B> Show the locations of all the included program modules</CODE>
+<P>
+<P>Show the name and location where every program module was load from. This
+is useful for checking where you think you have loaded a .pm file from.
+<P>
+<H2><A NAME="ss8.122">8.122 show/qra (0)</A>
+</H2>
+
+<P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
+between locators<BR>
+<B>show/qra <lat> <long></B> Convert latitude and longitude to a locator</CODE>
+<P>
+<P>This is a multipurpose command that allows you either to calculate the
+distance and bearing between two locators or (if only one locator is
+given on the command line) the distance and beraing from your station
+to the locator. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+SH/QRA IO92QL
+SH/QRA JN06 IN73
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The first example will show the distance and bearing to the locator from
+yourself, the second example will calculate the distance and bearing from
+the first locator to the second. You can use 4 or 6 character locators.
+<P>It is also possible to convert a latitude and longitude to a locator by
+using this command with a latitude and longitude as an argument, for
+example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+SH/QRA 52 41 N 0 58 E
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.123">8.123 show/qrz (0)</A>
+</H2>
+
+<P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE>
+<P>
+<P>This command queries the QRZ callbook server on the internet
+and returns any information available for that callsign. This service
+is provided for users of this software by http://www.qrz.com
+<P>
+<H2><A NAME="ss8.124">8.124 show/route (0)</A>
+</H2>
+
+<P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE>
+<P>
+<P>This command allows you to see to which node the callsigns specified are
+connected. It is a sort of inverse sh/config.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ sh/route n2tly
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.125">8.125 show/satellite (0)</A>
+</H2>
+
+<P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
+Show satellite tracking data</CODE>
+<P>
+<P>Show the tracking data from your location to the satellite of your choice
+from now on for the next few hours.
+<P>If you use this command without a satellite name it will display a list
+of all the satellites known currently to the system.
+<P>If you give a name then you can obtain tracking data of all the passes
+that start and finish 5 degrees below the horizon. As default it will
+give information for the next three hours for every five minute period.
+<P>You can alter the number of hours and the step size, within certain
+limits.
+<P>Each pass in a period is separated with a row of '-----' characters
+<P>So for example:-
<P>
-<P>BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
-ENTIRE SPIDER TREE!!
+<BLOCKQUOTE><CODE>
+<PRE>
+SH/SAT AO-10
+SH/SAT FENGYUN1 12 2
+</PRE>
+</CODE></BLOCKQUOTE>
<P>
-<P>Assuming you are connected to the Internet, you need to login to the
-CVS repository and then update your Spider source. There are several
-steps which are listed below ...
+<H2><A NAME="ss8.126">8.126 show/sun (0)</A>
+</H2>
+
+<P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
+sun rise and set times</CODE>
<P>
-<P>First login as the user <EM>sysop</EM>. Next you need to connect to the CVS
-repository. You do this with the command below ...
+<P>Show the sun rise and set times for a (list of) prefixes or callsigns,
+together with the azimuth and elevation of the sun currently at those
+locations.
+<P>If you don't specify any prefixes or callsigns, it will show the times for
+your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
+together with the current azimuth and elevation.
+<P>If all else fails it will show the sunrise and set times for the node
+that you are connected to.
+<P>For example:-
<P>
+<BLOCKQUOTE><CODE>
<PRE>
-cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
+ SH/SUN
+ SH/SUN G1TLH K9CW ZS
</PRE>
-<P>You will get a password prompt. Simply hit return here and your machine should
-return to a normal linux prompt.
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss8.127">8.127 show/time (0)</A>
+</H2>
+
+<P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
+the local time</CODE>
+<P>
+<P>If no prefixes or callsigns are given then this command returns the local
+time and UTC as the computer has it right now. If you give some prefixes
+then it will show UTC and UTC + the local offset (not including DST) at
+the prefixes or callsigns that you specify.
+<P>
+<H2><A NAME="ss8.128">8.128 show/wcy (0)</A>
+</H2>
+
+<P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
+<B>show/wcy <n></B> Show the last <n> WCY broadcasts</CODE>
+<P>
+<P>Display the most recent WCY information that has been received by the system
+<P>
+<H2><A NAME="ss8.129">8.129 show/wwv (0)</A>
+</H2>
+
+<P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
+<B>show/wwv <n></B> Show the last <n> WWV broadcasts</CODE>
+<P>
+<P>Display the most recent WWV information that has been received by the system
+<P>
+<P>
+<H2><A NAME="ss8.130">8.130 shutdown (5)</A>
+</H2>
+
+<P><CODE><B>shutdown</B> Shutdown the cluster</CODE>
+<P>
+<P>Shutdown the cluster and disconnect all the users. If you have Spider
+set to respawn in /etc/inittab it will of course restart.
+<P>
+<H2><A NAME="ss8.131">8.131 spoof (9)</A>
+</H2>
+
+<P><CODE><B>spoof <callsign> <command></B> Run commands as another user</CODE>
+<P>
+<P>This is a very simple yet powerful command for the sysop. It allows you to
+issue commands as if you were a different user. This is very useful for the
+kind of things that users seem to always get wrong.. like home_node for
+example.
+<P>
+<H2><A NAME="ss8.132">8.132 stat/db (5)</A>
+</H2>
+
+<P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE>
+<P>
+<P>Show the internal status of a database descriptor.
+<P>Depending on your privilege level you will see more or less information.
+This command is unlikely to be of much use to anyone other than a sysop.
<P>
-<P>What happens next depends on whether you have an existing installation that
-you want to update with the latest and greatest or whether you just want
-to see what is there and/or run it on a new machine for testing.
-<P>If you are installing Spider from CVS then change directory to /home/sysop
-<P>If you are wanting to update Spider then cd to /tmp
+<H2><A NAME="ss8.133">8.133 stat/channel (5)</A>
+</H2>
+
+<P><CODE><B>stat/channel <callsign></B> Show the status of a channel on the cluster</CODE>
+<P>
+<P>Show the internal status of the channel object either for the channel that
+you are on or else for the callsign that you asked for.
+<P>Only the fields that are defined (in perl term) will be displayed.
+<P>
+<H2><A NAME="ss8.134">8.134 stat/msg (5)</A>
+</H2>
+
+<P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE>
+<P>
+<P>This command shows the internal status of a message and includes information
+such as to whom it has been forwarded, its size, origin etc etc.
+<P>
+<H2><A NAME="ss8.135">8.135 stat/user (5)</A>
+</H2>
+
+<P><CODE><B>stat/user <callsign></B> Show the full status of a user</CODE>
+<P>
+<P>Shows the full contents of a user record including all the secret flags
+and stuff.
+<P>Only the fields that are defined (in perl term) will be displayed.
<P>
-<P>The next step will create a brand new 'spider' directory in your current
-directory.
+<H2><A NAME="ss8.136">8.136 sysop (0)</A>
+</H2>
+
+<P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE>
+<P>
+<P>The system automatically reduces your privilege level to that of a
+normal user if you login in remotely. This command allows you to
+regain your normal privilege level. It uses the normal system: five
+numbers are returned that are indexes into the character array that is
+your assigned password (see SET/PASSWORD). The indexes start from
+zero.
+<P>You are expected to return a string which contains the characters
+required in the correct order. You may intersperse those characters
+with others to obscure your reply for any watchers. For example (and
+these values are for explanation :-):
<P>
+<BLOCKQUOTE><CODE>
<PRE>
-cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
+ password = 012345678901234567890123456789
+ > sysop
+ 22 10 15 17 3
</PRE>
-<P>This command is all on one line.
+</CODE></BLOCKQUOTE>
+<P>you type:-
<P>
-<P>Hopefully your screen should show you downloading files. The -z3 simply compresses
-the download to improve speed.
-When this has finished, you will have exactly the same as if you had untarred a full
-tarball PLUS some extra directories and files that CVS needs to do the magic that
-it does.
+<BLOCKQUOTE><CODE>
+<PRE>
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>They will all match. If there is no password you will still be offered
+numbers but nothing will happen when you input a string. Any match is
+case sensitive.
<P>
-<P>Now if you are doing a new installation, that's it. Carry on as if you have
-just downloaded and untarred the lastest tarball.
+<H2><A NAME="ss8.137">8.137 talk (0)</A>
+</H2>
+
+<P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
+<B>talk <callsign> <text></B> Send a text message to <callsign><BR>
+<B>talk <callsign> > <node_call> [<text>]</B>
+Send a text message to <callsign> via <node_call></CODE>
<P>
-<P>If you want to upgrade your current installation then do this ...
+<P>Send a short message to any other station that is visible on the cluster
+system. You can send it to anyone you can see with a SHOW/CONFIGURATION
+command, they don't have to be connected locally.
+<P>The second form of TALK is used when other cluster nodes are connected
+with restricted information. This usually means that they don't send
+the user information usually associated with logging on and off the cluster.
+<P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
+see GB7TLH in the SH/C list but with no users, then you would use the
+second form of the talk message.
+<P>If you want to have a ragchew with someone you can leave the text message
+out and the system will go into 'Talk' mode. What this means is that a
+short message is sent to the recipient telling them that you are in a 'Talking'
+frame of mind and then you just type - everything you send will go to the
+station that you asked for.
+<P>All the usual announcements, spots and so on will still come out on your
+terminal.
+<P>If you want to do something (such as send a spot) you precede the normal
+command with a '/' character, eg:-
<P>
<BLOCKQUOTE><CODE>
<PRE>
-tar cvfz /tmp/s.tgz spider
-cd /
-tar xvfzp /tmp/s.tgz
+ /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
+ /HELP talk
</PRE>
</CODE></BLOCKQUOTE>
-<P>This is assuming you downloaded to the /tmp directory of course.
+<P>To leave talk mode type:
<P>
-<P>NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions
-correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????
-<P>Remember to recompile the C client (cd /spider/src; make)
+<BLOCKQUOTE><CODE>
+<PRE>
+ /EX
+</PRE>
+</CODE></BLOCKQUOTE>
<P>
-<P>At this point the files have been upgraded. You can (usually) restart the cluster
-in your own time. However, if you attempt to use any new commands or features
-expect it to be fatal! At least your cluster will have been restarted then so it
-will be too late to worry about it!
+<H2><A NAME="ss8.138">8.138 type (0)</A>
+</H2>
+
+<P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE>
<P>
-<P>Now the magic part! From now on when you want to update, simply connect to the
-Internet and then, as the user <EM>sysop</EM> ...
+<P>Type out the contents of a file in a filearea. So, for example, in
+filearea 'bulletins' you want to look at file 'arld051' you would
+enter:-
<P>
<BLOCKQUOTE><CODE>
<PRE>
-cd /spider
-cvs -z3 update -d
+ TYPE bulletins/arld051
</PRE>
</CODE></BLOCKQUOTE>
-<P>and your files will be updated. As above, remember to recompile the "C" client
-if it has been updated (CVS will tell you) and restart if any of the perl scripts
-have been altered or added, again, CVS will tell you.
+<P>See also SHOW/FILES to see what fileareas are available and a
+list of content.
+<P>
+<H2><A NAME="ss8.139">8.139 who (0)</A>
+</H2>
+
+<P><CODE><B>who</B> Show who is physically connected locally</CODE>
+<P>
+<P>This is a quick listing that shows which callsigns are connected and
+what sort of connection they have
+<P>
+<H2><A NAME="ss8.140">8.140 wx (0)</A>
+</H2>
+
+<P><CODE><B>wx <text></B> Send a weather message to local users<BR>
+<B>wx full <text> </B> Send a weather message to all cluster users</CODE>
+<P>
+<P>Weather messages can sometimes be useful if you are experiencing an extreme
+that may indicate enhanced conditions
+<P>
+<H2><A NAME="ss8.141">8.141 wx (enhanced for sysops) (5)</A>
+</H2>
+
+<P><CODE><B>wx sysop <text></B> Send a weather message to other clusters only</CODE>
+<P>
+<P>Send a weather message only to other cluster nodes and not to general users.
+<P>
<P>
-<P>You will find any changes documented in the /spider/Changes file.
<P>
<HR>
-<A HREF="adminmanual-9.html">Next</A>
+Next
<A HREF="adminmanual-7.html">Previous</A>
<A HREF="adminmanual.html#toc8">Contents</A>
</BODY>
<HR>
<H1>The DXSpider Administration Manual v1.47</H1>
-<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.47 April 2001 revision 1.0
+<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.48 July 2001 revision 1.0
<P><HR>
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
<HR>
<P>
-<H2><A NAME="toc1">1.</A> <A HREF="adminmanual-1.html">Hop control</A></H2>
+<H2><A NAME="toc1">1.</A> <A HREF="adminmanual-1.html">Routing and Filtering</A></H2>
<UL>
-<LI><A HREF="adminmanual-1.html#ss1.1">1.1 Basic hop control</A>
-<LI><A HREF="adminmanual-1.html#ss1.2">1.2 Isolating networks</A>
+<LI><A HREF="adminmanual-1.html#ss1.1">1.1 Introduction</A>
+<LI><A HREF="adminmanual-1.html#ss1.2">1.2 Route Filters</A>
+<LI><A HREF="adminmanual-1.html#ss1.3">1.3 The default_node filter</A>
+<LI><A HREF="adminmanual-1.html#ss1.4">1.4 General route filtering</A>
+<LI><A HREF="adminmanual-1.html#ss1.5">1.5 General filter rules</A>
+<LI><A HREF="adminmanual-1.html#ss1.6">1.6 Types of filter</A>
+<LI><A HREF="adminmanual-1.html#ss1.7">1.7 Filter options</A>
+<LI><A HREF="adminmanual-1.html#ss1.8">1.8 Default filters</A>
+<LI><A HREF="adminmanual-1.html#ss1.9">1.9 Advanced filtering</A>
+<LI><A HREF="adminmanual-1.html#ss1.10">1.10 Basic hop control</A>
+<LI><A HREF="adminmanual-1.html#ss1.11">1.11 Isolating networks</A>
</UL>
<P>
-<H2><A NAME="toc2">2.</A> <A HREF="adminmanual-2.html">Filtering (Old Style upto v1.44)</A></H2>
+<H2><A NAME="toc2">2.</A> <A HREF="adminmanual-2.html">Other filters</A></H2>
<UL>
-<LI><A HREF="adminmanual-2.html#ss2.1">2.1 Spots</A>
-<LI><A HREF="adminmanual-2.html#ss2.2">2.2 Announcements</A>
-<LI><A HREF="adminmanual-2.html#ss2.3">2.3 WWV</A>
+<LI><A HREF="adminmanual-2.html#ss2.1">2.1 Filtering Mail</A>
+<LI><A HREF="adminmanual-2.html#ss2.2">2.2 Filtering DX callouts (Depricated)</A>
+<LI><A HREF="adminmanual-2.html#ss2.3">2.3 Filtering words from text fields in Announce, Talk and DX spots</A>
</UL>
<P>
-<H2><A NAME="toc3">3.</A> <A HREF="adminmanual-3.html">Filtering (New Style v1.45 and later)</A></H2>
+<H2><A NAME="toc3">3.</A> <A HREF="adminmanual-3.html">Mail</A></H2>
<UL>
-<LI><A HREF="adminmanual-3.html#ss3.1">3.1 General filter rules</A>
-<LI><A HREF="adminmanual-3.html#ss3.2">3.2 Types of filter</A>
-<LI><A HREF="adminmanual-3.html#ss3.3">3.3 Filter options</A>
-<LI><A HREF="adminmanual-3.html#ss3.4">3.4 Default filters</A>
-<LI><A HREF="adminmanual-3.html#ss3.5">3.5 Advanced filtering</A>
+<LI><A HREF="adminmanual-3.html#ss3.1">3.1 Personal mail</A>
+<LI><A HREF="adminmanual-3.html#ss3.2">3.2 Bulletin mail</A>
+<LI><A HREF="adminmanual-3.html#ss3.3">3.3 Forward.pl</A>
+<LI><A HREF="adminmanual-3.html#ss3.4">3.4 The msg command</A>
+<LI><A HREF="adminmanual-3.html#ss3.5">3.5 Message status</A>
+<LI><A HREF="adminmanual-3.html#ss3.6">3.6 Filtering mail</A>
+<LI><A HREF="adminmanual-3.html#ss3.7">3.7 Distribution lists</A>
+<LI><A HREF="adminmanual-3.html#ss3.8">3.8 BBS interface</A>
</UL>
<P>
-<H2><A NAME="toc4">4.</A> <A HREF="adminmanual-4.html">Other filters</A></H2>
+<H2><A NAME="toc4">4.</A> <A HREF="adminmanual-4.html">Databases</A></H2>
<UL>
-<LI><A HREF="adminmanual-4.html#ss4.1">4.1 Filtering Mail</A>
-<LI><A HREF="adminmanual-4.html#ss4.2">4.2 Filtering DX callouts (Depricated)</A>
-<LI><A HREF="adminmanual-4.html#ss4.3">4.3 Filtering words from text fields in Announce, Talk and DX spots</A>
+<LI><A HREF="adminmanual-4.html#ss4.1">4.1 Creating databases</A>
+<LI><A HREF="adminmanual-4.html#ss4.2">4.2 Importing databases</A>
+<LI><A HREF="adminmanual-4.html#ss4.3">4.3 Checking available databases</A>
+<LI><A HREF="adminmanual-4.html#ss4.4">4.4 Looking up databases</A>
+<LI><A HREF="adminmanual-4.html#ss4.5">4.5 Removing databases</A>
</UL>
<P>
-<H2><A NAME="toc5">5.</A> <A HREF="adminmanual-5.html">Mail</A></H2>
+<H2><A NAME="toc5">5.</A> <A HREF="adminmanual-5.html">Information, files and useful programs</A></H2>
<UL>
-<LI><A HREF="adminmanual-5.html#ss5.1">5.1 Personal mail</A>
-<LI><A HREF="adminmanual-5.html#ss5.2">5.2 Bulletin mail</A>
-<LI><A HREF="adminmanual-5.html#ss5.3">5.3 Forward.pl</A>
-<LI><A HREF="adminmanual-5.html#ss5.4">5.4 The msg command</A>
-<LI><A HREF="adminmanual-5.html#ss5.5">5.5 Message status</A>
-<LI><A HREF="adminmanual-5.html#ss5.6">5.6 Filtering mail</A>
-<LI><A HREF="adminmanual-5.html#ss5.7">5.7 Distribution lists</A>
-<LI><A HREF="adminmanual-5.html#ss5.8">5.8 BBS interface</A>
+<LI><A HREF="adminmanual-5.html#ss5.1">5.1 MOTD</A>
+<LI><A HREF="adminmanual-5.html#ss5.2">5.2 Downtime message</A>
+<LI><A HREF="adminmanual-5.html#ss5.3">5.3 Other text messages</A>
+<LI><A HREF="adminmanual-5.html#ss5.4">5.4 The Aliases file</A>
+<LI><A HREF="adminmanual-5.html#ss5.5">5.5 Console.pl</A>
+<LI><A HREF="adminmanual-5.html#ss5.6">5.6 Updating kepler data</A>
+<LI><A HREF="adminmanual-5.html#ss5.7">5.7 The QRZ callbook</A>
</UL>
<P>
-<H2><A NAME="toc6">6.</A> <A HREF="adminmanual-6.html">Databases</A></H2>
-
-<UL>
-<LI><A HREF="adminmanual-6.html#ss6.1">6.1 Creating databases</A>
-<LI><A HREF="adminmanual-6.html#ss6.2">6.2 Importing databases</A>
-<LI><A HREF="adminmanual-6.html#ss6.3">6.3 Checking available databases</A>
-<LI><A HREF="adminmanual-6.html#ss6.4">6.4 Looking up databases</A>
-<LI><A HREF="adminmanual-6.html#ss6.5">6.5 Removing databases</A>
-</UL>
-<P>
-<H2><A NAME="toc7">7.</A> <A HREF="adminmanual-7.html">Information, files and useful programs</A></H2>
-
-<UL>
-<LI><A HREF="adminmanual-7.html#ss7.1">7.1 MOTD</A>
-<LI><A HREF="adminmanual-7.html#ss7.2">7.2 Downtime message</A>
-<LI><A HREF="adminmanual-7.html#ss7.3">7.3 Other text messages</A>
-<LI><A HREF="adminmanual-7.html#ss7.4">7.4 The Aliases file</A>
-<LI><A HREF="adminmanual-7.html#ss7.5">7.5 Console.pl</A>
-<LI><A HREF="adminmanual-7.html#ss7.6">7.6 Updating kepler data</A>
-<LI><A HREF="adminmanual-7.html#ss7.7">7.7 The QRZ callbook</A>
-</UL>
-<P>
-<H2><A NAME="toc8">8.</A> <A HREF="adminmanual-8.html">CVS</A></H2>
+<H2><A NAME="toc6">6.</A> <A HREF="adminmanual-6.html">CVS</A></H2>
<P>
-<H2><A NAME="toc9">9.</A> <A HREF="adminmanual-9.html">The DXSpider command set</A></H2>
+<H2><A NAME="toc7">7.</A> <A HREF="adminmanual-7.html">The DXSpider command set</A></H2>
<UL>
-<LI><A HREF="adminmanual-9.html#ss9.1">9.1 accept/announce (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.2">9.2 accept/announce (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.3">9.3 accept/spots (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.4">9.4 accept/spots (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.5">9.5 accept/wcy (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.6">9.6 accept/wcy (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.7">9.7 accept/wwv (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.8">9.8 accept/wwv (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.9">9.9 announce (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.10">9.10 announce full (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.11">9.11 announce sysop (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.12">9.12 apropos (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.13">9.13 bye (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.14">9.14 catchup (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.15">9.15 clear/spots (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.16">9.16 connect (5) </A>
-<LI><A HREF="adminmanual-9.html#ss9.17">9.17 dbavail (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.18">9.18 dbcreate (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.19">9.19 dbimport (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.20">9.20 dbremove (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.21">9.21 dbshow (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.22">9.22 debug (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.23">9.23 directory (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.24">9.24 directory (extended for sysops) (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.25">9.25 disconnect (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.26">9.26 dx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.27">9.27 export (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.28">9.28 export_users (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.29">9.29 forward/latlong (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.30">9.30 forward/opername (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.31">9.31 help (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.32">9.32 init (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.33">9.33 kill (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.34">9.34 kill (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.35">9.35 kill full (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.36">9.36 links (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.37">9.37 load/aliases (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.38">9.38 load/baddx (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.39">9.39 load/badmsg (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.40">9.40 load/badwords (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.41">9.41 load/bands (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.42">9.42 load/cmd_cache (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.43">9.43 load/forward (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.44">9.44 load/messages (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.45">9.45 load/prefixes (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.46">9.46 merge (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.47">9.47 msg (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.48">9.48 pc (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.49">9.49 ping (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.50">9.50 rcmd (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.51">9.51 read (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.52">9.52 read (extended for sysops) (5) </A>
-<LI><A HREF="adminmanual-9.html#ss9.53">9.53 reject/announce</A>
-<LI><A HREF="adminmanual-9.html#ss9.54">9.54 reject/announce (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.55">9.55 reject/spots (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.56">9.56 reject/spots (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.57">9.57 reject/wcy (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.58">9.58 reject/wcy (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.59">9.59 reject/wwv (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.60">9.60 reject/wwv (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.61">9.61 reply (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.62">9.62 send (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.63">9.63 set/address (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.64">9.64 set/announce (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.65">9.65 set/arcluster (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.66">9.66 set/baddx (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.67">9.67 set/badnode (6)</A>
-<LI><A HREF="adminmanual-9.html#ss9.68">9.68 set/badspotter (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.69">9.69 set/beep (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.70">9.70 set/clx (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.71">9.71 set/debug (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.72">9.72 set/dx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.73">9.73 set/dxgrid (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.74">9.74 set/dxnet (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.75">9.75 set/echo (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.76">9.76 set/here (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.77">9.77 set/homenode (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.78">9.78 set/hops (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.79">9.79 set/isolate (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.80">9.80 set/language (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.81">9.81 set/location (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.82">9.82 set/sys_location (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.83">9.83 set/logininfo (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.84">9.84 set/lockout (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.85">9.85 set/name (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.86">9.86 set/node (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.87">9.87 set/obscount (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.88">9.88 set/page (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.89">9.89 set/password (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.90">9.90 set/pinginterval (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.91">9.91 set/privilege (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.92">9.92 set/spider (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.93">9.93 set/sys_qra (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.94">9.94 set/qra (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.95">9.95 set/qth (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.96">9.96 set/talk (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.97">9.97 set/wcy (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.98">9.98 set/wwv (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.99">9.99 set/wx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.100">9.100 show/baddx (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.101">9.101 show/badnode (6)</A>
-<LI><A HREF="adminmanual-9.html#ss9.102">9.102 show/badspotter (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.103">9.103 show/configuration (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.104">9.104 show/configuration/node (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.105">9.105 show/connect (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.106">9.106 show/date (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.107">9.107 show/debug (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.108">9.108 show/dx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.109">9.109 show/dxcc (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.110">9.110 show/files (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.111">9.111 show/filter (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.112">9.112 show/filter (extended for sysops) (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.113">9.113 show/hops (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.114">9.114 show/isolate (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.115">9.115 show/lockout (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.116">9.116 show/log (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.117">9.117 show/moon (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.118">9.118 show/muf (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.119">9.119 show/node (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.120">9.120 show/prefix (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.121">9.121 show/program (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.122">9.122 show/qra (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.123">9.123 show/qrz (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.124">9.124 show/route (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.125">9.125 show/satellite (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.126">9.126 show/sun (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.127">9.127 show/time (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.128">9.128 show/wcy (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.129">9.129 show/wwv (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.130">9.130 shutdown (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.131">9.131 spoof (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.132">9.132 stat/db (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.133">9.133 stat/channel (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.134">9.134 stat/msg (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.135">9.135 stat/user (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.136">9.136 sysop (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.137">9.137 talk (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.138">9.138 type (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.139">9.139 who (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.140">9.140 wx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.141">9.141 wx (enhanced for sysops) (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.1">7.1 accept/announce (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.2">7.2 accept/announce (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.3">7.3 accept/route (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.4">7.4 accept/spots (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.5">7.5 accept/spots (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.6">7.6 accept/wcy (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.7">7.7 accept/wcy (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.8">7.8 accept/wwv (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.9">7.9 accept/wwv (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.10">7.10 announce (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.11">7.11 announce full (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.12">7.12 announce sysop (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.13">7.13 apropos (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.14">7.14 bye (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.15">7.15 catchup (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.16">7.16 clear/spots (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.17">7.17 connect (5) </A>
+<LI><A HREF="adminmanual-7.html#ss7.18">7.18 dbavail (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.19">7.19 dbcreate (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.20">7.20 dbimport (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.21">7.21 dbremove (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.22">7.22 dbshow (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.23">7.23 debug (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.24">7.24 directory (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.25">7.25 directory (extended for sysops) (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.26">7.26 disconnect (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.27">7.27 dx (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.28">7.28 export (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.29">7.29 export_users (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.30">7.30 forward/latlong (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.31">7.31 forward/opername (1)</A>
+<LI><A HREF="adminmanual-7.html#ss7.32">7.32 help (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.33">7.33 init (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.34">7.34 kill (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.35">7.35 kill (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.36">7.36 kill full (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.37">7.37 links (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.38">7.38 load/aliases (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.39">7.39 load/baddx (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.40">7.40 load/badmsg (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.41">7.41 load/badwords (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.42">7.42 load/bands (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.43">7.43 load/cmd_cache (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.44">7.44 load/forward (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.45">7.45 load/messages (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.46">7.46 load/prefixes (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.47">7.47 merge (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.48">7.48 msg (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.49">7.49 pc (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.50">7.50 ping (1)</A>
+<LI><A HREF="adminmanual-7.html#ss7.51">7.51 rcmd (1)</A>
+<LI><A HREF="adminmanual-7.html#ss7.52">7.52 read (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.53">7.53 read (extended for sysops) (5) </A>
+<LI><A HREF="adminmanual-7.html#ss7.54">7.54 reject/announce</A>
+<LI><A HREF="adminmanual-7.html#ss7.55">7.55 reject/announce (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.56">7.56 reject/route (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.57">7.57 reject/spots (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.58">7.58 reject/spots (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.59">7.59 reject/wcy (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.60">7.60 reject/wcy (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.61">7.61 reject/wwv (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.62">7.62 reject/wwv (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.63">7.63 reply (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.64">7.64 send (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.65">7.65 set/address (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.66">7.66 set/announce (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.67">7.67 set/arcluster (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.68">7.68 set/baddx (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.69">7.69 set/badnode (6)</A>
+<LI><A HREF="adminmanual-7.html#ss7.70">7.70 set/badspotter (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.71">7.71 set/beep (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.72">7.72 set/bbs (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.73">7.73 set/clx (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.74">7.74 set/debug (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.75">7.75 set/dx (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.76">7.76 set/dxgrid (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.77">7.77 set/dxnet (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.78">7.78 set/echo (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.79">7.79 set/here (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.80">7.80 set/homenode (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.81">7.81 set/hops (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.82">7.82 set/isolate (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.83">7.83 set/language (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.84">7.84 set/location (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.85">7.85 set/sys_location (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.86">7.86 set/logininfo (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.87">7.87 set/lockout (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.88">7.88 set/name (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.89">7.89 set/node (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.90">7.90 set/obscount (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.91">7.91 set/page (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.92">7.92 set/password (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.93">7.93 set/pinginterval (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.94">7.94 set/privilege (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.95">7.95 set/spider (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.96">7.96 set/sys_qra (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.97">7.97 set/qra (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.98">7.98 set/qth (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.99">7.99 set/talk (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.100">7.100 set/wcy (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.101">7.101 set/wwv (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.102">7.102 set/wx (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.103">7.103 show/baddx (1)</A>
+<LI><A HREF="adminmanual-7.html#ss7.104">7.104 show/badnode (6)</A>
+<LI><A HREF="adminmanual-7.html#ss7.105">7.105 show/badspotter (1)</A>
+<LI><A HREF="adminmanual-7.html#ss7.106">7.106 show/configuration (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.107">7.107 show/configuration/node (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.108">7.108 show/connect (1)</A>
+<LI><A HREF="adminmanual-7.html#ss7.109">7.109 show/date (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.110">7.110 show/debug (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.111">7.111 show/dx (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.112">7.112 show/dxcc (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.113">7.113 show/files (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.114">7.114 show/filter (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.115">7.115 show/filter (extended for sysops) (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.116">7.116 show/hops (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.117">7.117 show/isolate (1)</A>
+<LI><A HREF="adminmanual-7.html#ss7.118">7.118 show/lockout (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.119">7.119 show/log (8)</A>
+<LI><A HREF="adminmanual-7.html#ss7.120">7.120 show/moon (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.121">7.121 show/muf (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.122">7.122 show/node (1)</A>
+<LI><A HREF="adminmanual-7.html#ss7.123">7.123 show/prefix (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.124">7.124 show/program (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.125">7.125 show/qra (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.126">7.126 show/qrz (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.127">7.127 show/route (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.128">7.128 show/satellite (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.129">7.129 show/sun (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.130">7.130 show/time (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.131">7.131 show/wcy (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.132">7.132 show/wwv (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.133">7.133 shutdown (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.134">7.134 spoof (9)</A>
+<LI><A HREF="adminmanual-7.html#ss7.135">7.135 stat/db (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.136">7.136 stat/channel (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.137">7.137 stat/msg (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.138">7.138 stat/route_node (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.139">7.139 stat/route_user (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.140">7.140 stat/user (5)</A>
+<LI><A HREF="adminmanual-7.html#ss7.141">7.141 sysop (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.142">7.142 talk (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.143">7.143 type (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.144">7.144 who (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.145">7.145 wx (0)</A>
+<LI><A HREF="adminmanual-7.html#ss7.146">7.146 wx (enhanced for sysops) (5)</A>
</UL>
<HR>
<A HREF="adminmanual-1.html">Next</A>
The DXSpider Administration Manual v1.47
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.47 April 2001 revision 1.0
+ Version 1.48 July 2001 revision 1.0
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
- 1. Hop control
+ 1. Routing and Filtering
- 1.1 Basic hop control
- 1.2 Isolating networks
+ 1.1 Introduction
+ 1.2 Route Filters
+ 1.3 The default_node filter
+ 1.4 General route filtering
+ 1.5 General filter rules
+ 1.6 Types of filter
+ 1.7 Filter options
+ 1.8 Default filters
+ 1.9 Advanced filtering
+ 1.10 Basic hop control
+ 1.11 Isolating networks
- 2. Filtering (Old Style upto v1.44)
+ 2. Other filters
- 2.1 Spots
- 2.2 Announcements
- 2.3 WWV
+ 2.1 Filtering Mail
+ 2.2 Filtering DX callouts (Depricated)
+ 2.3 Filtering words from text fields in Announce, Talk and DX spots
- 3. Filtering (New Style v1.45 and later)
+ 3. Mail
- 3.1 General filter rules
- 3.2 Types of filter
- 3.3 Filter options
- 3.4 Default filters
- 3.5 Advanced filtering
+ 3.1 Personal mail
+ 3.2 Bulletin mail
+ 3.3 Forward.pl
+ 3.4 The msg command
+ 3.5 Message status
+ 3.6 Filtering mail
+ 3.7 Distribution lists
+ 3.8 BBS interface
- 4. Other filters
+ 4. Databases
- 4.1 Filtering Mail
- 4.2 Filtering DX callouts (Depricated)
- 4.3 Filtering words from text fields in Announce, Talk and DX spots
+ 4.1 Creating databases
+ 4.2 Importing databases
+ 4.3 Checking available databases
+ 4.4 Looking up databases
+ 4.5 Removing databases
- 5. Mail
+ 5. Information, files and useful programs
- 5.1 Personal mail
- 5.2 Bulletin mail
- 5.3 Forward.pl
- 5.4 The msg command
- 5.5 Message status
- 5.6 Filtering mail
- 5.7 Distribution lists
- 5.8 BBS interface
+ 5.1 MOTD
+ 5.2 Downtime message
+ 5.3 Other text messages
+ 5.4 The Aliases file
+ 5.5 Console.pl
+ 5.6 Updating kepler data
+ 5.7 The QRZ callbook
- 6. Databases
+ 6. CVS
- 6.1 Creating databases
- 6.2 Importing databases
- 6.3 Checking available databases
- 6.4 Looking up databases
- 6.5 Removing databases
+ 7. The DXSpider command set
- 7. Information, files and useful programs
-
- 7.1 MOTD
- 7.2 Downtime message
- 7.3 Other text messages
- 7.4 The Aliases file
- 7.5 Console.pl
- 7.6 Updating kepler data
- 7.7 The QRZ callbook
-
- 8. CVS
-
- 9. The DXSpider command set
-
- 9.1 accept/announce (0)
- 9.2 accept/announce (extended for sysops) (8)
- 9.3 accept/spots (0)
- 9.4 accept/spots (extended for sysops) (8)
- 9.5 accept/wcy (0)
- 9.6 accept/wcy (extended for sysops) (8)
- 9.7 accept/wwv (0)
- 9.8 accept/wwv (extended for sysops) (8)
- 9.9 announce (0)
- 9.10 announce full (0)
- 9.11 announce sysop (5)
- 9.12 apropos (0)
- 9.13 bye (0)
- 9.14 catchup (5)
- 9.15 clear/spots (0)
- 9.16 connect (5)
- 9.17 dbavail (0)
- 9.18 dbcreate (9)
- 9.19 dbimport (9)
- 9.20 dbremove (9)
- 9.21 dbshow (0)
- 9.22 debug (9)
- 9.23 directory (0)
- 9.24 directory (extended for sysops) (5)
- 9.25 disconnect (8)
- 9.26 dx (0)
- 9.27 export (9)
- 9.28 export_users (9)
- 9.29 forward/latlong (8)
- 9.30 forward/opername (1)
- 9.31 help (0)
- 9.32 init (5)
- 9.33 kill (0)
- 9.34 kill (5)
- 9.35 kill full (5)
- 9.36 links (0)
- 9.37 load/aliases (9)
- 9.38 load/baddx (9)
- 9.39 load/badmsg (9)
- 9.40 load/badwords (9)
- 9.41 load/bands (9)
- 9.42 load/cmd_cache (9)
- 9.43 load/forward (9)
- 9.44 load/messages (9)
- 9.45 load/prefixes (9)
- 9.46 merge (5)
- 9.47 msg (9)
- 9.48 pc (8)
- 9.49 ping (1)
- 9.50 rcmd (1)
- 9.51 read (0)
- 9.52 read (extended for sysops) (5)
- 9.53 reject/announce
- 9.54 reject/announce (extended for sysops) (8)
- 9.55 reject/spots (0)
- 9.56 reject/spots (extended for sysops) (8)
- 9.57 reject/wcy (0)
- 9.58 reject/wcy (extended for sysops) (8)
- 9.59 reject/wwv (0)
- 9.60 reject/wwv (extended for sysops) (8)
- 9.61 reply (0)
- 9.62 send (0)
- 9.63 set/address (0)
- 9.64 set/announce (0)
- 9.65 set/arcluster (5)
- 9.66 set/baddx (8)
- 9.67 set/badnode (6)
- 9.68 set/badspotter (8)
- 9.69 set/beep (0)
- 9.70 set/clx (5)
- 9.71 set/debug (9)
- 9.72 set/dx (0)
- 9.73 set/dxgrid (0)
- 9.74 set/dxnet (5)
- 9.75 set/echo (0)
- 9.76 set/here (0)
- 9.77 set/homenode (0)
- 9.78 set/hops (8)
- 9.79 set/isolate (9)
- 9.80 set/language (0)
- 9.81 set/location (0)
- 9.82 set/sys_location (9)
- 9.83 set/logininfo (0)
- 9.84 set/lockout (9)
- 9.85 set/name (0)
- 9.86 set/node (9)
- 9.87 set/obscount (9)
- 9.88 set/page (0)
- 9.89 set/password (9)
- 9.90 set/pinginterval (9)
- 9.91 set/privilege (9)
- 9.92 set/spider (5)
- 9.93 set/sys_qra (9)
- 9.94 set/qra (0)
- 9.95 set/qth (0)
- 9.96 set/talk (0)
- 9.97 set/wcy (0)
- 9.98 set/wwv (0)
- 9.99 set/wx (0)
- 9.100 show/baddx (1)
- 9.101 show/badnode (6)
- 9.102 show/badspotter (1)
- 9.103 show/configuration (0)
- 9.104 show/configuration/node (0)
- 9.105 show/connect (1)
- 9.106 show/date (0)
- 9.107 show/debug (9)
- 9.108 show/dx (0)
- 9.109 show/dxcc (0)
- 9.110 show/files (0)
- 9.111 show/filter (0)
- 9.112 show/filter (extended for sysops) (5)
- 9.113 show/hops (8)
- 9.114 show/isolate (1)
- 9.115 show/lockout (9)
- 9.116 show/log (8)
- 9.117 show/moon (0)
- 9.118 show/muf (0)
- 9.119 show/node (1)
- 9.120 show/prefix (0)
- 9.121 show/program (5)
- 9.122 show/qra (0)
- 9.123 show/qrz (0)
- 9.124 show/route (0)
- 9.125 show/satellite (0)
- 9.126 show/sun (0)
- 9.127 show/time (0)
- 9.128 show/wcy (0)
- 9.129 show/wwv (0)
- 9.130 shutdown (5)
- 9.131 spoof (9)
- 9.132 stat/db (5)
- 9.133 stat/channel (5)
- 9.134 stat/msg (5)
- 9.135 stat/user (5)
- 9.136 sysop (0)
- 9.137 talk (0)
- 9.138 type (0)
- 9.139 who (0)
- 9.140 wx (0)
- 9.141 wx (enhanced for sysops) (5)
+ 7.1 accept/announce (0)
+ 7.2 accept/announce (extended for sysops) (8)
+ 7.3 accept/route (8)
+ 7.4 accept/spots (0)
+ 7.5 accept/spots (extended for sysops) (8)
+ 7.6 accept/wcy (0)
+ 7.7 accept/wcy (extended for sysops) (8)
+ 7.8 accept/wwv (0)
+ 7.9 accept/wwv (extended for sysops) (8)
+ 7.10 announce (0)
+ 7.11 announce full (0)
+ 7.12 announce sysop (5)
+ 7.13 apropos (0)
+ 7.14 bye (0)
+ 7.15 catchup (5)
+ 7.16 clear/spots (0)
+ 7.17 connect (5)
+ 7.18 dbavail (0)
+ 7.19 dbcreate (9)
+ 7.20 dbimport (9)
+ 7.21 dbremove (9)
+ 7.22 dbshow (0)
+ 7.23 debug (9)
+ 7.24 directory (0)
+ 7.25 directory (extended for sysops) (5)
+ 7.26 disconnect (8)
+ 7.27 dx (0)
+ 7.28 export (9)
+ 7.29 export_users (9)
+ 7.30 forward/latlong (8)
+ 7.31 forward/opername (1)
+ 7.32 help (0)
+ 7.33 init (5)
+ 7.34 kill (0)
+ 7.35 kill (5)
+ 7.36 kill full (5)
+ 7.37 links (0)
+ 7.38 load/aliases (9)
+ 7.39 load/baddx (9)
+ 7.40 load/badmsg (9)
+ 7.41 load/badwords (9)
+ 7.42 load/bands (9)
+ 7.43 load/cmd_cache (9)
+ 7.44 load/forward (9)
+ 7.45 load/messages (9)
+ 7.46 load/prefixes (9)
+ 7.47 merge (5)
+ 7.48 msg (9)
+ 7.49 pc (8)
+ 7.50 ping (1)
+ 7.51 rcmd (1)
+ 7.52 read (0)
+ 7.53 read (extended for sysops) (5)
+ 7.54 reject/announce
+ 7.55 reject/announce (extended for sysops) (8)
+ 7.56 reject/route (8)
+ 7.57 reject/spots (0)
+ 7.58 reject/spots (extended for sysops) (8)
+ 7.59 reject/wcy (0)
+ 7.60 reject/wcy (extended for sysops) (8)
+ 7.61 reject/wwv (0)
+ 7.62 reject/wwv (extended for sysops) (8)
+ 7.63 reply (0)
+ 7.64 send (0)
+ 7.65 set/address (0)
+ 7.66 set/announce (0)
+ 7.67 set/arcluster (5)
+ 7.68 set/baddx (8)
+ 7.69 set/badnode (6)
+ 7.70 set/badspotter (8)
+ 7.71 set/beep (0)
+ 7.72 set/bbs (5)
+ 7.73 set/clx (5)
+ 7.74 set/debug (9)
+ 7.75 set/dx (0)
+ 7.76 set/dxgrid (0)
+ 7.77 set/dxnet (5)
+ 7.78 set/echo (0)
+ 7.79 set/here (0)
+ 7.80 set/homenode (0)
+ 7.81 set/hops (8)
+ 7.82 set/isolate (9)
+ 7.83 set/language (0)
+ 7.84 set/location (0)
+ 7.85 set/sys_location (9)
+ 7.86 set/logininfo (0)
+ 7.87 set/lockout (9)
+ 7.88 set/name (0)
+ 7.89 set/node (9)
+ 7.90 set/obscount (9)
+ 7.91 set/page (0)
+ 7.92 set/password (9)
+ 7.93 set/pinginterval (9)
+ 7.94 set/privilege (9)
+ 7.95 set/spider (5)
+ 7.96 set/sys_qra (9)
+ 7.97 set/qra (0)
+ 7.98 set/qth (0)
+ 7.99 set/talk (0)
+ 7.100 set/wcy (0)
+ 7.101 set/wwv (0)
+ 7.102 set/wx (0)
+ 7.103 show/baddx (1)
+ 7.104 show/badnode (6)
+ 7.105 show/badspotter (1)
+ 7.106 show/configuration (0)
+ 7.107 show/configuration/node (0)
+ 7.108 show/connect (1)
+ 7.109 show/date (0)
+ 7.110 show/debug (9)
+ 7.111 show/dx (0)
+ 7.112 show/dxcc (0)
+ 7.113 show/files (0)
+ 7.114 show/filter (0)
+ 7.115 show/filter (extended for sysops) (5)
+ 7.116 show/hops (8)
+ 7.117 show/isolate (1)
+ 7.118 show/lockout (9)
+ 7.119 show/log (8)
+ 7.120 show/moon (0)
+ 7.121 show/muf (0)
+ 7.122 show/node (1)
+ 7.123 show/prefix (0)
+ 7.124 show/program (5)
+ 7.125 show/qra (0)
+ 7.126 show/qrz (0)
+ 7.127 show/route (0)
+ 7.128 show/satellite (0)
+ 7.129 show/sun (0)
+ 7.130 show/time (0)
+ 7.131 show/wcy (0)
+ 7.132 show/wwv (0)
+ 7.133 shutdown (5)
+ 7.134 spoof (9)
+ 7.135 stat/db (5)
+ 7.136 stat/channel (5)
+ 7.137 stat/msg (5)
+ 7.138 stat/route_node (5)
+ 7.139 stat/route_user (5)
+ 7.140 stat/user (5)
+ 7.141 sysop (0)
+ 7.142 talk (0)
+ 7.143 type (0)
+ 7.144 who (0)
+ 7.145 wx (0)
+ 7.146 wx (enhanced for sysops) (5)
______________________________________________________________________
- 1. Hop control
-
- Starting with version 1.13 there is simple hop control available on a
- per node basis. Also it is possible to isolate a network completely so
- that you get all the benefits of being on that network, but can't pass
- on information from it to any other networks you may be connected to
- (or vice versa).
-
-
- 1.1. Basic hop control
-
- In /spider/data you will find a file called hop_table.pl. This is the
- file that controls your hop count settings. It has a set of default
- hops on the various PC frames and also a set for each node you want to
- alter the hops for. You may be happy with the default settings of
- course, but this powerful tool can help to protect and improve the
- network. The file will look something like this ...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #
- # hop table construction
- #
-
- package DXProt;
-
- # default hopcount to use
- $def_hopcount = 5;
-
- # some variable hop counts based on message type
- %hopcount =
- (
- 11 => 10,
- 16 => 10,
- 17 => 10,
- 19 => 10,
- 21 => 10,
- );
-
-
- # the per node hop control thingy
-
-
- %nodehops =
-
- GB7ADX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
-
- GB7UDX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- GB7BAA => {
- 11 => 5,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- };
-
-
-
-
-
- Each set of hops is contained within a pair of curly braces and
- contains a series of PC frame types. PC11 for example is a DX spot.
- The figures here are not exhaustive but should give you a good idea of
- how the file works.
-
-
- You can alter this file at any time, including whilst the cluster is
- running. If you alter the file during runtime, the command load/hops
- will bring your changes into effect.
-
-
-
- 1.2. Isolating networks
-
- It is possible to isolate networks from each other on a "gateway" node
- using the set/isolate <node_call> command.
-
-
- The effect of this is to partition an isolated network completely from
- another nodes connected to your node. Your node will appear on and
- otherwise behave normally on every network to which you are connected,
- but data from an isolated network will not cross onto any other
- network or vice versa. However all the spot, announce and WWV traffic
- and personal messages will still be handled locally (because you are a
- real node on all connected networks), that is locally connected users
- will appear on all networks and will be able to access and receive
- information from all networks transparently. All routed messages will
- be sent as normal, so if a user on one network knows that you are a
- gateway for another network, he can still still send a talk/announce
- etc message via your node and it will be routed across.
-
-
- The only limitation currently is that non-private messages cannot be
- passed down isolated links regardless of whether they are generated
- locally. This will change when the bulletin routing facility is added.
-
-
- If you use isolate on a node connection you will continue to receive
- all information from the isolated partner, however you will not pass
- any information back to the isolated node. There are times when you
- would like to forward only spots across a link (maybe during a contest
- for example). To do this, isolate the node in the normal way and put
- in a filter in the /spider/filter/spots directory to override the
- isolate. This filter can be very simple and consists of just one line
- ....
-
-
-
- $in = [
- [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count
- ];
-
-
-
-
-
- There is a lot more on filtering in the next section.
-
-
- 2. Filtering (Old Style upto v1.44)
-
- Filters can be set for spots, announcements and WWV. You will find
- the directories for these under /spider/filter. You will find some
- examples in the directories with the suffix .issue. There are two
- types of filter, one for incoming information and one for outgoing
- information. Outgoing filters are in the form CALLSIGN.pl and
- incoming filters are in the form in_CALLSIGN.pl. Filters can be set
- for both nodes and users.
-
-
- All filters work in basically the same way. There are several
- elements delimited by commas. There can be many lines in the filter
- and they are read from the top by the program. When writing a filter
- you need to think carefully about just what you want to achieve. You
- are either going to write a filter to accept or to reject. Think of a
- filter as having 2 main elements. For a reject filter, you would have
- a line or multiple lines rejecting the things you do not wish to
- receive and then a default line accepting everything else that is not
- included in the filter. Likewise, for an accept filter, you would
- have a line or multiple lines accepting the things you wish to receive
- and a default line rejecting everthing else.
-
-
- In the example below, a user requires a filter that would only return
- SSB spots posted in Europe on the HF bands. This is achieved by first
- rejecting the CW section of each HF band and rejecting all of VHF, UHF
- etc based on frequency. Secondly, a filter rule is set based on CQ
- zones to only accept spots posted in Europe. Lastly, a default filter
- rule is set to reject anything outside the filter.
-
-
-
- $in = [
- [ 0, 0, 'r', # reject all CW spots
- [
- 1800.0, 1850.0,
- 3500.0, 3600.0,
- 7000.0, 7040.0,
- 14000.0, 14100.0,
- 18068.0, 18110.0,
- 21000.0, 21150.0,
- 24890.0, 24930.0,
- 28000.0, 28180.0,
- 30000.0, 49000000000.0,
- ] ,1 ],
- [ 1, 11, 'n', [ 14, 15, 16, 20, 33, ], 15 ], #accept EU
- [ 0, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
- ];
-
-
-
-
-
- The actual elements of each filter are described more fully in the
- following sections.
-
-
- 2.1. Spots
-
- The elements of the Spot filter are ....
-
-
-
- [action, field_no, sort, possible_values, hops]
-
-
-
-
-
- There are 3 elements here to look at. Firstly, the action element.
- This is very simple and only 2 possible states exist, accept (1) or
- drop (0).
-
+ 1. Routing and Filtering
- The second element is the field_no. There are 13 possiblities to
- choose from here ....
+ 1.1. Introduction
+ From DXSpider version 1.48, major changes were introduced to the way
+ node connections are treated. This is part of an ongoing process to
+ remove problems with loops and to enable talk and other functions to
+ propagate across the whole of the worldwide cluster network. In fact,
+ in a Spider network, it would be useful, perhaps even necessary to
+ have loops. This would give real resilience to the network, meaning
+ that if a link dropped, the information flow would simply come in and
+ go out via a different route. Of course, we do not have a complete
+ network of Spider nodes, there are other programs out there. Some of
+ these do not have any protection from loops. Certainly AK1A does not
+ handle loops well at all. It is therefore necessary to have some form
+ of protection for these nodes.
+ This is achieved by using filtering on a route basis. There is a
+ default setting to help to protect the network, especially useful for
+ new and inexperienced SysOps. The idea is simple. When Spider is
+ started for the first time and a connection is made to or from another
+ node, the default is to only send the nodes you already have that are
+ in your own zone. For example, in the UK the default setting would be
+ to send only UK nodes to any connection. This can be filtered further
+ (down to a single node if needed) or expanded as required.
+ 1.2. Route Filters
+ As mentioned in the introduction, a default setting exists. If this
+ is all you want to use then that is fine, you have nothing else to do.
+ However, if you want to make any alterations then you need to know a
+ bit about filters.
- 0 = frequency
- 1 = call
- 2 = date in unix format
- 3 = comment
- 4 = spotter
- 5 = spotted dxcc country
- 6 = spotter's dxcc country
- 7 = origin
- 8 = spotted itu
- 9 = spotted cq
- 10 = spotter's itu
- 11 = spotter's cq
- 12 = callsign of the channel on which the spot has appeared
+ It is possible to reset the default setting for node connections
+ should you wish to do so, however this can be dangerous to the network
+ unless you have some experience in how all this works.... be careful!
+ It is also possible to change settings for one connection only. You
+ can, therefore, have many different filters set dependent on the
+ amount of node links you have.
+ I should at this stage give a little bit of background on filters.
+ All the filters in Spider work in basically the same way. You can
+ either accept or reject various options in order to create the filter
+ rules you wish to achieve. Some filters are user settable, others can
+ only be altered by the sysop. Route filtering can only be done by the
+ sysop.
- The third element tells us what to expect in the fourth element.
- There are 4 possibilities ....
+ 1.3. The default_node filter
+ As discussed previously, a default setting exists that only sends
+ nodes from your own zone. This can be overridden by using the
+ default_node filter option like this ...
- n - numeric list of numbers e.g. [ 1,2,3 ]
- r - ranges of pairs of numbers e.g. between 2 and 4 or 10 to 17 - [ 2,4, 10,17 ]
- a - an alphanumeric regex
- d - the default rule
+ reject/route default_node <filter_option>
+ or
+ accept/route default_node <filter_option>
- The fifth element is simply the hops to set in this filter. This
- would only be used if the filter was for a node of course and
- overrides the hop count in hop_table.pl.
-
-
- So, let's look at an example spot filter. It does not matter in the
- example who the filter is to be used for. So, what do we need in the
- filter? We need to filter the spots the user/node requires and also
- set a default rule for anything else outside the filter. Below is a
- simple filter that stops spots arriving from outside Europe.
-
-
-
- $in = [
- [ 0, 4, 'a', '^(K|N|A|W|VE|VA|J)'], # 0 = drop, 'a' = alphanumeric
- [ 1, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
- ];
-
-
-
-
-
- So the filter is wrapped in between a pair of square brackets. This
- tells Spider to look in between these limits. Then each line is
- contained within its own square brackets and ends with a comma. Lets
- look carefully at the first line. The first element is 0 (drop).
- Therefore anything we put on this line will not be accepted. The next
- element is 4. This means we are filtering by the spotter. The third
- element is the letter "a" which tells the program to expect an
- alphanumeric expression in the fourth element. The fourth element is
- a list of letters separated by the pipe symbol.
-
-
-
- What this line does is tell the program to drop any spots posted by
- anyone in the USA, Canada or Japan.
-
-
- The second line is the default rule for anything else. The "d" tells
- us this and the line simply reads... accept anything else.
-
-
- You can add as many lines as you need to complete the filter but if
- there are several lines of the same type it is neater to enclose them
- all as one line. An example of this is where specific bands are set.
- We could write this like this ....
-
- [ 0,0,'r',[1800.0, 2000.0], 1],
- [ 0,0,'r',[10100.0, 10150.0], 1],
- [ 0,0,'r',[14000.0, 14350.0], 1],
- [ 0,0,'r',[18000.0, 18200.0], 1],
+ where filter_option is one of the following ...
+ call <prefixes>
+ call_dxcc <numbers>
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes>
+ origin_dxcc <numbers>
+ origin_itu <numbers>
+ origin_zone <numbers>
- But the line below achieves the same thing and is more efficient ....
- [ 0, 0, 'r',
- [
- 1800.0, 2000.0, # top band
- 10100.0, 10150.0, # WARC
- 14000.0, 14350.0, # 20m
- 18000.0, 18200.0, # WARC
- [ ,1 ],
+ Please be careful if you alter this setting, it will affect ALL your
+ links!
+ 1.4. General route filtering
+ Exactly the same rules apply for general route filtering. You would
+ use either an accept filter or a reject filter like this ...
- 2.2. Announcements
+ reject/route <node_call> <filter_option>
+ or
+ accept/route <node_call> <filter_option>
- # This is an example announce or filter allowing only West EU announces
- #
- # The element list is:-
- # 0 - callsign of announcer
- # 1 - destination * = all, <callsign> = routed to the node
- # 2 - text
- # 3 - * - sysop, <some text> - special list eg 6MUK, ' ', normal announce
- # 4 - origin
- # 5 - 0 - announce, 1 - wx
- # 6 - channel callsign (the interface from which this spot came)
- $in = [
- [ 1, 0, 'a', '^(P[ABCDE]|DK0WCY|G|M|2|EI|F|ON)' ],
- [ 0, 0, 'd', 0 ]
- ];
+ where filter_option is one of the following ...
- In this example, only the prefixes listed will be allowed. It is
- possible to be quite specific. The Dutch prefix "P" is followed by
- several secondary identifiers which are allowed. So, in the example,
- "PA" or "PE" would be ok but not "PG". It is even possible to allow
- information from a single callsign. In the example this is DK0WCY, to
- allow the posting of his Aurora Beacon.
+ call <prefixes>
+ call_dxcc <numbers>
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes>
+ origin_dxcc <numbers>
+ origin_itu <numbers>
+ origin_zone <numbers>
- 2.3. WWV
- # This is an example WWV filter
- #
- # The element list is:-
- # 0 - nominal unix date of spot (ie the day + hour:13)
- # 1 - the hour
- # 2 - SFI
- # 3 - K
- # 4 - I
- # 5 - text
- # 6 - spotter
- # 7 - origin
- # 8 - incoming interface callsign
- # this one doesn't filter, it just sets the hop count to 6 and is
- # used mainly just to override any isolation from WWV coming from
- # the internet.
+ Here are some examples of route filters ...
- $in = [
- [ 1, 0, 'd', 0, 6 ]
- ];
+ rej/route gb7djk call_zone 61,38 (everything except UK+EIRE nodes)
+ rej/route all (equiv to [very] restricted mode)
+ acc/route gb7djk call_zone 61,38 (send only UK+EIRE nodes)
+ acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
- It should be noted that the filter will start to be used only once a
- user/node has logged out and back in again.
- I am not going to spend any more time on these filters now as they
- will become more "comprehensive" in the near future.
-
- 3. Filtering (New Style v1.45 and later)
-
- 3.1. General filter rules
+ 1.5. General filter rules
Upto v1.44 it was not possible for the user to set their own filters.
From v1.45 though that has all changed. It is now possible to set
In general terms you can create a 'reject' or an 'accept' filter which
can have up to 10 lines in it. You do this using, for example ...
+
+
+
accept/spots .....
reject/spots .....
- show/filter
+
+ show/filter
the same principles to all types of filter.
- 3.2. Types of filter
+ 1.6. Types of filter
There are two main types of filter, accept or reject. You can use
either to achieve the result you want dependent on your own preference
then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
+
If you set a reject filter like this ...
-
which achieves exactly the same thing. You should choose one or the
other until you are comfortable with the way it works. You can mix
them if you wish (actually you can have an accept AND a reject on the
originated there). If you did not have the brackets to separate the 2
sections, then Spider would read it logically from the front and see a
different expression entirely ...
+
+
+
(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
clear/spots 1
-
-
-
To remove all the filter lines in the spot filter ...
- 3.3. Filter options
+ 1.7. Filter options
You can filter in several different ways. The options are listed in
the various helpfiles for accept, reject and filter.
- 3.4. Default filters
+ 1.8. Default filters
Sometimes all that is needed is a general rule for node connects.
This can be done with a node_default filter. This rule will always be
to add a rule for the hops for spots also.
- 3.5. Advanced filtering
+ 1.9. Advanced filtering
Once you are happy with the results you get, you may like to
experiment.
VHF/UHF spots from EU.
+ 1.10. Basic hop control
+
+ In /spider/data you will find a file called hop_table.pl. This is the
+ file that controls your hop count settings. It has a set of default
+ hops on the various PC frames and also a set for each node you want to
+ alter the hops for. You may be happy with the default settings of
+ course, but this powerful tool can help to protect and improve the
+ network. The file will look something like this ...
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ #
+ # hop table construction
+ #
+
+ package DXProt;
+
+ # default hopcount to use
+ $def_hopcount = 5;
+
+ # some variable hop counts based on message type
+ %hopcount =
+ (
+ 11 => 10,
+ 16 => 10,
+ 17 => 10,
+ 19 => 10,
+ 21 => 10,
+ );
+
+
+ # the per node hop control thingy
+
+
+ %nodehops =
+
+ GB7ADX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+
+ GB7UDX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ GB7BAA => {
+ 11 => 5,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ };
+
+
+
+
+
+ Each set of hops is contained within a pair of curly braces and
+ contains a series of PC frame types. PC11 for example is a DX spot.
+ The figures here are not exhaustive but should give you a good idea of
+ how the file works.
+
+
+ You can alter this file at any time, including whilst the cluster is
+ running. If you alter the file during runtime, the command load/hops
+ will bring your changes into effect.
+
+
+
+ 1.11. Isolating networks
+
+ It is possible to isolate networks from each other on a "gateway" node
+ using the set/isolate <node_call> command.
+
+
+ The effect of this is to partition an isolated network completely from
+ another node connected to your node. Your node will appear on and
+ otherwise behave normally on every network to which you are connected,
+ but data from an isolated network will not cross onto any other
+ network or vice versa. However all the spot, announce and WWV traffic
+ and personal messages will still be handled locally (because you are a
+ real node on all connected networks), that is locally connected users
+ will appear on all networks and will be able to access and receive
+ information from all networks transparently. All routed messages will
+ be sent as normal, so if a user on one network knows that you are a
+ gateway for another network, he can still still send a talk/announce
+ etc message via your node and it will be routed across.
+
+
+ The only limitation currently is that non-private messages cannot be
+ passed down isolated links regardless of whether they are generated
+ locally. This will change when the bulletin routing facility is added.
+
+
+ If you use isolate on a node connection you will continue to receive
+ all information from the isolated partner, however you will not pass
+ any information back to the isolated node. There are times when you
+ would like to forward only spots across a link (maybe during a contest
+ for example). To do this, isolate the node in the normal way and put
+ in a filter in the /spider/filter/spots directory to override the
+ isolate. This filter can be very simple and consists of just one line
+ ....
+
+
+
+ $in = [
+ [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count
+ ];
+
+
+
- 4. Other filters
- 4.1. Filtering Mail
+ 2. Other filters
+
+ 2.1. Filtering Mail
In the /spider/msg directory you will find a file called
badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
-
-
# the list of regexes for messages that we won't store having
# received them (bear in mind that we must receive them fully before
# we can bin them)
etc in a particular country.
- 4.2. Filtering DX callouts (Depricated)
+ 2.2. Filtering DX callouts (Depricated)
From version 1.47, this method is replaced by the command set/baddx
- 4.3. Filtering words from text fields in Announce, Talk and DX spots
+ 2.3. Filtering words from text fields in Announce, Talk and DX spots
Create a file in /spider/data called badwords. The format is quite
simple. Lines beginning with # are ignored so comments can be added.
load/badwords.
- 5. Mail
+ 3. Mail
DXSpider deals seamlessly with standard AK1A type mail. It supports
both personal and bulletin mail and the sysop has additional commands
The cluster mail is automatically deleted after 30 days unless the
sysop sets the "keep" flag using the msg command.
- 5.1. Personal mail
+ 3.1. Personal mail
Personal mail is sent using the sp command. This is actually the
default method of sending mail and so a simple s for send will do. A
section, so I will not duplicate them here.
- 5.2. Bulletin mail
+ 3.2. Bulletin mail
Bulletin mail is sent by using the sb command. This is one of the
most common mistakes users make when sending mail. They send a
Bulletin addresses can be set using the Forward.pl file.
- 5.3. Forward.pl
+ 3.3. Forward.pl
DXSpider receives all and any mail sent to it without any alterations
needed in files. Because personal and bulletin mail are treated
- 5.4. The msg command
+ 3.4. The msg command
The msg command is a very powerful and flexible tool for the sysop.
It allows the sysop to alter to and from fields and make other changes
user.
- 5.5. Message status
+ 3.5. Message status
You can check on a message from within the cluster by using the
command stat/msg. This will give you additional information on the
- 5.6. Filtering mail
+ 3.6. Filtering mail
This is described in the section on Other filters so I will not
duplicate it here.
- 5.7. Distribution lists
+ 3.7. Distribution lists
Distribution lists are simply a list of users to send certain types of
mail to. An example of this is mail you only wish to send to other
list.
- 5.8. BBS interface
+ 3.8. BBS interface
Spider provides a simple BBS interface. No input is required from the
sysop of the cluster at all. The BBS simply sets the cluster as a BBS
using the Forward.pl file very carefully.
- 6. Databases
+ 4. Databases
Spider allows the creation of local or remote databases. It supports
chained databases, allowing several different databases to be scanned
database but will expand with time.
- 6.1. Creating databases
+ 4.1. Creating databases
Creating a database could not be more simple. All the commands are
sent from the cluster prompt as the sysop user.
chain can be a remote database.
- 6.2. Importing databases
+ 4.2. Importing databases
The only databases that Spider can currently import are the standard
AK1A databases such as OBLAST or the DB0SDX qsl and address database.
does not exist.
- 6.3. Checking available databases
+ 4.3. Checking available databases
Once a database is created, you will want to check that it has been
added. To do this use the dbavail command. This will output the
- 6.4. Looking up databases
+ 4.4. Looking up databases
To look for information in a defined database, simply use the dbshow
command, for example ...
Now you can simply use show/buckmaster or an abreviation.
- 6.5. Removing databases
+ 4.5. Removing databases
To delete an existing database you use the dbremove command. For
example ...
created from scratch if you still required it.
- 7. Information, files and useful programs
+ 5. Information, files and useful programs
- 7.1. MOTD
+ 5.1. MOTD
One of the more important things a cluster sysop needs to do is to get
information to his users. The simplest way to do this is to have a
to the cluster.
- 7.2. Downtime message
+ 5.2. Downtime message
If for any reason the cluster is down, maybe for upgrade or
maintenance but the machine is still running, a message can be sent to
actually running.
- 7.3. Other text messages
+ 5.3. Other text messages
You can set other text messages to be read by the user if they input
the file name. This could be for news items or maybe information for
The page length will of course depend on what you have it set to!
- 7.4. The Aliases file
+ 5.4. The Aliases file
You will find a file in /spider/cmd/ called Aliases. First, copy this
file to /spider/local_cmd/Aliases and edit this file. You will see
the results once you have set an alias.
- 7.5. Console.pl
+ 5.5. Console.pl
In later versions of Spider a simple console program is provided for
the sysop. This has a type ahead buffer with line editing facilities
edit the file with your favourite editor.
- 7.6. Updating kepler data
+ 5.6. Updating kepler data
Spider has a powerful and flexible show/satellite command. In order
for this to be accurate, the kepler data has to be updated regularly.
- 7.7. The QRZ callbook
+ 5.7. The QRZ callbook
The command sh/qrz will only work once you have followed a few simple
steps. First you need to get a user ID and password from qrz.com.
proprieter of qrz.com for allowing this access.
- 8. CVS
+ 6. CVS
CVS stands for "Concurrent Versions System" and the CVS for DXSpider
is held at Sourceforge. This means that it is possible to update your
You will find any changes documented in the /spider/Changes file.
- 9. The DXSpider command set
+ 7. The DXSpider command set
Below is a complete list of commands available from the cluster
prompt. Most maintenance tasks are automatic but there are some
is the permissions level needed to use the command.
- 9.1. accept/announce (0)
+ 7.1. accept/announce (0)
accept/announce [0-9] <pattern> Set an accept filter line for announce
but this probably for advanced users...
- 9.2. accept/announce (extended for sysops) (8)
+ 7.2. accept/announce (extended for sysops) (8)
accept/announce <call> [input] [0-9]<pattern> Announce filter sysop
version
- 9.3. accept/spots (0)
+ 7.3. accept/route (8)
+
+ accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
+ routing
+
+
+ Create an 'accept this routing PC Protocol' line for a filter.
+
+
+ An accept filter line means that if a PC16/17/19/21/24/41/50 matches
+ this filter it is passed thru that interface. See HELP FILTERING for
+ more info. Please read this to understand how filters work - it will
+ save a lot of grief later on.
+
+
+ You can use any of the following things in this line:-
+
+
+
+ call <prefixes> the callsign of the thingy
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes> really the interface it came in on
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+
+
+
+
+
+ some examples:-
+
+
+
+ acc/route gb7djk call_zone 61,38 (send only UK+EIRE nodes)
+ acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
+
+ You can use the tag 'all' to accept everything eg:
+
+
+
+ acc/route all
+
+
+
+
+
+ 7.4. accept/spots (0)
accept/announce [0-9] <pattern> Set an accept filter line for spots
thus: hf/ssb. You can also just have a simple range like: 0/30000 -
this is more efficient than saying simply: freq HF (but don't get too
hung up about that)
+
some examples:-
acc/spot 3 all
-
-
-
but this probably for advanced users...
- 9.4. accept/spots (extended for sysops) (8)
+ 7.5. accept/spots (extended for sysops) (8)
accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
- 9.5. accept/wcy (0)
+ 7.6. accept/wcy (0)
accept/wcy [0-9] <pattern> set an accept WCY filter
See HELP FILTER for information.
- 9.6. accept/wcy (extended for sysops) (8)
+ 7.7. accept/wcy (extended for sysops) (8)
accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
- accept/wcy node_default all
- set/hops node_default 10
+ accept/wcy node_default all
+ set/hops node_default 10
- 9.7. accept/wwv (0)
+ 7.8. accept/wwv (0)
accept/wwv [0-9] <pattern> Set an accept WWV filter
See HELP FILTER for information.
-
-
- 9.8. accept/wwv (extended for sysops) (8)
+ 7.9. accept/wwv (extended for sysops) (8)
accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
- 9.9. announce (0)
+
+ 7.10. announce (0)
announce <text> Send an announcement to local users
Send an announcement to LOCAL users only, where <text> is the text of
- the announcement you wish to broadcast
+ the announcement you wish to broadcast. If you do not wish to receive
+ announces, use the set/noannounce command. Any announces made by a
+ sysop will override set/noannounce.
- 9.10. announce full (0)
+ 7.11. announce full (0)
announce full <text> Send an announcement cluster wide
- 9.11. announce sysop (5)
+ 7.12. announce sysop (5)
announce sysop <text>
Send an announcement to Sysops only
- 9.12. apropos (0)
+ 7.13. apropos (0)
apropos <string> Search the help database
print the names of all the commands that may be relevant.
- 9.13. bye (0)
+ 7.14. bye (0)
bye Exit from the cluster
This will disconnect you from the cluster
-
-
- 9.14. catchup (5)
+ 7.15. catchup (5)
catchup <node_call> All|[<msgno> ...] Mark a message as sent
Order is not important.
- 9.15. clear/spots (0)
+ 7.16. clear/spots (0)
clear/spots [1|all] Clear a spot filter line
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
- 9.16. connect (5)
+
+
+ 7.17. connect (5)
connect <callsign> Start a connection to another DX Cluster
cluster <callsign>.
- 9.17. dbavail (0)
+ 7.18. dbavail (0)
dbavail Show a list of all the databases in the system
defined in the system. It is also aliased to SHOW/COMMAND.
- 9.18. dbcreate (9)
+ 7.19. dbcreate (9)
dbcreate <name> Create a database entry
dbcreate <name> chain <name> [<name>..] Create a chained database
No checking is done to see if the any of the chained databases exist,
in fact it is usually better to do the above statement first then do
each of the chained databases.
+
Databases can exist offsite. To define a database that lives on
another node do:
It would be normal for you to add an entry into your local Aliases
file to allow people to use the 'SHOW/<dbname>' style syntax. So you
would need to add a line like:-
-
-
-
's' => [
..
..
databases. See DBSHOW for generic database enquiry
- 9.19. dbimport (9)
+ 7.20. dbimport (9)
dbimport <dbname> Import AK1A data into a database
oblast database held locally.
- 9.20. dbremove (9)
+ 7.21. dbremove (9)
dbremove <dbname> Delete a database
You have been warned.
- 9.21. dbshow (0)
+ 7.22. dbshow (0)
dbshow <dbname> <key> Display an entry, if it exists, in a database
+
This is the generic user interface to the database to the database
system. It is expected that the sysop will add an entry to the local
Aliases file so that users can use the more familiar AK1A style of
- 9.22. debug (9)
+ 7.23. debug (9)
debug Set the cluster program into debug mode
finished.
- 9.23. directory (0)
+ 7.24. directory (0)
directory List messages
directory own List your own messages
You can combine some of the various directory commands together eg:-
-
DIR TO G1TLH 5
or
DIR SUBJECT IOTA 200-250
- 9.24. directory (extended for sysops) (5)
+ 7.25. directory (extended for sysops) (5)
Works just like the user command except that sysops can see ALL
messages.
- 9.25. disconnect (8)
+ 7.26. disconnect (8)
disconnect <call> [<call> ...] Disconnect a user or node
Disconnect any <call> connected locally
- 9.26. dx (0)
+ 7.27. dx (0)
dx [by <call>] <freq> <call> <remarks> Send a DX spot
-
-
- DX FR0G 144.600
- DX 144.600 FR0G
- DX 144600 FR0G
+ DX FR0G 144.600
+ DX 144.600 FR0G
+ DX 144600 FR0G
- DX by G1TLH FR0G 144.600 he isn't on the cluster
+
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
cluster. See SHOW/BANDS for more information.
- 9.27. export (9)
+ 7.28. export (9)
export <msgno> <filename> Export a message to a file
EXPORT 2345 /tmp/a
- 9.28. export_users (9)
+ 7.29. export_users (9)
export_users [<filename>] Export the users database to ascii
check is made on the filename (if any) that you specify.
-
-
- 9.29. forward/latlong (8)
+ 7.30. forward/latlong (8)
forward/latlong <node_call> Send latitude and longitude information to
another cluster
so it is not recommended on slow links.
- 9.30. forward/opername (1)
+ 7.31. forward/opername (1)
forward/opername <call> Send out information on this <call> to all
clusters
available.
- 9.31. help (0)
+ 7.32. help (0)
help <cmd> Get help on a command
commands to look at with HELP.
- 9.32. init (5)
+ 7.33. init (5)
init <node call> Re-initialise a link to an AK1A compatible node
Best of luck - you will need it.
- 9.33. kill (0)
+ 7.34. kill (0)
kill <msgno> [<msgno> ..] Delete a message from the local system
the sysop).
-
-
-
- 9.34. kill (5)
+ 7.35. kill (5)
kill <msgno> [<msgno> ...] Remove or erase a message from the system
kill from <call> Remove all messages from a callsign
As a sysop you can kill any message on the system.
- 9.35. kill full (5)
+ 7.36. kill full (5)
kill full <msgno> [<msgno>] Delete a message from the whole cluster
same subject will be deleted. Beware!
- 9.36. links (0)
+
+
+ 7.37. links (0)
links Show which nodes are physically connected
- 9.37. load/aliases (9)
+ 7.38. load/aliases (9)
load/aliases Reload the command alias table
- 9.38. load/baddx (9)
+ 7.39. load/baddx (9)
load/baddx Reload the bad DX table
if spotted, will not be passed on. FR0G and TEST are classic examples.
- 9.39. load/badmsg (9)
+ 7.40. load/badmsg (9)
load/badmsg Reload the bad message table
each message. If any of them match then that message is immediately
deleted on receipt.
- 9.40. load/badwords (9)
+
+ 7.41. load/badwords (9)
load/badwords Reload the badwords file
ignored.
- 9.41. load/bands (9)
+ 7.42. load/bands (9)
load/bands Reload the band limits table
whilst the cluster is running.
- 9.42. load/cmd_cache (9)
+ 7.43. load/cmd_cache (9)
load/cmd_cache Reload the automatic command cache
was just after a cluster restart.
- 9.43. load/forward (9)
+ 7.44. load/forward (9)
load/forward Reload the msg forwarding routing table
whilst the cluster is running.
- 9.44. load/messages (9)
+ 7.45. load/messages (9)
load/messages Reload the system messages file
unknown message 'xxxx' in lang 'en'
- 9.45. load/prefixes (9)
+ 7.46. load/prefixes (9)
load/prefixes Reload the prefix table
manually whilst the cluster is running.
- 9.46. merge (5)
+ 7.47. merge (5)
merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
data).
- 9.47. msg (9)
+ 7.48. msg (9)
msg <cmd> <msgno> [data ...] Alter various message parameters
Alter message parameters like To, From, Subject, whether private or
bulletin or return receipt (RR) is required or whether to keep this
message from timing out.
-
-
-
MSG TO <msgno> <call> - change TO callsign to <call>
MSG FRom <msgno> <call> - change FROM callsign to <call>
MSG PRrivate <msgno> - set private flag
This will display more information on the message than DIR does.
- 9.48. pc (8)
+ 7.49. pc (8)
pc <call> <text> Send text (eg PC Protocol) to <call>
You can also use in the same way as a talk command to a connected user
but without any processing, added of "from <blah> to <blah>" or
whatever.
+
pc G1TLH Try doing that properly!!!
- 9.49. ping (1)
+ 7.50. ping (1)
ping <node> Check the link quality between nodes
- 9.50. rcmd (1)
+ 7.51. rcmd (1)
rcmd <node call> <cmd> Send a command to another DX cluster
This command allows you to send nearly any command to another DX
Cluster node that is connected to the system.
+
Whether you get any output is dependant on a) whether the other system
knows that the node callsign of this cluster is in fact a node b)
whether the other system is allowing RCMDs from this node and c)
whether you have permission to send this command at all.
- 9.51. read (0)
+ 7.52. read (0)
read Read the next unread personal message addressed to you
read <msgno> Read the specified message
- 9.52. read (extended for sysops) (5)
+ 7.53. read (extended for sysops) (5)
read <msgno> Read a message on the system
As a sysop you may read any message on the system
- 9.53. reject/announce
+ 7.54. reject/announce
reject/announce [0-9] <pattern> Set a reject filter for announce
-
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
but this probably for advanced users...
- 9.54. reject/announce (extended for sysops) (8)
+ 7.55. reject/announce (extended for sysops) (8)
reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
version
- 9.55. reject/spots (0)
+ 7.56. reject/route (8)
+
+ reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
+ routing
+
+
+ Create an 'reject this routing PC Protocol' line for a filter.
+
+
+ An reject filter line means that if a PC16/17/19/21/24/41/50 matches
+ this filter it is NOT passed thru that interface. See HELP FILTERING
+ for more info. Please read this to understand how filters work - it
+ will save a lot of grief later on. You can use any of the following
+ things in this line:-
+
+
+
+ call <prefixes> the callsign of the thingy
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes> really the interface it came in on
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+
+
+
+
+
+ some examples:-
+
+
+
+
+ rej/route gb7djk call_zone 61,38 (everything except UK+EIRE nodes)
+
+
+
+
+
+ You can use the tag 'all' to reject everything eg:
+
+
+
+ rej/route all (equiv to [very] restricted mode)
+
+
+
+
+
+ 7.57. reject/spots (0)
reject/spots [0-9] <pattern> Set a reject filter line for spots
+
You can use the tag 'all' to reject everything eg:
but this probably for advanced users...
- 9.56. reject/spots (extended for sysops) (8)
+ 7.58. reject/spots (extended for sysops) (8)
reject/spots <call> [input] [0-9] <pattern> Reject spot filter sysop
version
+ reject/spot db0sue-7 1 by_zone 14,15,16
+ reject/spot node_default all
+ set/hops node_default 10
-
-
-
- reject/spot db0sue-7 1 by_zone 14,15,16
- reject/spot node_default all
- set/hops node_default 10
-
- reject/spot user_default by G,M,2
+ reject/spot user_default by G,M,2
- 9.57. reject/wcy (0)
+ 7.59. reject/wcy (0)
reject/wcy [0-9] <pattern> Set a reject WCY filter
See HELP FILTER for information.
- 9.58. reject/wcy (extended for sysops) (8)
+
+ 7.60. reject/wcy (extended for sysops) (8)
reject/wcy <call> [input] [0-9] <pattern> WCY reject filter sysop
version
reject/wcy gb7djk all
- 9.59. reject/wwv (0)
+ 7.61. reject/wwv (0)
reject/wwv [0-9] <pattern> Set a reject WWV filter
-
-
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
See HELP FILTER for information.
- 9.60. reject/wwv (extended for sysops) (8)
+ 7.62. reject/wwv (extended for sysops) (8)
reject/wwv <call> [input] [0-9] <pattern> WWV reject filter sysop
version
reject/wwv user_default by W
-
-
-
-
- 9.61. reply (0)
+ 7.63. reply (0)
reply Reply (privately) to the last message that you have read
reply <msgno> Reply (privately) to the specified message
further details)
-
- 9.62. send (0)
+ 7.64. send (0)
send <call> [<call> ...] Send a message to one or more callsigns
send RR <call> Send a message and ask for a read receipt
is an alias for SEND PRIVATE
- 9.63. set/address (0)
+ 7.65. set/address (0)
set/address <your_address> Record your postal address
Literally, record your address details on the cluster.
- 9.64. set/announce (0)
+ 7.66. set/announce (0)
set/announce Allow announce messages
Allow announce messages to arrive at your terminal.
-
- 9.65. set/arcluster (5)
+ 7.67. set/arcluster (5)
set/arcluster <node_call> [<node_call> ...] Make the node_call an AR-
Cluster type node
Set the node_call as an AR-Cluster type node
- 9.66. set/baddx (8)
+ 7.68. set/baddx (8)
set/baddx <call> Stop words we do not wish to see in the callsign
field of a dx spot being propagated
-
Setting a word as 'baddx' will prevent spots with that word in the
callsign field of a DX spot from going any further. They will not be
displayed and they will not be sent onto other nodes.
- 9.67. set/badnode (6)
+ 7.69. set/badnode (6)
set/badnode <node_call> Stop spots from this node_call being
propagated
FILTERing.
- 9.68. set/badspotter (8)
+ 7.70. set/badspotter (8)
set/badspotter <call> Stop spots from this callsign being propagated
FILTERing.
- 9.69. set/beep (0)
+ 7.71. set/beep (0)
set/beep Add beeps to terminal messages
Add a beep to DX and other terminal messages.
- 9.70. set/clx (5)
+ 7.72. set/bbs (5)
+
+ set/bbs <call> [<call>..]Make <call> a BBS
+
+
+ 7.73. set/clx (5)
set/clx <node_call> [<node_call> ...] Make the node_call a CLX type
node
Set the node_call as a CLX type node
- 9.71. set/debug (9)
+ 7.74. set/debug (9)
set/debug <name> Add a debug level to the debug set
-
You can choose to log several different levels. The levels are
chan state msg cron connect
You can remove a debug level with unset/debug <name>
- 9.72. set/dx (0)
+ 7.75. set/dx (0)
set/dxAllow DX messages to arrive at your terminal
You can stop DX messages with the unset/dx command
-
-
- 9.73. set/dxgrid (0)
+ 7.76. set/dxgrid (0)
set/dxgridAllow grid squares on the end of DX messages
to remove the grid squares.
- 9.74. set/dxnet (5)
+ 7.77. set/dxnet (5)
set/dxnet <node_call> [<node_call> ...] Make the node_call a DXNet
type node
Set the node_call as a DXNet type node
- 9.75. set/echo (0)
+ 7.78. set/echo (0)
set/echo Make the cluster echo your input
YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
- 9.76. set/here (0)
+ 7.79. set/here (0)
set/here Set the here flag
brackets around your callsign to indicate you are not available.
- 9.77. set/homenode (0)
+
+
+ 7.80. set/homenode (0)
set/homenode <node_call> Set your home cluster
-
-
- 9.78. set/hops (8)
+ 7.81. set/hops (8)
set/hops <node_call> ann|spots|wwv|wcy <n> Set hop count
creates a filter and works in conjunction with the filter system.
- 9.79. set/isolate (9)
+ 7.82. set/isolate (9)
set/isolate <node call> Isolate a node from the rest of the network
You can remove the isolation with the command unset/isolate.
- 9.80. set/language (0)
+ 7.83. set/language (0)
set/language <language> Set the language you wish to use
You can select the language that you want the cluster to use.
Currently the languages available are en (English) and nl (Dutch).
-
- 9.81. set/location (0)
+ 7.84. set/location (0)
set/location <lat and long> Set your latitude and longitude
- 9.82. set/sys_location (9)
+
+ 7.85. set/sys_location (9)
set/sys_location <lat & long> Set your cluster latitude and longitude
- 9.83. set/logininfo (0)
+ 7.86. set/logininfo (0)
set/logininfo Show logins and logouts of nodes and users
- 9.84. set/lockout (9)
+ 7.87. set/lockout (9)
set/lockout <call> Stop a callsign connecting to the cluster
allow the user to connect again, use the unset/lockout command.
- 9.85. set/name (0)
+ 7.88. set/name (0)
set/name <your_name> Set your name
set/name Dirk
-
-
-
- 9.86. set/node (9)
+ 7.89. set/node (9)
set/node <call> [<call> ...] Make the callsign an AK1A cluster
-
-
- set/spider
- set/dxnet
- set/clx
- set/arcluster
+ set/spider
+ set/dxnet
+ set/clx
+ set/arcluster
To see what your nodes are set to, use the show/nodes command.
- 9.87. set/obscount (9)
+ 7.90. set/obscount (9)
set/obscount <count> <node call> Set the 'pump-up' obsolescence
counter
minutes, it is disconnected.
- 9.88. set/page (0)
+ 7.91. set/page (0)
set/page <n> Set the number of lines per page
- 9.89. set/password (9)
+
+ 7.92. set/password (9)
set/password <callsign> <string> Set a users password
type password.
-
- 9.90. set/pinginterval (9)
+ 7.93. set/pinginterval (9)
set/pinginterval <time> <node call> Set the ping time to neighbouring
nodes
for more information.
- 9.91. set/privilege (9)
+ 7.94. set/privilege (9)
set/privilege <n> <call> [<call> ...] Set the privilege level on a
call
connection your privilege will automatically be set to 0.
- 9.92. set/spider (5)
+ 7.95. set/spider (5)
set/spider <node_call> [<node_call> ...] Make the node_call a DXSpider
type node
+
Set the node_call as a DXSpider type node
- 9.93. set/sys_qra (9)
+ 7.96. set/sys_qra (9)
set/sys_qra <locator> Set your cluster QRA locator
- 9.94. set/qra (0)
+ 7.97. set/qra (0)
set/qra <locator> Set your QRA locator
- 9.95. set/qth (0)
+ 7.98. set/qth (0)
set/qth <your QTH> Set your QTH
- 9.96. set/talk (0)
+ 7.99. set/talk (0)
set/talk Allow talk messages to be seen at your console
talks with the unset/talk command.
- 9.97. set/wcy (0)
+ 7.100. set/wcy (0)
set/wcy Allow WCY messages to be seen at your console
WCY messages with the unset/wcy command.
- 9.98. set/wwv (0)
+ 7.101. set/wwv (0)
set/wwv Allow WWV messages to be seen at your console
Allow WWV information to be seen at your console. You can switch off
WWV messages with the unset/wwv command.
-
- 9.99. set/wx (0)
+ 7.102. set/wx (0)
set/wx Allow WX messages to be seen at your console
WX messages with the unset/wx command.
-
-
-
- 9.100. show/baddx (1)
+ 7.103. show/baddx (1)
show/baddxShow all the bad dx calls in the system
information.
- 9.101. show/badnode (6)
+ 7.104. show/badnode (6)
show/badnode Show all the bad nodes in the system
more information.
- 9.102. show/badspotter (1)
+ 7.105. show/badspotter (1)
show/badspotter Show all the bad spotters in the system
SET/BADSPOTTER for more information.
- 9.103. show/configuration (0)
+ 7.106. show/configuration (0)
show/configuration [<node>] Show all visible nodes and their users
BE WARNED: the list that is returned can be VERY long
- 9.104. show/configuration/node (0)
+ 7.107. show/configuration/node (0)
show/configuration/node Show all the nodes connected
connected.
- 9.105. show/connect (1)
+ 7.108. show/connect (1)
show/connect Show all the active connections
This command shows information on all the active connections known to
the node. This command gives slightly more information than WHO.
-
-
- 9.106. show/date (0)
+ 7.109. show/date (0)
show/date [<prefix>|<callsign>] Show the local time
This is very nearly the same as SHOW/TIME, the only difference the
format of the date string if no arguments are given.
+
If no prefixes or callsigns are given then this command returns the
local time and UTC as the computer has it right now. If you give some
prefixes then it will show UTC and UTC + the local offset (not
including DST) at the prefixes or callsigns that you specify.
- 9.107. show/debug (9)
+ 7.110. show/debug (9)
show/debug Show what levels of debug you are logging
The levels can be set with set/debug
- 9.108. show/dx (0)
+ 7.111. show/dx (0)
show/dx [options] interrogate the spot database
qra [<locator>] - this will look for the specific locator if
you specify one or else anything that looks like a locator.
-
-
-
e.g.
- SH/DX 9m0
- SH/DX on 20m info iota
- SH/DX 9a on vhf day 30
- SH/DX rf1p qsl
- SH/DX iota
- SH/DX iota eu-064
- SH/DX qra jn86
+ SH/DX 9m0
+ SH/DX on 20m info iota
+ SH/DX 9a on vhf day 30
+ SH/DX rf1p qsl
+ SH/DX iota
+ SH/DX iota eu-064
+ SH/DX qra jn86
- 9.109. show/dxcc (0)
+ 7.112. show/dxcc (0)
show/dxcc <prefix> Interrogate the spot database by country
- 9.110. show/files (0)
+ 7.113. show/files (0)
show/files [<filearea> [<string>]] List the contents of a filearea
-
See also TYPE - to see the contents of a file.
-
- 9.111. show/filter (0)
+ 7.114. show/filter (0)
show/filter Show the filters you have set
displays all the filters set - for all the various categories.
- 9.112. show/filter (extended for sysops) (5)
+ 7.115. show/filter (extended for sysops) (5)
show/filter <callsign> Show the filters set by <callsign>
A sysop can look at any filters that have been set.
- 9.113. show/hops (8)
+ 7.116. show/hops (8)
show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a
node
the categories will be listed.
- 9.114. show/isolate (1)
+ 7.117. show/isolate (1)
show/isolate Show a list of isolated nodes
Show which nodes are currently set to be isolated.
- 9.115. show/lockout (9)
+ 7.118. show/lockout (9)
show/lockout Show a list of excluded callsigns
cluster locally with the set/lockout command
- 9.116. show/log (8)
+ 7.119. show/log (8)
show/log [<callsign>] Show excerpts from the system log
show output from the log associated with that callsign.
- 9.117. show/moon (0)
+ 7.120. show/moon (0)
show/moon [<prefix>|<callsign>] Show moon rise and set times
Show the Moon rise and set times for a (list of) prefixes or
callsigns, together with the azimuth and elevation of the sun
currently at those locations.
-
If you don't specify any prefixes or callsigns, it will show the times
for your QTH (assuming you have set it with either SET/LOCATION or
SET/QRA), together with the current azimuth and elevation.
- 9.118. show/muf (0)
+ 7.121. show/muf (0)
show/muf <prefix> [<hours>][long] Show the likely propagation to
<prefix>
- SH/MUF W
+ SH/MUF W
+
+
+
produces:
terrible accurate, but it is included for completeness.
- 9.119. show/node (1)
+ 7.122. show/node (1)
show/node [<node_call> ...] Show the type and version number of nodes
the non-user callsigns known to the system will be displayed.
- 9.120. show/prefix (0)
+ 7.123. show/prefix (0)
show/prefix <callsign> Interrogate the prefix database
See also SHOW/DXCC
- 9.121. show/program (5)
+
+
+ 7.124. show/program (5)
show/program Show the locations of all the included program modules
from.
- 9.122. show/qra (0)
+ 7.125. show/qra (0)
show/qra <locator> [<locator>] Show the distance between locators
show/qra <lat> <long> Convert latitude and longitude to a locator
- 9.123. show/qrz (0)
+ 7.126. show/qrz (0)
show/qrz <callsign> Show any callbook details on a callsign
provided for users of this software by http://www.qrz.com
- 9.124. show/route (0)
+
+
+
+ 7.127. show/route (0)
show/route <callsign> Show the route to <callsign>
- sh/route n2tly
+ sh/route n2tly
- 9.125. show/satellite (0)
+ 7.128. show/satellite (0)
show/satellite <name> [<hours> <interval>] Show satellite tracking
data
- 9.126. show/sun (0)
+ 7.129. show/sun (0)
show/sun [<prefix>|<callsign>] Show sun rise and set times
If all else fails it will show the sunrise and set times for the node
that you are connected to.
+
For example:-
- 9.127. show/time (0)
+ 7.130. show/time (0)
show/time [<prefix>|<callsign>] Show the local time
including DST) at the prefixes or callsigns that you specify.
- 9.128. show/wcy (0)
+ 7.131. show/wcy (0)
show/wcy Show the last 10 WCY broadcasts
show/wcy <n> Show the last <n> WCY broadcasts
system
- 9.129. show/wwv (0)
+ 7.132. show/wwv (0)
show/wwv Show the last 10 WWV broadcasts
show/wwv <n> Show the last <n> WWV broadcasts
- 9.130. shutdown (5)
+ 7.133. shutdown (5)
shutdown Shutdown the cluster
set to respawn in /etc/inittab it will of course restart.
- 9.131. spoof (9)
+ 7.134. spoof (9)
spoof <callsign> <command> Run commands as another user
like home_node for example.
- 9.132. stat/db (5)
+
+
+
+ 7.135. stat/db (5)
stat/db <dbname> Show the status of a database
other than a sysop.
-
-
- 9.133. stat/channel (5)
+ 7.136. stat/channel (5)
stat/channel <callsign> Show the status of a channel on the cluster
Only the fields that are defined (in perl term) will be displayed.
- 9.134. stat/msg (5)
+ 7.137. stat/msg (5)
stat/msg <msgno> Show the status of a message
etc etc.
- 9.135. stat/user (5)
+ If no message number is given then the status of the message system is
+ displayed.
+
+
+ 7.138. stat/route_node (5)
+
+ stat/route_node <callsign> Show the data in a Route::Node object
+
+
+ 7.139. stat/route_user (5)
+
+ stat/route_user <callsign> Show the data in a Route::User object
+
+
+ 7.140. stat/user (5)
stat/user <callsign> Show the full status of a user
Only the fields that are defined (in perl term) will be displayed.
- 9.136. sysop (0)
+ 7.141. sysop (0)
sysop Regain your privileges if you login remotely
or 2 0 5 7 3
or 20573
+
+
+
They will all match. If there is no password you will still be offered
numbers but nothing will happen when you input a string. Any match is
case sensitive.
- 9.137. talk (0)
+ 7.142. talk (0)
talk <callsign> Enter talk mode with <callsign>
talk <callsign> <text> Send a text message to <callsign>
If you want to do something (such as send a spot) you precede the
normal command with a '/' character, eg:-
-
-
-
/DX 14001 G1TLH What's a B class licensee doing on 20m CW?
/HELP talk
- 9.138. type (0)
+ 7.143. type (0)
type <filearea>/<name> Look at a file in one of the fileareas
enter:-
+
TYPE bulletins/arld051
content.
- 9.139. who (0)
+ 7.144. who (0)
who Show who is physically connected locally
what sort of connection they have
- 9.140. wx (0)
+ 7.145. wx (0)
wx <text> Send a weather message to local users
wx full <text> Send a weather message to all cluster users
extreme that may indicate enhanced conditions
- 9.141. wx (enhanced for sysops) (5)
+ 7.146. wx (enhanced for sysops) (5)
wx sysop <text> Send a weather message to other clusters only
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
projects / spider.git / commitdiff