From: minima Date: Mon, 29 Dec 2003 20:37:52 +0000 (+0000) Subject: updated dxoldtonew.pl to be more modern... X-Git-Tag: R1_51~11 X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=commitdiff_plain;h=ebba9c9a990734611de84b91a3483de1ff9ed514;p=spider.git updated dxoldtonew.pl to be more modern... --- diff --git a/Changes b/Changes index f907316f..06cf5d21 100644 --- a/Changes +++ b/Changes @@ -1,3 +1,10 @@ +29Dec03======================================================================= +1. updated dxoldtonew.pl so that it takes an AK1A DX.DAT file (argument on +command line or a default of /spider/data/DX.DAT and outputs the standard +DXSpider format spot files. Please be warned that if any of these files +already exist, the data will be appended onto the end of the file. Please +make sure you have backups or at least be aware that this may give strange +results which may be 'out of order'. 24May03======================================================================= 1. Added more french translations from Robert (HB9BZA) and we now have some french help as well (also from Robert). A splendid effort. Thank you. diff --git a/html/adminmanual_en-1.html b/html/adminmanual_en-1.html index 9b9fc4e4..06815637 100644 --- a/html/adminmanual_en-1.html +++ b/html/adminmanual_en-1.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Routing and Filtering diff --git a/html/adminmanual_en-10.html b/html/adminmanual_en-10.html index fe817abd..3b03dd0f 100644 --- a/html/adminmanual_en-10.html +++ b/html/adminmanual_en-10.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: CVS diff --git a/html/adminmanual_en-11.html b/html/adminmanual_en-11.html index 6e42dd74..c445b70c 100644 --- a/html/adminmanual_en-11.html +++ b/html/adminmanual_en-11.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: The DXSpider Command Reference diff --git a/html/adminmanual_en-2.html b/html/adminmanual_en-2.html index 837e236b..039f23b0 100644 --- a/html/adminmanual_en-2.html +++ b/html/adminmanual_en-2.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Other filters diff --git a/html/adminmanual_en-3.html b/html/adminmanual_en-3.html index f3443197..7f354a63 100644 --- a/html/adminmanual_en-3.html +++ b/html/adminmanual_en-3.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Mail diff --git a/html/adminmanual_en-4.html b/html/adminmanual_en-4.html index 52a31ea5..6863b980 100644 --- a/html/adminmanual_en-4.html +++ b/html/adminmanual_en-4.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Scripts diff --git a/html/adminmanual_en-5.html b/html/adminmanual_en-5.html index 9d86d91c..6a83c10f 100644 --- a/html/adminmanual_en-5.html +++ b/html/adminmanual_en-5.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Databases diff --git a/html/adminmanual_en-6.html b/html/adminmanual_en-6.html index e18855f8..8ed02026 100644 --- a/html/adminmanual_en-6.html +++ b/html/adminmanual_en-6.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Information, files and useful programs diff --git a/html/adminmanual_en-7.html b/html/adminmanual_en-7.html index f90b8ec2..212009db 100644 --- a/html/adminmanual_en-7.html +++ b/html/adminmanual_en-7.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Java Web applet diff --git a/html/adminmanual_en-8.html b/html/adminmanual_en-8.html index 39a1a80d..1d150c04 100644 --- a/html/adminmanual_en-8.html +++ b/html/adminmanual_en-8.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Web based statistics diff --git a/html/adminmanual_en-9.html b/html/adminmanual_en-9.html index bfa3bd7a..b5303af5 100644 --- a/html/adminmanual_en-9.html +++ b/html/adminmanual_en-9.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Security diff --git a/html/adminmanual_en.html b/html/adminmanual_en.html index 8d0b65cc..017411e6 100644 --- a/html/adminmanual_en.html +++ b/html/adminmanual_en.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50 diff --git a/html/filtering_en-1.html b/html/filtering_en-1.html index 83a0e170..469e00d3 100644 --- a/html/filtering_en-1.html +++ b/html/filtering_en-1.html @@ -1,7 +1,7 @@ - + The DXSpider User Filtering Primer v1.0: Introduction. diff --git a/html/filtering_en-10.html b/html/filtering_en-10.html index f3ee4abe..ebc97ffc 100644 --- a/html/filtering_en-10.html +++ b/html/filtering_en-10.html @@ -1,7 +1,7 @@ - + The DXSpider User Filtering Primer v1.0: Contacts diff --git a/html/filtering_en-2.html b/html/filtering_en-2.html index 84005ffa..dcbe8255 100644 --- a/html/filtering_en-2.html +++ b/html/filtering_en-2.html @@ -1,7 +1,7 @@ - + The DXSpider User Filtering Primer v1.0: Foreword diff --git a/html/filtering_en-3.html b/html/filtering_en-3.html index b14c853a..4131ebd1 100644 --- a/html/filtering_en-3.html +++ b/html/filtering_en-3.html @@ -1,7 +1,7 @@ - + The DXSpider User Filtering Primer v1.0: Configuring Spot Filters diff --git a/html/filtering_en-4.html b/html/filtering_en-4.html index e90394c5..d6a70339 100644 --- a/html/filtering_en-4.html +++ b/html/filtering_en-4.html @@ -1,7 +1,7 @@ - + The DXSpider User Filtering Primer v1.0: Types of spot filters used in DXSpider diff --git a/html/filtering_en-5.html b/html/filtering_en-5.html index 53c8e61a..759a63b8 100644 --- a/html/filtering_en-5.html +++ b/html/filtering_en-5.html @@ -1,7 +1,7 @@ - + The DXSpider User Filtering Primer v1.0: Reject filters diff --git a/html/filtering_en-6.html b/html/filtering_en-6.html index faaa9fb4..3ce8ce9d 100644 --- a/html/filtering_en-6.html +++ b/html/filtering_en-6.html @@ -1,7 +1,7 @@ - + The DXSpider User Filtering Primer v1.0: Filters to reject spots based on frequency diff --git a/html/filtering_en-7.html b/html/filtering_en-7.html index f200b211..12fd03a1 100644 --- a/html/filtering_en-7.html +++ b/html/filtering_en-7.html @@ -1,7 +1,7 @@ - + The DXSpider User Filtering Primer v1.0: Accept filters diff --git a/html/filtering_en-8.html b/html/filtering_en-8.html index 200fc63e..1979c443 100644 --- a/html/filtering_en-8.html +++ b/html/filtering_en-8.html @@ -1,7 +1,7 @@ - + The DXSpider User Filtering Primer v1.0: Clear filters diff --git a/html/filtering_en-9.html b/html/filtering_en-9.html index 71ab6ff8..cfcf57b6 100644 --- a/html/filtering_en-9.html +++ b/html/filtering_en-9.html @@ -1,7 +1,7 @@ - + The DXSpider User Filtering Primer v1.0: Some Practice Examples diff --git a/html/filtering_en.html b/html/filtering_en.html index 6022d3ec..f7dd8515 100644 --- a/html/filtering_en.html +++ b/html/filtering_en.html @@ -1,7 +1,7 @@ - + The DXSpider User Filtering Primer v1.0 diff --git a/html/installation_en-1.html b/html/installation_en-1.html index 89470902..72c3a30f 100644 --- a/html/installation_en-1.html +++ b/html/installation_en-1.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: Linux Installation diff --git a/html/installation_en-2.html b/html/installation_en-2.html index 62444f79..98a92b4c 100644 --- a/html/installation_en-2.html +++ b/html/installation_en-2.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: Linux quick installation guide diff --git a/html/installation_en-3.html b/html/installation_en-3.html index 60e6f9d1..42f17673 100644 --- a/html/installation_en-3.html +++ b/html/installation_en-3.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: Setting up the AX25 Utilities diff --git a/html/installation_en-4.html b/html/installation_en-4.html index 19920e78..96ebacec 100644 --- a/html/installation_en-4.html +++ b/html/installation_en-4.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: Configuration diff --git a/html/installation_en-5.html b/html/installation_en-5.html index 0c02ed74..dae7e584 100644 --- a/html/installation_en-5.html +++ b/html/installation_en-5.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: Microsoft Windows Installation diff --git a/html/installation_en-6.html b/html/installation_en-6.html index 41a846fe..7c7cf6e7 100644 --- a/html/installation_en-6.html +++ b/html/installation_en-6.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: Installing the software diff --git a/html/installation_en-7.html b/html/installation_en-7.html index 7e4bda1a..837a532b 100644 --- a/html/installation_en-7.html +++ b/html/installation_en-7.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: General Information diff --git a/html/installation_en.html b/html/installation_en.html index 3f1ead27..31d730c7 100644 --- a/html/installation_en.html +++ b/html/installation_en.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50 diff --git a/html/spiderCVS_en.html b/html/spiderCVS_en.html index 83f9a587..d45f6da1 100644 --- a/html/spiderCVS_en.html +++ b/html/spiderCVS_en.html @@ -1,7 +1,7 @@ - + The DXSpider CVS Changes Addendum v1.50 diff --git a/html/spiderFAQ_en-1.html b/html/spiderFAQ_en-1.html index b7ae5cc4..da75dbbf 100644 --- a/html/spiderFAQ_en-1.html +++ b/html/spiderFAQ_en-1.html @@ -1,7 +1,7 @@ - + The DXSpider FAQ: Installation diff --git a/html/spiderFAQ_en-2.html b/html/spiderFAQ_en-2.html index d3865721..07ba7d06 100644 --- a/html/spiderFAQ_en-2.html +++ b/html/spiderFAQ_en-2.html @@ -1,7 +1,7 @@ - + The DXSpider FAQ: Administration diff --git a/html/spiderFAQ_en.html b/html/spiderFAQ_en.html index ee0c9f3b..9b26ad23 100644 --- a/html/spiderFAQ_en.html +++ b/html/spiderFAQ_en.html @@ -1,7 +1,7 @@ - + The DXSpider FAQ diff --git a/html/usermanual_en-1.html b/html/usermanual_en-1.html index fbb001d6..9e515218 100644 --- a/html/usermanual_en-1.html +++ b/html/usermanual_en-1.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Introduction diff --git a/html/usermanual_en-10.html b/html/usermanual_en-10.html index db5e642f..429de050 100644 --- a/html/usermanual_en-10.html +++ b/html/usermanual_en-10.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Filtering (From version 1.45) diff --git a/html/usermanual_en-11.html b/html/usermanual_en-11.html index 310711a2..c8a780b7 100644 --- a/html/usermanual_en-11.html +++ b/html/usermanual_en-11.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Hints, tips and common questions. diff --git a/html/usermanual_en-12.html b/html/usermanual_en-12.html index 838cbea1..f9cb0fe6 100644 --- a/html/usermanual_en-12.html +++ b/html/usermanual_en-12.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: The DXSpider Command Reference diff --git a/html/usermanual_en-2.html b/html/usermanual_en-2.html index e3d91de7..22eb6bc9 100644 --- a/html/usermanual_en-2.html +++ b/html/usermanual_en-2.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Logins and logouts. diff --git a/html/usermanual_en-3.html b/html/usermanual_en-3.html index 5e8351e0..1d0aa45a 100644 --- a/html/usermanual_en-3.html +++ b/html/usermanual_en-3.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Setting your personal details. diff --git a/html/usermanual_en-4.html b/html/usermanual_en-4.html index c82e949f..876358b9 100644 --- a/html/usermanual_en-4.html +++ b/html/usermanual_en-4.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Getting and posting DX. diff --git a/html/usermanual_en-5.html b/html/usermanual_en-5.html index 9941cc8c..0e4e2a5d 100644 --- a/html/usermanual_en-5.html +++ b/html/usermanual_en-5.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Headings and propagation diff --git a/html/usermanual_en-6.html b/html/usermanual_en-6.html index c935cac6..95d85bc2 100644 --- a/html/usermanual_en-6.html +++ b/html/usermanual_en-6.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Announcements. diff --git a/html/usermanual_en-7.html b/html/usermanual_en-7.html index ecc74e7c..8f958e41 100644 --- a/html/usermanual_en-7.html +++ b/html/usermanual_en-7.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Nodes and users. diff --git a/html/usermanual_en-8.html b/html/usermanual_en-8.html index a2a6913e..ae5a7e03 100644 --- a/html/usermanual_en-8.html +++ b/html/usermanual_en-8.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Talk mode. diff --git a/html/usermanual_en-9.html b/html/usermanual_en-9.html index 534c7b96..5ed05336 100644 --- a/html/usermanual_en-9.html +++ b/html/usermanual_en-9.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Mail. diff --git a/html/usermanual_en.html b/html/usermanual_en.html index c4a8544c..68453652 100644 --- a/html/usermanual_en.html +++ b/html/usermanual_en.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50 diff --git a/perl/dxoldtonew.pl b/perl/dxoldtonew.pl index 9ad35605..e4261b58 100755 --- a/perl/dxoldtonew.pl +++ b/perl/dxoldtonew.pl @@ -1,34 +1,56 @@ #!/usr/bin/perl # -# convert an Ak1a DX.DAT file to comma delimited form +# convert an AK1A DX.DAT file to comma delimited form # +# PLEASE BE WARNED: # +# This routine is really designed for archive data. It will create and add to +# standard DXSpider spot files. If those spot files already exist (because you +# were running DXSpider at the same time as collecting this 'old' data) then +# this will simply append the data onto the end of the appropriate spot file +# for that day. This may then give strange 'out of order' results when viewed +# with the show/dx command +# +# $Id$ +# +# Copyright (c) 1998-2003 Dirk Koopman G1TLH +# + +# search local then perl directories +BEGIN { + # root of directory tree for this system + $root = "/spider"; + $root = $ENV{'DXSPIDER_ROOT'} if $ENV{'DXSPIDER_ROOT'}; + + unshift @INC, "$root/perl"; # this IS the right way round! + unshift @INC, "$root/local"; +} -use Date::Parse; +use DXUtil; use Spot; use Prefix; -sysopen(IN, "../data/DX.DAT", 0) or die "can't open DX.DAT ($!)"; -open(OUT, ">../data/dxcomma") or die "can't open dxcomma ($!)"; +$ifn = "$root/data/DX.DAT"; +$ifn = shift if @ARGV; +print "Using: $ifn as input... \n"; -Prefix::load(); +sysopen(IN, $ifn, 0) or die "can't open $ifn ($!)"; -$fn = Spot::prefix(); -system("rm -rf $fn/*"); +Prefix::init(); +Spot::init(); while (sysread(IN, $buf, 86)) { ($freq,$call,$date,$time,$comment,$spotter) = unpack 'A10A13A12A6A31A14', $buf; - $d = $date =~ s/^\s*(\d+)-(\w\w\w)-(19\d\d)$/$1 $2 $3/o; - $t = $time =~ s/^(\d\d)(\d\d)Z$/$1:$2 +0000/o; - $dt = undef; - $dt = str2time("$date $time") if $d && $t; +# printf "%-13s %10.1f %s %s by %s %s\n", $call, $freq, $date, $time, $spotter, $comment; + + $dt = cltounix($date, $time); $comment =~ s/^\s+//o; if ($dt ) { - Spot::add($freq, $call, $dt, $comment, $spotter); + my @spot = Spot::prepare($freq, $call, $dt, $comment, $spotter); + Spot::add(@spot); } else { - print "$call $freq $date $time\n"; + print "ERROR: $call $freq $date $time by $spotter $comment\n"; } } close(IN); -close(OUT); diff --git a/txt/adminmanual_en.txt b/txt/adminmanual_en.txt index 030f9cf5..79ee9c35 100644 --- a/txt/adminmanual_en.txt +++ b/txt/adminmanual_en.txt @@ -334,9 +334,9 @@ ______________________________________________________________________ - 1. Routing and Filtering + 1. Routing and Filtering - 1.1. Introduction + 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 @@ -353,15 +353,15 @@ In fact DXSpider has had a simple system for some time which is called - isolation. This is similar to what in other systems such as clx, is - called passive mode. A more detailed explanation of isolation is given + isolation. This is similar to what in other systems such as clx, is + called passive mode. A more detailed explanation of isolation is given further below. This system is still available and, for simple networks, is probably all that you need. The new functionality introduced in version 1.48 allows filtering the node and user protocol frames on a "per interface" basis. We call this - route filtering. This is used instead of isolation. + route filtering. This is used instead of isolation. What this really means is that you can control more or less completely @@ -369,10 +369,10 @@ partner nodes. You can also limit what comes into your node from your partners. It is even possible to control the settings that your partner node has for the routing information that it sends to you - (using the rcmd command). + (using the rcmd command). - 1.2. Route Filters + 1.2. Route Filters Initially when route filters were being tested we generated a "default" filter. Unfortunately it quickly became apparent that this @@ -382,11 +382,11 @@ The first thing that you must do is determine whether you need to use - route filtering at all. If you are a "normal" node with two or three + route filtering at all. If you are a "normal" node with two or three partners and you arranged in an "official" non-looping tree type - network, then you do not need to do route filtering and you will feel + network, then you do not need to do route filtering and you will feel a lot better for not getting involved. If you are successfully using - isolation then you also probably don't need to use route filtering. + isolation then you also probably don't need to use route filtering. To put it simply, you should not mix Isolation and Route Filtering. @@ -419,7 +419,7 @@ explanation. - 1.3. The node_default filter + 1.3. The node_default filter All normal systems should have a default routing filter and it should usually be set to send only the normal, unlooped, view of your @@ -456,9 +456,9 @@ - Please be careful if you alter this setting, it will affect ALL your - links! Remember, this is a default filter for node connections, not a - per link default. + Please be careful if you alter this setting, it will affect ALL your + links! Remember, this is a default filter for node connections, not a + per link default. For the default routing filter then you have two real choices: either @@ -471,15 +471,15 @@ acc/route node_default call gb7djk GB7DJK uses the first of these. The DXCC countries can be obtained - from the show/prefix command. + from the show/prefix command. - The example filters shown control output TO all your partner nodes + The example filters shown control output TO all your partner nodes unless they have a specific filter applied to them (see next section). - It is also possible to control the incoming routing information that - you are prepared to accept FROM your partner nodes. The reason this is + It is also possible to control the incoming routing information that + you are prepared to accept FROM your partner nodes. The reason this is necessary is to make sure that stuff like mail, pings and similar commands a) go down the correct links and b) don't loop around excessively. Again using GB7DJK as an example a typical default input @@ -516,7 +516,7 @@ - 1.4. General route filtering + 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 ... @@ -553,7 +553,7 @@ or restricting it quite a lot, in fact making it very nearly like an - isolated node, like this:- + isolated node, like this:- @@ -567,13 +567,13 @@ PC16s for my local users). - It is possible to write much more complex rules, there are up to 10 + It is possible to write much more complex rules, there are up to 10 accept/reject pairs per callsign per filter. For more information see the next section. - 1.5. 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 @@ -584,7 +584,7 @@ There are 3 basic commands involved in setting and manipulating - filters. These are accept, reject and clear. First we will look + filters. These are accept, reject and clear. 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. @@ -629,9 +629,9 @@ the same principles to all types of filter. - 1.6. Types of filter + 1.6. Types of filter - There are two main types of filter, accept or reject. You can use + 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 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 @@ -644,7 +644,7 @@ 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 - accept filter ... + accept filter ... @@ -652,7 +652,7 @@ - then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16. + then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16. If you set a reject filter like this ... @@ -662,7 +662,7 @@ - Then you will get everything EXCEPT HF CW spots. You could make this + Then you will get everything EXCEPT 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 ... @@ -712,7 +712,7 @@ 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 APART from those in zones 14, 15 and 16 (either spotted there or + above APART 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 ... @@ -751,13 +751,13 @@ - 1.7. 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. - 1.8. 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 @@ -782,7 +782,7 @@ to add a rule for the hops for spots also. - 1.9. Advanced filtering + 1.9. Advanced filtering Once you are happy with the results you get, you may like to experiment. @@ -801,9 +801,9 @@ 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 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. Each filter slot actually has a + said 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. Each filter slot actually has a 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE the accept slot. @@ -816,7 +816,7 @@ VHF/UHF spots from EU. - 1.10. Basic hop control + 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 @@ -906,11 +906,11 @@ 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 + running. If you alter the file during runtime, the command load/hops will bring your changes into effect. - 1.11. Hop Control on Specific Nodes + 1.11. Hop Control on Specific Nodes You can set a callsign specific hop count for any of the standard filter options so:- @@ -926,16 +926,16 @@ all work on their specific area of the protocol. - The set/hops command overrides any hops that you have set otherwise. + The set/hops command overrides any hops that you have set otherwise. - You can show what hops have been set using the show/hops command. + You can show what hops have been set using the show/hops command. - 1.12. Isolating networks + 1.12. Isolating networks It is possible to isolate networks from each other on a "gateway" node - using the set/isolate command. + using the set/isolate  command. The effect of this is to partition an isolated network completely from @@ -957,10 +957,10 @@ 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 use - an acc/spot >call< all filter to override the isolate. + an acc/spot >call< all filter to override the isolate. - 1.13. A DXSpider Filtering Tutorial + 1.13. A DXSpider Filtering Tutorial There is now an excellent primer/tutorial on filtering written by Jim Samuels, W3BG with an introduction by Dave Hawes N3RD that I strongly @@ -968,9 +968,9 @@ Primer - 2. Other filters + 2. Other filters - 2.1. Filtering Mail + 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 @@ -1017,20 +1017,20 @@ - 2.2. Filtering words from text fields in Announce, Talk and DX spots + 2.2. Filtering words from text fields in Announce, Talk and DX spots From version 1.48 onwards the interface to this has changed. You can - now use the commands set/badword to add words that you are not - prepared to see on the cluster, unset/badword to allow that word again - and show/badword to list the words that you have set. + now use the commands set/badword to add words that you are not + prepared to see on the cluster, unset/badword to allow that word again + and show/badword to list the words that you have set. - If you have a previous /spider/data/badwords, the first time you start + If you have a previous /spider/data/badwords, the first time you start the node, it will read and convert this file to the new commands. The old style file will then be removed. - 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters + 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters There are a number of commands that control whether a spot progresses @@ -1053,7 +1053,7 @@ - These work in the same as the set/badword command, you can add any + These work in the same as the set/badword command, you can add any words or callsigns or whatever to the appropriate database. For example, to stop a spot from a particular node you do: @@ -1080,11 +1080,11 @@ You can remove a word using the appropriate unset command - (unset/baddx, unset/badspotter, unset/badnode) or list them using one - of show/baddx, show/badspotter and show/badnode. + (unset/baddx, unset/badspotter, unset/badnode) or list them using one + of show/baddx, show/badspotter and show/badnode. - 3. Mail + 3. Mail DXSpider deals seamlessly with standard AK1A type mail. It supports both personal and bulletin mail and the sysop has additional commands @@ -1095,30 +1095,30 @@ will be queued until it has finished. The cluster mail is automatically deleted after 30 days unless the - sysop sets the "keep" flag using the msg command. + sysop sets the "keep" flag using the msg command. - 3.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 - full list of the send commands and options is in the command set + 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 + full list of the send commands and options is in the command set section, so I will not duplicate them here. - 3.2. Bulletin mail + 3.2. Bulletin mail - Bulletin mail is sent by using the sb command. This is one of the + 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 mail with s or sp instead of sb and of course the message + bulletin mail with s or sp instead of sb and of course the message never leaves the cluster. This can be rectified by the sysop by using - the msg command. + the msg command. Bulletin addresses can be set using the Forward.pl file. - 3.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 @@ -1183,9 +1183,9 @@ exist in this file, they will get an error. - 3.4. The msg command + 3.4. The msg command - The msg command is a very powerful and flexible tool for the sysop. + 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 to manage the cluster mail. @@ -1214,10 +1214,10 @@ user. - 3.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 + command stat/msg. 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 ... @@ -1241,17 +1241,17 @@ - 3.6. Filtering mail + 3.6. Filtering mail - This is described in the section on Other filters so I will not + This is described in the section on Other filters so I will not duplicate it here. - 3.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 - sysops. In /spider/msg there is a directory called distro. You put + sysops. In /spider/msg there is a directory called distro. You put any distibution lists in here. For example, here is a file called SYSOP.pl that caters for the UK sysops. @@ -1266,7 +1266,7 @@ list. - 3.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 @@ -1279,7 +1279,7 @@ using the Forward.pl file very carefully. - 4. Scripts + 4. Scripts From 1.48 onwards it will become increasingly possible to control DXSpider's operation with scripts of various kinds. @@ -1315,7 +1315,7 @@ As usual, any text behind a # is treated as a comment and not read. To use this file, simply rename it from startup.issue to startup. In our example above there are three options. The first option is the - amount of spots that a user can request with the sh/dx command. + amount of spots that a user can request with the sh/dx command. Normally the default is to give 10 spots unless the user specifies more. Without this line enabled, the maximum a user can request is 100 spots. Depending on your link quality you may wish to enable more @@ -1358,11 +1358,11 @@ Thirdly, there are 2 default scripts for users and nodes who do not - have a specifically defined script. These are user_default and - node_default + have a specifically defined script. These are user_default and + node_default - 5. Databases + 5. Databases Spider allows the creation of local or remote databases. It supports chained databases, allowing several different databases to be scanned @@ -1371,12 +1371,12 @@ database but will expand with time. - 5.1. Creating databases + 5.1. Creating databases Creating a database could not be more simple. All the commands are - sent from the cluster prompt as the sysop user. + sent from the cluster prompt as the sysop user. - To create a database you use the command dbcreate. It can be used in + To create a database you use the command dbcreate. It can be used in 3 different ways like so .. @@ -1417,7 +1417,7 @@ chain can be a remote database. - 5.2. Importing databases + 5.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. @@ -1436,10 +1436,10 @@ does not exist. - 5.3. Checking available databases + 5.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 + added. To do this use the dbavail command. This will output the available databases. For example ... @@ -1453,9 +1453,9 @@ - 5.4. Looking up databases + 5.4. Looking up databases - To look for information in a defined database, simply use the dbshow + To look for information in a defined database, simply use the dbshow command, for example ... @@ -1467,16 +1467,16 @@ 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 - show command like this ... + show command like this ... Now you can simply use show/buckmaster or an abreviation. - 5.5. Removing databases + 5.5. Removing databases - To delete an existing database you use the dbremove command. For + To delete an existing database you use the dbremove command. For example ... @@ -1491,9 +1491,9 @@ created from scratch if you still required it. - 6. Information, files and useful programs + 6. Information, files and useful programs - 6.1. MOTD + 6.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 @@ -1502,14 +1502,14 @@ /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. - 6.2. MOTD_NOR + 6.2. MOTD_NOR This message of the day file lives in the same directory as the standard motd file but is only sent to non-registered users. Once registered they will receive the same message as any other user. - 6.3. Downtime message + 6.3. 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 @@ -1520,13 +1520,13 @@ actually running. - 6.4. Other text messages + 6.4. 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 new users. To set this up, make a directory under /spider called - packclus. Under this directory you can create files called news or - newuser for example. In fact you can create files with any names you + packclus. Under this directory you can create files called news or + newuser for example. In fact you can create files with any names you like. These can be listed by the user with the command .... @@ -1543,17 +1543,17 @@ - If the file they want to read is called news. You could also set an - alias for this in the Alias file to allow them just to type news + If the file they want to read is called news. You could also set an + alias for this in the Alias file to allow them just to type news 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 bulletin. Now copy any OPDX or similar + /spider/packclus called bulletin. Now copy any OPDX or similar bulletins into it. These can be listed by the user in the same way as - above using the show/files command with an extension for the bulletin + above using the show/files command with an extension for the bulletin directory you have just created, like this .... @@ -1570,11 +1570,11 @@ You can see that in the files area (basically the packclus directory) - there is a file called news and a directory called bulletin. You can - also see that dates they were created. In the case of the file news, + there is a file called news and a directory called bulletin. You can + also see that dates they were created. In the case of the file news, 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 news you would simply issue the command .... + file called news you would simply issue the command .... @@ -1628,7 +1628,7 @@ The page length will of course depend on what you have it set to! - 6.5. The Aliases file + 6.5. The Aliases file You will find a file in /spider/cmd/ called Aliases. This is the file that controls what a user gets when issuing a command. It is also @@ -1690,22 +1690,22 @@ alias for 'news'. This is a file I have created in the /spider/packclus/ directory where I can inform users of new developments or points of interest. In it's initial form a user would - have to use the command type news. The alias allows them to simply - type news to get the info. Second is an alias for the show/qrz - command so that those users used to the original show/buck command in + have to use the command type news. The alias allows them to simply + type news to get the info. Second is an alias for the show/qrz + command so that those users used to the original show/buck command in AK1A will not get an error, and the rest of the lines are for locally - created databases so that a user can type show/hftest instead of - having to use the command dbshow hftest which is not as intuitive. + created databases so that a user can type show/hftest instead of + having to use the command dbshow hftest which is not as intuitive. This file is just an example and you should edit it to your own - requirements. Once created, simply issue the command load/alias at + requirements. Once created, simply issue the command load/alias at the cluster prompt as the sysop user and the aliases should be available. - 6.6. Console.pl + 6.6. 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 @@ -1717,13 +1717,13 @@ edit the file with your favourite editor. - 6.7. Updating kepler data + 6.7. 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. 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 export command from the cluster prompt as + file. You do this with the export command from the cluster prompt as the sysop. For example ... @@ -1737,7 +1737,7 @@ Now login to a VT as sysop and cd /spider/perl. There is a command in - the perl directory called convkeps.pl. All we need to do now is + the perl directory called convkeps.pl. All we need to do now is convert the file like so ... @@ -1757,9 +1757,9 @@ That is it! the kepler data has been updated. - 6.8. The QRZ callbook + 6.8. The QRZ callbook - The command sh/qrz will only work once you have followed a few simple + 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. 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 @@ -1768,14 +1768,14 @@ proprieter of qrz.com for allowing this access. - 6.9. Connecting logging programs + 6.9. Connecting logging programs There appear to be very few logging programs out there that support telnet especially the popular ones like LogEQF, Turbolog etc. This can make it difficult to connect to your own cluster! The way to do it is to make the logging program think it has a TNC attached to a com port on the logging PC and 'push' a linux login out to it. This is - achieved very simply by the use of agetty. + achieved very simply by the use of agetty. All that is required is to add a line in /etc/inittab to have the @@ -1790,16 +1790,16 @@ Add this after the standard runlevel lines in /etc/inittab. The above - line works on ttyS1 (com2). Now as root, issue the command telinit q + line works on ttyS1 (com2). Now as root, issue the command telinit q and it should be ready for connection. All that is required is a 3 wire serial lead (tx, rx and signal ground). Tell you logging program to use 8n1 at 9600 baud and you should see a Linux login prompt. Login as normal and then telnet from there to the cluster. - 7. Java Web applet + 7. Java Web applet - In the spider tree will be a directory spider-web. This is a neat + In the spider tree will be a directory spider-web. This is a neat little java web applet that can be run from a website. The applet must run on the same machine as the cluster. The included README file is shown below. @@ -1871,7 +1871,7 @@ - 8. Web based statistics + 8. Web based statistics From version 1.50, you can use the freeware software MRTG to produce really nice graphical statistics on your web site. For an example try @@ -1918,7 +1918,7 @@ Now you are nearly there! Login as the sysop user and change to the - /spider/html/mrtg/ directory. Now run the command indexmaker as shown + /spider/html/mrtg/ directory. Now run the command indexmaker as shown below... @@ -1970,7 +1970,7 @@ This will update the site every 5 minutes. - 9. Security + 9. Security From version 1.49 DXSpider has some additional security features. These are not by any means meant to be exhaustive, however they do @@ -1979,13 +1979,13 @@ security. - 9.1. Registration + 9.1. Registration The basic principle of registration is simple. If a user is not registered by the sysop, then they have read-only access to the cluster. The only thing they can actually send is a talk or a message to the sysop. In order for them to be able to spot, send announces or - talks etc the sysop must register them with the set/register command, + talks etc the sysop must register them with the set/register command, like this ... @@ -2013,16 +2013,16 @@ section on Information, files and useful programs. - To unregister a user use unset/register and to show the list of - registered users, use the command show/register. + To unregister a user use unset/register and to show the list of + registered users, use the command show/register. - 9.2. Passwords + 9.2. Passwords At the moment, passwords only affect users who login to a DXSpider cluster node via telnet. If a user requires a password, they can either set it themselves or have the sysop enter it for them by using - the set/password command. Any users who already have passwords, such + the set/password command. Any users who already have passwords, such as remote sysops, will be asked for their passwords automatically by the cluster. Using passwords in this way means that the user has a choice on whether to have a password or not. To force the use of @@ -2055,11 +2055,11 @@ - 10. CVS + 10. CVS - 10.1. CVS from a Linux platform + 10.1. CVS from a Linux platform CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held at Sourceforge. This means that it is possible to update your @@ -2086,7 +2086,7 @@ steps which are listed below ... - First login as the user sysop. Next you need to connect to the CVS + First login as the user sysop. Next you need to connect to the CVS repository. You do this with the command below ... @@ -2157,7 +2157,7 @@ Now the magic part! From now on when you want to update, simply - connect to the Internet and then, as the user sysop ... + connect to the Internet and then, as the user sysop ... @@ -2175,7 +2175,7 @@ You will find any changes documented in the /spider/Changes file. - 10.2. CVS from a Windows platform + 10.2. CVS from a Windows platform After the initial setup, an update to your DXSpider software is no more than a couple of clicks away. This section is intended to @@ -2293,18 +2293,18 @@ - 11. The DXSpider Command Reference + 11. The DXSpider Command Reference - 11.1. accept (0) + 11.1. accept (0) - accept Set a filter to accept something + accept Set a filter to accept something Create a filter to accept somethingThere are 2 types of filter, accept and reject. See HELP FILTERING for moreinfo. - 11.2. accept/announce [input] [0-9] (8) + 11.2. accept/announce [input] [0-9] (8) - accept/announce [input] [0-9] Announce filter sysop + accept/announce [input] [0-9] Announce filter sysop version This version allows a sysop to set a filter for a callsign as well as @@ -2315,9 +2315,9 @@ - 11.3. accept/announce [0-9] (0) + 11.3. accept/announce [0-9] (0) - accept/announce [0-9] Set an 'accept' filter line for + accept/announce [0-9] Set an 'accept' filter line for announce Create an 'accept this announce' line for a filter. An accept filter @@ -2361,9 +2361,9 @@ but this probably for advanced users... - 11.4. accept/route [0-9] (8) + 11.4. accept/route [0-9] (8) - accept/route [0-9] Set an 'accept' filter line for + accept/route [0-9] Set an 'accept' filter line for routing Create an 'accept this routing PC Protocol' line for a filter. An @@ -2399,9 +2399,9 @@ - 11.5. accept/spots [input] [0-9] (8) + 11.5. accept/spots [input] [0-9] (8) - accept/spots [input] [0-9] Spot filter sysop version + accept/spots [input] [0-9] Spot filter sysop version This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:- @@ -2415,9 +2415,9 @@ - 11.6. accept/spots [0-9] (0) + 11.6. accept/spots [0-9] (0) - accept/spots [0-9] Set an 'accept' filter line for spots + accept/spots [0-9] Set an 'accept' filter line for spots Create an 'accept this spot' line for a filter. An accept filter line means that if the spot matches this filter it ispassed onto the user. @@ -2450,9 +2450,9 @@ but this probably for advanced users... - 11.7. accept/wcy [input] [0-9] (8) + 11.7. accept/wcy [input] [0-9] (8) - accept/wcy [input] [0-9] WCY filter sysop version + accept/wcy [input] [0-9] WCY filter sysop version This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:- @@ -2462,9 +2462,9 @@ - 11.8. accept/wcy [0-9] (0) + 11.8. accept/wcy [0-9] (0) - accept/wcy [0-9] set an 'accept' WCY filter + accept/wcy [0-9] set an 'accept' WCY filter It is unlikely that you will want to do this, but if you do then you canfilter on the following fields:- @@ -2479,9 +2479,9 @@ them).This command is really provided for future use.See HELP FILTER for information. - 11.9. accept/wwv [input] [0-9] (8) + 11.9. accept/wwv [input] [0-9] (8) - accept/wwv [input] [0-9] WWV filter sysop version + accept/wwv [input] [0-9] WWV filter sysop version This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:- @@ -2495,9 +2495,9 @@ - 11.10. accept/wwv [0-9] (0) + 11.10. accept/wwv [0-9] (0) - accept/wwv [0-9] set an 'accept' WWV filter + accept/wwv [0-9] set an 'accept' WWV filter It is unlikely that you will want to do this, but if you do then you canfilter on the following fields:- @@ -2517,33 +2517,33 @@ is probably the only useful thing to do (which will only show WWV broadcastsby stations in the US).See HELP FILTER for information. - 11.11. announce (0) + 11.11. announce (0) - announce Send an announcement to LOCAL users only + announce Send an announcement to LOCAL users only is the text of the announcement you wish to broadcast - 11.12. announce full (0) + 11.12. announce full (0) - announce full Send an announcement cluster wide + announce full Send an announcement cluster wide This will send your announcement cluster wide - 11.13. announce sysop (5) + 11.13. announce sysop (5) - announce sysop Send an announcement to Sysops only + announce sysop Send an announcement to Sysops only - 11.14. apropos (0) + 11.14. apropos (0) - apropos Search help database for + apropos Search help database for Search the help database for (it isn't case sensitive), and printthe names of all the commands that may be relevant. - 11.15. blank [] [] (0) + 11.15. blank [] [] (0) - blank [] [] Print nn (default 1) blank lines (or strings) + blank [] [] Print nn (default 1) blank lines (or strings) In its basic form this command prints one or more blank lines. However ifyou pass it a string it will replicate the string for the width of @@ -2571,20 +2571,20 @@ prints 'abcabcabcabcabcabc....'This is really only of any use in a script file and you can print a maximumof 9 lines. - 11.16. bye (0) + 11.16. bye (0) - bye Exit from the cluster + bye Exit from the cluster This will disconnect you from the cluster - 11.17. catchup all|[ ...] (5) + 11.17. catchup all|[ ...] (5) - catchup all|[ ...] Mark a message as sent + catchup all|[ ...] Mark a message as sent - 11.18. chat (0) + 11.18. chat (0) - chat Chat or Conference to a group + chat Chat or Conference to a group It is now possible to JOIN a group and have network wide conferencing to thatgroup. DXSpider does not (and probably will not) implement the @@ -2636,47 +2636,47 @@ See also JOIN, LEAVE, SHOW/CHAT - 11.19. clear/announce [input] [0-9|all] (8) + 11.19. clear/announce [input] [0-9|all] (8) - clear/announce [input] [0-9|all] Clear a announce filter + clear/announce [input] [0-9|all] Clear a announce filter line A sysop can clear an input or normal output filter for a user or thenode_default or user_default. - 11.20. clear/announce [1|all] (0) + 11.20. clear/announce [1|all] (0) - clear/announce [1|all] Clear a announce filter line + clear/announce [1|all] Clear a announce filter line This command allows you to clear (remove) a line in a annouce filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation. - 11.21. clear/route [input] [0-9|all] (8) + 11.21. clear/route [input] [0-9|all] (8) - clear/route [input] [0-9|all] Clear a route filter line + clear/route [input] [0-9|all] Clear a route filter line A sysop can clear an input or normal output filter for a user or thenode_default or user_default. - 11.22. clear/route [1|all] (0) + 11.22. clear/route [1|all] (0) - clear/route [1|all] Clear a route filter line + clear/route [1|all] Clear a route filter line This command allows you to clear (remove) a line in a route filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation. - 11.23. clear/spots [input] [0-9|all] (8) + 11.23. clear/spots [input] [0-9|all] (8) - clear/spots [input] [0-9|all] Clear a spot filter line + clear/spots [input] [0-9|all] Clear a spot filter line A sysop can clear an input or normal output filter for a user or thenode_default or user_default. - 11.24. clear/spots [0-9|all] (0) + 11.24. clear/spots [0-9|all] (0) - clear/spots [0-9|all] Clear a spot filter line + clear/spots [0-9|all] Clear a spot filter line This command allows you to clear (remove) a line in a spot filter or to remove the whole filter.If you have a filter:- @@ -2709,39 +2709,39 @@ the filter will be completely removed. - 11.25. clear/wcy [input] [0-9|all] (8) + 11.25. clear/wcy [input] [0-9|all] (8) - clear/wcy [input] [0-9|all] Clear a WCY filter line + clear/wcy [input] [0-9|all] Clear a WCY filter line A sysop can clear an input or normal output filter for a user or thenode_default or user_default. - 11.26. clear/wcy [1|all] (0) + 11.26. clear/wcy [1|all] (0) - clear/wcy [1|all] Clear a WCY filter line + clear/wcy [1|all] Clear a WCY filter line This command allows you to clear (remove) a line in a WCY filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation. - 11.27. clear/wwv [input] [0-9|all] (8) + 11.27. clear/wwv [input] [0-9|all] (8) - clear/wwv [input] [0-9|all] Clear a WWV filter line + clear/wwv [input] [0-9|all] Clear a WWV filter line A sysop can clear an input or normal output filter for a user or thenode_default or user_default. - 11.28. clear/wwv [1|all] (0) + 11.28. clear/wwv [1|all] (0) - clear/wwv [1|all] Clear a WWV filter line + clear/wwv [1|all] Clear a WWV filter line This command allows you to clear (remove) a line in a WWV filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation. - 11.29. connect (5) + 11.29. connect (5) - connect Start a connection to another DX Cluster + connect Start a connection to another DX Cluster Start a connection process that will culminate in a new connection to theDX cluster . This process creates a new 'client' process @@ -2749,26 +2749,26 @@ 'chat' exchangenecessary to traverse the network(s) to logon to the cluster . - 11.30. dbavail (0) + 11.30. dbavail (0) - dbavail Show a list of all the Databases in the system + dbavail Show a list of all the Databases in the system Title says it all really, this command lists all the databases definedin the system. It is also aliased to SHOW/COMMAND. - 11.31. dbcreate (9) + 11.31. dbcreate (9) - dbcreate Create a database entry + dbcreate Create a database entry - 11.32. dbcreate chain [..] (9) + 11.32. dbcreate chain [..] (9) - dbcreate chain [..] Create a chained database + dbcreate chain [..] Create a chained database entry - 11.33. dbcreate cmd (9) + 11.33. dbcreate cmd (9) - dbcreate cmd make a local command available + dbcreate cmd make a local command available as a DB DBCREATE allows you to define a database in the system. It doesn't @@ -2846,14 +2846,14 @@ locally. See DBIMPORT for the importing of existing AK1A format data to databases.See DBSHOW for generic database enquiry - 11.34. dbcreate remote (9) + 11.34. dbcreate remote (9) - dbcreate remote Create a remote database entry + dbcreate remote Create a remote database entry - 11.35. dbimport (9) + 11.35. dbimport (9) - dbimport Import AK1A data into a database + dbimport Import AK1A data into a database If you want to import or update data in bulk to a database you can usethis command. It will either create or update entries into an @@ -2867,9 +2867,9 @@ will import the standard OBLAST database that comes with AK1A into theoblast database held locally. - 11.36. dbremove (9) + 11.36. dbremove (9) - dbremove Delete a database + dbremove Delete a database DBREMOVE will completely remove a database entry and also delete any datafile that is associated with it. There is no warning, no comeback, @@ -2884,9 +2884,9 @@ removethe associated datafile.I repeat:There is no warning, no come- back, no safety net.You have been warned. - 11.37. dbshow (0) + 11.37. dbshow (0) - dbshow Display an entry, if it exists, in a database + dbshow 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 @@ -2906,9 +2906,9 @@ - 11.38. debug (9) + 11.38. debug (9) - debug Set the cluster program into debug mode + debug Set the cluster program into debug mode Executing this command will only have an effect if you are running the clusterin debug mode i.e. @@ -2921,26 +2921,26 @@ It will interrupt the cluster just after the debug command has fin- ished. - 11.39. delete/usdb ... (9) + 11.39. delete/usdb ... (9) - delete/usdb ... Delete this user from the US State Database + delete/usdb ... Delete this user from the US State Database This command will completely remove a one or more callsignsfrom the US States database.There is NO SECOND CHANCE.It goes without saying that you should use this command CAREFULLY!Note that these callsign may be re-instated by any weekly updates from the FCC. - 11.40. delete/user ... (9) + 11.40. delete/user ... (9) - delete/user ... Delete this user from the User Database + delete/user ... Delete this user from the User Database This command will completely remove a one or more users from the database.There is NO SECOND CHANCE.It goes without saying that you should use this command CAREFULLY! - 11.41. demonstrate (9) + 11.41. demonstrate (9) - demonstrate Demonstrate a command to another user + demonstrate Demonstrate a command to another user This command is provided so that sysops can demonstrate commands to other users. It runs a command as though that user had typed it in @@ -2956,15 +2956,15 @@ sideeffects. Commands are run at the privilege of the user which is beingdemonstrated to. - 11.42. directory (0) + 11.42. directory (0) - directory List messages + directory List messages - 11.43. directory - (0) + 11.43. directory - (0) - directory - List messages message message + directory - List messages message message List the messages in the messages directory.If there is a 'p' one space after the message number then it is a personal message. If there @@ -2993,55 +2993,55 @@ - 11.44. directory (0) + 11.44. directory (0) - directory List last messages + directory List last messages - 11.45. directory all (0) + 11.45. directory all (0) - directory all List all messages + directory all List all messages - 11.46. directory from (0) + 11.46. directory from (0) - directory from List all messages from + directory from List all messages from - 11.47. directory new (0) + 11.47. directory new (0) - directory new List all new messages + directory new List all new messages - 11.48. directory own (0) + 11.48. directory own (0) - directory own List your own messages + directory own List your own messages - 11.49. directory subject (0) + 11.49. directory subject (0) - directory subject List all messages with in subject + directory subject List all messages with in subject - 11.50. directory to (0) + 11.50. directory to (0) - directory to List all messages to + directory to List all messages to - 11.51. directory- (5) + 11.51. directory- (5) - directory- + directory- Sysops can see all users' messages. - 11.52. disconnect [ ...] (8) + 11.52. disconnect [ ...] (8) - disconnect [ ...] Disconnect a user or cluster + disconnect [ ...] Disconnect a user or cluster Disconnect any connected locally - 11.53. dx [by ] (0) + 11.53. dx [by ] (0) - dx [by ] Send a DX spot + dx [by ] Send a DX spot This is how you send a DX Spot to other users. You can, in fact, nowenter the and the either way round. @@ -3069,9 +3069,9 @@ The is compared against the available bands set up in the clus- ter. See SHOW/BANDS for more information. - 11.54. echo (0) + 11.54. echo (0) - echo Echo the line to the output + echo Echo the line to the output This command is useful in scripts and so forth for printing theline that you give to the command to the output. You can use thisin @@ -3114,9 +3114,9 @@ on the output. - 11.55. export (9) + 11.55. export (9) - export Export a message to a file + export Export a message to a file Export a message to a file. This command can only be executed on a localconsole with a fully privileged user. The file produced will be @@ -3132,9 +3132,9 @@ - 11.56. export_users [] (9) + 11.56. export_users [] (9) - export_users [] Export the users database to ascii + export_users [] Export the users database to ascii Export the users database to a file in ascii format. If no filenameis given then it will export the file to /spider/data/user_asc.If the @@ -3143,9 +3143,9 @@ thesuffix. BE WARNED: this will write to any file you have write access to. No check ismade on the filename (if any) that you specify. - 11.57. filtering... (0) + 11.57. filtering... (0) - filtering... Filtering things in DXSpider + filtering... Filtering things in DXSpider There are a number of things you can filter in the DXSpider system. Theyall use the same general mechanism.In general terms you can create @@ -3302,9 +3302,9 @@ else on HF.The next filter line lets through just VHF/UHF spots from EU. - 11.58. forward/latlong (8) + 11.58. forward/latlong (8) - forward/latlong Send latitude and longitude information to + forward/latlong Send latitude and longitude information to another cluster This command sends all the latitude and longitude information that @@ -3314,9 +3314,9 @@ haveSET/DXGRID enabled. This could be a LOT of information though, soit is not recommended on slow links. - 11.59. forward/opernam (1) + 11.59. forward/opernam (1) - forward/opernam Send out information on this to all + forward/opernam Send out information on this to all clusters This command sends out any information held in the user file which can @@ -3324,9 +3324,9 @@ Locationand Homenode. PC41s are only sent for the information that is available. - 11.60. help (0) + 11.60. help (0) - help The HELP Command + help The HELP Command HELP is available for a number of commands. The syntax is:- @@ -3341,9 +3341,9 @@ which will search the help databasefor the you specify and give you a list of likely commandsto look at with HELP. - 11.61. init (5) + 11.61. init (5) - init Re-initialise a link to an AK1A compatible node + init Re-initialise a link to an AK1A compatible node This command attempts to re-initialise a link to a (usually) AK1A nodethat has got confused, usually by a protocol loop of some kind. It @@ -3351,9 +3351,9 @@ (orbetter, if it is a real AK1A node, doing an RCMD DISC/F ).Best of luck - you will need it. - 11.62. join (0) + 11.62. join (0) - join Join a chat or conference group + join Join a chat or conference group JOIN allows you to join a network wide conference group. To join agroup (called FOC in this case) type:- @@ -3365,37 +3365,37 @@ See also CHAT, LEAVE, SHOW/CHAT - 11.63. kill (5) + 11.63. kill (5) - kill + kill As a sysop you can kill any message on the system. - 11.64. kill - (0) + 11.64. kill - (0) - kill - Delete a range of messages + kill - Delete a range of messages - 11.65. kill - (5) + 11.65. kill - (5) - kill - Remove a range of messages from the system + kill - Remove a range of messages from the system - 11.66. kill [ [ [ [ [ ...] (0) + 11.67. kill [ ...] (0) - kill [ ...] Remove or erase a message from the system + kill [ ...] Remove or erase a message from the system 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. - 11.68. kill expunge [ [ [ [ (5) + 11.69. kill from (5) - kill from Remove all messages from a callsign + kill from Remove all messages from a callsign - 11.70. kill full [ [ [ [ [ [ [ [ (5) + 11.72. kill to (5) - kill to Remove all messages to a callsign + kill to Remove all messages to a callsign - 11.73. kill from (0) + 11.73. kill from (0) - kill from Delete messages FROM a callsign or pattern + kill from Delete messages FROM a callsign or pattern - 11.74. kill to (0) + 11.74. kill to (0) - kill to Delete messages TO a callsign or pattern + kill to Delete messages TO a callsign or pattern - 11.75. leave (0) + 11.75. leave (0) - leave Leave a chat or conference group + leave Leave a chat or conference group LEAVE allows you to leave a network wide conference group. To leave agroup (called FOC in this case) type:- @@ -3483,24 +3483,24 @@ See also CHAT, JOIN, SHOW/CHAT - 11.76. links (0) + 11.76. links (0) - links Show which nodes is physically connected + links Show which nodes is physically connected This is a quick listing that shows which links are connected andsome information about them. See WHO for a list of all connections. - 11.77. load/aliases (9) + 11.77. load/aliases (9) - load/aliases Reload the command alias table + load/aliases Reload the command alias table Reload the /spider/cmd/Aliases file after you have editted it. Youwill need to do this if you change this file whilst the cluster isrunning in order for the changes to take effect. - 11.78. load/badmsg (9) + 11.78. load/badmsg (9) - load/badmsg Reload the bad msg table + load/badmsg Reload the bad msg table Reload the /spider/msg/badmsg.pl file if you have changed it manually whilstthe cluster is running. This table contains a number of perl @@ -3508,9 +3508,9 @@ each message. If any of them match then that message is immediately deleted on receipt. - 11.79. load/badwords (9) + 11.79. load/badwords (9) - load/badwords Reload the bad words table + load/badwords Reload the bad words table Reload the /spider/data/badwords file if you have changed it manually whilstthe cluster is running. This file contains a list of words @@ -3520,16 +3520,16 @@ words can be one or more on a line, lines starting with '#' are ignored. - 11.80. load/bands (9) + 11.80. load/bands (9) - load/bands Reload the band limits table + load/bands Reload the band limits table Reload the /spider/data/bands.pl file if you have changed it manually whilstthe cluster is running. - 11.81. load/cmd_cache (9) + 11.81. load/cmd_cache (9) - load/cmd_cache Reload the automatic command cache + load/cmd_cache Reload the automatic command cache Normally, if you change a command file in the cmd or local_cmd tree itwill automatially be picked up by the cluster program. Sometimes @@ -3538,22 +3538,22 @@ oneagain. Execute this command to reset everything back to the state itwas just after a cluster restart. - 11.82. load/forward (9) + 11.82. load/forward (9) - load/forward Reload the msg forwarding routing table + load/forward Reload the msg forwarding routing table Reload the /spider/msg/forward.pl file if you have changed itmanually whilst the cluster is running. - 11.83. load/keps (5) + 11.83. load/keps (5) - load/keps Load new keps data + load/keps Load new keps data - 11.84. load/keps [nn] (5) + 11.84. load/keps [nn] (5) - load/keps [nn] Load new keps data from message + load/keps [nn] Load new keps data from message If there is no message number then reload the current Keps data fromthe Keps.pm data file. You create this file by running @@ -3568,25 +3568,25 @@ vkeps.pl on it and then load the data, all in one step.These messages are sent to ALL by GB7DJK (and others) from time to time. - 11.85. load/messages (9) + 11.85. load/messages (9) - load/messages Reload the system messages file + load/messages Reload the system messages file If you change the /spider/perl/Messages file (usually whilstfiddling/writing new commands) you can have them take effect during acluster session by executing this command. You need to do this if getsomething like :-unknown message 'xxxx' in lang 'en' - 11.86. load/prefixes (9) + 11.86. load/prefixes (9) - load/prefixes Reload the prefix table + load/prefixes Reload the prefix table Reload the /spider/data/prefix_data.pl file if you have changed itmanually whilst the cluster is running. - 11.87. merge [/] (5) + 11.87. merge [/] (5) - merge [/] Ask for the latest spots and WWV + merge [/] Ask for the latest spots and WWV MERGE allows you to bring your spot and wwv database up to date. By defaultit will request the last 10 spots and 5 WWVs from the node you @@ -3595,9 +3595,9 @@ they will not duplicate any that have recently been added (the last 2 days for spots and last month for WWV data). - 11.88. msg [data ... ] (9) + 11.88. msg [data ... ] (9) - msg [data ... ] Alter various message parameters + msg [data ... ] Alter various message parameters Alter message parameters like To, From, Subject, whether private or bulletinor return receipt (RR) is required or whether to keep this @@ -3617,9 +3617,9 @@ This will display more information on the message than DIR does. - 11.89. pc (8) + 11.89. pc (8) - pc Send arbitrary text to a connected callsign + pc Send arbitrary text to a connected callsign Send some arbitrary text to a locally connected callsign. Noprocessing is done on the text. This command allows you to send PCProtocol to @@ -3643,9 +3643,9 @@ nected user butwithout any processing, added of "from to (1) + 11.90. ping (1) - ping Check the link quality between nodes + ping Check the link quality between nodes This command allows you to send a frame to another cluster node onthe network and get a return frame. The time it takes to do thisis a good @@ -3653,9 +3653,9 @@ output to the console in seconds.Any visible cluster node can be PINGed. - 11.91. rcmd (1) + 11.91. rcmd (1) - rcmd Send a command to another DX Cluster + rcmd Send a command to another DX Cluster This command allows you to send nearly any command to another DX Clusternode that is connected to the system. Whether you get any @@ -3664,35 +3664,35 @@ is allowing RCMDs from this node and c) whether you havepermission to send this command at all. - 11.92. read (0) + 11.92. read (0) - read Read the next unread personal message addressed to you + read Read the next unread personal message addressed to you - 11.93. read (0) + 11.93. read (0) - read Read the specified message + read Read the specified message You can read any messages that are sent as 'non-personal' and also anymessage either sent by or sent to your callsign. - 11.94. read- (5) + 11.94. read- (5) - read- + read- As a sysop you may read any message on the system - 11.95. reject (0) + 11.95. reject (0) - reject Set a filter to reject something + reject Set a filter to reject something Create a filter to reject somethingThere are 2 types of filter, accept and reject. See HELP FILTERING for moreinfo. - 11.96. reject/announce [input] [0-9] (8) + 11.96. reject/announce [input] [0-9] (8) - reject/announce [input] [0-9] Announce filter sysop + reject/announce [input] [0-9] Announce filter sysop version This version allows a sysop to set a filter for a callsign as well as @@ -3703,9 +3703,9 @@ - 11.97. reject/announce [0-9] (0) + 11.97. reject/announce [0-9] (0) - reject/announce [0-9] Set a 'reject' filter line for + reject/announce [0-9] Set a 'reject' filter line for announce Create an 'reject this announce' line for a filter. A reject filter @@ -3735,9 +3735,9 @@ but this probably for advanced users... - 11.98. reject/route [0-9] (8) + 11.98. reject/route [0-9] (8) - reject/route [0-9] Set an 'reject' filter line for + reject/route [0-9] Set an 'reject' filter line for routing Create an 'reject this routing PC Protocol' line for a filter. An @@ -3768,9 +3768,9 @@ as with ACCEPT/ROUTE 'by' is now a synonym for 'call'. - 11.99. reject/spots [input] [0-9] (8) + 11.99. reject/spots [input] [0-9] (8) - reject/spots [input] [0-9] Spot filter sysop version + reject/spots [input] [0-9] Spot filter sysop version This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:- @@ -3784,9 +3784,9 @@ - 11.100. reject/spots [0-9] (0) + 11.100. reject/spots [0-9] (0) - reject/spots [0-9] Set a 'reject' filter line for spots + reject/spots [0-9] Set a 'reject' filter line for spots Create a 'reject this spot' line for a filter. A reject filter line means that if the spot matches this filter it isdumped (not passed @@ -3811,9 +3811,9 @@ but this probably for advanced users... - 11.101. reject/wcy [input] [0-9] (8) + 11.101. reject/wcy [input] [0-9] (8) - reject/wcy [input] [0-9] WCY filter sysop version + reject/wcy [input] [0-9] WCY filter sysop version This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:- @@ -3823,9 +3823,9 @@ - 11.102. reject/wcy [0-9] (0) + 11.102. reject/wcy [0-9] (0) - reject/wcy [0-9] set a 'reject' WCY filter + reject/wcy [0-9] set a 'reject' WCY filter It is unlikely that you will want to do this, but if you do then you canfilter on the following fields:- @@ -3840,9 +3840,9 @@ them).This command is really provided for future use.See HELP FILTER for information. - 11.103. reject/wwv [input] [0-9] (8) + 11.103. reject/wwv [input] [0-9] (8) - reject/wwv [input] [0-9] WWV filter sysop version + reject/wwv [input] [0-9] WWV filter sysop version This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:- @@ -3856,9 +3856,9 @@ - 11.104. reject/wwv [0-9] (0) + 11.104. reject/wwv [0-9] (0) - reject/wwv [0-9] set a 'reject' WWV filter + reject/wwv [0-9] set a 'reject' WWV filter It is unlikely that you will want to do this, but if you do then you canfilter on the following fields:- @@ -3878,38 +3878,38 @@ is probably the only useful thing to do (which will only show WWV broadcastsby stations in the US).See HELP FILTER for information. - 11.105. reply (0) + 11.105. reply (0) - reply Reply (privately) to the last message that you have read + reply Reply (privately) to the last message that you have read - 11.106. reply (0) + 11.106. reply (0) - reply Reply (privately) to the specified message + reply Reply (privately) to the specified message - 11.107. reply b (0) + 11.107. reply b (0) - reply b Reply as a Bulletin to the specified message + reply b Reply as a Bulletin to the specified message - 11.108. reply noprivate (0) + 11.108. reply noprivate (0) - reply noprivate Reply as a Bulletin to the specified message + reply noprivate Reply as a Bulletin to the specified message - 11.109. reply rr (0) + 11.109. reply rr (0) - reply rr Reply to the specified message with read receipt + reply rr Reply to the specified message with read receipt You can reply to a message and the subject will automatically have"Re:" inserted in front of it, if it isn't already present.You can also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B that you can use with the SEND command (see SENDfor further details) - 11.110. save [-d -t -a] "" [...] (9) + 11.110. save [-d -t -a] "" [...] (9) - save [-d -t -a] "" [...] Save command output to a file + save [-d -t -a] "" [...] Save command output to a file This sysop only cammand allows you to save the output of one or morecommands to a file. For example:- @@ -3960,19 +3960,19 @@ this can be varied if you know what you are doing. See theadmin manual for more details. - 11.111. send [ ...] (0) + 11.111. send [ ...] (0) - send [ ...] Send a message to one or more callsigns + send [ ...] Send a message to one or more callsigns - 11.112. send copy (0) + 11.112. send copy (0) - send copy Send a copy of a message to someone + send copy Send a copy of a message to someone - 11.113. send noprivate (0) + 11.113. send noprivate (0) - send noprivate Send a message to all stations + send noprivate Send a message to all stations All the SEND commands will create a message which will be sent either toan individual callsign or to one of the 'bulletin' addresses. SEND @@ -4037,121 +4037,121 @@ themessage. You can carry on with the message until you are ready to send it. - 11.114. send private (0) + 11.114. send private (0) - send private Send a personal message + send private Send a personal message - 11.115. send rr (0) + 11.115. send rr (0) - send rr Send a message and ask for a read receipt + send rr Send a message and ask for a read receipt - 11.116. set/address (0) + 11.116. set/address (0) - set/address Record your postal address + set/address Record your postal address - 11.117. set/announce (0) + 11.117. set/announce (0) - set/announce Allow announce messages to come out on your terminal + set/announce Allow announce messages to come out on your terminal - 11.118. set/anntalk (0) + 11.118. set/anntalk (0) - set/anntalk Allow talk like announce messages on your terminal + set/anntalk Allow talk like announce messages on your terminal - 11.119. set/arcluster [..] (5) + 11.119. set/arcluster [..] (5) - set/arcluster [..] Make the callsign an AR-Cluster node + set/arcluster [..] Make the callsign an AR-Cluster node - 11.120. set/baddx .. (8) + 11.120. set/baddx .. (8) - set/baddx .. Stop callsigns in a dx spot being propagated + set/baddx .. Stop callsigns in a dx spot being propagated - 11.121. set/badnode .. (8) + 11.121. set/badnode .. (8) - set/badnode .. Stop spots from this node being propagated + set/badnode .. Stop spots from this node being propagated - 11.122. set/badspotter .. (8) + 11.122. set/badspotter .. (8) - set/badspotter .. Stop spots from this callsign being propagated + set/badspotter .. Stop spots from this callsign being propagated - 11.123. set/badword .. (8) + 11.123. set/badword .. (8) - set/badword .. Stop things with this word being propagated + set/badword .. Stop things with this word being propagated - 11.124. set/bbs [..] (5) + 11.124. set/bbs [..] (5) - set/bbs [..] Make the callsign a BBS + set/bbs [..] Make the callsign a BBS - 11.125. set/beep (0) + 11.125. set/beep (0) - set/beep Add a beep to DX and other messages on your terminal + set/beep Add a beep to DX and other messages on your terminal - 11.126. set/clx [..] (5) + 11.126. set/clx [..] (5) - set/clx [..] Make the callsign an CLX node + set/clx [..] Make the callsign an CLX node - 11.127. set/debug (9) + 11.127. set/debug (9) - set/debug Add a debug level to the debug set + set/debug Add a debug level to the debug set - 11.128. set/dx (0) + 11.128. set/dx (0) - set/dx Allow DX messages to come out on your terminal + set/dx Allow DX messages to come out on your terminal - 11.129. set/dxcq (0) + 11.129. set/dxcq (0) - set/dxcq Show CQ Zones on the end of DX announcements + set/dxcq Show CQ Zones on the end of DX announcements - 11.130. set/dxgrid (0) + 11.130. set/dxgrid (0) - set/dxgrid Allow QRA Grid Squares on the end of DX announcements + set/dxgrid Allow QRA Grid Squares on the end of DX announcements - 11.131. set/dxitu (0) + 11.131. set/dxitu (0) - set/dxitu Show ITU Zones on the end of DX announcements + set/dxitu Show ITU Zones on the end of DX announcements - 11.132. set/dxnet [..] (5) + 11.132. set/dxnet [..] (5) - set/dxnet [..] Make the callsign an DXNet node + set/dxnet [..] Make the callsign an DXNet node - 11.133. set/echo (0) + 11.133. set/echo (0) - set/echo Make the cluster echo your input + set/echo Make the cluster echo your input - 11.134. set/email ... (0) + 11.134. set/email ... (0) - set/email ... Set email address(es) and forward your personals + set/email ... Set email address(es) and forward your personals - 11.135. set/here (0) + 11.135. set/here (0) - set/here Tell the system you are present at your terminal + set/here Tell the system you are present at your terminal - 11.136. set/homenode (0) + 11.136. set/homenode (0) - set/homenode Set your normal cluster callsign + set/homenode Set your normal cluster callsign Tell the cluster system where you normally connect to. Any Messages sentto you will normally find their way there should you not be @@ -4162,14 +4162,14 @@ - 11.137. set/hops ann|spots|route|wwv|wcy (8) + 11.137. set/hops ann|spots|route|wwv|wcy (8) - set/hops ann|spots|route|wwv|wcy Set hop count + set/hops ann|spots|route|wwv|wcy Set hop count - 11.138. set/isolate (9) + 11.138. set/isolate (9) - set/isolate Isolate a node from the rest of the network + set/isolate Isolate a node from the rest of the network Connect a node to your system in such a way that you are a full protocolmember of its network and can see all spots on it, but nothing @@ -4177,34 +4177,34 @@ connected to you.You can potentially connect several nodes in this way. - 11.139. set/language (0) + 11.139. set/language (0) - set/language Set the language you want to use + set/language Set the language you want to use You can select the language that you want the cluster to use. Currentlythe languages available are en (English), de (German), es (Spanish),Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch). - 11.140. set/location (0) + 11.140. set/location (0) - set/location Set your latitude and longitude + set/location Set your latitude and longitude - 11.141. set/lockout (9) + 11.141. set/lockout (9) - set/lockout Stop a callsign connecting to the cluster + set/lockout Stop a callsign connecting to the cluster - 11.142. set/logininfo (0) + 11.142. set/logininfo (0) - set/logininfo Inform when a station logs in locally + set/logininfo Inform when a station logs in locally - 11.143. set/name (0) + 11.143. set/name (0) - set/name Set your name + set/name Set your name Tell the system what your name is eg:- @@ -4213,16 +4213,16 @@ - 11.144. set/node [..] (5) + 11.144. set/node [..] (5) - set/node [..] Make the callsign an AK1A cluster + set/node [..] Make the callsign an AK1A cluster Tell the system that the call(s) are to be treated as AK1A cluster andfed PC Protocol rather normal user commands. - 11.145. set/obscount (8) + 11.145. set/obscount (8) - set/obscount Set the 'pump-up' obscelence PING counter + set/obscount Set the 'pump-up' obscelence PING counter From 1.35 onwards neighbouring nodes are pinged at regular intervals (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a @@ -4237,9 +4237,9 @@ between 1 and 9.It is STRONGLY recommended that you don't change the default. - 11.146. set/page (0) + 11.146. set/page (0) - set/page Set the lines per page + set/page Set the lines per page Tell the system how many lines you wish on a page when the number of lineof output from a command is more than this. The default is 20. @@ -4252,9 +4252,9 @@ The setting is stored in your user profile. - 11.147. set/password (0) + 11.147. set/password (0) - set/password Set your own password + set/password Set your own password This command only works for a 'telnet' user (currently). It willonly work if you have a password already set. This initial passwordcan only @@ -4264,9 +4264,9 @@ the screenas you type, depending on the type of telnet client you have. - 11.148. set/password (9) + 11.148. set/password (9) - set/password Set a users password + set/password Set a users password The password for a user can only be set by a full sysop. The stringcan contain any characters. The way this field is used depends on context. @@ -4283,9 +4283,9 @@ command is executed in the startup script, then a password prompt isgiven after the normal 'login: ' prompt. - 11.149. set/pinginterval