The DXSpider Installation and Administration Manual
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.33 February 2001
+ Version 1.34 (Revision 1.01) April 2001
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
- 1. Installation (Original version by Iain Phillips, G0RDI)
+ 1. Installation (Original version by Iain Philipps, G0RDI)
1.1 Introduction
1.2 Preparation
1.3 Installing the software
1.4 Setting callsigns etc
1.5 Starting up for the first time
+ 1.6 The Client program
- 2. The Client program
+ 2. Quick installation guide
3. Configuration
13.101 show/badnode (6)
13.102 show/badspotter (1)
13.103 show/date (0)
- 13.104 show/dx (0)
- 13.105 show/dxcc (0)
- 13.106 show/files (0)
- 13.107 show/filter (0)
- 13.108 show/filter (extended for sysops) (5)
- 13.109 show/hops (8)
- 13.110 show/isolate (1)
- 13.111 show/lockout (9)
- 13.112 show/log (8)
- 13.113 show/moon (0)
- 13.114 show/muf (0)
- 13.115 show/node (1)
- 13.116 show/prefix (0)
- 13.117 show/program (5)
- 13.118 show/qra (0)
- 13.119 show/qrz (0)
- 13.120 show/route (0)
- 13.121 show/satellite (0)
- 13.122 show/sun (0)
- 13.123 show/time (0)
- 13.124 show/wcy (0)
- 13.125 show/wwv (0)
- 13.126 shutdown (5)
- 13.127 spoof (9)
- 13.128 stat/db (5)
- 13.129 stat/channel (5)
- 13.130 stat/msg (5)
- 13.131 stat/user (5)
- 13.132 sysop (0)
- 13.133 talk (0)
- 13.134 type (0)
- 13.135 who (0)
- 13.136 wx (0)
- 13.137 wx (enhanced for sysops) (5)
+ 13.104 show/debug (9)
+ 13.105 show/dx (0)
+ 13.106 show/dxcc (0)
+ 13.107 show/files (0)
+ 13.108 show/filter (0)
+ 13.109 show/filter (extended for sysops) (5)
+ 13.110 show/hops (8)
+ 13.111 show/isolate (1)
+ 13.112 show/lockout (9)
+ 13.113 show/log (8)
+ 13.114 show/moon (0)
+ 13.115 show/muf (0)
+ 13.116 show/node (1)
+ 13.117 show/prefix (0)
+ 13.118 show/program (5)
+ 13.119 show/qra (0)
+ 13.120 show/qrz (0)
+ 13.121 show/route (0)
+ 13.122 show/satellite (0)
+ 13.123 show/sun (0)
+ 13.124 show/time (0)
+ 13.125 show/wcy (0)
+ 13.126 show/wwv (0)
+ 13.127 shutdown (5)
+ 13.128 spoof (9)
+ 13.129 stat/db (5)
+ 13.130 stat/channel (5)
+ 13.131 stat/msg (5)
+ 13.132 stat/user (5)
+ 13.133 sysop (0)
+ 13.134 talk (0)
+ 13.135 type (0)
+ 13.136 who (0)
+ 13.137 wx (0)
+ 13.138 wx (enhanced for sysops) (5)
______________________________________________________________________
- 1\b1.\b. I\bIn\bns\bst\bta\bal\bll\bla\bat\bti\bio\bon\bn (\b(O\bOr\bri\big\bgi\bin\bna\bal\bl v\bve\ber\brs\bsi\bio\bon\bn b\bby\by I\bIa\bai\bin\bn P\bPh\bhi\bil\bll\bli\bip\bps\bs,\b, G\bG0\b0R\bRD\bDI\bI)\b)
+ 1\b1.\b. I\bIn\bns\bst\bta\bal\bll\bla\bat\bti\bio\bon\bn (\b(O\bOr\bri\big\bgi\bin\bna\bal\bl v\bve\ber\brs\bsi\bio\bon\bn b\bby\by I\bIa\bai\bin\bn P\bPh\bhi\bil\bli\bip\bpp\bps\bs,\b, G\bG0\b0R\bRD\bDI\bI)\b)
1\b1.\b.1\b1.\b. I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
- This section describes the installation of DX Spider v1.35 on a RedHat
- Linux Distribution. I do not intend to try and cover the installation
- of Linux or the setup of the AX25 utilities. If you need help on this
- then read Iains original HOWTO on the DXSpider website.
+ This section describes the installation of DX Spider v1.46 on a RedHat
+ Linux Distribution. Wherever possible I will try to include
+ differences for other distributions. I do not intend to try and cover
+ the installation of Linux or the setup of the AX25 utilities. If you
+ need help on this then read Iains original installation guide that
+ comes with the Spider distribution.
I am assuming a general knowledge of Linux and its commands. You
editor.
- The crucial ingredient for all of this is Perl 5.004. Now I know Perl
- 5.005 is out and this will almost certainly work with it, but RedHat
- 5.1 comes with 5.004. _\bB_\be _\bW_\ba_\br_\bn_\be_\bd, earlier versions of RedHat d\bdo\bo n\bno\bot\bt
- come with 5.004 as standard, you need to upgrade
+ The crucial ingredient for all of this is Perl. Earlier versions of
+ Spider required perl 5.004, however it is now _\bS_\bT_\bR_\bO_\bN_\bG_\bL_\bY recommended
+ that you use at least version 5.005_03 as this is the version being
+ used in the development of Spider.
In addition to the standard Red Hat distribution you will require the
- following CPAN modules: -
+ following modules from http://www.cpan.org/CPAN.html ...
+\bo Data-Dumper-2.10.tar.gz
- +\bo FreezeThaw-0.3.tar.gz
-
- +\bo MLDBM-2.00.tar.gz
-
+\bo TimeDate-1.08.tar.gz
+\bo IO-1.20.tar.gz
I will assume that you have already downloaded the latest tarball of
the DXSpider software and are ready to install it. I am assuming
- version 1.35 for this section but of course you would use the latest
+ version 1.46 for this section but of course you would use the latest
version.
# cd ~sysop
- # tar xvfz spider-1.35.tar.gz
+ # tar xvfz spider-1.46.tar.gz
# ln -s ~sysop/spider /spider
# groupadd -g 251 spider (or another number)
P\bPL\bLE\bEA\bAS\bSE\bE U\bUS\bSE\bE C\bCA\bAP\bPI\bIT\bTA\bAL\bL L\bLE\bET\bTT\bTE\bER\bRS\bS F\bFO\bOR\bR C\bCA\bAL\bLL\bLS\bSI\bIG\bGN\bNS\bS
- DON'T alter the DXVars.pm (or any other file) in /spider/perl, they
- are overwritten with every release. Any files or commands you place in
- /spider/local or /spider/local_cmd will automagically be used in
- preference to the ones in /spider/perl EVEN while the cluster is
- running!
+ DON'T alter any file in /spider/perl, they are overwritten with every
+ release. Any files or commands you place in /spider/local or
+ /spider/local_cmd will automagically be used in preference to the ones
+ in /spider/perl EVEN while the cluster is running!
Save the new file and change directory to ../perl ....
- $ create_sysop.pl
+ $ ./create_sysop.pl
- $ cluster.pl
- DXSpider DX Cluster Version 1.35
+ $ ./cluster.pl
+ DXSpider DX Cluster Version 1.46
Copyright (c) 1998 Dirk Koopman G1TLH
loading prefixes ...
loading band data ...
If all is well then login on another term or console as _\bs_\by_\bs_\bo_\bp and cd
- to /spider/perl. Now issue the following command ...
- $ client.pl
+ to /spider/src. Now issue the following command ...
+
+ $ ./client
and both the cluster and the client should return to Linux prompts.
- 2\b2.\b. T\bTh\bhe\be C\bCl\bli\bie\ben\bnt\bt p\bpr\bro\bog\bgr\bra\bam\bm
+ 1\b1.\b.6\b6.\b. T\bTh\bhe\be C\bCl\bli\bie\ben\bnt\bt p\bpr\bro\bog\bgr\bra\bam\bm
In earlier versions of Spider, all the processes were Perl scripts.
This was fine but with a lot of users your computer memory would soon
small C program called _\bc_\bl_\bi_\be_\bn_\bt. Leave it in this directory.
+
+ 2\b2.\b. Q\bQu\bui\bic\bck\bk i\bin\bns\bst\bta\bal\bll\bla\bat\bti\bio\bon\bn g\bgu\bui\bid\bde\be
+
+ This section is designed for experienced Spider sysops who want to
+ install Spider from scratch. It is simply a check list of things that
+ need to be done without any explanations. The name in brackets at the
+ end of each line is the user that should be doing that process.
+
+
+ +\bo Login as root
+
+ +\bo Get the additional CPAN modules and install them (root)
+
+ +\bo Create the "sysop" user and set a password (root)
+
+ +\bo Put the Spider tarball in sysop and untar it (root)
+
+ +\bo ln -s sysop/spider /spider (root)
+
+ +\bo groupadd -g 251 spider (root)
+
+ +\bo Add any more users you need to the group entry in /etc/group (root)
+
+ +\bo Set the permissions on the spider tree (root)
+
+ +\bo Fix permissions on ax25_call and netrom_call (root)
+
+ +\bo Login as the sysop user
+
+ +\bo cd to /spider (sysop)
+
+ +\bo mkdir local (sysop)
+
+ +\bo mkdir local_cmd (sysop)
+
+ +\bo cp perl/DXVars.pm.issue local/DXVars.pm (sysop)
+
+ +\bo cd to /spider/local and edit DXVars to set your details (sysop)
+
+ +\bo cd ../perl (sysop)
+
+ +\bo ./create_sysop.pl (sysop)
+
+ +\bo ./cluster.pl (sysop)
+
+ Spider should now be running and you should be able to login using the
+ client program.
+
+
+ +\bo Login as root
+
+ +\bo Enter the correct line in ax25d.conf (root)
+
+ +\bo Enter the correct line in /etc/services (root)
+
+ +\bo Enter the correct line in /etc/inetd.conf (root)
+
+ +\bo killall -HUP inetd (root)
+
+ Spider should now be able to accept logins via telnet, netrom and
+ ax25.
+
+
+ +\bo Login as sysop
+
+ +\bo Start the cluster (sysop)
+
+ +\bo set/node and type for links (sysop)
+
+ +\bo Write any connect scripts (sysop)
+
+ +\bo Edit /spider/crontab as required (sysop)
+
+ +\bo Edit any other files as necessary (sysop)
+
+ +\bo Set filters, hops and forwarding files (sysop)
+
+ +\bo Login as root
+
+ +\bo Enter the correct line in /etc/inittab (root)
+
+
3\b3.\b. C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+
+
+
3\b3.\b.1\b1.\b. A\bAl\bll\blo\bow\bwi\bin\bng\bg a\bax\bx2\b25\b5 c\bco\bon\bnn\bne\bec\bct\bts\bs f\bfr\bro\bom\bm u\bus\bse\ber\brs\bs
As stated previously, the aim of this document is not to tell you how
+ or, if you wish your users to be able to use SSID's on their callsigns
+ ..
+
+
+
+ default * * * * * * - sysop /spider/src/client client %s ax25
+
- Now login as _\bs_\by_\bs_\bo_\bp and cd spider/perl. You can test that spider is
+ Now login as _\bs_\by_\bs_\bo_\bp and cd spider/src. You can test that spider is
accepting telnet logins by issuing the following command ....
- client.pl login telnet
+ ./client login telnet
You should now get the login prompt and be able to login as before.
-
-
3\b3.\b.3\b3.\b. S\bSe\bet\btt\bti\bin\bng\bg u\bup\bp n\bno\bod\bde\be c\bco\bon\bnn\bne\bec\bct\bts\bs
In order to allow cluster node connections, spider needs to know that
Start up the cluster as you did before and login as the sysop with
- client.pl. The cluster node I am wanting to make a connection to is
+ client. The cluster node I am wanting to make a connection to is
GB7BAA but you would obviously use whatever callsign you required. At
the prompt type ...
-
The case does not matter as long as you have a version of DXSpider
later than 1.33. Earlier versions required the callsign to be in
upper case.
That is now set, it is as simple as that. To prove it, login on yet
- another console as sysop and issue the command ...
+ another console as sysop, cd to spider/src and issue the command ...
- client.pl gb7baa (using the callsign you set as a node)
+ ./client gb7baa (using the callsign you set as a node)
- client.pl gb7baa
+ ./client gb7baa
PC38^GB7MBC^~
+
+
+
If the callsign you just set up as a cluster node is for an incoming
connect, this is all that needs to be done. If the connection is to
be outgoing then a connection script needs to be written.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
# All lines starting with a # are ignored, as are completely
blank lines.
-
-
- timeout 60
- abort (Busy|Sorry|Fail)
- # don't forget to chmod 4775 netrom_call!
- connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
- # you can leave this out if you call the script 'gb7dxm'
- client gb7dxm ax25
+ timeout 60
+ abort (Busy|Sorry|Fail)
+ # don't forget to chmod 4775 netrom_call!
+ connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
+ # you can leave this out if you call the script 'gb7dxm'
+ client gb7dxm ax25
client gb7djk telnet
-
-
-
Both these examples assume that everything is set up properly at the
other end. You will find other examples in the /spider/examples
directory.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <- D G1TLH connect gb7djk-1
- -> D G1TLH connection to GB7DJK-1 started
- -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
- timeout set to 15
- CONNECT sort: telnet command: dirkl.tobit.co.uk
- CHAT "login" -> "gb7djk"
- received "
- Red Hat Linux release 5.1 (Manhattan)
- Kernel 2.0.35 on an i586
- "
- received "login: "
- sent "gb7djk"
- CHAT "word" -> "gb7djk"
- received "gb7djk"
- received "Password: "
- sent "gb7djk"
- Connected to GB7DJK-1, starting normal protocol
- <- O GB7DJK-1 telnet
- -> B GB7DJK-1 0
- GB7DJK-1 channel func state 0 -> init
- <- D GB7DJK-1
- <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1
- <- D GB7DJK-1 PC38^GB7DJK-1^~
- <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime
- 0 00:00^5447^~
- etc
+ <- D G1TLH connect gb7djk-1
+ -> D G1TLH connection to GB7DJK-1 started
+ -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
+ timeout set to 15
+ CONNECT sort: telnet command: dirkl.tobit.co.uk
+ CHAT "login" -> "gb7djk"
+ received "
+ Red Hat Linux release 5.1 (Manhattan)
+ Kernel 2.0.35 on an i586
+ "
+ received "login: "
+ sent "gb7djk"
+ CHAT "word" -> "gb7djk"
+ received "gb7djk"
+ received "Password: "
+ sent "gb7djk"
+ Connected to GB7DJK-1, starting normal protocol
+ <- O GB7DJK-1 telnet
+ -> B GB7DJK-1 0
+ GB7DJK-1 channel func state 0 -> init
+ <- D GB7DJK-1
+ <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1
+ <- D GB7DJK-1 PC38^GB7DJK-1^~
+ <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime
+ 0 00:00^5447^~
+ etc
avoid this use the following line ...
-
-
-
-
-
-
In a script, this might look like ...
+
+ This line works fine for RedHat distributions. It is also fine for
+ SuSE up to 7.0. From Suse 7.1 you need to add runlevels 2 and 5 like
+ this ...
+
+
+
+ DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
+
+
+
+
+
+ The line required for Slackware distributions is slightly different.
+ My thanks to Aurelio, PA3EZL for this information.
+
+
+
+ DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7
+
+
+
+
+
This will automatically start DXSpider on tty7 (ALT-F7) on bootup and
restart it should it crash for any reason.
- # check every 10 minutes to see if gb7xxx is connected and if not
- # start a connect job going
- 0,10,20,30,40,50 * * * * start_connect('gb7xxx') if !connected('gb7xxx')
+
+
+ # check every 10 minutes to see if gb7xxx is connected and if not
+ # start a connect job going
+
+ 0,10,20,30,40,50 * * * * start_connect('gb7xxx') if !connected('gb7xxx')
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
#
# hop table construction
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 _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn_\bs. Now copy any OPDX or similar
+ /spider/packclus called _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn. Now copy any OPDX or similar
bulletins into it. These can be listed by the user in the same way as
- above using the _\bs_\bh_\bo_\bw_\b/_\bf_\bi_\bl_\be_\bs command with an extension for the bulletins
+ above using the _\bs_\bh_\bo_\bw_\b/_\bf_\bi_\bl_\be_\bs command with an extension for the bulletin
directory you have just created, like this ....
- show/files bulletins
+ show/files bulletin
sh/files
- bulletins DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
+ bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
You can see that in the files area (basically the packclus directory)
- there is a file called _\bn_\be_\bw_\bs and a directory called _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn_\bs. You can
+ there is a file called _\bn_\be_\bw_\bs and a directory called _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn. You can
also see that dates they were created. In the case of the file _\bn_\be_\bw_\bs,
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
- To look what is in the bulletins directory you issue the command ....
+ To look what is in the bulletin directory you issue the command ....
- show/files bulletins
+ show/files bulletin
opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
- type bulletins/opdx391
+ type bulletin/opdx391
Ohio/Penn DX Bulletin No. 391
The Ohio/Penn Dx PacketCluster
DX Bulletin No. 391
In later versions of Spider a simple console program is provided for
the sysop. This has a type ahead buffer with line editing facilities
and colour for spots, announces etc. To use this program, simply use
- console.pl instead of client.pl.
+ console.pl instead of client.
To edit the colours, copy /spider/perl/Console.pl to /spider/local and
s\bse\bet\bt/\b/d\bde\beb\bbu\bug\bg <\b<n\bna\bam\bme\be>\b> Add a debug level to the debug set
- You can remove this level with unset/debug <name>
+ You can choose to log several different levels. The levels are
+
+ chan state msg cron connect
+
+ You can show what levels you are logging with the _\bs_\bh_\bo_\bw_\b/_\bd_\be_\bb_\bu_\bg command.
+
+ You can remove a debug level with unset/debug <name>
1\b13\b3.\b.7\b72\b2.\b. s\bse\bet\bt/\b/d\bdx\bx (\b(0\b0)\b)
You can stop DX messages with the _\bu_\bn_\bs_\be_\bt_\b/_\bd_\bx command
+
+
1\b13\b3.\b.7\b73\b3.\b. s\bse\bet\bt/\b/d\bdx\bxg\bgr\bri\bid\bd (\b(0\b0)\b)
s\bse\bet\bt/\b/d\bdx\bxg\bgr\bri\bid\bdAllow grid squares on the end of DX messages
Some logging programs do not like the additional information at the
end of a DX spot. If this is the case, use the _\bu_\bn_\bs_\be_\bt_\b/_\bd_\bx_\bg_\br_\bi_\bd command
to remove the grid squares.
+
+
1\b13\b3.\b.7\b74\b4.\b. s\bse\bet\bt/\b/d\bdx\bxn\bne\bet\bt (\b(5\b5)\b)
s\bse\bet\bt/\b/d\bdx\bxn\bne\bet\bt <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> [\b[<\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Make the node_call a DXNet
+
+
1\b13\b3.\b.7\b78\b8.\b. s\bse\bet\bt/\b/h\bho\bop\bps\bs (\b(8\b8)\b)
s\bse\bet\bt/\b/h\bho\bop\bps\bs <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> a\ban\bnn\bn|\b|s\bsp\bpo\bot\bts\bs|\b|w\bww\bwv\bv|\b|w\bwc\bcy\by <\b<n\bn>\b> Set hop count
- eg:
- set/hops gb7djk ann 10
- set/hops gb7mbc spots 20
+ eg:
+ set/hops gb7djk ann 10
+ set/hops gb7mbc spots 20
-
1\b13\b3.\b.8\b82\b2.\b. s\bse\bet\bt/\b/s\bsy\bys\bs_\b_l\blo\boc\bca\bat\bti\bio\bon\bn (\b(9\b9)\b)
s\bse\bet\bt/\b/s\bsy\bys\bs_\b_l\blo\boc\bca\bat\bti\bio\bon\bn <\b<l\bla\bat\bt &\b& l\blo\bon\bng\bg>\b> Set your cluster latitude and longitude
example:-
+
SET/LOCATION 52 22 N 0 57 E
- set/spider
- set/dxnet
- set/clx
- set/arcluster
-
+ set/spider
+ set/dxnet
+ set/clx
+ set/arcluster
- To see what your nodes are set to, use the _\bs_\bh_\bo_\bw_\b/_\bn_\bo_\bd_\be_\bs command.
+ To see what your nodes are set to, use the _\bs_\bh_\bo_\bw_\b/_\bn_\bo_\bd_\be_\bs command.
1\b13\b3.\b.8\b87\b7.\b. s\bse\bet\bt/\b/o\bob\bbs\bsc\bco\bou\bun\bnt\bt (\b(9\b9)\b)
type password.
+
1\b13\b3.\b.9\b90\b0.\b. s\bse\bet\bt/\b/p\bpi\bin\bng\bgi\bin\bnt\bte\ber\brv\bva\bal\bl (\b(9\b9)\b)
s\bse\bet\bt/\b/p\bpi\bin\bng\bgi\bin\bnt\bte\ber\brv\bva\bal\bl <\b<t\bti\bim\bme\be>\b> <\b<n\bno\bod\bde\be c\bca\bal\bll\bl>\b> Set the ping time to neighbouring
in future, to affect routing decisions. The default interval is 300
secs or 5 minutes.
-
You can use this command to set a different interval. Please don't.
But if you do the value you enter is treated as minutes up 60 and
+
1\b13\b3.\b.9\b95\b5.\b. s\bse\bet\bt/\b/q\bqt\bth\bh (\b(0\b0)\b)
s\bse\bet\bt/\b/q\bqt\bth\bh <\b<y\byo\bou\bur\br Q\bQT\bTH\bH>\b> Set your QTH
WX messages with the _\bu_\bn_\bs_\be_\bt_\b/_\bw_\bx command.
+
+
+
1\b13\b3.\b.1\b10\b00\b0.\b. s\bsh\bho\bow\bw/\b/b\bba\bad\bdd\bdx\bx (\b(1\b1)\b)
s\bsh\bho\bow\bw/\b/b\bba\bad\bdd\bdx\bxShow all the bad dx calls in the system
s\bsh\bho\bow\bw/\b/b\bba\bad\bdn\bno\bod\bde\be Show all the bad nodes in the system
-
Display all the bad node callsigns in the system, see SET/BADNODE for
more information.
1\b13\b3.\b.1\b10\b02\b2.\b. s\bsh\bho\bow\bw/\b/b\bba\bad\bds\bsp\bpo\bot\btt\bte\ber\br (\b(1\b1)\b)
- s\bsh\bho\bow\bw/\b/b\bba\bad\bds\bsp\bpo\bot\btt\bte\ber\brShow all the bad spotters in the system
+ s\bsh\bho\bow\bw/\b/b\bba\bad\bds\bsp\bpo\bot\btt\bte\ber\br Show all the bad spotters in the system
Display all the bad spotter's callsigns in the system, see
including DST) at the prefixes or callsigns that you specify.
- 1\b13\b3.\b.1\b10\b04\b4.\b. s\bsh\bho\bow\bw/\b/d\bdx\bx (\b(0\b0)\b)
-
- s\bsh\bho\bow\bw/\b/d\bdx\bx [\b[o\bop\bpt\bti\bio\bon\bns\bs]\b] interrogate the spot database
-
-
- If you just type SHOW/DX you will get the last so many spots (sysop
- configurable, but usually 10).
-
- In addition you can add any number of these options in very nearly any
- order to the basic SHOW/DX command, they are:-
-
-
-
-
-
-
-
-
-
-
-
-
-
+ 1\b13\b3.\b.1\b10\b04\b4.\b. s\bsh\bho\bow\bw/\b/d\bde\beb\bbu\bug\bg (\b(9\b9)\b)
+ s\bsh\bho\bow\bw/\b/d\bde\beb\bbu\bug\bg Show what levels of debug you are logging
+ The levels can be set with _\bs_\be_\bt_\b/_\bd_\be_\bb_\bu_\bg
+ 1\b13\b3.\b.1\b10\b05\b5.\b. s\bsh\bho\bow\bw/\b/d\bdx\bx (\b(0\b0)\b)
+ s\bsh\bho\bow\bw/\b/d\bdx\bx [\b[o\bop\bpt\bti\bio\bon\bns\bs]\b] interrogate the spot database
+ If you just type SHOW/DX you will get the last so many spots (sysop
+ configurable, but usually 10).
+ In addition you can add any number of these options in very nearly any
+ order to the basic SHOW/DX command, they are:-
- 1\b13\b3.\b.1\b10\b05\b5.\b. s\bsh\bho\bow\bw/\b/d\bdx\bxc\bcc\bc (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b10\b06\b6.\b. s\bsh\bho\bow\bw/\b/d\bdx\bxc\bcc\bc (\b(0\b0)\b)
s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bxc
\bcc
\bc <
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b> Interrogate the spot database by country
- 1\b13\b3.\b.1\b10\b06\b6.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\ble\bes\bs (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b10\b07\b7.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\ble\bes\bs (\b(0\b0)\b)
s\bsh\bho\bow\bw/\b/f\bfi\bil\ble\bes\bs [\b[<\b<f\bfi\bil\ble\bea\bar\bre\bea\ba>\b> [\b[<\b<s\bst\btr\bri\bin\bng\bg>\b>]\b]]\b] List the contents of a filearea
See also TYPE - to see the contents of a file.
- 1\b13\b3.\b.1\b10\b07\b7.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b10\b08\b8.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br (\b(0\b0)\b)
s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br Show the filters you have set
displays all the filters set - for all the various categories.
- 1\b13\b3.\b.1\b10\b08\b8.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(5\b5)\b)
+ 1\b13\b3.\b.1\b10\b09\b9.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(5\b5)\b)
s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Show the filters set by <callsign>
A sysop can look at any filters that have been set.
- 1\b13\b3.\b.1\b10\b09\b9.\b. s\bsh\bho\bow\bw/\b/h\bho\bop\bps\bs (\b(8\b8)\b)
+ 1\b13\b3.\b.1\b11\b10\b0.\b. s\bsh\bho\bow\bw/\b/h\bho\bop\bps\bs (\b(8\b8)\b)
s\bsh\bho\bow\bw/\b/h\bho\bop\bps\bs <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> [\b[a\ban\bnn\bn|\b|s\bsp\bpo\bot\bts\bs|\b|w\bwc\bcy\by|\b|w\bww\bwv\bv|\b|]\b] Show the hop counts for a
node
which category you want to see. If you leave the category out then all
the categories will be listed.
- 1\b13\b3.\b.1\b11\b10\b0.\b. s\bsh\bho\bow\bw/\b/i\bis\bso\bol\bla\bat\bte\be (\b(1\b1)\b)
+ 1\b13\b3.\b.1\b11\b11\b1.\b. s\bsh\bho\bow\bw/\b/i\bis\bso\bol\bla\bat\bte\be (\b(1\b1)\b)
s\bsh\bho\bow\bw/\b/i\bis\bso\bol\bla\bat\bte\be Show a list of isolated nodes
Show which nodes are currently set to be isolated.
- 1\b13\b3.\b.1\b11\b11\b1.\b. s\bsh\bho\bow\bw/\b/l\blo\boc\bck\bko\bou\but\bt (\b(9\b9)\b)
+ 1\b13\b3.\b.1\b11\b12\b2.\b. s\bsh\bho\bow\bw/\b/l\blo\boc\bck\bko\bou\but\bt (\b(9\b9)\b)
s\bsh\bho\bow\bw/\b/l\blo\boc\bck\bko\bou\but\bt Show a list of excluded callsigns
cluster locally with the _\bs_\be_\bt_\b/_\bl_\bo_\bc_\bk_\bo_\bu_\bt command
- 1\b13\b3.\b.1\b11\b12\b2.\b. s\bsh\bho\bow\bw/\b/l\blo\bog\bg (\b(8\b8)\b)
+ 1\b13\b3.\b.1\b11\b13\b3.\b. s\bsh\bho\bow\bw/\b/l\blo\bog\bg (\b(8\b8)\b)
s\bsh\bho\bow\bw/\b/l\blo\bog\bg [\b[<\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b>]\b] Show excerpts from the system log
show output from the log associated with that callsign.
- 1\b13\b3.\b.1\b11\b13\b3.\b. s\bsh\bho\bow\bw/\b/m\bmo\boo\bon\bn (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b11\b14\b4.\b. s\bsh\bho\bow\bw/\b/m\bmo\boo\bon\bn (\b(0\b0)\b)
s
\bsh
\bho
\bow
\bw/
\b/m
\bmo
\boo
\bon
\bn [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show moon rise and set times
- 1\b13\b3.\b.1\b11\b14\b4.\b. s\bsh\bho\bow\bw/\b/m\bmu\buf\bf (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b11\b15\b5.\b. s\bsh\bho\bow\bw/\b/m\bmu\buf\bf (\b(0\b0)\b)
s
\bsh
\bho
\bow
\bw/
\b/m
\bmu
\buf
\bf <
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b> [
\b[<
\b<h
\bho
\bou
\bur
\brs
\bs>
\b>]
\b][
\b[l
\blo
\bon
\bng
\bg]
\b] Show the likely propagation to
<prefix>
terrible accurate, but it is included for completeness.
- 1\b13\b3.\b.1\b11\b15\b5.\b. s\bsh\bho\bow\bw/\b/n\bno\bod\bde\be (\b(1\b1)\b)
+ 1\b13\b3.\b.1\b11\b16\b6.\b. s\bsh\bho\bow\bw/\b/n\bno\bod\bde\be (\b(1\b1)\b)
s\bsh\bho\bow\bw/\b/n\bno\bod\bde\be [\b[<\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Show the type and version number of nodes
the non-user callsigns known to the system will be displayed.
- 1\b13\b3.\b.1\b11\b16\b6.\b. s\bsh\bho\bow\bw/\b/p\bpr\bre\bef\bfi\bix\bx (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b11\b17\b7.\b. s\bsh\bho\bow\bw/\b/p\bpr\bre\bef\bfi\bix\bx (\b(0\b0)\b)
s\bsh\bho\bow\bw/\b/p\bpr\bre\bef\bfi\bix\bx <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Interrogate the prefix database
- 1\b13\b3.\b.1\b11\b17\b7.\b. s\bsh\bho\bow\bw/\b/p\bpr\bro\bog\bgr\bra\bam\bm (\b(5\b5)\b)
+ 1\b13\b3.\b.1\b11\b18\b8.\b. s\bsh\bho\bow\bw/\b/p\bpr\bro\bog\bgr\bra\bam\bm (\b(5\b5)\b)
s\bsh\bho\bow\bw/\b/p\bpr\bro\bog\bgr\bra\bam\bm Show the locations of all the included program modules
from.
- 1\b13\b3.\b.1\b11\b18\b8.\b. s\bsh\bho\bow\bw/\b/q\bqr\bra\ba (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b11\b19\b9.\b. s\bsh\bho\bow\bw/\b/q\bqr\bra\ba (\b(0\b0)\b)
s\bsh\bho\bow\bw/\b/q\bqr\bra\ba <\b<l\blo\boc\bca\bat\bto\bor\br>\b> [\b[<\b<l\blo\boc\bca\bat\bto\bor\br>\b>]\b] Show the distance between locators
s\bsh\bho\bow\bw/\b/q\bqr\bra\ba <\b<l\bla\bat\bt>\b> <\b<l\blo\bon\bng\bg>\b> Convert latitude and longitude to a locator
- 1\b13\b3.\b.1\b11\b19\b9.\b. s\bsh\bho\bow\bw/\b/q\bqr\brz\bz (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b20\b0.\b. s\bsh\bho\bow\bw/\b/q\bqr\brz\bz (\b(0\b0)\b)
s\bsh\bho\bow\bw/\b/q\bqr\brz\bz <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Show any callbook details on a callsign
provided for users of this software by http://www.qrz.com
- 1\b13\b3.\b.1\b12\b20\b0.\b. s\bsh\bho\bow\bw/\b/r\bro\bou\but\bte\be (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b21\b1.\b. s\bsh\bho\bow\bw/\b/r\bro\bou\but\bte\be (\b(0\b0)\b)
s\bsh\bho\bow\bw/\b/r\bro\bou\but\bte\be <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Show the route to <callsign>
- 1\b13\b3.\b.1\b12\b21\b1.\b. s\bsh\bho\bow\bw/\b/s\bsa\bat\bte\bel\bll\bli\bit\bte\be (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b22\b2.\b. s\bsh\bho\bow\bw/\b/s\bsa\bat\bte\bel\bll\bli\bit\bte\be (\b(0\b0)\b)
s\bsh\bho\bow\bw/\b/s\bsa\bat\bte\bel\bll\bli\bit\bte\be <\b<n\bna\bam\bme\be>\b> [\b[<\b<h\bho\bou\bur\brs\bs>\b> <\b<i\bin\bnt\bte\ber\brv\bva\bal\bl>\b>]\b] Show satellite tracking
data
- 1\b13\b3.\b.1\b12\b22\b2.\b. s\bsh\bho\bow\bw/\b/s\bsu\bun\bn (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b23\b3.\b. s\bsh\bho\bow\bw/\b/s\bsu\bun\bn (\b(0\b0)\b)
s
\bsh
\bho
\bow
\bw/
\b/s
\bsu
\bun
\bn [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show sun rise and set times
- 1\b13\b3.\b.1\b12\b23\b3.\b. s\bsh\bho\bow\bw/\b/t\bti\bim\bme\be (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b24\b4.\b. s\bsh\bho\bow\bw/\b/t\bti\bim\bme\be (\b(0\b0)\b)
s
\bsh
\bho
\bow
\bw/
\b/t
\bti
\bim
\bme
\be [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show the local time
including DST) at the prefixes or callsigns that you specify.
- 1\b13\b3.\b.1\b12\b24\b4.\b. s\bsh\bho\bow\bw/\b/w\bwc\bcy\by (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b25\b5.\b. s\bsh\bho\bow\bw/\b/w\bwc\bcy\by (\b(0\b0)\b)
s\bsh\bho\bow\bw/\b/w\bwc\bcy\by Show the last 10 WCY broadcasts
s\bsh\bho\bow\bw/\b/w\bwc\bcy\by <\b<n\bn>\b> Show the last <n> WCY broadcasts
system
- 1\b13\b3.\b.1\b12\b25\b5.\b. s\bsh\bho\bow\bw/\b/w\bww\bwv\bv (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b26\b6.\b. s\bsh\bho\bow\bw/\b/w\bww\bwv\bv (\b(0\b0)\b)
s\bsh\bho\bow\bw/\b/w\bww\bwv\bv Show the last 10 WWV broadcasts
s\bsh\bho\bow\bw/\b/w\bww\bwv\bv <\b<n\bn>\b> Show the last <n> WWV broadcasts
- 1\b13\b3.\b.1\b12\b26\b6.\b. s\bsh\bhu\but\btd\bdo\bow\bwn\bn (\b(5\b5)\b)
+ 1\b13\b3.\b.1\b12\b27\b7.\b. s\bsh\bhu\but\btd\bdo\bow\bwn\bn (\b(5\b5)\b)
s\bsh\bhu\but\btd\bdo\bow\bwn\bn Shutdown the cluster
set to respawn in /etc/inittab it will of course restart.
- 1\b13\b3.\b.1\b12\b27\b7.\b. s\bsp\bpo\boo\bof\bf (\b(9\b9)\b)
+ 1\b13\b3.\b.1\b12\b28\b8.\b. s\bsp\bpo\boo\bof\bf (\b(9\b9)\b)
s\bsp\bpo\boo\bof\bf <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> <\b<c\bco\bom\bmm\bma\ban\bnd\bd>\b> Run commands as another user
like home_node for example.
- 1\b13\b3.\b.1\b12\b28\b8.\b. s\bst\bta\bat\bt/\b/d\bdb\bb (\b(5\b5)\b)
+ 1\b13\b3.\b.1\b12\b29\b9.\b. s\bst\bta\bat\bt/\b/d\bdb\bb (\b(5\b5)\b)
s\bst\bta\bat\bt/\b/d\bdb\bb <\b<d\bdb\bbn\bna\bam\bme\be>\b> Show the status of a database
other than a sysop.
- 1\b13\b3.\b.1\b12\b29\b9.\b. s\bst\bta\bat\bt/\b/c\bch\bha\ban\bnn\bne\bel\bl (\b(5\b5)\b)
+ 1\b13\b3.\b.1\b13\b30\b0.\b. s\bst\bta\bat\bt/\b/c\bch\bha\ban\bnn\bne\bel\bl (\b(5\b5)\b)
s\bst\bta\bat\bt/\b/c\bch\bha\ban\bnn\bne\bel\bl <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Show the status of a channel on the cluster
Only the fields that are defined (in perl term) will be displayed.
- 1\b13\b3.\b.1\b13\b30\b0.\b. s\bst\bta\bat\bt/\b/m\bms\bsg\bg (\b(5\b5)\b)
+ 1\b13\b3.\b.1\b13\b31\b1.\b. s\bst\bta\bat\bt/\b/m\bms\bsg\bg (\b(5\b5)\b)
s\bst\bta\bat\bt/\b/m\bms\bsg\bg <\b<m\bms\bsg\bgn\bno\bo>\b> Show the status of a message
etc etc.
- 1\b13\b3.\b.1\b13\b31\b1.\b. s\bst\bta\bat\bt/\b/u\bus\bse\ber\br (\b(5\b5)\b)
+ 1\b13\b3.\b.1\b13\b32\b2.\b. s\bst\bta\bat\bt/\b/u\bus\bse\ber\br (\b(5\b5)\b)
s\bst\bta\bat\bt/\b/u\bus\bse\ber\br <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Show the full status of a user
Only the fields that are defined (in perl term) will be displayed.
- 1\b13\b3.\b.1\b13\b32\b2.\b. s\bsy\bys\bso\bop\bp (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b13\b33\b3.\b. s\bsy\bys\bso\bop\bp (\b(0\b0)\b)
s\bsy\bys\bso\bop\bp Regain your privileges if you login remotely
case sensitive.
- 1\b13\b3.\b.1\b13\b33\b3.\b. t\bta\bal\blk\bk (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b13\b34\b4.\b. t\bta\bal\blk\bk (\b(0\b0)\b)
t\bta\bal\blk\bk <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Enter talk mode with <callsign>
t\bta\bal\blk\bk <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> <\b<t\bte\bex\bxt\bt>\b> Send a text message to <callsign>
- 1\b13\b3.\b.1\b13\b34\b4.\b. t\bty\byp\bpe\be (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b13\b35\b5.\b. t\bty\byp\bpe\be (\b(0\b0)\b)
t\bty\byp\bpe\be <\b<f\bfi\bil\ble\bea\bar\bre\bea\ba>\b>/\b/<\b<n\bna\bam\bme\be>\b> Look at a file in one of the fileareas
content.
- 1\b13\b3.\b.1\b13\b35\b5.\b. w\bwh\bho\bo (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b13\b36\b6.\b. w\bwh\bho\bo (\b(0\b0)\b)
w\bwh\bho\bo Show who is physically connected locally
what sort of connection they have
- 1\b13\b3.\b.1\b13\b36\b6.\b. w\bwx\bx (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b13\b37\b7.\b. w\bwx\bx (\b(0\b0)\b)
w\bwx\bx <\b<t\bte\bex\bxt\bt>\b> Send a weather message to local users
w\bwx\bx f\bfu\bul\bll\bl <\b<t\bte\bex\bxt\bt>\b> Send a weather message to all cluster users
extreme that may indicate enhanced conditions
- 1\b13\b3.\b.1\b13\b37\b7.\b. w\bwx\bx (\b(e\ben\bnh\bha\ban\bnc\bce\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(5\b5)\b)
+ 1\b13\b3.\b.1\b13\b38\b8.\b. w\bwx\bx (\b(e\ben\bnh\bha\ban\bnc\bce\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(5\b5)\b)
w\bwx\bx s\bsy\bys\bso\bop\bp <\b<t\bte\bex\bxt\bt>\b> Send a weather message to other clusters only
projects / spider.git / blobdiff