The DXSpider Administration Manual v1.50
Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll,
K1XX, (k1xx@ptcnh.net)
- July 2002 revision 0.1
+ January 2003 revision 0.2
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1. Routing and Filtering
-
1.1 Introduction
1.2 Route Filters
1.3 The node_default filter
1.12 Isolating networks
2. Other filters
-
2.1 Filtering Mail
2.2 Filtering words from text fields in Announce, Talk and DX spots
2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters
3. Mail
-
3.1 Personal mail
3.2 Bulletin mail
3.3 Forward.pl
3.8 BBS interface
4. Scripts
-
5. Databases
-
5.1 Creating databases
5.2 Importing databases
5.3 Checking available databases
5.5 Removing databases
6. Information, files and useful programs
-
6.1 MOTD
6.2 MOTD_NOR
6.3 Downtime message
6.9 Connecting logging programs
7. Java Web applet
-
- 8. Security
-
- 8.1 Registration
- 8.2 Passwords
-
- 9. CVS
-
- 9.1 CVS from a Linux platform
- 9.2 CVS from a Windows platform
-
- 10. The DXSpider command set
-
- 10.1 accept/announce (0)
- 10.2 accept/announce (extended for sysops) (8)
- 10.3 accept/route (8)
- 10.4 accept/spots (0)
- 10.5 accept/spots (extended for sysops) (8)
- 10.6 accept/wcy (0)
- 10.7 accept/wcy (extended for sysops) (8)
- 10.8 accept/wwv (0)
- 10.9 accept/wwv (extended for sysops) (8)
- 10.10 announce (0)
- 10.11 announce full (0)
- 10.12 announce sysop (5)
- 10.13 apropos (0)
- 10.14 bye (0)
- 10.15 catchup (5)
- 10.16 clear/announce (8)
- 10.17 clear/route (8)
- 10.18 clear/spots (0)
- 10.19 clear/spots (extended for sysops) (8)
- 10.20 clear/wcy (0)
- 10.21 clear/wcy (extended for sysops) (8)
- 10.22 clear/wwv (0)
- 10.23 clear/wwv (extended for sysops) (8)
- 10.24 connect (5)
- 10.25 dbavail (0)
- 10.26 dbcreate (9)
- 10.27 dbimport (9)
- 10.28 dbremove (9)
- 10.29 dbshow (0)
- 10.30 debug (9)
- 10.31 delete/user (9)
- 10.32 demonstrate (9)
- 10.33 directory (0)
- 10.34 directory (extended for sysops) (5)
- 10.35 disconnect (8)
- 10.36 dx (0)
- 10.37 export (9)
- 10.38 export_users (9)
- 10.39 filtering (0)
- 10.40 forward/latlong (8)
- 10.41 forward/opername (1)
- 10.42 help (0)
- 10.43 init (5)
- 10.44 kill (0)
- 10.45 kill (5)
- 10.46 kill full (5)
- 10.47 kill/expunge (6)
- 10.48 links (0)
- 10.49 load/aliases (9)
- 10.50 load/badmsg (9)
- 10.51 load/badwords (9)
- 10.52 load/bands (9)
- 10.53 load/cmd_cache (9)
- 10.54 load/forward (9)
- 10.55 load/messages (9)
- 10.56 load/prefixes (9)
- 10.57 merge (5)
- 10.58 msg (9)
- 10.59 pc (8)
- 10.60 ping (1)
- 10.61 rcmd (1)
- 10.62 read (0)
- 10.63 read (extended for sysops) (5)
- 10.64 reject/announce
- 10.65 reject/announce (extended for sysops) (8)
- 10.66 reject/route (8)
- 10.67 reject/spots (0)
- 10.68 reject/spots (extended for sysops) (8)
- 10.69 reject/wcy (0)
- 10.70 reject/wcy (extended for sysops) (8)
- 10.71 reject/wwv (0)
- 10.72 reject/wwv (extended for sysops) (8)
- 10.73 reply (0)
- 10.74 send (0)
- 10.75 set/address (0)
- 10.76 set/announce (0)
- 10.77 set/arcluster (5)
- 10.78 set/baddx (8)
- 10.79 set/badnode (6)
- 10.80 set/badspotter (8)
- 10.81 set/badword (8)
- 10.82 set/beep (0)
- 10.83 set/bbs (5)
- 10.84 set/clx (5)
- 10.85 set/debug (9)
- 10.86 set/dx (0)
- 10.87 set/dxgrid (0)
- 10.88 set/dxnet (5)
- 10.89 set/echo (0)
- 10.90 set/email (0)
- 10.91 set/here (0)
- 10.92 set/homenode (0)
- 10.93 set/hops (8)
- 10.94 set/isolate (9)
- 10.95 set/language (0)
- 10.96 set/location (0)
- 10.97 set/sys_location (9)
- 10.98 set/logininfo (0)
- 10.99 set/lockout (9)
- 10.100 set/name (0)
- 10.101 set/node (9)
- 10.102 set/obscount (9)
- 10.103 set/page (0)
- 10.104 set/password (0)
- 10.105 set/password (9)
- 10.106 set/pinginterval (9)
- 10.107 set/privilege (9)
- 10.108 set/spider (5)
- 10.109 set/sys_qra (9)
- 10.110 set/qra (0)
- 10.111 set/qth (0)
- 10.112 set/register (9)
- 10.113 set/talk (0)
- 10.114 set/wcy (0)
- 10.115 set/wwv (0)
- 10.116 set/wx (0)
- 10.117 show/baddx (1)
- 10.118 show/badnode (6)
- 10.119 show/badspotter (1)
- 10.120 show/badword (1)
- 10.121 show/configuration (0)
- 10.122 show/configuration/node (0)
- 10.123 show/connect (1)
- 10.124 show/date (0)
- 10.125 show/debug (9)
- 10.126 show/dx (0)
- 10.127 show/dxcc (0)
- 10.128 sh/dxstats (0)
- 10.129 show/files (0)
- 10.130 show/filter (0)
- 10.131 show/filter (extended for sysops) (5)
- 10.132 show/hfstats (0)
- 10.133 show/hftable (0)
- 10.134 show/hops (8)
- 10.135 show/isolate (1)
- 10.136 show/lockout (9)
- 10.137 show/log (8)
- 10.138 show/moon (0)
- 10.139 show/muf (0)
- 10.140 show/newconfiguration (0)
- 10.141 show/newconfiguration/node (0)
- 10.142 show/node (1)
- 10.143 show/prefix (0)
- 10.144 show/program (5)
- 10.145 show/qra (0)
- 10.146 show/qrz (0)
- 10.147 show/registered (9)
- 10.148 show/route (0)
- 10.149 show/satellite (0)
- 10.150 show/sun (0)
- 10.151 show/time (0)
- 10.152 show/vhfstats (0)
- 10.153 show/vhftable (0)
- 10.154 show/wcy (0)
- 10.155 show/wwv (0)
- 10.156 shutdown (5)
- 10.157 spoof (9)
- 10.158 stat/db (5)
- 10.159 stat/channel (5)
- 10.160 stat/msg (5)
- 10.161 stat/route_node (5)
- 10.162 stat/route_user (5)
- 10.163 stat/user (5)
- 10.164 sysop (0)
- 10.165 talk (0)
- 10.166 type (0)
- 10.167 who (0)
- 10.168 wx (0)
- 10.169 wx (enhanced for sysops) (5)
+ 8. Web based statistics
+ 9. Security
+ 9.1 Registration
+ 9.2 Passwords
+
+ 10. CVS
+ 10.1 CVS from a Linux platform
+ 10.2 CVS from a Windows platform
+
+ 11. The DXSpider command set
+ 11.1 accept/announce (0)
+ 11.2 accept/announce (extended for sysops) (8)
+ 11.3 accept/route (8)
+ 11.4 accept/spots (0)
+ 11.5 accept/spots (extended for sysops) (8)
+ 11.6 accept/wcy (0)
+ 11.7 accept/wcy (extended for sysops) (8)
+ 11.8 accept/wwv (0)
+ 11.9 accept/wwv (extended for sysops) (8)
+ 11.10 announce (0)
+ 11.11 announce full (0)
+ 11.12 announce sysop (5)
+ 11.13 apropos (0)
+ 11.14 bye (0)
+ 11.15 catchup (5)
+ 11.16 clear/announce (8)
+ 11.17 clear/route (8)
+ 11.18 clear/spots (0)
+ 11.19 clear/spots (extended for sysops) (8)
+ 11.20 clear/wcy (0)
+ 11.21 clear/wcy (extended for sysops) (8)
+ 11.22 clear/wwv (0)
+ 11.23 clear/wwv (extended for sysops) (8)
+ 11.24 connect (5)
+ 11.25 dbavail (0)
+ 11.26 dbcreate (9)
+ 11.27 dbimport (9)
+ 11.28 dbremove (9)
+ 11.29 dbshow (0)
+ 11.30 debug (9)
+ 11.31 delete/user (9)
+ 11.32 demonstrate (9)
+ 11.33 directory (0)
+ 11.34 directory (extended for sysops) (5)
+ 11.35 disconnect (8)
+ 11.36 dx (0)
+ 11.37 export (9)
+ 11.38 export_users (9)
+ 11.39 filtering (0)
+ 11.40 forward/latlong (8)
+ 11.41 forward/opername (1)
+ 11.42 help (0)
+ 11.43 init (5)
+ 11.44 kill (0)
+ 11.45 kill (5)
+ 11.46 kill full (5)
+ 11.47 kill/expunge (6)
+ 11.48 links (0)
+ 11.49 load/aliases (9)
+ 11.50 load/badmsg (9)
+ 11.51 load/badwords (9)
+ 11.52 load/bands (9)
+ 11.53 load/cmd_cache (9)
+ 11.54 load/forward (9)
+ 11.55 load/messages (9)
+ 11.56 load/prefixes (9)
+ 11.57 merge (5)
+ 11.58 msg (9)
+ 11.59 pc (8)
+ 11.60 ping (1)
+ 11.61 rcmd (1)
+ 11.62 read (0)
+ 11.63 read (extended for sysops) (5)
+ 11.64 reject/announce
+ 11.65 reject/announce (extended for sysops) (8)
+ 11.66 reject/route (8)
+ 11.67 reject/spots (0)
+ 11.68 reject/spots (extended for sysops) (8)
+ 11.69 reject/wcy (0)
+ 11.70 reject/wcy (extended for sysops) (8)
+ 11.71 reject/wwv (0)
+ 11.72 reject/wwv (extended for sysops) (8)
+ 11.73 reply (0)
+ 11.74 send (0)
+ 11.75 set/address (0)
+ 11.76 set/announce (0)
+ 11.77 set/arcluster (5)
+ 11.78 set/baddx (8)
+ 11.79 set/badnode (6)
+ 11.80 set/badspotter (8)
+ 11.81 set/badword (8)
+ 11.82 set/beep (0)
+ 11.83 set/bbs (5)
+ 11.84 set/clx (5)
+ 11.85 set/debug (9)
+ 11.86 set/dx (0)
+ 11.87 set/dxgrid (0)
+ 11.88 set/dxnet (5)
+ 11.89 set/echo (0)
+ 11.90 set/email (0)
+ 11.91 set/here (0)
+ 11.92 set/homenode (0)
+ 11.93 set/hops (8)
+ 11.94 set/isolate (9)
+ 11.95 set/language (0)
+ 11.96 set/location (0)
+ 11.97 set/sys_location (9)
+ 11.98 set/logininfo (0)
+ 11.99 set/lockout (9)
+ 11.100 set/name (0)
+ 11.101 set/node (9)
+ 11.102 set/obscount (9)
+ 11.103 set/page (0)
+ 11.104 set/password (0)
+ 11.105 set/password (9)
+ 11.106 set/pinginterval (9)
+ 11.107 set/privilege (9)
+ 11.108 set/spider (5)
+ 11.109 set/sys_qra (9)
+ 11.110 set/qra (0)
+ 11.111 set/qth (0)
+ 11.112 set/register (9)
+ 11.113 set/talk (0)
+ 11.114 set/wcy (0)
+ 11.115 set/wwv (0)
+ 11.116 set/wx (0)
+ 11.117 show/baddx (1)
+ 11.118 show/badnode (6)
+ 11.119 show/badspotter (1)
+ 11.120 show/badword (1)
+ 11.121 show/configuration (0)
+ 11.122 show/configuration/node (0)
+ 11.123 show/connect (1)
+ 11.124 show/date (0)
+ 11.125 show/debug (9)
+ 11.126 show/dx (0)
+ 11.127 show/dxcc (0)
+ 11.128 sh/dxstats (0)
+ 11.129 show/files (0)
+ 11.130 show/filter (0)
+ 11.131 show/filter (extended for sysops) (5)
+ 11.132 show/hfstats (0)
+ 11.133 show/hftable (0)
+ 11.134 show/hops (8)
+ 11.135 show/isolate (1)
+ 11.136 show/lockout (9)
+ 11.137 show/log (8)
+ 11.138 show/moon (0)
+ 11.139 show/muf (0)
+ 11.140 show/newconfiguration (0)
+ 11.141 show/newconfiguration/node (0)
+ 11.142 show/node (1)
+ 11.143 show/prefix (0)
+ 11.144 show/program (5)
+ 11.145 show/qra (0)
+ 11.146 show/qrz (0)
+ 11.147 show/registered (9)
+ 11.148 show/route (0)
+ 11.149 show/satellite (0)
+ 11.150 show/sun (0)
+ 11.151 show/time (0)
+ 11.152 show/vhfstats (0)
+ 11.153 show/vhftable (0)
+ 11.154 show/wcy (0)
+ 11.155 show/wwv (0)
+ 11.156 shutdown (5)
+ 11.157 spoof (9)
+ 11.158 stat/db (5)
+ 11.159 stat/channel (5)
+ 11.160 stat/msg (5)
+ 11.161 stat/route_node (5)
+ 11.162 stat/route_user (5)
+ 11.163 stat/user (5)
+ 11.164 sysop (0)
+ 11.165 talk (0)
+ 11.166 type (0)
+ 11.167 who (0)
+ 11.168 wx (0)
+ 11.169 wx (enhanced for sysops) (5)
______________________________________________________________________
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.
"national" network. Here in the UK that means nodes from the UK and
Eire, in EU it is more complex as the networks there grew up in a more
intertwined way.
- The generic commands are:-
- reject/route node_default <filter_option>
+ The generic commands are:-
- or
- accept/route node_default <filter_option>
+ reject/route node_default <filter_option>
+
+ or
+
+ accept/route node_default <filter_option>
-
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.
-
GB7DJK uses the first of these. The DXCC countries can be obtained
from the show/prefix command.
rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
+
What this does is accept node and user information for our national
network from nodes that are in our national network, but rejects such
information from anyone else. Although it doesn't explicitly say so,
-
After you have got tired of that, to put it back the way it was:-
-
-
1.4. General route filtering
Exactly the same rules apply for general route filtering. You would
-
-
Here are some examples of route filters ...
-
In practice you will either be opening the default filter out for a
partner by defining a specific filter for that callsign:-
acc/route gb7baa input all
+
or restricting it quite a lot, in fact making it very nearly like an
isolated node, like this:-
-
This last example takes everything except UK and Eire from PI4EHV-8
but only sends him my local configuration (just a PC19 for GB7DJK and
PC16s for my local users).
-
accept/spots .....
reject/spots .....
-
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
-
There is clear/xxxx command for each type of filter.
-
show/filter
-
-
For now we are going to use spots for the examples, but you can apply
the same principles to all types of filter.
-
then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
-
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
-
But in that case you might only be interested in iota and say:-
-
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
-
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.
-
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'.
-
To remove all the filter lines in the spot filter ...
-
-
1.7. Filter options
You can filter in several different ways. The options are listed in
-
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
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
#
# hop table construction
#
-
-
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
-
'DB0FHF-15' => {
11 => 5,
12 => 8,
-
If you do not do this, you will get errors and the file will not work
as expected.
-
all work on their specific area of the protocol.
-
# 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)
-
-
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
-
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:
-
a bad spotter:
-
and some bad dx:
-
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.
-
-
3. Mail
DXSpider deals seamlessly with standard AK1A type mail. It supports
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
#
# this is an example message forwarding file for the system
#
-
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.
-
-
-
-
-
MSG TO <msgno> <call> - change TO callsign to <call>
MSG FRom <msgno> <call> - change FROM callsign to <call>
MSG PRrivate <msgno> - set private flag
-
These commands are simply typed from within the cluster as the sysop
user.
-
-
3.6. Filtering mail
This is described in the section on Other filters so I will not
-
Any mail sent to "sysop" would only be sent to the callsigns in this
list.
-
-
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
-
The lines in between commands can simply insert a blank line or a
character such as a + sign to make the output easier to read. Simply
create this script with your favourite editor and save it with the
-
This creates a chained database entry. The first database will be
scanned, then the second, the third etc...
-
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...
-
Remote databases cannot be chained, however, the last database in a
chain can be a remote database.
-
This will update the existing local oblast database or create it if it
does not exist.
-
-
dbavail
DB Name Location Chain
qsl Local
-
-
5.4. Looking up databases
To look for information in a defined database, simply use the dbshow
-
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
-
-
-
-
Now you can simply use show/buckmaster or an abreviation.
-
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
-
They can be read by the user by typing the command ....
-
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
-
-
An example would look like this ....
sh/files
-
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,
-
To look what is in the bulletin directory you issue the command ....
-
You can now read any file in this directory using the type command,
like this ....
-
-
The page length will of course depend on what you have it set to!
-
#
# Local Aliases File
#
-
-
Each alphabetical section should be preceded by the initial letter and
the section should be wrapped in square brackets as you can see. The
syntax is straightforward. The first section on each line is the new
-
-
would export message number 5467 as a file called keps.in in the
/spider/perl directory.
-
-
Now go back to the cluster and issue the command ...
-
-
That is it! the kepler data has been updated.
-
-
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
and it should be ready for connection. All that is required is a 3
-
-
I have used /usr/bin/javac as an example, your path to javac may be
different.
+ 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
+ http://www.gb7mbc.net/mrtg/stats.html.
+
+
+ The following should help you get it all working.
+
+
+ First you need to download the latest version of MRTG from
+ http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need
+ the following files..
+
+
+
+ libpng-1.0.14.tar.gz
+ zlib-1.1.4.tar.gz
+ gd-1.8.3.tar.gz
+
+
+
+ Login to your machine as the root user, put all the downloaded files
+ in /usr/local/src/ (or wherever you prefer) and untar and compile
+ them. All the information to compile and install these sources come
+ with them. After compilation and installation, you will find MRTG in
+ /usr/local/mrtg-2.
+
+
+ Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
+ /spider/html/mrtg/
+
+
+ You now need to make 2 symbolic links like below...
+
+
+
+ ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
+ ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
+
+
+
+ Now login to the cluster as your sysop user and run the command "mrtg
+ all".
+
+
+ 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
+ below...
+
+
+
+ indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
+
+
+
+ Changing the callsign for your own cluster callsign of course!
+
+
+ And finally you need to login as the root user and create one last
+ symbolic link. Where this points will depend on where your html
+ documents are kept. For RedHat systems you use...
+
+
+
+ ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
+
+
+
+ and for SuSE systems...
+
+
+
+ ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
+
+
- 8. Security
+ If you now point your browser to your website as below it should all
+ be happening!
+
+
+
+ http://www.xxx.xxx/mrtg/stats.html
+
+
+
+ Of course, to get the stats to update, you need to add some
+ information in the spider crontab file as below...
+
+
+
+ # Update stats for mrtg on website
+ 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
+
+
+
+ This will update the site every 5 minutes.
+
+
+ 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
security.
- 8.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
-
The user g0vgs can now fully use the cluster. In order to enable
registration, you can issue the command ...
-
-
set/var $main::reqreg = 1
-
Any users that are not registered will now see the motd_nor file
rather than the motd file as discussed in the Information, files and
useful programs section.
registered users, use the command show/register.
- 8.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
-
-
at the cluster prompt. This can also be added to the
/spider/scripts/startup file as above to make the change permanent.
+ 10. CVS
- 9. CVS
- 9.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
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.
-
-
Now if you are doing a new installation, that's it. Carry on as if
you have just downloaded and untarred the lastest tarball.
-
This is assuming you downloaded to the /tmp directory of course.
-
-
- cd /spider
- cvs -z3 update -d
-
+ cd /spider
+ cvs -z3 update -d
You will find any changes documented in the /spider/Changes file.
- 9.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
Pick your download mirror and then install WinCVS after the download
is complete.
+
In this next section I have included a series of links to .jpg files
to take advantage of the picture and 1000 words equivalency. The .jpg
files are in the C:\spider\html directory. If someone using a Linux
-
and select
-
- "passwd" file on the cvs server
-
+ "passwd" file on the cvs server
-
appear in the lower pane. You're done. The updated files are in
place ready for you to stop and then restart your DXSpider. After the
restart, you're running with the latest version of DXSpider.
WinCVS.
+ Click on the greyed-out Spider directory in the left screen
+ Click on the green down arrow
+ Click OK on the Update Settings dialog box
+ Restart your Spider software
- Click on the greyed-out Spider directory in the left screen
- Click on the green down arrow
- Click OK on the Update Settings dialog box
- Restart your Spider software
-
-
-
-
-
- 10. The DXSpider command set
+ 11. 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
- 10.1. accept/announce (0)
+ 11.1. accept/announce (0)
accept/announce [0-9] <pattern> Set an accept filter line for announce
You can use any of the following things in this line:-
-
-
info <string> eg: iota or qsl
by <prefixes> eg: G,M,2
origin <prefixes>
-
some examples:-
-
or
-
- acc/ann by G,M,2
-
+ acc/ann by G,M,2
-
but this probably for advanced users...
- 10.2. accept/announce (extended for sysops) (8)
+ 11.2. accept/announce (extended for sysops) (8)
accept/announce <call> [input] [0-9]<pattern> Announce filter sysop
version
-
-
- 10.3. accept/route (8)
+ 11.3. accept/route (8)
accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
routing
origin_zone <numbers>
+
some examples:-
-
-
You can use the tag 'all' to accept everything eg:
-
-
- 10.4. accept/spots (0)
+ 11.4. accept/spots (0)
accept/spots [0-9] <pattern> Set an accept filter line for spots
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.
+
Please read the following section carefully. Though it looks similar,
reformatting, corrections, and hopefully clarifications have been
added.
+ Filters for the station being spotted:
+ call <letters of the prefix, but NOT country inclusive>
+ call G --> G1AAA, GJ2BBB, GU3CCC, etc will be spotted
+ call K --> K1XX, K1XXX will be spotted
+ W1XX, W1XXX will NOT be spotted
+ call PA --> PA3EZL will be spotted
+ PB2FG will NOT be spotted
+ call_dxcc <numbers or prefixes>
+ call_dxcc G --> G1AAA will be spotted
+ GU1AAA will NOT be spotted (different country)
+ call_dxcc K --> K1XX, W1XX will be spotted (same country)
+ call_dxcc 139 --> PA3EZL and PB2FG will be spotted
+ call_itu <numbers>
+ call_zone <numbers>
+ Filters for the callsign of the station doing the spotting:
+ by <letters of the prefix, but NOT country inclusive>
+ by G --> spots from G1AAA, GJ2BBB, GU3CCC, etc will be spotted
+ by K --> spots from K1XX, K1XXX will be spotted
+ spots from W1XX, W1XXX will NOT be spotted
+ by_dxcc <numbers or prefixes>
+ by_dxcc G --> spots from G1AAA will be spotted
+ spots from GU1AAA will NOT be spotted (different
+ country)
+ by_dxcc K --> spots from K1XX, W1XX will be spotted (same country)
+ by_dxcc 139 --> spots from PA3EZL or PB2FG will be spotted
+ by_itu <numbers>
+ by_zone <numbers>
+ Filters for the callsign of the "node" doing the spotting:
+ origin <letters of the prefix, but NOT country inclusive>
+ origin K --> spots from a node starting with K will be spotted
+ spots from a node starting with KK will NOT be spotted
+ spots from a node starting with W will NOT be spotted
+ Filters for the callsign of the connected node or user (channel) doing the spotting:
+ channel <prefixes>
+ channel W1HR --> spots from the connected node W1HR will be spotted
+ channel K1QX --> spots from the connected user K1QX will be spotted
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Filters for the station being spotted:
- call <letters of the prefix, but NOT country inclusive>
- call G --> G1AAA, GJ2BBB, GU3CCC, etc will be spotted
- call K --> K1XX, K1XXX will be spotted
- W1XX, W1XXX will NOT be spotted
- call PA --> PA3EZL will be spotted
- PB2FG will NOT be spotted
-
- call_dxcc <numbers or prefixes>
- call_dxcc G --> G1AAA will be spotted
- GU1AAA will NOT be spotted (different country)
- call_dxcc K --> K1XX, W1XX will be spotted (same country)
- call_dxcc 139 --> PA3EZL and PB2FG will be spotted
-
- call_itu <numbers>
- call_zone <numbers>
-
- Filters for the callsign of the station doing the spotting:
- by <letters of the prefix, but NOT country inclusive>
- by G --> spots from G1AAA, GJ2BBB, GU3CCC, etc will be spotted
- by K --> spots from K1XX, K1XXX will be spotted
- spots from W1XX, W1XXX will NOT be spotted
-
- by_dxcc <numbers or prefixes>
- by_dxcc G --> spots from G1AAA will be spotted
- spots from GU1AAA will NOT be spotted (different
- country)
- by_dxcc K --> spots from K1XX, W1XX will be spotted (same country)
- by_dxcc 139 --> spots from PA3EZL or PB2FG will be spotted
-
- by_itu <numbers>
- by_zone <numbers>
-
- Filters for the callsign of the "node" doing the spotting:
- origin <letters of the prefix, but NOT country inclusive>
- origin K --> spots from a node starting with K will be spotted
- spots from a node starting with KK will NOT be spotted
- spots from a node starting with W will NOT be spotted
-
- Filters for the callsign of the connected node or user (channel) doing the spotting:
- channel <prefixes>
- channel W1HR --> spots from the connected node W1HR will be spotted
- channel K1QX --> spots from the connected user K1QX will be spotted
-
- info <string> eg: iota or qsl
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
- on <range> same as 'freq'
-
-
+ info <string> eg: iota or qsl
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
You can use the tag 'all' to accept everything, eg:
-
but this probably for advanced users...
- 10.5. accept/spots (extended for sysops) (8)
+ 11.5. accept/spots (extended for sysops) (8)
accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
-
-
- 10.6. accept/wcy (0)
+ 11.6. accept/wcy (0)
accept/wcy [0-9] <pattern> set an accept WCY filter
-
-
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).
See HELP FILTER for information.
-
- 10.7. accept/wcy (extended for sysops) (8)
+ 11.7. accept/wcy (extended for sysops) (8)
accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
-
-
- 10.8. accept/wwv (0)
+ 11.8. accept/wwv (0)
accept/wwv [0-9] <pattern> Set an accept WWV filter
-
for example
-
is probably the only useful thing to do (which will only show WWV
broadcasts by stations in the US).
See HELP FILTER for information.
- 10.9. accept/wwv (extended for sysops) (8)
+
+ 11.9. accept/wwv (extended for sysops) (8)
accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
+ accept/wwv db0sue-7 1 by_zone 4
+ accept/wwv node_default all
+ set/hops node_default 10
- 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
-
-
+ accept/wwv user_default by W,K
- 10.10. announce (0)
+ 11.10. announce (0)
announce <text> Send an announcement to local users
sysop will override set/noannounce.
- 10.11. announce full (0)
+ 11.11. announce full (0)
announce full <text> Send an announcement cluster wide
- 10.12. announce sysop (5)
+ 11.12. announce sysop (5)
announce sysop <text>
Send an announcement to Sysops only
- 10.13. apropos (0)
+ 11.13. apropos (0)
apropos <string> Search the help database
print the names of all the commands that may be relevant.
- 10.14. bye (0)
+ 11.14. bye (0)
bye Exit from the cluster
This will disconnect you from the cluster
- 10.15. catchup (5)
+ 11.15. catchup (5)
catchup <node_call> All|[<msgno> ...] Mark a message as sent
-
and to undo what you have just done:-
-
which will arrange for them to be forward candidates again.
Order is not important.
- 10.16. clear/announce (8)
+ 11.16. clear/announce (8)
clear/announce [input] <callsign> [0-9|all] Clear an announce filter
line
node_default or user_default.
- 10.17. clear/route (8)
+ 11.17. clear/route (8)
clear/route [input] ^lt;callsign> [0-9|all] Clear a route filter line
node_default or user_default.
- 10.18. clear/spots (0)
+ 11.18. clear/spots (0)
clear/spots [1|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:-
-
you will be left with:-
-
If you do:
-
the filter will be completely removed.
- 10.19. clear/spots (extended for sysops) (8)
+ 11.19. clear/spots (extended for sysops) (8)
clear/spots [input] <callsign> [0-9|all] Clear a spot filter line
node_default or user_default.
- 10.20. clear/wcy (0)
+ 11.20. clear/wcy (0)
clear/wcy [1|all] Clear a WCY filter line
see CLEAR/SPOTS for a more detailed explanation.
- 10.21. clear/wcy (extended for sysops) (8)
+ 11.21. clear/wcy (extended for sysops) (8)
clear/wcy [input] <callsign> [0-9|all] Clear a WCY filter line
+
A sysop can clear an input or normal output filter for a user or the
node_default or user_default.
- 10.22. clear/wwv (0)
+ 11.22. clear/wwv (0)
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.
- 10.23. clear/wwv (extended for sysops) (8)
+ 11.23. clear/wwv (extended for sysops) (8)
clear/wwv [input] <callsign> [0-9|all] Clear a WWV filter line
node_default or user_default.
- 10.24. connect (5)
+ 11.24. connect (5)
connect <callsign> Start a connection to another DX Cluster
cluster <callsign>.
- 10.25. dbavail (0)
+ 11.25. dbavail (0)
dbavail Show a list of all the databases in the system
defined in the system. It is also aliased to SHOW/COMMAND.
- 10.26. dbcreate (9)
+ 11.26. dbcreate (9)
dbcreate <name> Create a database entry
dbcreate <name> chain <name> [<name>..] Create a chained database
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:
-
DBCREATE sdx_qsl chain sql_ad
No checking is done to see if the any of the chained databases exist,
-
to allow
SH/BUCK g1tlh
databases. See DBSHOW for generic database enquiry
- 10.27. dbimport (9)
+ 11.27. dbimport (9)
dbimport <dbname> Import AK1A data into a database
oblast database held locally.
- 10.28. dbremove (9)
+ 11.28. dbremove (9)
dbremove <dbname> Delete a database
-
DBREMOVE will completely remove a database entry and also delete any
data file that is associated with it.
DBREMOVE oblast
-
will remove the oblast database from the system and it will also
remove the associated datafile.
You have been warned.
- 10.29. dbshow (0)
+ 11.29. dbshow (0)
dbshow <dbname> <key> Display an entry, if it exists, in a database
-
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:
-
-
-
- 10.30. debug (9)
+ 11.30. debug (9)
debug Set the cluster program into debug mode
-
It will interrupt the cluster just after the debug command has
finished.
-
- 10.31. delete/user (9)
+ 11.31. delete/user (9)
delete/user <callsign> Delete a user from the User Database
It goes without saying that you should use this command CAREFULLY!
- 10.32. demonstrate (9)
+ 11.32. demonstrate (9)
demonstrate <call> <command> Demonstrate a command to another user
-
Note that this command is similar to SPOOF and will have the same side
effects. Commands are run at the privilege of the user which is being
demonstrated to.
- 10.33. directory (0)
+ 11.33. directory (0)
directory List messages
directory own List your own messages
-
You can abbreviate all the commands to one letter and use ak1a
syntax:-
-
-
- DIR/T G1* 10
- DIR/S QSL 10-100 5
+ DIR/T G1* 10
+ DIR/S QSL 10-100 5
-
-
-
- 10.34. directory (extended for sysops) (5)
+ 11.34. directory (extended for sysops) (5)
Works just like the user command except that sysops can see ALL
messages.
- 10.35. disconnect (8)
+ 11.35. disconnect (8)
disconnect <call> [<call> ...] Disconnect a user or node
Disconnect any <call> connected locally
- 10.36. dx (0)
+ 11.36. dx (0)
dx [by <call>] <freq> <call> <remarks> Send a DX spot
-
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.
-
You can credit someone else by saying:-
-
The <freq> is compared against the available bands set up in the
cluster. See SHOW/BANDS for more information.
-
- 10.37. export (9)
+ 11.37. export (9)
export <msgno> <filename> Export a message to a file
+
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
EXPORT 2345 /tmp/a
- 10.38. export_users (9)
+ 11.38. export_users (9)
export_users [<filename>] Export the users database to ascii
check is made on the filename (if any) that you specify.
- 10.39. filtering (0)
+ 11.39. filtering (0)
filtering Filtering things in DXSpider
clear/spots 1
-
To remove the filter in its entirty:-
clear/spots all
The next filter line lets through just VHF/UHF spots from EU.
- 10.40. forward/latlong (8)
+ 11.40. forward/latlong (8)
forward/latlong <node_call> Send latitude and longitude information to
another cluster
so it is not recommended on slow links.
- 10.41. forward/opername (1)
+ 11.41. forward/opername (1)
forward/opername <call> Send out information on this <call> to all
clusters
available.
- 10.42. help (0)
+ 11.42. help (0)
help <cmd> Get help on a command
+
All commands can be abbreviated, so SHOW/DX can be abbreviated to
SH/DX, ANNOUNCE can be shortened to AN and so on.
commands to look at with HELP.
- 10.43. init (5)
+ 11.43. init (5)
init <node call> Re-initialise a link to an AK1A compatible node
Best of luck - you will need it.
- 10.44. kill (0)
+ 11.44. kill (0)
kill <msgno> [<msgno> ..] Delete a message from the local system
the sysop).
- 10.45. kill (5)
+ 11.45. 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.
- 10.46. kill full (5)
+ 11.46. kill full (5)
kill full <msgno> [<msgno>] Delete a message from the whole cluster
same subject will be deleted. Beware!
- 10.47. kill/expunge (6)
+ 11.47. kill/expunge (6)
kill/expunge <msgno> [<msgno>..]Expunge a message
message for deletion. The actual deletion only happens later (usually
two days later).
+
The KILL EXPUNGE command causes the message to be truly deleted more
or less immediately.
It otherwise is used in the same way as the KILL command.
- 10.48. links (0)
+
+ 11.48. links (0)
links Show which nodes are physically connected
- 10.49. load/aliases (9)
+ 11.49. load/aliases (9)
load/aliases Reload the command alias table
running in order for the changes to take effect.
- 10.50. load/badmsg (9)
+ 11.50. load/badmsg (9)
load/badmsg Reload the bad message table
deleted on receipt.
- 10.51. load/badwords (9)
+ 11.51. load/badwords (9)
load/badwords Reload the bad words table
ignored.
- 10.52. load/bands (9)
+ 11.52. load/bands (9)
load/bands Reload the band limits table
whilst the cluster is running.
- 10.53. load/cmd_cache (9)
+ 11.53. load/cmd_cache (9)
load/cmd_cache Reload the automatic command cache
-
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.
- 10.54. load/forward (9)
+
+
+ 11.54. load/forward (9)
load/forward Reload the msg forwarding routing table
whilst the cluster is running.
- 10.55. load/messages (9)
+ 11.55. load/messages (9)
load/messages Reload the system messages file
unknown message 'xxxx' in lang 'en'
- 10.56. load/prefixes (9)
+ 11.56. load/prefixes (9)
load/prefixes Reload the prefix table
manually whilst the cluster is running.
- 10.57. merge (5)
+ 11.57. merge (5)
merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
data).
- 10.58. msg (9)
+ 11.58. msg (9)
msg <cmd> <msgno> [data ...] Alter various message parameters
-
-
-
-
-
-
-
-
-
-
MSG TO <msgno> <call> - change TO callsign to <call>
MSG FRom <msgno> <call> - change FROM callsign to <call>
MSG PRrivate <msgno> - set private flag
-
You can look at the status of a message by using:-
STAT/MSG <msgno>
This will display more information on the message than DIR does.
- 10.59. pc (8)
+ 11.59. pc (8)
pc <call> <text> Send text (eg PC Protocol) to <call>
pc G1TLH Try doing that properly!!!
- 10.60. ping (1)
+ 11.60. ping (1)
ping <node> Check the link quality between nodes
- 10.61. rcmd (1)
+ 11.61. rcmd (1)
rcmd <node call> <cmd> Send a command to another DX cluster
whether you have permission to send this command at all.
- 10.62. read (0)
+ 11.62. read (0)
read Read the next unread personal message addressed to you
read <msgno> Read the specified message
- 10.63. read (extended for sysops) (5)
+ 11.63. read (extended for sysops) (5)
read <msgno> Read a message on the system
As a sysop you may read any message on the system
- 10.64. reject/announce
+ 11.64. reject/announce
reject/announce [0-9] <pattern> Set a reject filter for announce
-
some examples:-
-
You can use the tag 'all' to reject everything eg:
-
but this probably for advanced users...
- 10.65. reject/announce (extended for sysops) (8)
+ 11.65. reject/announce (extended for sysops) (8)
reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
version
-
-
- 10.66. reject/route (8)
+ 11.66. reject/route (8)
reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
routing
-
-
some examples:-
-
rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
-
-
You can use the tag 'all' to reject everything eg:
-
-
- 10.67. reject/spots (0)
+ 11.67. reject/spots (0)
reject/spots [0-9] <pattern> Set a reject filter line for spots
-
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 -
-
-
You can use the tag 'all' to reject everything eg:
-
but this probably for advanced users...
- 10.68. reject/spots (extended for sysops) (8)
+ 11.68. reject/spots (extended for sysops) (8)
reject/spots <call> [input] [0-9] <pattern> Reject spot filter sysop
version
-
-
- 10.69. reject/wcy (0)
+ 11.69. reject/wcy (0)
reject/wcy [0-9] <pattern> Set a reject WCY filter
-
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).
- 10.70. reject/wcy (extended for sysops) (8)
+ 11.70. reject/wcy (extended for sysops) (8)
reject/wcy <call> [input] [0-9] <pattern> WCY reject filter sysop
version
reject/wcy gb7djk all
- 10.71. reject/wwv (0)
+ 11.71. reject/wwv (0)
reject/wwv [0-9] <pattern> Set a reject WWV filter
-
for example
-
is probably the only useful thing to do (which will only show WWV
broadcasts by stations in the US).
See HELP FILTER for information.
- 10.72. reject/wwv (extended for sysops) (8)
+ 11.72. reject/wwv (extended for sysops) (8)
reject/wwv <call> [input] [0-9] <pattern> WWV reject filter sysop
version
reject/wwv user_default by W
- 10.73. reply (0)
+ 11.73. reply (0)
reply Reply (privately) to the last message that you have read
reply <msgno> Reply (privately) to the specified message
further details)
- 10.74. send (0)
+ 11.74. 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
-
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.
is an alias for SEND PRIVATE
- 10.75. set/address (0)
+ 11.75. set/address (0)
set/address <your_address> Record your postal address
Literally, record your address details on the cluster.
- 10.76. set/announce (0)
+ 11.76. set/announce (0)
set/announce Allow announce messages
Allow announce messages to arrive at your terminal.
- 10.77. set/arcluster (5)
+ 11.77. 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
- 10.78. set/baddx (8)
+ 11.78. set/baddx (8)
set/baddx <call> Stop words we do not wish to see in the callsign
field of a dx spot being propagated
-
To allow a word again, use the following command ...
-
-
- 10.79. set/badnode (6)
+ 11.79. set/badnode (6)
set/badnode <node_call> Stop spots from this node_call being
propagated
-
will stop anything from K1TTT (including any SSID's)
-
will allow spots from him again.
Use with extreme care. This command may well be superceded by
FILTERing.
- 10.80. set/badspotter (8)
+ 11.80. set/badspotter (8)
set/badspotter <call> Stop spots from this callsign being propagated
-
will stop anything from VE2STN. If you want SSIDs as well then you
must enter them specifically.
-
will allow spots from him again.
Use with extreme care. This command may well be superceded by
FILTERing.
- 10.81. set/badword (8)
+ 11.81. set/badword (8)
set/badword <word> Stop things with this word being propogated
- 10.82. set/beep (0)
+ 11.82. set/beep (0)
set/beep Add beeps to terminal messages
Add a beep to DX and other terminal messages.
- 10.83. set/bbs (5)
+ 11.83. set/bbs (5)
set/bbs <call> [<call>..]Make <call> a BBS
- 10.84. set/clx (5)
+ 11.84. 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
- 10.85. set/debug (9)
+ 11.85. set/debug (9)
set/debug <name> Add a debug level to the debug set
You can remove a debug level with unset/debug <name>
- 10.86. set/dx (0)
+ 11.86. set/dx (0)
set/dxAllow DX messages to arrive at your terminal
You can stop DX messages with the unset/dx command
- 10.87. set/dxgrid (0)
+ 11.87. set/dxgrid (0)
set/dxgridAllow grid squares on the end of DX messages
to remove the grid squares.
- 10.88. set/dxnet (5)
+ 11.88. 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
- 10.89. set/echo (0)
+ 11.89. 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.
- 10.90. set/email (0)
+ 11.90. set/email (0)
set/email <email_address> Set email address(es) and forward your
personals
UNSET/EMAIL
- 10.91. set/here (0)
+ 11.91. set/here (0)
set/here Set the here flag
brackets around your callsign to indicate you are not available.
- 10.92. set/homenode (0)
+ 11.92. set/homenode (0)
set/homenode <node_call> Set your home cluster
-
-
- 10.93. set/hops (8)
+ 11.93. set/hops (8)
set/hops <node_call> ann|spots|wwv|wcy <n> Set hop count
-
Set SHOW/HOPS for information on what is already set. This command
creates a filter and works in conjunction with the filter system.
- 10.94. set/isolate (9)
+ 11.94. 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.
- 10.95. set/language (0)
+ 11.95. set/language (0)
set/language <language> Set the language you wish to use
Currently the languages available are en (English) and nl (Dutch).
- 10.96. set/location (0)
+ 11.96. set/location (0)
set/location <lat and long> Set your latitude and longitude
-
-
-
- 10.97. set/sys_location (9)
+ 11.97. set/sys_location (9)
set/sys_location <lat & long> Set your cluster latitude and longitude
-
-
- 10.98. set/logininfo (0)
+ 11.98. set/logininfo (0)
set/logininfo Show logins and logouts of nodes and users
- 10.99. set/lockout (9)
+ 11.99. set/lockout (9)
set/lockout <call> Stop a callsign connecting to the cluster
allow the user to connect again, use the unset/lockout command.
- 10.100. set/name (0)
+ 11.100. set/name (0)
set/name <your_name> Set your name
-
-
- 10.101. set/node (9)
+ 11.101. set/node (9)
set/node <call> [<call> ...] Make the callsign an AK1A cluster
-
To see what your nodes are set to, use the show/nodes command.
-
-
- 10.102. set/obscount (9)
+ 11.102. set/obscount (9)
set/obscount <count> <node call> Set the 'pump-up' obsolescence
counter
minutes, it is disconnected.
- 10.103. set/page (0)
+ 11.103. set/page (0)
set/page <n> Set the number of lines per page
-
The setting is stored in your user profile.
- 10.104. set/password (0)
+ 11.104. set/password (0)
set/password Set your own password
type, depending on the type of telnet client you have.
- 10.105. set/password (9)
+ 11.105. set/password (9)
set/password <callsign> <string> Set a users password
password.
- 10.106. set/pinginterval (9)
+ 11.106. set/pinginterval (9)
set/pinginterval <time> <node call> Set the ping time to neighbouring
nodes
for more information.
- 10.107. set/privilege (9)
+ 11.107. set/privilege (9)
set/privilege <n> <call> [<call> ...] Set the privilege level on a
call
-
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.
-
-
- 10.108. set/spider (5)
+ 11.108. 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
- 10.109. set/sys_qra (9)
+ 11.109. set/sys_qra (9)
set/sys_qra <locator> Set your cluster QRA locator
- 10.110. set/qra (0)
+ 11.110. set/qra (0)
set/qra <locator> Set your QRA locator
-
-
- 10.111. set/qth (0)
+ 11.111. set/qth (0)
set/qth <your QTH> Set your QTH
-
-
- 10.112. set/register (9)
+ 11.112. set/register (9)
set/register <call> Mark a user as registered
To unset a user use the 'unset/register' command
- 10.113. set/talk (0)
+ 11.113. set/talk (0)
set/talk Allow talk messages to be seen at your console
talks with the unset/talk command.
- 10.114. set/wcy (0)
+ 11.114. set/wcy (0)
set/wcy Allow WCY messages to be seen at your console
WCY messages with the unset/wcy command.
- 10.115. set/wwv (0)
+ 11.115. set/wwv (0)
set/wwv Allow WWV messages to be seen at your console
WWV messages with the unset/wwv command.
- 10.116. set/wx (0)
+ 11.116. set/wx (0)
set/wx Allow WX messages to be seen at your console
WX messages with the unset/wx command.
- 10.117. show/baddx (1)
+ 11.117. show/baddx (1)
show/baddxShow all the bad dx calls in the system
information.
- 10.118. show/badnode (6)
+ 11.118. show/badnode (6)
show/badnode Show all the bad nodes in the system
more information.
- 10.119. show/badspotter (1)
+ 11.119. show/badspotter (1)
show/badspotter Show all the bad spotters in the system
SET/BADSPOTTER for more information.
- 10.120. show/badword (1)
+ 11.120. show/badword (1)
show/badword Show all the bad words in the system
information.
- 10.121. show/configuration (0)
+ 11.121. show/configuration (0)
show/configuration [<node>] Show all visible nodes and their users
BE WARNED: the list that is returned can be VERY long
- 10.122. show/configuration/node (0)
+ 11.122. show/configuration/node (0)
show/configuration/node Show all the nodes connected
connected.
- 10.123. show/connect (1)
+ 11.123. show/connect (1)
show/connect Show all the active connections
the node. This command gives slightly more information than WHO.
- 10.124. show/date (0)
+ 11.124. show/date (0)
show/date [<prefix>|<callsign>] Show the local time
including DST) at the prefixes or callsigns that you specify.
- 10.125. show/debug (9)
+ 11.125. show/debug (9)
show/debug Show what levels of debug you are logging
-
-
- 10.126. show/dx (0)
+ 11.126. show/dx (0)
show/dx [options] interrogate the spot database
-
on <band> - eg 160m 20m 2m 23cm 6mm
on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
-
e.g.
-
SH/DX 9m0
SH/DX on 20m info iota
SH/DX 9a on vhf day 30
-
-
-
-
- 10.127. show/dxcc (0)
+ 11.127. show/dxcc (0)
show/dxcc <prefix> Interrogate the spot database by country
-
SH/DXCC G
SH/DXCC W on 20m info iota
-
-
- 10.128. sh/dxstats (0)
+ 11.128. sh/dxstats (0)
sh/dxstats Show the DX Statistics for last 31 days
- 10.129. show/files (0)
+ 11.129. show/files (0)
show/files [<filearea> [<string>]] List the contents of a filearea
-
where <filearea> is the name of the filearea you want to see the
contents of.
-
See also TYPE - to see the contents of a file.
- 10.130. show/filter (0)
+ 11.130. show/filter (0)
show/filter Show the filters you have set
displays all the filters set - for all the various categories.
- 10.131. show/filter (extended for sysops) (5)
+ 11.131. 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.
- 10.132. show/hfstats (0)
+ 11.132. show/hfstats (0)
show/hfstats Show the HF DX Statistics for last 31 days
Show the HF DX spots breakdown by band for the last 31 days
- 10.133. show/hftable (0)
+ 11.133. show/hftable (0)
show/hftable Show the HF DX Spotter Table for your country
Show the HF DX Spotter table for your country for the last 31 days
- 10.134. show/hops (8)
+ 11.134. show/hops (8)
show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a
node
the categories will be listed.
- 10.135. show/isolate (1)
+ 11.135. show/isolate (1)
show/isolate Show a list of isolated nodes
Show which nodes are currently set to be isolated.
- 10.136. show/lockout (9)
+ 11.136. show/lockout (9)
show/lockout Show a list of excluded callsigns
cluster locally with the set/lockout command
- 10.137. show/log (8)
+ 11.137. show/log (8)
show/log [<callsign>] Show excerpts from the system log
show output from the log associated with that callsign.
- 10.138. show/moon (0)
+ 11.138. show/moon (0)
show/moon [<prefix>|<callsign>] Show moon rise and set times
-
-
- 10.139. show/muf (0)
+ 11.139. show/muf (0)
show/muf <prefix> [<hours>][long] Show the likely propagation to
<prefix>
-
produces:
-
indicating that you will have weak, fading circuits on top band and
80m but usable signals on 40m (about S3).
-
will get you the above display, but with the next 24 hours worth of
propagation data.
-
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.
- 10.140. show/newconfiguration (0)
+ 11.140. show/newconfiguration (0)
show/newconfiguration [<node>] Show all the nodes and users visible
BE WARNED: the list that is returned can be VERY long
- 10.141. show/newconfiguration/node (0)
+ 11.141. show/newconfiguration/node (0)
show/newconfiguration/node Show all the nodes connected locally
Show all the nodes connected to this node in the new format.
- 10.142. show/node (1)
+ 11.142. 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.
- 10.143. show/prefix (0)
+ 11.143. show/prefix (0)
show/prefix <callsign> Interrogate the prefix database
- 10.144. show/program (5)
+ 11.144. show/program (5)
show/program Show the locations of all the included program modules
from.
- 10.145. show/qra (0)
+ 11.145. show/qra (0)
show/qra <locator> [<locator>] Show the distance between locators
show/qra <lat> <long> Convert latitude and longitude to a locator
-
-
- 10.146. show/qrz (0)
+ 11.146. show/qrz (0)
show/qrz <callsign> Show any callbook details on a callsign
provided for users of this software by http://www.qrz.com
- 10.147. show/registered (9)
+ 11.147. show/registered (9)
show/registered [<prefix>[ Show the registered users
- 10.148. show/route (0)
+ 11.148. show/route (0)
show/route <callsign> Show the route to <callsign>
-
-
- 10.149. show/satellite (0)
+ 11.149. show/satellite (0)
show/satellite <name> [<hours> <interval>] Show satellite tracking
data
-
-
- 10.150. show/sun (0)
+ 11.150. show/sun (0)
show/sun [<prefix>|<callsign>] Show sun rise and set times
-
-
- 10.151. show/time (0)
+ 11.151. show/time (0)
show/time [<prefix>|<callsign>] Show the local time
including DST) at the prefixes or callsigns that you specify.
- 10.152. show/vhfstats (0)
+ 11.152. show/vhfstats (0)
show/vhfstats Show the VHF DX Statistics for last 31 days
Show the VHF DX spots breakdown by band for the last 31 days
- 10.153. show/vhftable (0)
+ 11.153. show/vhftable (0)
show/vhftable Show the VHF DX Spotter Table for your country
Show the VHF DX Spotter table for your country for the last 31 days
- 10.154. show/wcy (0)
+ 11.154. show/wcy (0)
show/wcy Show the last 10 WCY broadcasts
show/wcy <n> Show the last <n> WCY broadcasts
system
- 10.155. show/wwv (0)
+ 11.155. show/wwv (0)
show/wwv Show the last 10 WWV broadcasts
show/wwv <n> Show the last <n> WWV broadcasts
- 10.156. shutdown (5)
+ 11.156. shutdown (5)
shutdown Shutdown the cluster
set to respawn in /etc/inittab it will of course restart.
- 10.157. spoof (9)
+ 11.157. spoof (9)
spoof <callsign> <command> Run commands as another user
like home_node for example.
- 10.158. stat/db (5)
+ 11.158. stat/db (5)
stat/db <dbname> Show the status of a database
other than a sysop.
- 10.159. stat/channel (5)
+ 11.159. 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.
- 10.160. stat/msg (5)
+ 11.160. stat/msg (5)
stat/msg <msgno> Show the status of a message
displayed.
- 10.161. stat/route_node (5)
+ 11.161. stat/route_node (5)
stat/route_node <callsign> Show the data in a Route::Node object
- 10.162. stat/route_user (5)
+ 11.162. stat/route_user (5)
stat/route_user <callsign> Show the data in a Route::User object
- 10.163. stat/user (5)
+ 11.163. 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.
- 10.164. sysop (0)
+ 11.164. sysop (0)
sysop Regain your privileges if you login remotely
-
you type:-
-
aa2bbbb0ccc5ddd7xxx3n
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.
- 10.165. talk (0)
+ 11.165. talk (0)
talk <callsign> Enter talk mode with <callsign>
talk <callsign> <text> Send a text message to <callsign>
-
To leave talk mode type:
-
-
-
-
-
- 10.166. type (0)
+ 11.166. type (0)
type <filearea>/<name> Look at a file in one of the fileareas
-
See also SHOW/FILES to see what fileareas are available and a list of
content.
- 10.167. who (0)
+ 11.167. who (0)
who Show who is physically connected locally
what sort of connection they have
- 10.168. wx (0)
+ 11.168. 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
- 10.169. wx (enhanced for sysops) (5)
+ 11.169. wx (enhanced for sysops) (5)
wx sysop <text> Send a weather message to other clusters only
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
projects / spider.git / blobdiff