The DXSpider Installation and Administration Manual
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.33 (Revision 1.22) March 2001
+ Version 1.47 (Revision 1.30), April 2001
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
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 (Linux version)
3. Configuration
3.1 Allowing ax25 connects from users
3.2 Allowing telnet connects from users
- 3.3 Setting up node connects
- 3.4 Connection scripts
- 3.5 Starting the connection
- 3.6 Telnet echo
+ 3.3 Setting up telnet connects (from 1.47 onwards)
+ 3.4 Setting up for AGW Engine (1.47 onwards)
+ 3.5 Setting up node connects
+ 3.6 Connection scripts
+ 3.7 Starting the connection
+ 3.8 Telnet echo
4. Automating things
13.100 show/baddx (1)
13.101 show/badnode (6)
13.102 show/badspotter (1)
- 13.103 show/date (0)
- 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)
+ 13.103 show/configuration (0)
+ 13.104 show/configuration/node (0)
+ 13.105 show/connect (1)
+ 13.106 show/date (0)
+ 13.107 show/debug (9)
+ 13.108 show/dx (0)
+ 13.109 show/dxcc (0)
+ 13.110 show/files (0)
+ 13.111 show/filter (0)
+ 13.112 show/filter (extended for sysops) (5)
+ 13.113 show/hops (8)
+ 13.114 show/isolate (1)
+ 13.115 show/lockout (9)
+ 13.116 show/log (8)
+ 13.117 show/moon (0)
+ 13.118 show/muf (0)
+ 13.119 show/node (1)
+ 13.120 show/prefix (0)
+ 13.121 show/program (5)
+ 13.122 show/qra (0)
+ 13.123 show/qrz (0)
+ 13.124 show/route (0)
+ 13.125 show/satellite (0)
+ 13.126 show/sun (0)
+ 13.127 show/time (0)
+ 13.128 show/wcy (0)
+ 13.129 show/wwv (0)
+ 13.130 shutdown (5)
+ 13.131 spoof (9)
+ 13.132 stat/db (5)
+ 13.133 stat/channel (5)
+ 13.134 stat/msg (5)
+ 13.135 stat/user (5)
+ 13.136 sysop (0)
+ 13.137 talk (0)
+ 13.138 type (0)
+ 13.139 who (0)
+ 13.140 wx (0)
+ 13.141 wx (enhanced for sysops) (5)
______________________________________________________________________
- +\bo MD5-1.7.tar.gz
+ +\bo Data-Dumper-2.101.tar.gz
- +\bo Data-Dumper-2.10.tar.gz
+ +\bo TimeDate-1.10.tar.gz
- +\bo TimeDate-1.08.tar.gz
-
- +\bo IO-1.20.tar.gz
+ +\bo IO-1.20.tar.gz (for perl 5.00403 and lower)
+\bo Net-Telnet-3.02.tar.gz
If you do not have the command _\bg_\br_\bo_\bu_\bp_\ba_\bd_\bd available to you simply add a
line in /etc/group by hand.
+ # vi /etc/group (or your favorite editor)
+
- # vi /etc/group (or your favorite editor)
You also need to add some others to the group, including your own
callsign (this will be used as an alias) and root. The finished line
alter the text of any section. Some of the lines look a little odd.
Take this line for example ....
-
$myemail = "ianmaude\@btinternet.com";
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 ...
+ to /spider/src. Now issue the following command ...
+
+ $ ./client
+
- $ ./client.pl
This should log you into the cluster as the sysop under the alias
callsign we set earlier. In this case the callsign is G0VGS. The
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 (\b(L\bLi\bin\bnu\bux\bx v\bve\ber\brs\bsi\bio\bon\bn)\b)
+
+ 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
+ For most purposes this is not desirable. The only time you probably
+ will need this is when you need to allow other cluster nodes that are
+ using SSID's in. In this case it would probably be better to use the
+ first example and then add a specific line for that node like this:
+
+
+
+ GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25
+ default * * * * * * - sysop /spider/src/client client %u ax25
+
+
+
+
+
3\b3.\b.2\b2.\b. A\bAl\bll\blo\bow\bwi\bin\bng\bg t\bte\bel\bln\bne\bet\bt c\bco\bon\bnn\bne\bec\bct\bts\bs f\bfr\bro\bom\bm u\bus\bse\ber\brs\bs
+
+ From version 1.47 there is a new (more efficient) way of doing this
+ (see next section) but, if you prefer, the method of doing it
+ described here will continue to work just fine.
+
+
Allowing telnet connections is quite simple. Firstly you need to add
a line in /etc/services to allow connections to a port number, like
this ....
-
-
- This needs to be added above the standard services such as ftp, telnet
- etc. Once this is done, you need to restart inetd like this ....
+ Once this is done, you need to restart inetd like this ....
- 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 t\bte\bel\bln\bne\bet\bt c\bco\bon\bnn\bne\bec\bct\bts\bs (\b(f\bfr\bro\bom\bm 1\b1.\b.4\b47\b7 o\bon\bnw\bwa\bar\brd\bds\bs)\b)
+
+ From version 1.47 you can choose to allow the perl cluster.pl program
+ to allow connections directly (i.e. not via the /spider/src/client
+ interface program). If you are using Windows then this is the only
+ method available of allowing incoming telnet connections.
+
+
+ To do this you need first to remove any line that you may previously
+ have set up in /etc/inetd.conf. Remember to:-
+
+
+
+ killall -HUP inetd
+
+
+
+
+
+ to make the change happen...
+
+
+ Having done that, you need to copy the file _\b/_\bs_\bp_\bi_\bd_\be_\br_\b/_\bp_\be_\br_\bl_\b/_\bL_\bi_\bs_\bt_\be_\bn_\be_\br_\bs_\b._\bp_\bm
+ to _\b/_\bs_\bp_\bi_\bd_\be_\br_\b/_\bl_\bo_\bc_\ba_\bl and then edit it. You will need to uncomment the line
+ containing "0.0.0.0" and select the correct port to listen on. So that
+ it looks like this:-
+ @listen = (
+ ["0.0.0.0", 8000],
+ );
- 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
+
+
+
+ As standard, the listener will listen on all interfaces
+ simultaneously. If you require more control than this, you can
+ specify each interface individually:-
+
+
+
+ @listen = (
+ ["gb7baa.dxcluster.net", 8000],
+ ["44.131.16.2", 6300],
+ );
+
+
+
+
+
+ This will only be successful if the IP addresses on each interface are
+ static. If you are using some kind of dynamic IP addressing then the
+ 'default' method is the only one that will work.
+
+
+ Restart the cluster.pl program to enable the listener.
+
+
+ One important difference with the internal listener is that no echoing
+ is done by the cluster program. Users will need to set 'local-echo' on
+ in their telnet clients if it isn't set automatically (as per the
+ standards). Needless to say this will probably only apply to Windows
+ users.
+
+
+ 3\b3.\b.4\b4.\b. S\bSe\bet\btt\bti\bin\bng\bg u\bup\bp f\bfo\bor\br A\bAG\bGW\bW E\bEn\bng\bgi\bin\bne\be (\b(1\b1.\b.4\b47\b7 o\bon\bnw\bwa\bar\brd\bds\bs)\b)
+
+ AGW Engine is a Windows based ax25 stack. You can connect to an AGW
+ engine from Linux as well as Windows based machines.
+
+
+ In order to enable access to an AGW Engine you need to copy
+ _\b/_\bs_\bp_\bi_\bd_\be_\br_\b/_\bp_\be_\br_\bl_\b/_\bA_\bG_\bW_\bC_\bo_\bn_\bn_\be_\bc_\bt_\b._\bp_\bm to _\b/_\bs_\bp_\bi_\bd_\be_\br_\b/_\bl_\bo_\bc_\ba_\bl and edit it. Specifically
+ you must:-
+
+
+ +\bo set $enable to 1.
+
+ +\bo set $login and $passwd to the values set up in your AGW
+ installation. If you haven't set any there, then you should not
+ touch these values.
+
+ +\bo You can connect to a remote AGW engine (ie on some other machine)
+ by changing $addr and $port appropriately.
+
+ +\bo Restart the cluster.pl program
+
+
+
+
+
+
+
+ 3\b3.\b.5\b5.\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
the connecting callsign is a cluster node. This is the case whether
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 ...
That is now set, it is as simple as that. To prove it, login on yet
- another console as sysop, cd to spider/perl 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
be outgoing then a connection script needs to be written.
- 3\b3.\b.4\b4.\b. C\bCo\bon\bnn\bne\bec\bct\bti\bio\bon\bn s\bsc\bcr\bri\bip\bpt\bts\bs
+ Sometimes you make a mistake... Honest, it does happen. If you want
+ to make a node back to being a normal user, regardless of what type it
+ is, do:
+
+
+
+ unset/node gb7baa
+
+
+
+
+
+ 3\b3.\b.6\b6.\b. C\bCo\bon\bnn\bne\bec\bct\bti\bio\bon\bn s\bsc\bcr\bri\bip\bpt\bts\bs
Because DXSpider operates under Linux, connections can be made using
just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all
- # All lines starting with a # are ignored, as are completely
- blank lines.
+ #\b# All lines starting with a # are ignored, as are completely blank
+ lines.
+
- timeout timeout followed by a number is the number of seconds to wait for a
- command to complete. If there is no timeout specified in the script
- then the default is 60 seconds.
+ t\bti\bim\bme\beo\bou\but\bt
+ timeout followed by a number is the number of seconds to wait
+ for a command to complete. If there is no timeout specified in
+ the script then the default is 60 seconds.
- abort abort is a regular expression containing one or more strings to look
- for to abort a connection. This is a perl regular expression and is
- executed ignoring case.
- connect connect followed by ax25 or telnet and some type dependent
- information. In the case of a telnet connection, there can be up to
- two parameters.
- The first is the ip address or hostname of the computer you wish to
- connect to and the second is the port number you want to use (this
- can be left out if it is a normal telnet session).
- In the case of an ax25 session then this would normally be a call to
- ax25_call or netrom_call as in the example above. It is your
- responsibility to get your node and other ax25 parameters to work
- before going down this route!
+ a\bab\bbo\bor\brt\bt
+ abort is a regular expression containing one or more strings to
+ look for to abort a connection. This is a perl regular
+ expression and is executed ignoring case.
- ' line in a chat type script. The words/phrases normally come in pairs,
- either can be empty. Each line reads input from the connection until
- it sees the string (or perl regular expression) contained in the
- left hand string. If the left hand string is empty then it doesn't
- read or wait for anything. The comparison is done ignoring case.
- When the left hand string has found what it is looking for (if it is)
- then the right hand string is sent to the connection.
- This process is repeated for every line of chat script.
- client client starts the connection, put the arguments you would want here
- if you were starting the client program manually. You only need this
- if the script has a different name to the callsign you are trying to
- connect to (i.e. you have a script called other which actually
- connects to GB7DJK-1 [instead of a script called gb7djk-1]).
+ c\bco\bon\bnn\bne\bec\bct\bt
+ connect followed by ax25, agw (for Windows users) or telnet and
+ some type dependent information. In the case of a telnet
+ connection, there can be up to two parameters. The first is the
+ ip address or hostname of the computer you wish to connect to
+ and the second is the port number you want to use (this can be
+ left out if it is a normal telnet session). In the case of an
+ ax25 session then this would normally be a call to ax25_call or
+ netrom_call as in the example above. It is your responsibility
+ to get your node and other ax25 parameters to work before going
+ down this route!
+ '\b' line in a chat type script. The words/phrases normally come in
+ pairs, either can be empty. Each line reads input from the
+ connection until it sees the string (or perl regular expression)
+ contained in the left hand string. If the left hand string is
+ empty then it doesn't read or wait for anything. The comparison
+ is done ignoring case. When the left hand string has found what
+ it is looking for (if it is) then the right hand string is sent
+ to the connection. This process is repeated for every line of
+ chat script.
- There are many possible ways to configure the script but here are two
- examples, one for a NETRom/AX25 connect and one for tcp/ip.
+ c\bcl\bli\bie\ben\bnt\bt
+ client starts the connection, put the arguments you would want
+ here if you were starting the client program manually. You only
+ need this if the script has a different name to the callsign you
+ are trying to connect to (i.e. you have a script called other
+ which actually connects to GB7DJK-1 [instead of a script called
+ gb7djk-1]).
+ There are many possible ways to configure the script but here are
+ three examples, one for a NETRom/AX25 connect, one for AGW engines and
+ one for tcp/ip.
- 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
+
+
+
+
+
+
+
+
+ timeout 60
+ abort (Busy|Sorry|Fail)
+ # this does exactly the same as the previous example
+ # the '1' is the AGW port number to connect thru for g1tlh
+ connect agw 1 g1tlh
+ # you can leave this out if you call the script 'gb7dxm'
+ client gb7dxm ax25
directory.
- 3\b3.\b.5\b5.\b. S\bSt\bta\bar\brt\bti\bin\bng\bg t\bth\bhe\be c\bco\bon\bnn\bne\bec\bct\bti\bio\bon\bn
+
+
+ 3\b3.\b.7\b7.\b. S\bSt\bta\bar\brt\bti\bin\bng\bg t\bth\bhe\be c\bco\bon\bnn\bne\bec\bct\bti\bio\bon\bn
You start the connection, from within a sysop enabled cluster login,
by typing in the word _\bc_\bo_\bn_\bn_\be_\bc_\bt followed by a script name like this ....
This will start a connection using the script called _\bg_\bb_\b7_\bd_\bj_\bk_\b-_\b1. You
can follow the connection by watching the term or console from where
- you started _\bc_\bl_\bu_\bs_\bt_\be_\br_\b._\bp_\bl. You should see something like this ...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <- 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
+ you started _\bc_\bl_\bu_\bs_\bt_\be_\br_\b._\bp_\bl. From version 1.47 onwards, you will need to
+ set/debug connect first. You should see something like this ...
+
+
+
+ <- 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
-
-
In a script, this might look like ...
- 3\b3.\b.6\b6.\b. T\bTe\bel\bln\bne\bet\bt e\bec\bch\bho\bo
+ 3\b3.\b.8\b8.\b. T\bTe\bel\bln\bne\bet\bt e\bec\bch\bho\bo
Cluster links in particular suffer greatly from the presence of telnet
echo. This is caused by the telnet negotiation itself and can create
Telnet echo itself should only be a problem if the connection is being
made to the telnet port (23). This port uses special rules that
include echo negotiation. If the connection is to a different port,
- such as 8000, this negotiation does not happen and therefore no echo
+ such as 7300, this negotiation does not happen and therefore no echo
should be present.
+
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 ...
- # 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 unless connected('gb7xxx')
website at the cron page where it is explained more fully.
-
-
-
5\b5.\b. H\bHo\bop\bp c\bco\bon\bnt\btr\bro\bol\bl
Starting with version 1.13 there is simple hop control available on a
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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
SET/BADSPOTTER for more information.
- 1\b13\b3.\b.1\b10\b03\b3.\b. s\bsh\bho\bow\bw/\b/d\bda\bat\bte\be (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b10\b03\b3.\b. s\bsh\bho\bow\bw/\b/c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn (\b(0\b0)\b)
+
+ s\bsh\bho\bow\bw/\b/c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn [\b[<\b<n\bno\bod\bde\be>\b>]\b] Show all visible nodes and their users
+
+
+ This command allows you to see all the users that can be seen and the
+ nodes to which they are connected. With the optional _\bn_\bo_\bd_\be, you can
+ specify a particular node to look at.
+
+ This command is normally abbreviated to: sh/c
+
+ BE WARNED: the list that is returned can be VERY long
+
+
+ 1\b13\b3.\b.1\b10\b04\b4.\b. s\bsh\bho\bow\bw/\b/c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn/\b/n\bno\bod\bde\be (\b(0\b0)\b)
+
+ s\bsh\bho\bow\bw/\b/c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn/\b/n\bno\bod\bde\be Show all the nodes connected
+
+
+ Show all the nodes connected locally and the nodes they have
+ connected.
+
+
+ 1\b13\b3.\b.1\b10\b05\b5.\b. s\bsh\bho\bow\bw/\b/c\bco\bon\bnn\bne\bec\bct\bt (\b(1\b1)\b)
+
+ s\bsh\bho\bow\bw/\b/c\bco\bon\bnn\bne\bec\bct\bt Show all the active connections
+
+
+ This command shows information on all the active connections known to
+ the node. This command gives slightly more information than WHO.
+
+
+ 1\b13\b3.\b.1\b10\b06\b6.\b. s\bsh\bho\bow\bw/\b/d\bda\bat\bte\be (\b(0\b0)\b)
s
\bsh
\bho
\bow
\bw/
\b/d
\bda
\bat
\bte
\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
This is very nearly the same as SHOW/TIME, the only difference the
format of the date string if no arguments are given.
-
If no prefixes or callsigns are given then this command returns the
local time and UTC as the computer has it right now. If you give some
prefixes then it will show UTC and UTC + the local offset (not
including DST) at the prefixes or callsigns that you specify.
- 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)
+ 1\b13\b3.\b.1\b10\b07\b7.\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)
+ 1\b13\b3.\b.1\b10\b08\b8.\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
+ on <band> - eg 160m 20m 2m 23cm 6mm
+ on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
+ <number> - the number of spots you want
+ <from>-<to> - <from> spot no <to> spot no in
+ the selected list
+ <prefix> - for a spotted callsign beginning with <prefix>
+ *<suffix> - for a spotted callsign ending in <suffix>
+ *<string>* - for a spotted callsign containing <string>
- on <band> - eg 160m 20m 2m 23cm 6mm
- on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
-
- <number> - the number of spots you want
- <from>-<to> - <from> spot no <to> spot no in
- the selected list
+ day <number> - starting <number> days ago
+ day <from>-<to> - <from> days <to> days ago
- <prefix> - for a spotted callsign beginning with <prefix>
- *<suffix> - for a spotted callsign ending in <suffix>
- *<string>* - for a spotted callsign containing <string>
+ info <text> - any spots containing <text> in the info or remarks
- day <number> - starting <number> days ago
- day <from>-<to> - <from> days <to> days ago
+ by <call> - any spots spotted by <call> (spotter <call>
+ is the same).
- info <text> - any spots containing <text> in the info or remarks
+ qsl - this automatically looks for any qsl info on the call
+ held in the spot database.
- by <call> - any spots spotted by <call> (spotter <call>
- is the same).
+ iota [<iota>] - If the iota island number is missing it will
+ look for the string iota and anything which looks like
+ an iota island number. If you specify then it will look
+ for that island.
- qsl - this automatically looks for any qsl info on the call
- held in the spot database.
-
- iota [<iota>] - If the iota island number is missing it will
- look for the string iota and anything which looks like
- an iota island number. If you specify then it will look
- for that island.
-
- qra [<locator>] - this will look for the specific locator if
- you specify one or else anything that looks like a locator.
+ qra [<locator>] - this will look for the specific locator if
+ you specify one or else anything that looks like a locator.
- SH/DX 9m0
- SH/DX on 20m info iota
- SH/DX 9a on vhf day 30
- SH/DX rf1p qsl
- SH/DX iota
- SH/DX iota eu-064
- SH/DX qra jn86
+ SH/DX 9m0
+ SH/DX on 20m info iota
+ SH/DX 9a on vhf day 30
+ SH/DX rf1p qsl
+ SH/DX iota
+ SH/DX iota eu-064
+ SH/DX qra jn86
- 1\b13\b3.\b.1\b10\b06\b6.\b. s\bsh\bho\bow\bw/\b/d\bdx\bxc\bcc\bc (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b10\b09\b9.\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
-
-
- SH/DXCC G
- SH/DXCC W on 20m info iota
+ SH/DXCC G
+ SH/DXCC W on 20m info iota
- 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)
+ 1\b13\b3.\b.1\b11\b10\b0.\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\b08\b8.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br (\b(0\b0)\b)
+
+ 1\b13\b3.\b.1\b11\b11\b1.\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\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)
+ 1\b13\b3.\b.1\b11\b12\b2.\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\b11\b10\b0.\b. s\bsh\bho\bow\bw/\b/h\bho\bop\bps\bs (\b(8\b8)\b)
+ 1\b13\b3.\b.1\b11\b13\b3.\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\b11\b1.\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\b14\b4.\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\b12\b2.\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\b15\b5.\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\b13\b3.\b. s\bsh\bho\bow\bw/\b/l\blo\bog\bg (\b(8\b8)\b)
+ 1\b13\b3.\b.1\b11\b16\b6.\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\b14\b4.\b. s\bsh\bho\bow\bw/\b/m\bmo\boo\bon\bn (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b11\b17\b7.\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\b15\b5.\b. s\bsh\bho\bow\bw/\b/m\bmu\buf\bf (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b11\b18\b8.\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>
SH/MUF W
-
-
-
produces:
SH/MUF W 24
+
+
+
will get you the above display, but with the next 24 hours worth of
propagation data.
terrible accurate, but it is included for completeness.
- 1\b13\b3.\b.1\b11\b16\b6.\b. s\bsh\bho\bow\bw/\b/n\bno\bod\bde\be (\b(1\b1)\b)
+ 1\b13\b3.\b.1\b11\b19\b9.\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\b17\b7.\b. s\bsh\bho\bow\bw/\b/p\bpr\bre\bef\bfi\bix\bx (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b20\b0.\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
See also SHOW/DXCC
-
-
- 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)
+ 1\b13\b3.\b.1\b12\b21\b1.\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\b19\b9.\b. s\bsh\bho\bow\bw/\b/q\bqr\bra\ba (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b22\b2.\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
SH/QRA IO92QL
SH/QRA JN06 IN73
+
+
+
The first example will show the distance and bearing to the locator
from yourself, the second example will calculate the distance and
bearing from the first locator to the second. You can use 4 or 6
- 1\b13\b3.\b.1\b12\b20\b0.\b. s\bsh\bho\bow\bw/\b/q\bqr\brz\bz (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b23\b3.\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\b21\b1.\b. s\bsh\bho\bow\bw/\b/r\bro\bou\but\bte\be (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b24\b4.\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>
- sh/route n2tly
+ sh/route n2tly
- 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)
+ 1\b13\b3.\b.1\b12\b25\b5.\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
Each pass in a period is separated with a row of '-----' characters
-
So for example:-
- 1\b13\b3.\b.1\b12\b23\b3.\b. s\bsh\bho\bow\bw/\b/s\bsu\bun\bn (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b26\b6.\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\b24\b4.\b. s\bsh\bho\bow\bw/\b/t\bti\bim\bme\be (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b27\b7.\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\b25\b5.\b. s\bsh\bho\bow\bw/\b/w\bwc\bcy\by (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b28\b8.\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\b26\b6.\b. s\bsh\bho\bow\bw/\b/w\bww\bwv\bv (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b12\b29\b9.\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
-
Display the most recent WWV information that has been received by the
system
- 1\b13\b3.\b.1\b12\b27\b7.\b. s\bsh\bhu\but\btd\bdo\bow\bwn\bn (\b(5\b5)\b)
+ 1\b13\b3.\b.1\b13\b30\b0.\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\b28\b8.\b. s\bsp\bpo\boo\bof\bf (\b(9\b9)\b)
+ 1\b13\b3.\b.1\b13\b31\b1.\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\b29\b9.\b. s\bst\bta\bat\bt/\b/d\bdb\bb (\b(5\b5)\b)
+ 1\b13\b3.\b.1\b13\b32\b2.\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\b13\b30\b0.\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\b33\b3.\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\b31\b1.\b. s\bst\bta\bat\bt/\b/m\bms\bsg\bg (\b(5\b5)\b)
+ 1\b13\b3.\b.1\b13\b34\b4.\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\b32\b2.\b. s\bst\bta\bat\bt/\b/u\bus\bse\ber\br (\b(5\b5)\b)
+ 1\b13\b3.\b.1\b13\b35\b5.\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\b33\b3.\b. s\bsy\bys\bso\bop\bp (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b13\b36\b6.\b. s\bsy\bys\bso\bop\bp (\b(0\b0)\b)
s\bsy\bys\bso\bop\bp Regain your privileges if you login remotely
or 2 0 5 7 3
or 20573
-
-
-
They will all match. If there is no password you will still be offered
numbers but nothing will happen when you input a string. Any match is
case sensitive.
- 1\b13\b3.\b.1\b13\b34\b4.\b. t\bta\bal\blk\bk (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b13\b37\b7.\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\b35\b5.\b. t\bty\byp\bpe\be (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b13\b38\b8.\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
enter:-
-
TYPE bulletins/arld051
content.
- 1\b13\b3.\b.1\b13\b36\b6.\b. w\bwh\bho\bo (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b13\b39\b9.\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\b37\b7.\b. w\bwx\bx (\b(0\b0)\b)
+ 1\b13\b3.\b.1\b14\b40\b0.\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
-
Weather messages can sometimes be useful if you are experiencing an
extreme that may indicate enhanced conditions
- 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)
+ 1\b13\b3.\b.1\b14\b41\b1.\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