Various additions and changes to documentation

[spider.git] / txt / adminmanual.txt

  The DXSpider Installation and Administration Manual
  Ian Maude, G0VGS, (ianmaude@btinternet.com)
  Version 1.32 February 2001

  A reference for SysOps of the DXSpider DXCluster program.
  ______________________________________________________________________

  Table of Contents


























































  1. Installation (Original version by Iain Phillips, 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

  2. The Client program

  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

  4. Automating things

     4.1 Autostarting the cluster
     4.2 The crontab file

  5. Hop control

     5.1 Basic hop control
     5.2 Isolating networks

  6. Filtering (Old Style upto v1.44)

     6.1 Spots
     6.2 Announcements
     6.3 WWV

  7. Filtering (New Style v1.45 and later)

     7.1 General filter rules
     7.2 Types of filter
     7.3 Filter options
     7.4 Default filters
     7.5 Advanced filtering

  8. Other filters

     8.1 Filtering Mail
     8.2 Filtering DX callouts (Depricated)
     8.3 Filtering words from text fields in Announce, Talk and DX spots

  9. Mail

     9.1 Personal mail
     9.2 Bulletin mail
     9.3 Forward.pl
     9.4 The msg command
     9.5 Message status
     9.6 Filtering mail
     9.7 Distribution lists
     9.8 BBS interface

  10. Databases

     10.1 Creating databases
     10.2 Importing databases
     10.3 Checking available databases
     10.4 Looking up databases
     10.5 Removing databases

  11. Information, files and useful programs

     11.1 MOTD
     11.2 Downtime message
     11.3 Other text messages
     11.4 The Aliases file
     11.5 Console.pl
     11.6 Updating kepler data

  12. CVS

  13. The DXSpider command set

     13.1 accept/announce (0)
     13.2 accept/announce (extended for sysops) (8)
     13.3 accept/spots (0)
     13.4 accept/spots (extended for sysops) (8)
     13.5 accept/wcy (0)
     13.6 accept/wcy (extended for sysops) (8)
     13.7 accept/wwv (0)
     13.8 accept/wwv (extended for sysops) (8)
     13.9 announce (0)
     13.10 announce full (0)
     13.11 announce sysop (5)
     13.12 apropos (0)
     13.13 bye (0)
     13.14 catchup (5)
     13.15 clear/spots (0)
     13.16 connect (5)
     13.17 dbavail (0)
     13.18 dbcreate (9)
     13.19 dbimport (9)
     13.20 dbremove (9)
     13.21 dbshow (0)
     13.22 debug (9)
     13.23 directory (0)
     13.24 directory (extended for sysops) (5)
     13.25 disconnect (8)
     13.26 dx (0)
     13.27 export (9)
     13.28 export_users (9)
     13.29 forward/latlong (8)
     13.30 forward/opername (1)
     13.31 help (0)
     13.32 init (5)
     13.33 kill (0)
     13.34 kill (5)
     13.35 kill full (5)
     13.36 links (0)
     13.37 load/aliases (9)
     13.38 load/baddx (9)
     13.39 load/badmsg (9)
     13.40 load/badwords (9)
     13.41 load/bands (9)
     13.42 load/cmd_cache (9)
     13.43 load/forward (9)
     13.44 load/messages (9)
     13.45 load/prefixes (9)
     13.46 merge (5)
     13.47 msg (9)
     13.48 pc (8)
     13.49 ping (1)
     13.50 rcmd (1)
     13.51 read (0)
     13.52 read (extended for sysops) (5)
     13.53 reject/announce
     13.54 reject/announce (extended for sysops) (8)
     13.55 reject/spots (0)
     13.56 reject/spots (extended for sysops) (8)
     13.57 reject/wcy (0)
     13.58 reject/wcy (extended for sysops) (8)
     13.59 reject/wwv (0)
     13.60 reject/wwv (extended for sysops) (8)
     13.61 reply (0)
     13.62 send (0)
     13.63 set/address (0)
     13.64 set/announce (0)
     13.65 set/arcluster (5)
     13.66 set/baddx (8)
     13.67 set/badnode (6)
     13.68 set/badspotter (8)
     13.69 set/beep (0)
     13.70 set/clx (5)
     13.71 set/debug (9)
     13.72 set/dx (0)
     13.73 set/dxgrid (0)
     13.74 set/dxnet (5)
     13.75 set/echo (0)
     13.76 set/here (0)
     13.77 set/homenode (0)
     13.78 set/hops (8)
     13.79 set/isolate (9)
     13.80 set/language (0)
     13.81 set/location (0)
     13.82 set/sys_location (9)
     13.83 set/logininfo (0)
     13.84 set/lockout (9)
     13.85 set/name (0)
     13.86 set/node (9)
     13.87 set/obscount (9)
     13.88 set/page (0)
     13.89 set/password (9)
     13.90 set/pinginterval (9)
     13.91 set/privilege (9)
     13.92 set/spider (5)
     13.93 set/sys_qra (9)
     13.94 set/qra (0)
     13.95 set/qth (0)
     13.96 set/talk (0)
     13.97 set/wcy (0)
     13.98 set/wwv (0)
     13.99 set/wx (0)
     13.100 show/baddx (1)
     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)


  ______________________________________________________________________

  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.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.


  I am assuming a general knowledge of Linux and its commands.  You
  should know how to use _\bt_\ba_\br and how to edit files using your favourite
  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


  In addition to the standard Red Hat distribution you will require the
  following CPAN modules: -



  +\bo  MD5-1.7.tar.gz

  +\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

  +\bo  Net-Telnet-3.02.tar.gz

  +\bo  Curses-1.05.tar.gz

  +\bo  Time-HiRes-01.20.tar.gz



  _\bD_\bo get the latest versions of these packages and install them but use
  the above list as the earliest versions usable.


  1\b1.\b.2\b2.\b.  P\bPr\bre\bep\bpa\bar\bra\bat\bti\bio\bon\bn

  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.


  Login as root and create a user to run the cluster under.  _\bU_\bN_\bD_\bE_\bR _\bN_\bO
  _\bC_\bI_\bR_\bC_\bU_\bM_\bS_\bT_\bA_\bN_\bC_\bE_\bS _\bU_\bS_\bE _\bR_\bO_\bO_\bT _\bA_\bS _\bT_\bH_\bI_\bS _\bU_\bS_\bE_\bR_\b!.  I am going to use the name
  _\bs_\by_\bs_\bo_\bp.  You can call it anything you wish.  Depending on your security
  requirements you may wish to use an existing user, however this is
  your own choice.




       # adduser -m sysop





  Now set a password for the user ...



       # passwd sysop
       # New UNIX password:
       # Retype new UNIX password:
       passwd: all authentication tokens updated successfully





  1\b1.\b.3\b3.\b.  I\bIn\bns\bst\bta\bal\bll\bli\bin\bng\bg t\bth\bhe\be s\bso\bof\bft\btw\bwa\bar\bre\be

  Now to unpack the DX Spider distribution, set symbolic links and group
  permissions.  Copy the tarball to /home/sysop and do the following.



       # cd ~sysop
       # tar xvfz spider-1.35.tar.gz
       # ln -s ~sysop/spider /spider
       # groupadd -g 251 spider       (or another number)




  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)

  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
  in /etc/group should look something like this

  spider:x:251:sysop,g0vgs,root


  The next step is to set the permissions on the Spider directory tree
  and files ....



       # chown -R sysop.spider spider
       # find . -type d -exec chmod 2775 {} \;
       # find . -type f -exec chmod 775 {} \;





  This last step allows various users of the group _\bs_\bp_\bi_\bd_\be_\br to have write
  access to all the directories.  This is not really needed just yet but
  will be useful when web interfaces start to appear.


  Finally, you need to fix the permissions on the ax25_call and
  netrom_call programs.  Check where they are with the _\bl_\bo_\bc_\ba_\bt_\be command
  and alter the permissions with the _\bc_\bh_\bm_\bo_\bd command like this ..



       # chown root ax25_call netrom_call
       # chmod 4775 ax25_call netrom_call





  1\b1.\b.4\b4.\b.  S\bSe\bet\btt\bti\bin\bng\bg c\bca\bal\bll\bls\bsi\big\bgn\bns\bs e\bet\btc\bc

  Now login to your machine as the user you created earlier.  In my case
  that user is called _\bs_\by_\bs_\bo_\bp.  Once logged in, issue the following
  commands ....



       $ cd /spider
       $ mkdir local
       $ mkdir local_cmd
       $ cp perl/DXVars.pm.issue local/DXVars.pm
       $ cd local
       $ vi DXVars.pm (or your favourite editor)





  Using the distributed DXVars.pm as a a template, set your cluster
  callsign, sysop callsign and other user info to suit your own
  environment. Note that this a perl file which will be parsed and
  executed as part of the cluster. If you get it wrong then perl will
  complain when you start the cluster process.  It is important only to
  alter the text of any section.  Some of the lines look a little odd.
  Take this line for example ....


  $myemail = "ianmaude\@btinternet.com";


  There appears to be an extra slash in there.  However this has to be
  there for the file to work so leave it in.


  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!


  Save the new file and change directory to ../perl ....



       $ cd ../perl





  Now type the following command which creates the basic user file with
  you as the sysop.



       $ create_sysop.pl





  1\b1.\b.5\b5.\b.  S\bSt\bta\bar\brt\bti\bin\bng\bg u\bup\bp f\bfo\bor\br t\bth\bhe\be f\bfi\bir\brs\bst\bt t\bti\bim\bme\be

  We can now bring spider up for the first time and see if all is well
  or not!  It should look something like this ...



       $ cluster.pl
       DXSpider DX Cluster Version 1.35
       Copyright (c) 1998 Dirk Koopman G1TLH
       loading prefixes ...
       loading band data ...
       loading user file system ...
       starting listener ...
       reading existing message headers
       reading cron jobs
       orft we jolly well go ...





  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





  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
  cluster callsign is set in the DXVars.pm file in /spider/local.  In
  this case we will assume that this was set as GB7MBC.  You should
  therefore see this when you login ....



       G0VGS de GB7MBC 19-Nov-1999 2150Z >




  If you do, congratulations!  If not, look over the instructions again,
  you have probably missed something out.  You can shut spider down
  again with the command ....



       shutdown





  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

  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
  be used up.  To combat this a new client was written in "C".  This
  client only works for _\bi_\bn_\bc_\bo_\bm_\bi_\bn_\bg connects at the moment.  Before you can
  use it though it has to be "made".  CD to /spider/src and type _\bm_\ba_\bk_\be.
  You should see the output on your screen and hopefully now have a
  small C program called _\bc_\bl_\bi_\be_\bn_\bt.  Leave it in this directory.


  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
  to configure Linux or the ax25 utilities.  However, you do need to add
  a line in your ax25d.conf to allow connections to DXSpider for your
  users.  For each interface that you wish to allow connections on, use
  the following format ...



       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

  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 ....



       spdlogin   8000/tcp     # spider anonymous login port




  Then add a line in /etc/inetd.conf like this ....



       spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet





  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 ....



       killall -HUP inetd






  Now login as _\bs_\by_\bs_\bo_\bp and cd spider/perl. You can test that spider is
  accepting telnet logins by issuing the following command ....



       client.pl login telnet




  You should get a login prompt and on issuing a callsign, you will be
  given access to the cluster.  Note, you will not get a password login.
  There seems no good reason for a password prompt to be given so it is
  not asked for.


  Assuming all is well, then try a telnet from your linux console ....



       telnet localhost 8000





  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
  the connecting callsign is a cluster node.  This is the case whether
  the connect is incoming or outgoing.  In spider this is a simple task
  and can be done in runtime.


  Later versions of Spider can distinguish different software and treat
  them differently.  For example, the WCY beacon cannot be handles by
  AK1A type nodes as AK1A does not know what to do with PC73.  There are
  4 different types of node at present and although they may not have
  any major differences at the moment, it allows for compatibility.  The
  4 types are ...



       set/node        (AK1A type)
       set/spider
       set/dxnet
       set/clx





  For now, we will assume that the cluster we are going to connect to is
  an AK1A type node.


  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
  GB7BAA but you would obviously use whatever callsign you required.  At
  the prompt type ...



       set/node gb7baa





  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 ...



       client.pl gb7baa (using the callsign you set as a node)





  You should get an initialisation string from DXSpider like this ...



       client.pl 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.


  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

  Because DXSpider operates under Linux, connections can be made using
  just about any protocol;  AX25, NETRom, tcp/ip, ROSE etc are all
  possible examples.  Connect scripts live in the /spider/connect
  directory and are simple ascii files.  Writing a script for
  connections is therefore relatively simple.


  The connect scripts consist of lines which start with the following
  keywords or symbols:-



  #               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.

  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!

  '               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]).




  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.





  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 15
       connect telnet dirkl.tobit.co.uk
       # tell GB7DJK-1 that it is connected to GB7DJK
       # you can leave this out if you call this script 'gb7djk'
       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.


  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

  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 ....



       G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1
       connection to GB7DJK-1 started
       G0VGS de GB7MBC 13-Dec-1998 2043Z >




  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





  With later versions of Spider there is a set/login command for users.
  This tells them when a user or node logs in or out.  If you do not add
  a line to your scripts after the final line (or before the client line
  which should always be last if needed) then the login/logout
  information will be sent to users _\bb_\be_\bf_\bo_\br_\be the login actually completes.
  This means if a node is unreachable, it will continue sending logins
  and logouts to users even though it is not actually connecting.  To
  avoid this use the following line ...








  In a script, this might look like ...



       timeout 35
       abort (Busy|Sorry|Fail)
       connect telnet mary 3000





  3\b3.\b.6\b6.\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
  at worst severe loops.  At best it creates unnecessary bandwidth and
  large logfiles!  There are things that can be done to limit this
  problem but will not always work dependent on the route taken to
  connect.


  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
  should be present.


  Sometimes it is not possible to make a direct connection to another
  node and this can cause problems.  There is a way of trying to
  suppress the telnet echo but this will not always work, unfortunately
  it is difficult to be more specific.  Here is an example of what I
  mean ...



       timeout 35
       abort (Busy|Sorry|Fail)
       connect telnet mary.lancs.ac.uk




  So, the first connection is made by Spider.  This is fine as Spider
  uses the Net_Telnet script from within perl.  This actually uses TCP
  rather than TELNET so no negotiation will be done on the first
  connection.  Once connected to mary.lancs.ac.uk, the command is sent
  to suppress echo.  Now a telnet is made to a cluster node that is
  accepting connections on port 23.  The problem with this link is that
  the negotiation is made by the remote machine, therefore you have no
  control over it.  The chances are that this link will create echo and
  there will be no way you can stop it.



  4\b4.\b.  A\bAu\but\bto\bom\bma\bat\bti\bin\bng\bg t\bth\bhi\bin\bng\bgs\bs

  Ok, you should now have DXSpider running nicely and allowing connects
  by cluster nodes or users.  However, it has to be shutdown and
  restarted manually and if connection scripts fail they have to be
  started again manually too, not much use if you are not at the
  console!  So, in this section we will automate both.  Firstly starting
  the cluster.


  4\b4.\b.1\b1.\b.  A\bAu\but\bto\bos\bst\bta\bar\brt\bti\bin\bng\bg t\bth\bhe\be c\bcl\blu\bus\bst\bte\ber\br

  This is not only a way to start the cluster automatically, it also
  works as a watchdog, checking the sanity of DXSpider and respawning it
  should it crash for any reason.  Before doing the following, shutdown
  the cluster as you did earlier.


  Login as root and bring up the /etc/inittab file in your favourite
  editor.  Add the following lines to the file near the end ...



       ##Start DXSpider on bootup and respawn it should it crash
       DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7




  This will automatically start DXSpider on tty7 (ALT-F7) on bootup and
  restart it should it crash for any reason.


  As root type the command _\bt_\be_\bl_\bi_\bn_\bi_\bt _\bq.  DXSpider should start up
  immediately.  You will see the output on tty7 and if you login as
  _\bs_\by_\bs_\bo_\bp you should find everything running nicely.


  So far so good, now to automate script connections...


  4\b4.\b.2\b2.\b.  T\bTh\bhe\be c\bcr\bro\bon\bnt\bta\bab\bb f\bfi\bil\ble\be

  Login as _\bs_\by_\bs_\bo_\bp and create a file in /spider/local_cmd called crontab.
  Edit it with your favourite editor and add a line like this (I have
  included a comment)



       # 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')





  The callsign involved will be the callsign of the cluster node you are
  going to connect to.  This will now check every 10 minutes to see if
  gb7xxx is connected, if it is then nothing will be done.  If it is
  not, then a connect attempt will be started.


  There are probably lots of other things you could use this crontab
  file for.  If you want to know more about it, look at the DXSpider
  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
  per node basis. Also it is possible to isolate a network completely so
  that you get all the benefits of being on that network, but can't pass
  on information from it to any other networks you may be connected to
  (or vice versa).


  5\b5.\b.1\b1.\b.  B\bBa\bas\bsi\bic\bc h\bho\bop\bp c\bco\bon\bnt\btr\bro\bol\bl

  In /spider/data you will find a file called hop_table.pl.  This is the
  file that controls your hop count settings.  It has a set of default
  hops on the various PC frames and also a set for each node you want to
  alter the hops for.  You may be happy with the default settings of
  course, but this powerful tool can help to protect and improve the
  network.  The file will look something like this ...









  #
  # hop table construction
  #

  package DXProt;

  # default hopcount to use
  $def_hopcount = 5;

  # some variable hop counts based on message type
  %hopcount =
  (
   11 => 10,
   16 => 10,
   17 => 10,
   19 => 10,
   21 => 10,
  );


  # the per node hop control thingy


  %nodehops =

   GB7ADX => {            11 => 8,
                          12 => 8,
                          16 => 8,
                          17 => 8,
                          19 => 8,
                          21 => 8,
                     },

   GB7UDX => {            11 => 8,
                          12 => 8,
                          16 => 8,
                          17 => 8,
                          19 => 8,
                          21 => 8,
                     },
   GB7BAA => {
                          11 => 5,
                          12 => 8,
                          16 => 8,
                          17 => 8,
                          19 => 8,
                          21 => 8,
                     },
  };





  Each set of hops is contained within a pair of curly braces and
  contains a series of PC frame types.  PC11 for example is a DX spot.
  The figures here are not exhaustive but should give you a good idea of
  how the file works.


  You can alter this file at any time, including whilst the cluster is
  running.  If you alter the file during runtime, the command _\bl_\bo_\ba_\bd_\b/_\bh_\bo_\bp_\bs
  will bring your changes into effect.



  5\b5.\b.2\b2.\b.  I\bIs\bso\bol\bla\bat\bti\bin\bng\bg n\bne\bet\btw\bwo\bor\brk\bks\bs

  It is possible to isolate networks from each other on a "gateway" node
  using the _\bs_\be_\bt_\b/_\bi_\bs_\bo_\bl_\ba_\bt_\be _\b<_\bn_\bo_\bd_\be_\b__\bc_\ba_\bl_\bl_\b> command.


  The effect of this is to partition an isolated network completely from
  another nodes connected to your node. Your node will appear on and
  otherwise behave normally on every network to which you are connected,
  but data from an isolated network will not cross onto any other
  network or vice versa. However all the spot, announce and WWV traffic
  and personal messages will still be handled locally (because you are a
  real node on all connected networks), that is locally connected users
  will appear on all networks and will be able to access and receive
  information from all networks transparently.  All routed messages will
  be sent as normal, so if a user on one network knows that you are a
  gateway for another network, he can still still send a talk/announce
  etc message via your node and it will be routed across.


  The only limitation currently is that non-private messages cannot be
  passed down isolated links regardless of whether they are generated
  locally. This will change when the bulletin routing facility is added.


  If you use isolate on a node connection you will continue to receive
  all information from the isolated partner, however you will not pass
  any information back to the isolated node.  There are times when you
  would like to forward only spots across a link (maybe during a contest
  for example).  To do this, isolate the node in the normal way and put
  in a filter in the /spider/filter/spots directory to override the
  isolate.  This filter can be very simple and consists of just one line
  ....



       $in = [
               [ 1, 0, 'd', 0, 3]      # The last figure (3) is the hop count
       ];





  There is a lot more on filtering in the next section.


  6\b6.\b.  F\bFi\bil\blt\bte\ber\bri\bin\bng\bg (\b(O\bOl\bld\bd S\bSt\bty\byl\ble\be u\bup\bpt\bto\bo v\bv1\b1.\b.4\b44\b4)\b)

  Filters can be set for spots, announcements and WWV.  You will find
  the directories for these under /spider/filter.  You will find some
  examples in the directories with the suffix _\b._\bi_\bs_\bs_\bu_\be.  There are two
  types of filter, one for incoming information and one for outgoing
  information.  Outgoing filters are in the form _\bC_\bA_\bL_\bL_\bS_\bI_\bG_\bN_\b._\bp_\bl and
  incoming filters are in the form _\bi_\bn_\b__\bC_\bA_\bL_\bL_\bS_\bI_\bG_\bN_\b._\bp_\bl.  Filters can be set
  for both nodes and users.


  All filters work in basically the same way.  There are several
  elements delimited by commas.  There can be many lines in the filter
  and they are read from the top by the program.  When writing a filter
  you need to think carefully about just what you want to achieve.  You
  are either going to write a filter to _\ba_\bc_\bc_\be_\bp_\bt or to _\br_\be_\bj_\be_\bc_\bt.  Think of a
  filter as having 2 main elements.  For a reject filter, you would have
  a line or multiple lines rejecting the things you do not wish to
  receive and then a default line accepting everything else that is not
  included in the filter.  Likewise, for an accept filter, you would
  have a line or multiple lines accepting the things you wish to receive
  and a default line rejecting everthing else.


  In the example below, a user requires a filter that would only return
  SSB spots posted in Europe on the HF bands.  This is achieved by first
  rejecting the CW section of each HF band and rejecting all of VHF, UHF
  etc based on frequency.  Secondly, a filter rule is set based on CQ
  zones to only accept spots posted in Europe.  Lastly, a default filter
  rule is set to reject anything outside the filter.



       $in = [
               [ 0, 0, 'r', # reject all CW spots
                       [
                       1800.0, 1850.0,
                       3500.0, 3600.0,
                       7000.0, 7040.0,
                       14000.0, 14100.0,
                       18068.0, 18110.0,
                       21000.0, 21150.0,
                       24890.0, 24930.0,
                       28000.0, 28180.0,
                       30000.0, 49000000000.0,
                       ] ,1 ],
               [ 1, 11, 'n', [ 14, 15, 16, 20, 33, ], 15 ], #accept EU
               [ 0, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
       ];





  The actual elements of each filter are described more fully in the
  following sections.


  6\b6.\b.1\b1.\b.  S\bSp\bpo\bot\bts\bs

  The elements of the Spot filter are ....



       [action, field_no, sort, possible_values, hops]





  There are 3 elements here to look at.  Firstly, the action element.
  This is very simple and only 2 possible states exist, accept (1) or
  drop (0).


  The second element is the field_no.  There are 13 possiblities to
  choose from here ....








        0 = frequency
        1 = call
        2 = date in unix format
        3 = comment
        4 = spotter
        5 = spotted dxcc country
        6 = spotter's dxcc country
        7 = origin
        8 = spotted itu
        9 = spotted cq
        10 = spotter's itu
        11 = spotter's cq
        12 = callsign of the channel on which the spot has appeared





  The third element tells us what to expect in the fourth element.
  There are 4 possibilities ....



            n - numeric list of numbers e.g. [ 1,2,3 ]
            r - ranges of pairs of numbers e.g. between 2 and 4 or 10 to 17 - [ 2,4, 10,17 ]
            a - an alphanumeric regex
            d - the default rule





  The fifth element is simply the hops to set in this filter.  This
  would only be used if the filter was for a node of course and
  overrides the hop count in hop_table.pl.


  So, let's look at an example spot filter.  It does not matter in the
  example who the filter is to be used for.  So, what do we need in the
  filter?  We need to filter the spots the user/node requires and also
  set a default rule for anything else outside the filter.  Below is a
  simple filter that stops spots arriving from outside Europe.



       $in = [
         [ 0, 4, 'a', '^(K|N|A|W|VE|VA|J)'],  # 0 = drop, 'a' = alphanumeric
         [ 1, 0, 'd', 0, 1 ],                 # 1 = want, 'd' = everything else
                            ];





  So the filter is wrapped in between a pair of square brackets.  This
  tells Spider to look in between these limits.  Then each line is
  contained within its own square brackets and ends with a comma. Lets
  look carefully at the first line.  The first element is 0 (drop).
  Therefore anything we put on this line will not be accepted.  The next
  element is 4.  This means we are filtering by the spotter.  The third
  element is the letter "a" which tells the program to expect an
  alphanumeric expression in the fourth element.  The fourth element is
  a list of letters separated by the pipe symbol.



  What this line does is tell the program to drop any spots posted by
  anyone in the USA, Canada or Japan.


  The second line is the default rule for anything else.  The "d" tells
  us this and the line simply reads... accept anything else.


  You can add as many lines as you need to complete the filter but if
  there are several lines of the same type it is neater to enclose them
  all as one line.  An example of this is where specific bands are set.
  We could write this like this ....



       [ 0,0,'r',[1800.0, 2000.0], 1],
       [ 0,0,'r',[10100.0, 10150.0], 1],
       [ 0,0,'r',[14000.0, 14350.0], 1],
       [ 0,0,'r',[18000.0, 18200.0], 1],





  But the line below achieves the same thing and is more efficient ....



         [ 0, 0, 'r',
           [
             1800.0, 2000.0,         # top band
             10100.0, 10150.0,       # WARC
             14000.0, 14350.0,       # 20m
             18000.0, 18200.0,       # WARC
           [ ,1 ],






  6\b6.\b.2\b2.\b.  A\bAn\bnn\bno\bou\bun\bnc\bce\bem\bme\ben\bnt\bts\bs




       # This is an example announce or filter allowing only West EU announces
       #
       # The element list is:-
       # 0 - callsign of announcer
       # 1 - destination * = all, <callsign> = routed to the node
       # 2 - text
       # 3 - * - sysop, <some text> - special list eg 6MUK, ' ', normal announce
       # 4 - origin
       # 5 - 0 - announce, 1 - wx
       # 6 - channel callsign (the interface from which this spot came)

       $in = [
               [ 1, 0, 'a', '^(P[ABCDE]|DK0WCY|G|M|2|EI|F|ON)' ],
               [ 0, 0, 'd', 0 ]
       ];





  In this example, only the prefixes listed will be allowed.  It is
  possible to be quite specific.  The Dutch prefix "P" is followed by
  several secondary identifiers which are allowed.  So, in the example,
  "PA" or "PE" would be ok but not "PG".  It is even possible to allow
  information from a single callsign.  In the example this is DK0WCY, to
  allow the posting of his Aurora Beacon.


  6\b6.\b.3\b3.\b.  W\bWW\bWV\bV




       # This is an example WWV filter
       #
       # The element list is:-
       # 0 - nominal unix date of spot (ie the day + hour:13)
       # 1 - the hour
       # 2 - SFI
       # 3 - K
       # 4 - I
       # 5 - text
       # 6 - spotter
       # 7 - origin
       # 8 - incoming interface callsign

       # this one doesn't filter, it just sets the hop count to 6 and is
       # used mainly just to override any isolation from WWV coming from
       # the internet.

       $in = [
               [ 1, 0, 'd', 0, 6 ]
       ];





  It should be noted that the filter will start to be used only once a
  user/node has logged out and back in again.

  I am not going to spend any more time on these filters now as they
  will become more "comprehensive" in the near future.


  7\b7.\b.  F\bFi\bil\blt\bte\ber\bri\bin\bng\bg (\b(N\bNe\bew\bw S\bSt\bty\byl\ble\be v\bv1\b1.\b.4\b45\b5 a\ban\bnd\bd l\bla\bat\bte\ber\br)\b)

  7\b7.\b.1\b1.\b.  G\bGe\ben\bne\ber\bra\bal\bl f\bfi\bil\blt\bte\ber\br r\bru\bul\ble\bes\bs

  Upto v1.44 it was not possible for the user to set their own filters.
  From v1.45 though that has all changed.  It is now possible to set
  filters for just about anything you wish.  If you have just updated
  from an older version of DXSpider you will need to update your new
  filters.  You do not need to do anything with your old filters, they
  will be renamed as you update.


  There are 3 basic commands involved in setting and manipulating
  filters.  These are _\ba_\bc_\bc_\be_\bp_\bt, _\br_\be_\bj_\be_\bc_\bt and _\bc_\bl_\be_\ba_\br.  First we will look
  generally at filtering. There are a number of things you can filter in
  the DXSpider system. They all use the same general mechanism.


  In general terms you can create a 'reject' or an 'accept' filter which
  can have up to 10 lines in it. You do this using, for example ...

       accept/spots .....
       reject/spots .....




  where ..... are the specific commands for that type of filter. There
  are filters for spots, wwv, announce, wcy and (for sysops) connects.
  See each different accept or reject command reference for more
  details.

  There is also a command to clear out one or more lines in a filter.
  They are ...



       clear/spots 1
       clear/spots all




  There is clear/xxxx command for each type of filter.


  and you can check that your filters have worked by the command ...




       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.


  7\b7.\b.2\b2.\b.  T\bTy\byp\bpe\bes\bs o\bof\bf f\bfi\bil\blt\bte\ber\br

  There are two main types of filter, _\ba_\bc_\bc_\be_\bp_\bt or _\br_\be_\bj_\be_\bc_\bt.  You can use
  either to achieve the result you want dependent on your own preference
  and which is more simple to do.  It is pointless writing 8 lines of
  reject filters when 1 accept filter would do the same thing!  Each
  filter has 10 lines (of any length) which are tried in order.  If a
  line matches then the action you have specified is taken (ie reject
  means ignore it and accept means take it)


  If you specify reject filters, then any lines that arrive that match
  the filter will be dumped but all else will be accepted.  If you use
  an accept filter, then ONLY the lines in the filter will be accepted
  and all else will be dumped.  For example if you have a single line
  _\ba_\bc_\bc_\be_\bp_\bt filter ...



       accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)




  then you will _\bO_\bN_\bL_\bY get VHF spots _\bf_\br_\bo_\bm or _\bt_\bo CQ zones 14, 15 and 16.

  If you set a reject filter like this ...



       reject/spots on hf/cw




  Then you will get everything _\bE_\bX_\bC_\bE_\bP_\bT HF CW spots.  You could make this
  single filter even more flexible.  For example, if you are interested
  in IOTA and will work it even on CW even though normally you are not
  interested in CW, then you could say ...



       reject/spots on hf/cw and not info iota




  But in that case you might only be interested in iota and say:-



       accept/spots not on hf/cw or info iota




  which achieves exactly the same thing. You should choose one or the
  other until you are comfortable with the way it works. You can mix
  them if you wish (actually you can have an accept AND a reject on the
  same line) but don't attempt this until you are sure you know what you
  are doing!


  You can arrange your filter lines into logical units, either for your
  own understanding or simply convenience. Here is an example ...



       reject/spots 1 on hf/cw
       reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)




  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.


  This is an example where you would use a line number (1 and 2 in this
  case), if you leave the digit out, the system assumes '1'. Digits
  '0'-'9' are available.  This make it easier to see just what filters
  you have set.  It also makes it more simple to remove individual
  filters, during a contest for example.


  You will notice in the above example that the second line has
  brackets.  Look at the line logically.  You can see there are 2
  separate sections to it.  We are saying reject spots that are VHF or
  above _\bA_\bP_\bA_\bR_\bT from those in zones 14, 15 and 16 (either spotted there or
  originated there).  If you did not have the brackets to separate the 2
  sections, then Spider would read it logically from the front and see a
  different expression entirely ...
       (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16




  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'.

  As mentioned earlier, setting several filters can be more flexible
  than simply setting one complex one.  Doing it in this way means that
  if you want to alter your filter you can just redefine or remove one
  or more lines of it or one line. For example ...



       reject/spots 1 on hf/ssb




  would redefine our earlier example, or



       clear/spots 1




  To remove all the filter lines in the spot filter ...



       clear/spots all





  7\b7.\b.3\b3.\b.  F\bFi\bil\blt\bte\ber\br o\bop\bpt\bti\bio\bon\bns\bs

  You can filter in several different ways.  The options are listed in
  the various helpfiles for accept, reject and filter.


  7\b7.\b.4\b4.\b.  D\bDe\bef\bfa\bau\bul\blt\bt f\bfi\bil\blt\bte\ber\brs\bs

  Sometimes all that is needed is a general rule for node connects.
  This can be done with a node_default filter.  This rule will always be
  followed, even if the link is isolated, unless another filter is set
  specifically.  Default rules can be set for nodes and users.  They can
  be set for spots, announces, WWV and WCY.  They can also be used for
  hops.  An example might look like this ...



       accept/spot node_default by_zone 14,15,16,20,33
       set/hops node_default spot 50




  This filter is for spots only, you could set others for announce, WWV
  and WCY.  This filter would work for ALL nodes unless a specific
  filter is written to override it for a particular node.  You can also
  set a user_default should you require.  It is important to note that
  default filters should be considered to be "connected".  By this I
  mean that should you override the default filter for spots, you need
  to add a rule for the hops for spots also.


  7\b7.\b.5\b5.\b.  A\bAd\bdv\bva\ban\bnc\bce\bed\bd f\bfi\bil\blt\bte\ber\bri\bin\bng\bg

  Once you are happy with the results you get, you may like to
  experiment.


  The previous example that filters hf/cw spots and accepts vhf/uhf
  spots from EU can be written with a mixed filter, for example ...



       rej/spot on hf/cw
       acc/spot on 0/30000
       acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)




  Note that the first filter has not been specified with a number.  This
  will automatically be assumed to be number 1.  In this case, we have
  said _\br_\be_\bj_\be_\bc_\bt _\ba_\bl_\bl _\bH_\bF _\bs_\bp_\bo_\bt_\bs _\bi_\bn _\bt_\bh_\be _\bC_\bW _\bs_\be_\bc_\bt_\bi_\bo_\bn _\bo_\bf _\bt_\bh_\be _\bb_\ba_\bn_\bd_\bs _\bb_\bu_\bt _\ba_\bc_\bc_\be_\bp_\bt _\ba_\bl_\bl
  _\bo_\bt_\bh_\be_\br_\bs _\ba_\bt _\bH_\bF_\b.  _\bA_\bl_\bs_\bo _\ba_\bc_\bc_\be_\bp_\bt _\ba_\bn_\by_\bt_\bh_\bi_\bn_\bg _\bi_\bn _\bV_\bH_\bF _\ba_\bn_\bd _\ba_\bb_\bo_\bv_\be _\bs_\bp_\bo_\bt_\bt_\be_\bd _\bi_\bn _\bo_\br _\bb_\by
  _\bo_\bp_\be_\br_\ba_\bt_\bo_\br_\bs _\bi_\bn _\bt_\bh_\be _\bz_\bo_\bn_\be_\bs _\b1_\b4_\b, _\b1_\b5 _\ba_\bn_\bd _\b1_\b6.  Each filter slot actually has a
  'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
  the accept slot.


  It was mentioned earlier that after a reject test that doesn't match,
  the default for following tests is 'accept', the reverse is true for
  'accept'. In the example what happens is that the reject is executed
  first, any non hf/cw spot is passed to the accept line, which lets
  through everything else on HF.  The next filter line lets through just
  VHF/UHF spots from EU.



  8\b8.\b.  O\bOt\bth\bhe\ber\br f\bfi\bil\blt\bte\ber\brs\bs

  8\b8.\b.1\b1.\b.  F\bFi\bil\blt\bte\ber\bri\bin\bng\bg M\bMa\bai\bil\bl

  In the /spider/msg directory you will find a file called
  badmsg.pl.issue.  Rename this to badmsg.pl and edit the file.  The
  original looks something like this ....

















  # the list of regexes for messages that we won't store having
  # received them (bear in mind that we must receive them fully before
  # we can bin them)


  # The format of each line is as follows

  #     type      source             pattern
  #     P/B/F     T/F/O/S            regex

  # type: P - private, B - bulletin (msg), F - file (ak1a bull)
  # source: T - to field, F - from field,  O - origin, S - subject
  # pattern: a perl regex on the field requested

  # Currently only type B and P msgs are affected by this code.
  #
  # The list is read from the top down, the first pattern that matches
  # causes the action to be taken.

  # The pattern can be undef or 0 in which case it will always be selected
  # for the action specified



  package DXMsg;

  @badmsg = (
  );





  I think this is fairly self explanatory.  It is simply a list of
  subject headers that we do not want to pass on to either the users of
  the cluster or the other cluster nodes that we are linked to.  This is
  usually because of rules and regulations pertaining to items for sale
  etc in a particular country.


  8\b8.\b.2\b2.\b.  F\bFi\bil\blt\bte\ber\bri\bin\bng\bg D\bDX\bX c\bca\bal\bll\blo\bou\but\bts\bs (\b(D\bDe\bep\bpr\bri\bic\bca\bat\bte\bed\bd)\b)

  _\bF_\br_\bo_\bm _\bv_\be_\br_\bs_\bi_\bo_\bn _\b1_\b._\b4_\b7_\b, _\bt_\bh_\bi_\bs _\bm_\be_\bt_\bh_\bo_\bd _\bi_\bs _\br_\be_\bp_\bl_\ba_\bc_\be_\bd _\bb_\by _\bt_\bh_\be _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\bs_\be_\bt_\b/_\bb_\ba_\bd_\bd_\bx


  In the same way as mail, there are some types of spot we do not wish
  to pass on to users or linked cluster nodes.  In the /spider/data
  directory you will find a file called baddx.pl.issue.  Rename this to
  baddx.pl and edit the file.  The original looks like this ....

















  # the list of dx spot addresses that we don't store and don't pass on


  package DXProt;

  @baddx = qw

   FROG
   SALE
   FORSALE
   WANTED
   P1RATE
   PIRATE
   TEST
   DXTEST
   NIL
   NOCALL
  );





  Again, this is simply a list of names we do not want to see in the
  spotted field of a DX callout.



  8\b8.\b.3\b3.\b.  F\bFi\bil\blt\bte\ber\bri\bin\bng\bg w\bwo\bor\brd\bds\bs f\bfr\bro\bom\bm t\bte\bex\bxt\bt f\bfi\bie\bel\bld\bds\bs i\bin\bn A\bAn\bnn\bno\bou\bun\bnc\bce\be,\b, T\bTa\bal\blk\bk a\ban\bnd\bd D\bDX\bX s\bsp\bpo\bot\bts\bs

  Create a file in /spider/data called _\bb_\ba_\bd_\bw_\bo_\br_\bd_\bs.  The format is quite
  simple.  Lines beginning with # are ignored so comments can be added.
  An example file is below ...



       # Below is a list of words we do not wish to see on the cluster
       grunge grunged grunging
       splodge splodger splodging
       grince
       fluffle




  Multiple words can be used on the same line as shown.  Obviously these
  are just examples :-)


  You can reload the file from the cluster prompt as sysop with
  load/badwords.


  9\b9.\b.  M\bMa\bai\bil\bl

  DXSpider deals seamlessly with standard AK1A type mail.  It supports
  both personal and bulletin mail and the sysop has additional commands
  to ensure that mail gets to where it is meant.  DXSpider will send
  mail almost immediately, assuming that the target is on line.
  However, only one mail message is dealt with at any one time.  If a
  mail message is already being sent or recieved, then the new message
  will be queued until it has finished.

  The cluster mail is automatically deleted after 30 days unless the
  sysop sets the "keep" flag using the _\bm_\bs_\bg command.

  9\b9.\b.1\b1.\b.  P\bPe\ber\brs\bso\bon\bna\bal\bl m\bma\bai\bil\bl

  Personal mail is sent using the _\bs_\bp command.  This is actually the
  default method of sending mail and so a simple _\bs for send will do.  A
  full list of the send commands and options is in the _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\bs_\be_\bt
  section, so I will not duplicate them here.


  9\b9.\b.2\b2.\b.  B\bBu\bul\bll\ble\bet\bti\bin\bn m\bma\bai\bil\bl

  Bulletin mail is sent by using the _\bs_\bb command.  This is one of the
  most common mistakes users make when sending mail.  They send a
  bulletin mail with _\bs or _\bs_\bp instead of _\bs_\bb and of course the message
  never leaves the cluster.  This can be rectified by the sysop by using
  the _\bm_\bs_\bg command.


  Bulletin addresses can be set using the Forward.pl file.


  9\b9.\b.3\b3.\b.  F\bFo\bor\brw\bwa\bar\brd\bd.\b.p\bpl\bl

  DXSpider receives all and any mail sent to it without any alterations
  needed in files.  Because personal and bulletin mail are treated
  differently, there is no need for a list of accepted bulletin
  addresses.  It is necessary, however, to tell the program which links
  accept which bulletins.  For example, it is pointless sending
  bulletins addresses to "UK" to any links other than UK ones.  The file
  that does this is called forward.pl and lives in /spider/msg.  At
  default, like other spider files it is named forward.pl.issue.  Rename
  it to forward.pl and edit the file to match your requirements.  The
  format is below ...


































  #
  # this is an example message forwarding file for the system
  #
  # The format of each line is as follows
  #
  #     type    to/from/at pattern action  destinations
  #     P/B/F     T/F/A     regex   I/F    [ call [, call ...] ]
  #
  # type: P - private, B - bulletin (msg), F - file (ak1a bull)
  # to/from/at: T - to field, F - from field, A - home bbs, O - origin
  # pattern: a perl regex on the field requested
  # action: I - ignore, F - forward
  # destinations: a reference to an array containing node callsigns
  #
  # if it is non-private and isn't in here then it won't get forwarded
  #
  # Currently only type B msgs are affected by this code.
  #
  # The list is read from the top down, the first pattern that matches
  # causes the action to be taken.
  #
  # The pattern can be undef or 0 in which case it will always be selected
  # for the action specified
  #
  # If the BBS list is undef or 0 and the action is 'F' (and it matches the
  # pattern) then it will always be forwarded to every node that doesn't have
  # it (I strongly recommend you don't use this unless you REALLY mean it, if
  # you allow a new link with this on EVERY bull will be forwarded immediately
  # on first connection)
  #

  package DXMsg;

  @forward = (
  );




  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.


  To force the cluster to reread the file use load/forward



  9\b9.\b.4\b4.\b.  T\bTh\bhe\be m\bms\bsg\bg c\bco\bom\bmm\bma\ban\bnd\bd

  The _\bm_\bs_\bg command is a very powerful and flexible tool for the sysop.
  It allows the sysop to alter to and from fields and make other changes
  to manage the cluster mail.

  Here is a full list of the various options ...











    MSG TO <msgno> <call>     - change TO callsign to <call>
    MSG FRom <msgno> <call>   - change FROM callsign to <call>
    MSG PRrivate <msgno>      - set private flag
    MSG NOPRrivate <msgno>    - unset private flag
    MSG RR <msgno>            - set RR flag
    MSG NORR <msgno>          - unset RR flag
    MSG KEep <msgno>          - set the keep flag (message won't be deleted ever)
    MSG NOKEep <msgno>        - unset the keep flag
    MSG SUbject <msgno> <new> - change the subject to <new>
    MSG WAittime <msgno>      - remove any waiting time for this message
    MSG NOREad <msgno>        - mark message as unread
    MSG REad <msgno>          - mark message as read
    MSG QUeue                 - queue any outstanding bulletins
    MSG QUeue 1               - queue any outstanding private messages




  These commands are simply typed from within the cluster as the sysop
  user.


  9\b9.\b.5\b5.\b.  M\bMe\bes\bss\bsa\bag\bge\be s\bst\bta\bat\btu\bus\bs

  You can check on a message from within the cluster by using the
  command _\bs_\bt_\ba_\bt_\b/_\bm_\bs_\bg.  This will give you additional information on the
  message number including which nodes have received it, which node it
  was received from and when etc.  Here is an example of the output of
  the command ...



       G0VGS de GB7MBC 28-Jan-2001 1308Z >
       stat/msg 6869
               From: GB7DJK
           Msg Time: 26-Jan-2001 1302Z
              Msgno: 6869
             Origin: GB7DJK
               Size: 8012
            Subject: AMSAT 2line KEPS 01025.AMSAT
                 To: UK
       Got it Nodes: GB7BAA, GB7ADX
            Private: 0
       Read Confirm: 0
         Times read: 0
       G0VGS de GB7MBC 28-Jan-2001 1308Z >





  9\b9.\b.6\b6.\b.  F\bFi\bil\blt\bte\ber\bri\bin\bng\bg m\bma\bai\bil\bl

  This is described in the section on _\bO_\bt_\bh_\be_\br _\bf_\bi_\bl_\bt_\be_\br_\bs so I will not
  duplicate it here.


  9\b9.\b.7\b7.\b.  D\bDi\bis\bst\btr\bri\bib\bbu\but\bti\bio\bon\bn l\bli\bis\bst\bts\bs

  Distribution lists are simply a list of users to send certain types of
  mail to.  An example of this is mail you only wish to send to other
  sysops.  In /spider/msg there is a directory called _\bd_\bi_\bs_\bt_\br_\bo.  You put
  any distibution lists in here.  For example, here is a file called
  SYSOP.pl that caters for the UK sysops.


       qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
          GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
          GB7DXK GB7DXI GB7DXS)




  Any mail sent to "sysop" would only be sent to the callsigns in this
  list.


  9\b9.\b.8\b8.\b.  B\bBB\bBS\bS i\bin\bnt\bte\ber\brf\bfa\bac\bce\be

  Spider provides a simple BBS interface.  No input is required from the
  sysop of the cluster at all.  The BBS simply sets the cluster as a BBS
  and pushes any required mail to the cluster.  No mail can flow from
  Spider to the BBS, the interface is one-way.


  Please be careful not to flood the cluster network with unnecessary
  mail.  Make sure you only send mail to the clusters that want it by
  using the Forward.pl file very carefully.


  1\b10\b0.\b.  D\bDa\bat\bta\bab\bba\bas\bse\bes\bs

  Spider allows the creation of local or remote databases.  It supports
  chained databases, allowing several different databases to be scanned
  with one simple command.  Importing of databases is limited at present
  to the standard AK1A databases such as OBLAST and the DB0SDX QSL
  database but will expand with time.


  1\b10\b0.\b.1\b1.\b.  C\bCr\bre\bea\bat\bti\bin\bng\bg d\bda\bat\bta\bab\bba\bas\bse\bes\bs

  Creating a database could not be more simple.  All the commands are
  sent from the cluster prompt as the _\bs_\by_\bs_\bo_\bp user.

  To create a database you use the command _\bd_\bb_\bc_\br_\be_\ba_\bt_\be.  It can be used in
  3 different ways like so ..



       dbcreate <name>




  To simply create a database locally, you just tell the command the
  name of the database.  This does not create the actual database, it
  simply defines it to say that it exists.



       dbcreate <name> chain <name> [<name>...]




  This creates a chained database entry.  The first database will be
  scanned, then the second, the third etc...



       dbcreate <name> remote <name>

  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...



       dbcreate buckmaster remote gb7dxc




  Remote databases cannot be chained, however, the last database in a
  chain can be a remote database.


  1\b10\b0.\b.2\b2.\b.  I\bIm\bmp\bpo\bor\brt\bti\bin\bng\bg d\bda\bat\bta\bab\bba\bas\bse\bes\bs

  The only databases that Spider can currently import are the standard
  AK1A databases such as OBLAST or the DB0SDX qsl and address database.
  This will be added to with time.

  To import such a database, first put the file somewhere useful like
  /tmp and then issue the following command ...



       dbimport oblast /tmp/OBLAST.FUL




  This will update the existing local oblast database or create it if it
  does not exist.


  1\b10\b0.\b.3\b3.\b.  C\bCh\bhe\bec\bck\bki\bin\bng\bg a\bav\bva\bai\bil\bla\bab\bbl\ble\be d\bda\bat\bta\bab\bba\bas\bse\bes\bs

  Once a database is created, you will want to check that it has been
  added.  To do this use the _\bd_\bb_\ba_\bv_\ba_\bi_\bl command.  This will output the
  available databases.  For example ...



       dbavail
       DB Name          Location   Chain
       qsl              Local
       buck             GB7ADX
       hftest           GB7DXM
       G0VGS de GB7MBC  3-Feb-2001 1925Z >





  1\b10\b0.\b.4\b4.\b.  L\bLo\boo\bok\bki\bin\bng\bg u\bup\bp d\bda\bat\bta\bab\bba\bas\bse\bes\bs

  To look for information in a defined database, simply use the _\bd_\bb_\bs_\bh_\bo_\bw
  command, for example ...



       dbshow buckmaster G0YLM




  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
  _\bs_\bh_\bo_\bw command like this ...







  Now you can simply use show/buckmaster or an abreviation.


  1\b10\b0.\b.5\b5.\b.  R\bRe\bem\bmo\bov\bvi\bin\bng\bg d\bda\bat\bta\bab\bba\bas\bse\bes\bs

  To delete an existing database you use the _\bd_\bb_\br_\be_\bm_\bo_\bv_\be command.  For
  example ...



       dbremove oblast




  would remove the oblast database and its associated datafile from the
  system.  There are no warnings or recovery possible from this command.
  If you remove a database it ceases to exist and would have to be
  created from scratch if you still required it.


  1\b11\b1.\b.  I\bIn\bnf\bfo\bor\brm\bma\bat\bti\bio\bon\bn,\b, f\bfi\bil\ble\bes\bs a\ban\bnd\bd u\bus\bse\bef\bfu\bul\bl p\bpr\bro\bog\bgr\bra\bam\bms\bs

  1\b11\b1.\b.1\b1.\b.  M\bMO\bOT\bTD\bD

  One of the more important things a cluster sysop needs to do is to get
  information to his users.  The simplest way to do this is to have a
  banner that is sent to the user on login.  This is know as a "message
  of the day" or "motd".  To set this up, simply create a file in
  /spider/data called motd and edit it to say whatever you want.  It is
  purely a text file and will be sent automatically to anyone logging in
  to the cluster.


  1\b11\b1.\b.2\b2.\b.  D\bDo\bow\bwn\bnt\bti\bim\bme\be m\bme\bes\bss\bsa\bag\bge\be

  If for any reason the cluster is down, maybe for upgrade or
  maintenance but the machine is still running, a message can be sent to
  the user advising them of the fact.  This message lives in the
  /spider/data directory and is called "offline".  Simply create the
  file and edit it to say whatever you wish.  This file will be sent to
  a user attempting to log into the cluster when DXSpider is not
  actually running.


  1\b11\b1.\b.3\b3.\b.  O\bOt\bth\bhe\ber\br t\bte\bex\bxt\bt m\bme\bes\bss\bsa\bag\bge\bes\bs

  You can set other text messages to be read by the user if they input
  the file name.  This could be for news items or maybe information for
  new users.  To set this up, make a directory under /spider called
  _\bp_\ba_\bc_\bk_\bc_\bl_\bu_\bs.  Under this directory you can create files called _\bn_\be_\bw_\bs or
  _\bn_\be_\bw_\bu_\bs_\be_\br for example.  In fact you can create files with any names you
  like.  These can be listed by the user with the command ....


       show/files




  They can be read by the user by typing the command ....



       type news




  If the file they want to read is called _\bn_\be_\bw_\bs.  You could also set an
  alias for this in the Alias file to allow them just to type _\bn_\be_\bw_\bs


  You can also store other information in this directory, either
  directly or nested under directories.  One use for this would be to
  store DX bulletins such as the OPDX bulletins.  These can be listed
  and read by the user.  To keep things tidy, make a directory under
  /spider/packclus called _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn_\bs.  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
  directory you have just created, like this ....



       show/files bulletins





  An example would look like this ....



       sh/files
       bulletins      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
  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
  file called _\bn_\be_\bw_\bs you would simply issue the command ....



       type news




  To look what is in the bulletins directory you issue the command ....






  show/files bulletins
  opdx390      21381 29-Nov-1999 1621Z opdx390.1     1670 29-Nov-1999 1621Z
  opdx390.2     2193 29-Nov-1999 1621Z opdx391      25045 29-Nov-1999 1621Z
  opdx392      35969 29-Nov-1999 1621Z opdx393      15023 29-Nov-1999 1621Z
  opdx394      33429 29-Nov-1999 1621Z opdx394.1     3116 29-Nov-1999 1621Z
  opdx395      24319 29-Nov-1999 1621Z opdx396      32647 29-Nov-1999 1621Z
  opdx396.1     5537 29-Nov-1999 1621Z opdx396.2     6242 29-Nov-1999 1621Z
  opdx397      18433 29-Nov-1999 1621Z opdx398      19961 29-Nov-1999 1621Z
  opdx399      17719 29-Nov-1999 1621Z opdx400      19600 29-Nov-1999 1621Z
  opdx401      27738 29-Nov-1999 1621Z opdx402      18698 29-Nov-1999 1621Z
  opdx403      24994 29-Nov-1999 1621Z opdx404      15685 29-Nov-1999 1621Z
  opdx405      13984 29-Nov-1999 1621Z opdx405.1     4166 29-Nov-1999 1621Z
  opdx406      28934 29-Nov-1999 1621Z opdx407      24153 29-Nov-1999 1621Z
  opdx408      15081 29-Nov-1999 1621Z opdx409      23234 29-Nov-1999 1621Z
  Press Enter to continue, A to abort (16 lines) >




  You can now read any file in this directory using the type command,
  like this ....



       type bulletins/opdx391
       Ohio/Penn DX Bulletin No. 391
       The Ohio/Penn Dx PacketCluster
       DX Bulletin No. 391
       BID: $OPDX.391
       January 11, 1999
       Editor Tedd Mirgliotta, KB8NW
       Provided by BARF-80 BBS Cleveland, Ohio
       Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
       Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
       Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
       & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
       Press Enter to continue, A to abort (508 lines) >




  The page length will of course depend on what you have it set to!


  1\b11\b1.\b.4\b4.\b.  T\bTh\bhe\be A\bAl\bli\bia\bas\bse\bes\bs f\bfi\bil\ble\be

  You will find a file in /spider/cmd/ called Aliases.  First, copy this
  file to /spider/local_cmd/Aliases and edit this file.  You will see
  something like this ...

















  #!/usr/bin/perl

  # provide some standard aliases for commands for terminally
  # helpless ak1a user (helpless in the sense that they never
  # read nor understand help files)

  # This file is automagically reloaded if its modification time is
  # later than the one stored in CmdAlias.pm

  # PLEASE make this file consistant with reality! (the patterns MUST
  # match the filenames!)

  # Don't alter this file, copy it into the local_cmd tree and modify it.
  # This file will be replaced everytime I issue a new release.

  # You only need to put aliases in here for commands that don't work as
  # you desire naturally, e.g sh/dx on its own just works as you expect
  # so you need not add it as an alias.



  package CmdAlias;

  %alias = (
      '?' => [
            '^\?', 'apropos', 'apropos',
          ],
      'a' => [
            '^ann.*/full', 'announce full', 'announce',
            '^ann.*/sysop', 'announce sysop', 'announce',
            '^ann.*/(.*)$', 'announce $1', 'announce',
          ],
          'b' => [
          ],
          'c' => [
          ],
          'd' => [
            '^del', 'kill', 'kill',
            '^del\w*/fu', 'kill full', 'kill',
            '^di\w*/a\w*', 'directory all', 'directory',
            '^di\w*/b\w*', 'directory bulletins', 'directory',
            '^di\w*/n\w*', 'directory new', 'directory',
            '^di\w*/o\w*', 'directory own', 'directory',
            '^di\w*/s\w*', 'directory subject', 'directory',
            '^di\w*/t\w*', 'directory to', 'directory',
            '^di\w*/f\w*', 'directory from', 'directory',
            '^di\w*/(\d+)', 'directory $1', 'directory',
          ],
          'e' => [
          ],
          'f' => [
          ],
          'g' => [
          ],
          'h' => [
          ],
          'i' => [
          ],
          'j' => [
          ],
          'k' => [
          ],
          'l' => [
            '^l$', 'directory', 'directory',
            '^ll$', 'directory', 'directory',
            '^ll/(\d+)', 'directory $1', 'directory',
          ],
          'm' => [
          ],
          'n' => [
            '^news', 'type news', 'type',
          ],
          'o' => [
          ],
          'p' => [
          ],
          'q' => [
            '^q', 'bye', 'bye',
          ],
          'r' => [
            '^r$', 'read', 'read',
            '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
          ],
          's' => [
            '^s/p$', 'send', 'send',
            '^sb$', 'send noprivate', 'send',
            '^set/home$', 'set/homenode', 'set/homenode',
            '^set/nobe', 'unset/beep', 'unset/beep',
            '^set/nohe', 'unset/here', 'unset/here',
            '^set/noan', 'unset/announce', 'unset/announce',
            '^set/nodx', 'unset/dx', 'unset/dx',
            '^set/nota', 'unset/talk', 'unset/talk',
            '^set/noww', 'unset/wwv', 'unset/wwv',
            '^set/nowx', 'unset/wx', 'unset/wx',
            '^sh$', 'show', 'show',
            '^sh\w*/buck', 'dbshow buck', 'dbshow',
            '^sh\w*/bu', 'show/files bulletins', 'show/files',
            '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
            '^sh\w*/c$', 'show/configuration', 'show/configuration',
            '^sh\w*/com', 'dbavail', 'dbavail',
            '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
            '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
            '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
            '^sh\w*/email', 'dbshow email', 'dbshow',
            '^sh\w*/hftest', 'dbshow hftest', 'dbshow',
            '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
            '^sh\w*/qsl', 'dbshow qsl', 'dbshow',
            '^sh\w*/tnc', 'who', 'who',
            '^sh\w*/up', 'show/cluster', 'show/cluster',
            '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
            '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
            '^sp$', 'send', 'send',

      ],
          't' => [
            '^ta$', 'talk', 'talk',
            '^t$', 'talk', 'talk',
          ],
          'u' => [
          ],
          'v' => [
          ],
          'w' => [
            '^wx/full', 'wx full', 'wx',
            '^wx/sysop', 'wx sysop', 'wx',
          ],
          'x' => [
          ],
          'y' => [
          ],
          'z' => [
          ],
  )




  You can create aliases for commands at will.  Beware though, these may
  not always turn out as you think.  Care is needed and you need to test
  the results once you have set an alias.


  1\b11\b1.\b.5\b5.\b.  C\bCo\bon\bns\bso\bol\ble\be.\b.p\bpl\bl

  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.


  To edit the colours, copy /spider/perl/Console.pl to /spider/local and
  edit the file with your favourite editor.


  1\b11\b1.\b.6\b6.\b.  U\bUp\bpd\bda\bat\bti\bin\bng\bg k\bke\bep\bpl\ble\ber\br d\bda\bat\bta\ba

  Spider has a powerful and flexible show/satellite command.  In order
  for this to be accurate, the kepler data has to be updated regularly.
  In general, this data is available as an email or via cluster mail.
  Updating it is simple.  First you need to export the mail message as a
  file.  You do this with the _\be_\bx_\bp_\bo_\br_\bt command from the cluster prompt as
  the sysop.  For example ...



       export 5467 /spider/perl/keps.in




  would export message number 5467 as a file called keps.in in the
  /spider/perl directory.

  Now login to a VT as sysop and cd /spider/perl.  There is a command in
  the perl directory called _\bc_\bo_\bn_\bv_\bk_\be_\bp_\bs_\b._\bp_\bl.  All we need to do now is
  convert the file like so ...



       ./convkeps.pl keps.in




  Now go back to the cluster and issue the command ...



       load/keps




  That is it!  the kepler data has been updated.




  1\b12\b2.\b.  C\bCV\bVS\bS

  CVS stands for "Concurrent Versions System" and the CVS for DXSpider
  is held at Sourceforge.  This means that it is possible to update your
  DXSpider installation to the latest sources by using a few simple
  commands.


  THIS IS NOT FOR THE FAINT HEARTED!!!  ONLY DO THIS IF YOU HAVE A TEST
  INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!!  THIS
  MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!!  YOU
  HAVE BEEN WARNED!!!


  DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE
  CONSEQUENCES!!!


  I am of course assuming that you have a machine with both DXSpider and
  Internet access running.


  BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
  ENTIRE SPIDER TREE!!


  Assuming you are connected to the Internet, you need to login to the
  CVS repository and then update your Spider source.  There are several
  steps which are listed below ...


  First login as the user _\bs_\by_\bs_\bo_\bp.  Next you need to connect to the CVS
  repository.  You do this with the command below ...


  cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login



  You will get a password prompt.  Simply hit return here and your
  machine should return to a normal linux prompt.


  What happens next depends on whether you have an existing installation
  that you want to update with the latest and greatest or whether you
  just want to see what is there and/or run it on a new machine for
  testing.  Either way you will want to change directory to a new place,
  if you want to update an existing installation then I suggest /tmp,
  otherwise choose a suitable place according to the normal installation
  instructions.


  The next step will create a brand new 'spider' directory in your
  current directory.


  cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider



  This command is all on one line.


  Hopefully your screen should show you downloading files.  The -z3
  simply compresses the download to improve speed.  When this has
  finished, you will have exactly the same as if you had untarred a full
  tarball PLUS some extra directories and files that CVS needs to do the
  magic that it does.


  Now if you are doing a new installation, that's it.  Carry on as if
  you have just downloaded and untarred the lastest tarball.


  If you want to upgrade your current installation then do this ...



       tar cvfz /tmp/s.tgz spider
       cd /
       tar xvfzp /tmp/s.tgz




  This is assuming you downloaded to the /tmp directory of course.


  NOTE:  the 'p' on the end of the 'xvfz' is IMPORTANT!   It keeps the
  permissions correct.  YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
  YOU?????

  Remember to recompile the C client (cd /spider/src; make)


  At this point the files have been upgraded.  You can (usually) restrt
  the cluster in your own time.  However, if you attempt to use any new
  commands or features expect it to be fatal!  At least your cluster
  will have been restarted then so it will be too late to worry about
  it!


  Now the magic part!  From now on when you want to update, simply
  connect to the Internet and then, as the user _\bs_\by_\bs_\bo_\bp ...



       cd /spider
       cvs -z3 update -d




  and your files will be updated.  As above, remember to recompile the
  "C" client if it has been updated (CVS will tell you) and restart if
  any of the perl scripts have been altered or added, again, CVS will
  tell you.


  You will find any changes documented in the /spider/Changes file.


  1\b13\b3.\b.  T\bTh\bhe\be D\bDX\bXS\bSp\bpi\bid\bde\ber\br c\bco\bom\bmm\bma\ban\bnd\bd s\bse\bet\bt

  Below is a complete list of commands available from the cluster
  prompt.  Most maintenance tasks are automatic but there are some
  commands that are useful for a sysop.  These are listed below in
  alphabetical order.  The number in brackets following the command name
  is the permissions level needed to use the command.



  1\b13\b3.\b.1\b1.\b.  a\bac\bcc\bce\bep\bpt\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be (\b(0\b0)\b)

  a\bac\bcc\bce\bep\bpt\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Set an accept filter line for announce


  Create an 'accept this announce' line for a filter.

  An accept filter line means that if the announce matches this filter
  it is passed onto the user. See HELP FILTERS for more info. Please
  read this to understand how filters work - it will save a lot of grief
  later on.

  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>
         origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
         origin_itu <numbers>
         origin_zone <numbers>
         by_dxcc <numbers>
         by_itu <numbers>
         by_zone <numbers>
         channel <prefixes>
         wx 1                     filter WX announces
         dest <prefixes>          eg: 6MUK,WDX      (distros)




  some examples:-



         acc/ann dest 6MUK
         acc/ann 2 by_zone 14,15,16
         (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)




  or



         acc/ann by G,M,2




  This filter would only allow announces that were posted buy UK
  stations.  You can use the tag 'all' to accept everything eg:



         acc/ann all




  but this probably for advanced users...



  1\b13\b3.\b.2\b2.\b.  a\bac\bcc\bce\bep\bpt\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)

  a\bac\bcc\bce\bep\bpt\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b]<\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Announce filter sysop
  version


  This version allows a sysop to set a filter for a callsign as well as
  the default for nodes and users eg:-



         accept/ann by G,M,2
         accept/ann input node_default by G,M,2
         accept/ann user_default by G,M,2





  1\b13\b3.\b.3\b3.\b.  a\bac\bcc\bce\bep\bpt\bt/\b/s\bsp\bpo\bot\bts\bs (\b(0\b0)\b)

  a\bac\bcc\bce\bep\bpt\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Set an accept filter line for spots


  Create an 'accept this spot' line for a filter.


  An accept filter line means that if the spot matches this filter it is
  passed onto the user. See HELP FILTERS for more info. Please read this
  to understand how filters work - it will save a lot of grief later on.

  You can use any of the following things in this line:-



         freq <range>           eg: 0/30000 or hf or hf/cw or 6m,4m,2m
         on <range>             same as 'freq'
         call <prefixes>        eg: G,PA,HB9
         info <string>          eg: iota or qsl
         by <prefixes>
         call_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
         call_itu <numbers>
         call_zone <numbers>
         by_dxcc <numbers>
         by_itu <numbers>
         by_zone <numbers>
         origin <prefixes>
         channel <prefixes>





  For frequencies, you can use any of the band names defined in
  SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
  thus: hf/ssb. You can also just have a simple range like: 0/30000 -
  this is more efficient than saying simply: freq HF (but don't get too
  hung up about that)

  some examples:-



         acc/spot 1 on hf/cw
         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:



         acc/spot 3 all




  but this probably for advanced users...


  1\b13\b3.\b.4\b4.\b.  a\bac\bcc\bce\bep\bpt\bt/\b/s\bsp\bpo\bot\bts\bs (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)

  a\bac\bcc\bce\bep\bpt\bt/\b/s\bsp\bpo\bot\bts\bs <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Spot filter sysop version


  This version allows a sysop to set a filter for a callsign as well as
  the default for nodes and users eg:-



         accept/spot db0sue-7 1 by_zone 14,15,16
         accept/spot node_default all
         set/hops node_default 10

         accept/spot user_default by G,M,2





  1\b13\b3.\b.5\b5.\b.  a\bac\bcc\bce\bep\bpt\bt/\b/w\bwc\bcy\by (\b(0\b0)\b)

  a\bac\bcc\bce\bep\bpt\bt/\b/w\bwc\bcy\by [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> set an accept WCY filter


  It is unlikely that you will want to do this, but if you do then you
  can filter on the following fields:-



         by <prefixes>            eg: G,M,2
         origin <prefixes>
         origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
         origin_itu <numbers>
         origin_zone <numbers>
         by_dxcc <numbers>
         by_itu <numbers>
         by_zone <numbers>
         channel <prefixes>





  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).

  This command is really provided for future use.

  See HELP FILTER for information.



  1\b13\b3.\b.6\b6.\b.  a\bac\bcc\bce\bep\bpt\bt/\b/w\bwc\bcy\by (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)

  a\bac\bcc\bce\bep\bpt\bt/\b/w\bwc\bcy\by <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> WCY filter sysop version


  This version allows a sysop to set a filter for a callsign as well as
  the default for nodes and users eg:-



         accept/wcy node_default all
         set/hops node_default 10





  1\b13\b3.\b.7\b7.\b.  a\bac\bcc\bce\bep\bpt\bt/\b/w\bww\bwv\bv (\b(0\b0)\b)

  a\bac\bcc\bce\bep\bpt\bt/\b/w\bww\bwv\bv [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Set an accept WWV filter


  It is unlikely that you will want to do this, but if you do then you
  can filter on the following fields:-



         by <prefixes>            eg: G,M,2
         origin <prefixes>
         origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
         origin_itu <numbers>
         origin_zone <numbers>
         by_dxcc <numbers>
         by_itu <numbers>
         by_zone <numbers>
         channel <prefixes>




  for example



         accept/wwv by_zone 4




  is probably the only useful thing to do (which will only show WWV
  broadcasts by stations in the US).

  See HELP FILTER for information.


  1\b13\b3.\b.8\b8.\b.  a\bac\bcc\bce\bep\bpt\bt/\b/w\bww\bwv\bv (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)

  a\bac\bcc\bce\bep\bpt\bt/\b/w\bww\bwv\bv <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> WWV filter sysop version


  This version allows a sysop to set a filter for a callsign as well as
  the default for nodes and users eg:-




    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





  1\b13\b3.\b.9\b9.\b.  a\ban\bnn\bno\bou\bun\bnc\bce\be (\b(0\b0)\b)

  a\ban\bnn\bno\bou\bun\bnc\bce\be <\b<t\bte\bex\bxt\bt>\b> Send an announcement to local users


  Send an announcement to LOCAL users only, where <text> is the text of
  the announcement you wish to broadcast


  1\b13\b3.\b.1\b10\b0.\b.  a\ban\bnn\bno\bou\bun\bnc\bce\be f\bfu\bul\bll\bl (\b(0\b0)\b)

  a\ban\bnn\bno\bou\bun\bnc\bce\be f\bfu\bul\bll\bl <\b<t\bte\bex\bxt\bt>\b> Send an announcement cluster wide


  This command will send your announcement across the whole cluster
  network.



  1\b13\b3.\b.1\b11\b1.\b.  a\ban\bnn\bno\bou\bun\bnc\bce\be s\bsy\bys\bso\bop\bp (\b(5\b5)\b)

  a\ban\bnn\bno\bou\bun\bnc\bce\be s\bsy\bys\bso\bop\bp <\b<t\bte\bex\bxt\bt>\b>


  Send an announcement to Sysops only


  1\b13\b3.\b.1\b12\b2.\b.  a\bap\bpr\bro\bop\bpo\bos\bs (\b(0\b0)\b)

  a\bap\bpr\bro\bop\bpo\bos\bs <\b<s\bst\btr\bri\bin\bng\bg>\b> Search the help database


  Search the help database for <string> (it isn't case sensitive), and
  print the names of all the commands that may be relevant.


  1\b13\b3.\b.1\b13\b3.\b.  b\bby\bye\be (\b(0\b0)\b)

  b\bby\bye\be Exit from the cluster


  This will disconnect you from the cluster


  1\b13\b3.\b.1\b14\b4.\b.  c\bca\bat\btc\bch\bhu\bup\bp (\b(5\b5)\b)

  c\bca\bat\btc\bch\bhu\bup\bp <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> A\bAl\bll\bl|\b|[\b[<\b<m\bms\bsg\bgn\bno\bo>\b> .\b..\b..\b.]\b] Mark a message as sent


  When you send messages the fact that you have forwarded it to another
  node is remembered so that it isn't sent again. When you have a new
  partner node and you add their callsign to your /spider/msg/forward.pl
  file, all outstanding non-private messages will be forwarded to them.
  This may well be ALL the non-private messages. You can prevent this by
  using these commmands:-

         catchup GB7DJK all
         catchup GB7DJK 300 301 302 303 500-510




  and to undo what you have just done:-



         uncatchup GB7DJK all
         uncatchup GB7DJK 300 301 302 303 500-510




  which will arrange for them to be forward candidates again.

  Order is not important.


  1\b13\b3.\b.1\b15\b5.\b.  c\bcl\ble\bea\bar\br/\b/s\bsp\bpo\bot\bts\bs (\b(0\b0)\b)

  c\bcl\ble\bea\bar\br/\b/s\bsp\bpo\bot\bts\bs [\b[1\b1|\b|a\bal\bll\bl]\b] 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:-



         acc/spot 1 on hf/cw
         acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)




  and you say:-



         clear/spot 1




  you will be left with:-



         acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)




  If you do:



         clear/spot all




  the filter will be completely removed.



  1\b13\b3.\b.1\b16\b6.\b.  c\bco\bon\bnn\bne\bec\bct\bt (\b(5\b5)\b)

  c\bco\bon\bnn\bne\bec\bct\bt <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Start a connection to another DX Cluster


  Start a connection process that will culminate in a new connection to
  the DX cluster <callsign>. This process creates a new 'client' process
  which will use the script in /spider/connect/<callsign> to effect the
  'chat' exchange necessary to traverse the network(s) to logon to the
  cluster <callsign>.


  1\b13\b3.\b.1\b17\b7.\b.  d\bdb\bba\bav\bva\bai\bil\bl (\b(0\b0)\b)

  d\bdb\bba\bav\bva\bai\bil\bl Show a list of all the databases in the system


  The title says it all really, this command lists all the databases
  defined in the system. It is also aliased to SHOW/COMMAND.


  1\b13\b3.\b.1\b18\b8.\b.  d\bdb\bbc\bcr\bre\bea\bat\bte\be (\b(9\b9)\b)

  d\bdb\bbc\bcr\bre\bea\bat\bte\be <\b<n\bna\bam\bme\be>\b> Create a database entry
  d\bdb\bbc\bcr\bre\bea\bat\bte\be <\b<n\bna\bam\bme\be>\b> c\bch\bha\bai\bin\bn <\b<n\bna\bam\bme\be>\b> [\b[<\b<n\bna\bam\bme\be>\b>.\b..\b.]\b] Create a chained database
  entry
  d\bdb\bbc\bcr\bre\bea\bat\bte\be <\b<n\bna\bam\bme\be>\b> r\bre\bem\bmo\bot\bte\be <\b<n\bno\bod\bde\be>\b> Create a remote database entry


  DBCREATE allows you to define a database in the system. It doesn't
  actually create anything, just defines it.

  The databases that are created are simple DB_File hash databases, they
  are therefore already 'indexed'.

  You can define a local database with the first form of the command eg:

  DBCREATE oblast

  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,
  in fact it is usually better to do the above statement first then do
  each of the chained databases.

  Databases can exist offsite. To define a database that lives on
  another node do:

  DBCREATE buckmaster remote gb7dxc

  Remote databases cannot be chained; however, the last database in a a
  chain can be a remote database eg:

  DBCREATE qsl chain gb7dxc

  To see what databases have been defined do:


  DBAVAIL (or it will have been aliased to SHOW/COMMAND)

  It would be normal for you to add an entry into your local Aliases
  file to allow people to use the 'SHOW/<dbname>' style syntax. So you
  would need to add a line like:-



         's' => [
           ..
           ..
           '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
           ..
           ..
          ],




  to allow

  SH/BUCK g1tlh

  to work as they may be used to.

  See DBIMPORT for the importing of existing AK1A format data to
  databases.  See DBSHOW for generic database enquiry


  1\b13\b3.\b.1\b19\b9.\b.  d\bdb\bbi\bim\bmp\bpo\bor\brt\bt (\b(9\b9)\b)

  d\bdb\bbi\bim\bmp\bpo\bor\brt\bt <\b<d\bdb\bbn\bna\bam\bme\be>\b> Import AK1A data into a database


  If you want to import or update data in bulk to a database you can use
  this command. It will either create or update entries into an existing
  database. For example:-

  DBIMPORT oblast /tmp/OBLAST.FUL

  will import the standard OBLAST database that comes with AK1A into the
  oblast database held locally.


  1\b13\b3.\b.2\b20\b0.\b.  d\bdb\bbr\bre\bem\bmo\bov\bve\be (\b(9\b9)\b)

  d\bdb\bbr\bre\bem\bmo\bov\bve\be <\b<d\bdb\bbn\bna\bam\bme\be>\b> Delete a database


  DBREMOVE will completely remove a database entry and also delete any
  data file that is associated with it.

  There is no warning, no comeback, no safety net.

  For example:

  DBREMOVE oblast

  will remove the oblast database from the system and it will also
  remove the associated datafile.

  I repeat:

  There is no warning, no comeback, no safety net.


  You have been warned.


  1\b13\b3.\b.2\b21\b1.\b.  d\bdb\bbs\bsh\bho\bow\bw (\b(0\b0)\b)

  d\bdb\bbs\bsh\bho\bow\bw <\b<d\bdb\bbn\bna\bam\bme\be>\b> <\b<k\bke\bey\by>\b> Display an entry, if it exists, in a database


  This is the generic user interface to the database to the database
  system.  It is expected that the sysop will add an entry to the local
  Aliases file so that users can use the more familiar AK1A style of
  enquiry such as:



         SH/BUCK G1TLH




  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:



         DBSHOW buck G1TLH






  1\b13\b3.\b.2\b22\b2.\b.  d\bde\beb\bbu\bug\bg (\b(9\b9)\b)

  d\bde\beb\bbu\bug\bg Set the cluster program into debug mode


  Executing this command will only have an effect if you are running the
  cluster in debug mode i.e.



               perl -d cluster.pl




  It will interrupt the cluster just after the debug command has
  finished.


  1\b13\b3.\b.2\b23\b3.\b.  d\bdi\bir\bre\bec\bct\bto\bor\bry\by (\b(0\b0)\b)

  d\bdi\bir\bre\bec\bct\bto\bor\bry\by List messages
  d\bdi\bir\bre\bec\bct\bto\bor\bry\by o\bow\bwn\bn List your own messages
  d\bdi\bir\bre\bec\bct\bto\bor\bry\by n\bne\bew\bw List all new messages
  d\bdi\bir\bre\bec\bct\bto\bor\bry\by t\bto\bo <\b<c\bca\bal\bll\bl>\b> List all messages to <call>
  d\bdi\bir\bre\bec\bct\bto\bor\bry\by f\bfr\bro\bom\bm <\b<c\bca\bal\bll\bl>\b> List all messages from <call>
  d\bdi\bir\bre\bec\bct\bto\bor\bry\by s\bsu\bub\bbj\bje\bec\bct\bt <\b<s\bst\btr\bri\bin\bng\bg>\b> List all messages with <string> in subject
  d\bdi\bir\bre\bec\bct\bto\bor\bry\by <\b<n\bnn\bn>\b> List last <nn> messages
  d\bdi\bir\bre\bec\bct\bto\bor\bry\by <\b<f\bfr\bro\bom\bm>\b>-\b-<\b<t\bto\bo>\b> List messages <from> message <to> message


  List the messages in the messages directory.


  If there is a 'p' one space after the message number then it is a
  personal message. If there is a '-' between the message number and the

  You can use shell escape characters such as '*' and '?' in the <call>
  fields.

  You can combine some of the various directory commands together eg:-



          DIR TO G1TLH 5
       or
          DIR SUBJECT IOTA 200-250




  You can abbreviate all the commands to one letter and use ak1a
  syntax:-



          DIR/T G1* 10
          DIR/S QSL 10-100 5






  1\b13\b3.\b.2\b24\b4.\b.  d\bdi\bir\bre\bec\bct\bto\bor\bry\by (\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)

  Works just like the user command except that sysops can see ALL
  messages.


  1\b13\b3.\b.2\b25\b5.\b.  d\bdi\bis\bsc\bco\bon\bnn\bne\bec\bct\bt (\b(8\b8)\b)

  d\bdi\bis\bsc\bco\bon\bnn\bne\bec\bct\bt <\b<c\bca\bal\bll\bl>\b> [\b[<\b<c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Disconnect a user or node


  Disconnect any <call> connected locally


  1\b13\b3.\b.2\b26\b6.\b.  d\bdx\bx (\b(0\b0)\b)

  d\bdx\bx [\b[b\bby\by <\b<c\bca\bal\bll\bl>\b>]\b] <\b<f\bfr\bre\beq\bq>\b> <\b<c\bca\bal\bll\bl>\b> <\b<r\bre\bem\bma\bar\brk\bks\bs>\b> Send a DX spot


  This is how you send a DX Spot to other users. You can, in fact, now
  enter the <freq> and the <call> either way round.



          DX FR0G 144.600
          DX 144.600 FR0G
          DX 144600 FR0G




  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.



     DX FR0G 144600 this is a test




  You can credit someone else by saying:-



          DX by G1TLH FR0G 144.600 he isn't on the cluster




  The <freq> is compared against the available bands set up in the
  cluster.  See SHOW/BANDS for more information.


  1\b13\b3.\b.2\b27\b7.\b.  e\bex\bxp\bpo\bor\brt\bt (\b(9\b9)\b)

  e\bex\bxp\bpo\bor\brt\bt <\b<m\bms\bsg\bgn\bno\bo>\b> <\b<f\bfi\bil\ble\ben\bna\bam\bme\be>\b> 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
  the import directory (/spider/msg/import).

  This command cannot overwrite an existing file. This is to provide
  some measure of security. Any files written will owned by the same
  user as the main cluster, otherwise you can put the new files anywhere
  the cluster can access. For example:-

  EXPORT 2345 /tmp/a


  1\b13\b3.\b.2\b28\b8.\b.  e\bex\bxp\bpo\bor\brt\bt_\b_u\bus\bse\ber\brs\bs (\b(9\b9)\b)

  e\bex\bxp\bpo\bor\brt\bt_\b_u\bus\bse\ber\brs\bs [\b[<\b<f\bfi\bil\ble\ben\bna\bam\bme\be>\b>]\b] Export the users database to ascii


  Export the users database to a file in ascii format. If no filename is
  given then it will export the file to /spider/data/user_asc.

  If the file already exists it will be renamed to <filename>.o. In fact
  up to 5 generations of the file can be kept each one with an extra 'o'
  on the suffix.

  BE WARNED: this will write to any file you have write access to. No
  check is made on the filename (if any) that you specify.


  1\b13\b3.\b.2\b29\b9.\b.  f\bfo\bor\brw\bwa\bar\brd\bd/\b/l\bla\bat\btl\blo\bon\bng\bg (\b(8\b8)\b)

  f\bfo\bor\brw\bwa\bar\brd\bd/\b/l\bla\bat\btl\blo\bon\bng\bg <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> Send latitude and longitude information to
  another cluster


  This command sends all the latitude and longitude information that
  your cluster is holding against callsigns.  One advantage of recieving
  this information is that more locator information is held by you.
  This means that more locators are given on the DX line assuming you
  have _\bs_\be_\bt_\b/_\bd_\bx_\bg_\br_\bi_\bd enabled.  This could be a LOT of information though,
  so it is not recommended on slow links.


  1\b13\b3.\b.3\b30\b0.\b.  f\bfo\bor\brw\bwa\bar\brd\bd/\b/o\bop\bpe\ber\brn\bna\bam\bme\be (\b(1\b1)\b)

  f\bfo\bor\brw\bwa\bar\brd\bd/\b/o\bop\bpe\ber\brn\bna\bam\bme\be <\b<c\bca\bal\bll\bl>\b> Send out information on this <call> to all
  clusters


  This command sends out any information held in the user file which can
  be broadcast in PC41 protocol packets. This information is Name, QTH,
  Location and Homenode. PC41s are only sent for the information that is
  available.


  1\b13\b3.\b.3\b31\b1.\b.  h\bhe\bel\blp\bp (\b(0\b0)\b)

  h\bhe\bel\blp\bp <\b<c\bcm\bmd\bd>\b> 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.

  Look at the APROPOS <string> command which will search the help
  database for the <string> you specify and give you a list of likely
  commands to look at with HELP.


  1\b13\b3.\b.3\b32\b2.\b.  i\bin\bni\bit\bt (\b(5\b5)\b)

  i\bin\bni\bit\bt <\b<n\bno\bod\bde\be c\bca\bal\bll\bl>\b> Re-initialise a link to an AK1A compatible node


  This command attempts to re-initialise a link to a (usually) AK1A node
  that has got confused, usually by a protocol loop of some kind. It may
  work - but you usually will be better off simply disconnecting it (or
  better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
  node>).

  Best of luck - you will need it.


  1\b13\b3.\b.3\b33\b3.\b.  k\bki\bil\bll\bl (\b(0\b0)\b)

  k\bki\bil\bll\bl <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[<\b<m\bms\bsg\bgn\bno\bo>\b> .\b..\b.]\b] Delete a message from the local system


  Delete a message from the local system. You will only be able to
  delete messages that you have originated or been sent (unless you are
  the sysop).


  1\b13\b3.\b.3\b34\b4.\b.  k\bki\bil\bll\bl (\b(5\b5)\b)

  k\bki\bil\bll\bl <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[<\b<m\bms\bsg\bgn\bno\bo>\b> .\b..\b..\b.]\b] Remove or erase a message from the system
  k\bki\bil\bll\bl f\bfr\bro\bom\bm <\b<c\bca\bal\bll\bl>\b> Remove all messages from a callsign
  k\bki\bil\bll\bl t\bto\bo <\b<c\bca\bal\bll\bl>\b> Remove all messages to a callsign


  You can get rid of any message to or originating from your callsign
  using this command. You can remove more than one message at a time.

  As a sysop you can kill any message on the system.


  1\b13\b3.\b.3\b35\b5.\b.  k\bki\bil\bll\bl f\bfu\bul\bll\bl (\b(5\b5)\b)

  k\bki\bil\bll\bl f\bfu\bul\bll\bl <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[<\b<m\bms\bsg\bgn\bno\bo>\b>]\b] Delete a message from the whole cluster

  Delete a message (usually a 'bulletin') from the whole cluster system.

  This uses the subject field, so any messages that have exactly the
  same subject will be deleted. Beware!


  1\b13\b3.\b.3\b36\b6.\b.  l\bli\bin\bnk\bks\bs (\b(0\b0)\b)

  l\bli\bin\bnk\bks\bs Show which nodes are physically connected


  This is a quick listing that shows which links are connected and some
  information about them. See WHO for a list of all connections.



  1\b13\b3.\b.3\b37\b7.\b.  l\blo\boa\bad\bd/\b/a\bal\bli\bia\bas\bse\bes\bs (\b(9\b9)\b)

  l\blo\boa\bad\bd/\b/a\bal\bli\bia\bas\bse\bes\bs Reload the command alias table


  Reload the /spider/cmd/Aliases file after you have editted it. You
  will need to do this if you change this file whilst the cluster is
  running in order for the changes to take effect.



  1\b13\b3.\b.3\b38\b8.\b.  l\blo\boa\bad\bd/\b/b\bba\bad\bdd\bdx\bx (\b(9\b9)\b)

  l\blo\boa\bad\bd/\b/b\bba\bad\bdd\bdx\bx Reload the bad DX table


  Reload the /spider/data/baddx.pl file if you have changed it manually
  whilst the cluster is running. This table contains the DX Calls that,
  if spotted, will not be passed on. FR0G and TEST are classic examples.


  1\b13\b3.\b.3\b39\b9.\b.  l\blo\boa\bad\bd/\b/b\bba\bad\bdm\bms\bsg\bg (\b(9\b9)\b)

  l\blo\boa\bad\bd/\b/b\bba\bad\bdm\bms\bsg\bg Reload the bad message table


  Reload the /spider/msg/badmsg.pl file if you have changed it manually
  whilst the cluster is running. This table contains a number of perl
  regular expressions which are searched for in the fields targetted of
  each message.  If any of them match then that message is immediately
  deleted on receipt.


  1\b13\b3.\b.4\b40\b0.\b.  l\blo\boa\bad\bd/\b/b\bba\bad\bdw\bwo\bor\brd\bds\bs (\b(9\b9)\b)

  l\blo\boa\bad\bd/\b/b\bba\bad\bdw\bwo\bor\brd\bds\bs Reload the badwords file


  Reload the /spider/data/badwords file if you have changed it manually
  whilst the cluster is running. This file contains a list of words
  which, if found on certain text portions of PC protocol, will cause
  those protocol frames to be rejected. It will all put out a message if
  any of these words are used on the announce, dx and talk commands. The
  words can be one or more on a line, lines starting with '#' are
  ignored.





  1\b13\b3.\b.4\b41\b1.\b.  l\blo\boa\bad\bd/\b/b\bba\ban\bnd\bds\bs (\b(9\b9)\b)

  l\blo\boa\bad\bd/\b/b\bba\ban\bnd\bds\bs Reload the band limits table


  Reload the /spider/data/bands.pl file if you have changed it manually
  whilst the cluster is running.


  1\b13\b3.\b.4\b42\b2.\b.  l\blo\boa\bad\bd/\b/c\bcm\bmd\bd_\b_c\bca\bac\bch\bhe\be (\b(9\b9)\b)

  l\blo\boa\bad\bd/\b/c\bcm\bmd\bd_\b_c\bca\bac\bch\bhe\be 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.


  1\b13\b3.\b.4\b43\b3.\b.  l\blo\boa\bad\bd/\b/f\bfo\bor\brw\bwa\bar\brd\bd (\b(9\b9)\b)

  l\blo\boa\bad\bd/\b/f\bfo\bor\brw\bwa\bar\brd\bd Reload the msg forwarding routing table

  Reload the /spider/msg/forward.pl file if you have changed it manually
  whilst the cluster is running.


  1\b13\b3.\b.4\b44\b4.\b.  l\blo\boa\bad\bd/\b/m\bme\bes\bss\bsa\bag\bge\bes\bs (\b(9\b9)\b)

  l\blo\boa\bad\bd/\b/m\bme\bes\bss\bsa\bag\bge\bes\bs Reload the system messages file


  If you change the /spider/perl/Messages file (usually whilst
  fiddling/writing ne commands) you can have them take effect during a
  cluster session by executing this command. You need to do this if get
  something like :-

  unknown message 'xxxx' in lang 'en'


  1\b13\b3.\b.4\b45\b5.\b.  l\blo\boa\bad\bd/\b/p\bpr\bre\bef\bfi\bix\bxe\bes\bs (\b(9\b9)\b)

  l\blo\boa\bad\bd/\b/p\bpr\bre\bef\bfi\bix\bxe\bes\bs Reload the prefix table


  Reload the /spider/data/prefix_data.pl file if you have changed it
  manually whilst the cluster is running.


  1\b13\b3.\b.4\b46\b6.\b.  m\bme\ber\brg\bge\be (\b(5\b5)\b)

  m\bme\ber\brg\bge\be <\b<n\bno\bod\bde\be>\b> [\b[<\b<n\bno\bo s\bsp\bpo\bot\bts\bs>\b>/\b/<\b<n\bno\bo w\bww\bwv\bv>\b>]\b] Ask for the latest spots and WWV


  MERGE allows you to bring your spot and wwv database up to date. By
  default it will request the last 10 spots and 5 WWVs from the node you
  select. The node must be connected locally.

  You can request any number of spots or wwv and although they will be
  appended to your databases they will not duplicate any that have
  recently been added (the last 2 days for spots and last month for WWV
  data).

  1\b13\b3.\b.4\b47\b7.\b.  m\bms\bsg\bg (\b(9\b9)\b)

  m\bms\bsg\bg <\b<c\bcm\bmd\bd>\b> <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[d\bda\bat\bta\ba .\b..\b..\b.]\b] Alter various message parameters


  Alter message parameters like To, From, Subject, whether private or
  bulletin or return receipt (RR) is required or whether to keep this
  message from timing out.



         MSG TO <msgno> <call>     - change TO callsign to <call>
         MSG FRom <msgno> <call>   - change FROM callsign to <call>
         MSG PRrivate <msgno>      - set private flag
         MSG NOPRrivate <msgno>    - unset private flag
         MSG RR <msgno>            - set RR flag
         MSG NORR <msgno>          - unset RR flag
         MSG KEep <msgno>          - set the keep flag (message won't be deleted ever)
         MSG NOKEep <msgno>        - unset the keep flag
         MSG SUbject <msgno> <new> - change the subject to <new>
         MSG WAittime <msgno>      - remove any waitting time for this message
         MSG NOREad <msgno>        - mark message as unread
         MSG REad <msgno>          - mark message as read
         MSG QUeue                 - queue any outstanding bulletins
         MSG QUeue 1               - queue any outstanding private messages




  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.


  1\b13\b3.\b.4\b48\b8.\b.  p\bpc\bc (\b(8\b8)\b)

  p\bpc\bc <\b<c\bca\bal\bll\bl>\b> <\b<t\bte\bex\bxt\bt>\b> Send text (eg PC Protocol) to <call>


  Send some arbitrary text to a locally connected callsign. No
  processing is done on the text. This command allows you to send PC
  Protocol to unstick things if problems arise (messages get stuck etc).
  eg:-

  pc gb7djk PC33^GB7TLH^GB7DJK^400^

  You can also use in the same way as a talk command to a connected user
  but without any processing, added of "from <blah> to <blah>" or
  whatever.

  pc G1TLH Try doing that properly!!!


  1\b13\b3.\b.4\b49\b9.\b.  p\bpi\bin\bng\bg (\b(1\b1)\b)

  p\bpi\bin\bng\bg <\b<n\bno\bod\bde\be>\b> Check the link quality between nodes


  his command allows you to send a frame to another cluster node on the
  network and get a return frame.  The time it takes to do this is a
  good indication of the quality of the link.  The actual time it takes
  is output to the console in seconds.  Any visible cluster node can be
  PINGed.

  1\b13\b3.\b.5\b50\b0.\b.  r\brc\bcm\bmd\bd (\b(1\b1)\b)

  r\brc\bcm\bmd\bd <\b<n\bno\bod\bde\be c\bca\bal\bll\bl>\b> <\b<c\bcm\bmd\bd>\b> Send a command to another DX cluster


  This command allows you to send nearly any command to another DX
  Cluster node that is connected to the system.

  Whether you get any output is dependant on a) whether the other system
  knows that the node callsign of this cluster is in fact a node b)
  whether the other system is allowing RCMDs from this node and c)
  whether you have permission to send this command at all.


  1\b13\b3.\b.5\b51\b1.\b.  r\bre\bea\bad\bd (\b(0\b0)\b)

  r\bre\bea\bad\bd Read the next unread personal message addressed to you
  r\bre\bea\bad\bd <\b<m\bms\bsg\bgn\bno\bo>\b> Read the specified message


  You can read any messages that are sent as 'non-personal' and also any
  message either sent by or sent to your callsign.



  1\b13\b3.\b.5\b52\b2.\b.  r\bre\bea\bad\bd (\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)

  r\bre\bea\bad\bd <\b<m\bms\bsg\bgn\bno\bo>\b> Read a message on the system


  As a sysop you may read any message on the system


  1\b13\b3.\b.5\b53\b3.\b.  r\bre\bej\bje\bec\bct\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be

  r\bre\bej\bje\bec\bct\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Set a reject filter for announce


  Create an 'reject this announce' line for a filter.

  An reject filter line means that if the announce matches this filter
  it is passed onto the user. See HELP FILTERS for more info. Please
  read this to understand how filters work - it will save a lot of grief
  later on.

  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>
         origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
         origin_itu <numbers>
         origin_zone <numbers>
         by_dxcc <numbers>
         by_itu <numbers>
         by_zone <numbers>
         channel <prefixes>
         wx 1                     filter WX announces
         dest <prefixes>          eg: 6MUK,WDX      (distros)





  some examples:-



         rej/ann by_zone 14,15,16 and not by G,M,2




  You can use the tag 'all' to reject everything eg:



         rej/ann all




  but this probably for advanced users...


  1\b13\b3.\b.5\b54\b4.\b.  r\bre\bej\bje\bec\bct\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)

  r\bre\bej\bje\bec\bct\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Announce filter sysop
  version


  This version allows a sysop to set a filter for a callsign as well as
  the default for nodes and users eg:-



         reject/ann by G,M,2
         reject/ann input node_default by G,M,2
         reject/ann user_default by G,M,2





  1\b13\b3.\b.5\b55\b5.\b.  r\bre\bej\bje\bec\bct\bt/\b/s\bsp\bpo\bot\bts\bs (\b(0\b0)\b)

  r\bre\bej\bje\bec\bct\bt/\b/s\bsp\bpo\bot\bts\bs [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Set a reject filter line for spots


  Create a 'reject this spot' line for a filter.

  A reject filter line means that if the spot matches this filter it is
  dumped (not passed on). See HELP FILTERS for more info. Please read
  this to understand how filters work - it will save a lot of grief
  later on.

  You can use any of the following things in this line:-













    freq <range>           eg: 0/30000 or hf or hf/cw or 6m,4m,2m
    on <range>             same as 'freq'
    call <prefixes>        eg: G,PA,HB9
    info <string>          eg: iota or qsl
    by <prefixes>
    call_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
    call_itu <numbers>
    call_zone <numbers>
    by_dxcc <numbers>
    by_itu <numbers>
    by_zone <numbers>
    origin <prefixes>
    channel <prefixes>




  For frequencies, you can use any of the band names defined in
  SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
  thus: hf/ssb. You can also just have a simple range like: 0/30000 -
  this is more efficient than saying simply: on HF (but don't get too
  hung up about that)

  some examples:-



         rej/spot 1 on hf
         rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)




  You can use the tag 'all' to reject everything eg:



         rej/spot 3 all




  but this probably for advanced users...


  1\b13\b3.\b.5\b56\b6.\b.  r\bre\bej\bje\bec\bct\bt/\b/s\bsp\bpo\bot\bts\bs (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)

  r\bre\bej\bje\bec\bct\bt/\b/s\bsp\bpo\bot\bts\bs <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Reject spot filter sysop
  version


  This version allows a sysop to set a filter for a callsign as well as
  the default for nodes and users eg:-



         reject/spot db0sue-7 1 by_zone 14,15,16
         reject/spot node_default all
         set/hops node_default 10

         reject/spot user_default by G,M,2





  1\b13\b3.\b.5\b57\b7.\b.  r\bre\bej\bje\bec\bct\bt/\b/w\bwc\bcy\by (\b(0\b0)\b)

  r\bre\bej\bje\bec\bct\bt/\b/w\bwc\bcy\by [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Set a reject WCY filter


  It is unlikely that you will want to do this, but if you do then you
  can filter on the following fields:-



         by <prefixes>            eg: G,M,2
         origin <prefixes>
         origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
         origin_itu <numbers>
         origin_zone <numbers>
         by_dxcc <numbers>
         by_itu <numbers>
         by_zone <numbers>
         channel <prefixes>




  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).

  This command is really provided for future use.

  See HELP FILTER for information.


  1\b13\b3.\b.5\b58\b8.\b.  r\bre\bej\bje\bec\bct\bt/\b/w\bwc\bcy\by (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)

  r\bre\bej\bje\bec\bct\bt/\b/w\bwc\bcy\by <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> WCY reject filter sysop
  version


  This version allows a sysop to set a filter for a callsign as well as
  the default for nodes and users eg:-

  reject/wcy gb7djk all


  1\b13\b3.\b.5\b59\b9.\b.  r\bre\bej\bje\bec\bct\bt/\b/w\bww\bwv\bv (\b(0\b0)\b)

  r\bre\bej\bje\bec\bct\bt/\b/w\bww\bwv\bv [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Set a reject WWV filter


  It is unlikely that you will want to do this, but if you do then you
  can filter on the following fields:-



         by <prefixes>            eg: G,M,2
         origin <prefixes>
         origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
         origin_itu <numbers>
         origin_zone <numbers>
         by_dxcc <numbers>
         by_itu <numbers>
         by_zone <numbers>
         channel <prefixes>



  for example



         reject/wwv by_zone 14,15,16




  is probably the only useful thing to do (which will only show WWV
  broadcasts by stations in the US).

  See HELP FILTER for information.


  1\b13\b3.\b.6\b60\b0.\b.  r\bre\bej\bje\bec\bct\bt/\b/w\bww\bwv\bv (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)

  r\bre\bej\bje\bec\bct\bt/\b/w\bww\bwv\bv <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> WWV reject filter sysop
  version


  This version allows a sysop to set a filter for a callsign as well as
  the default for nodes and users eg:-



         reject/wwv db0sue-7 1 by_zone 4
         reject/wwv node_default all

         reject/wwv user_default by W





  1\b13\b3.\b.6\b61\b1.\b.  r\bre\bep\bpl\bly\by (\b(0\b0)\b)

  r\bre\bep\bpl\bly\by Reply (privately) to the last message that you have read
  r\bre\bep\bpl\bly\by <\b<m\bms\bsg\bgn\bno\bo>\b> Reply (privately) to the specified message
  r\bre\bep\bpl\bly\by B\bB <\b<m\bms\bsg\bgn\bno\bo>\b> Reply as a Bulletin to the specified message
  r\bre\bep\bpl\bly\by N\bNO\bOP\bPr\bri\biv\bva\bat\bte\be <\b<m\bms\bsg\bgn\bno\bo>\b> Reply as a Bulletin to the specified message
  r\bre\bep\bpl\bly\by R\bRR\bR <\b<m\bms\bsg\bgn\bno\bo>\b> Reply to the specified message with read receipt


  You can reply to a message and the subject will automatically have
  "Re:" inserted in front of it, if it isn't already present.

  You can also use all the extra qualifiers such as RR, PRIVATE,
  NOPRIVATE, B that you can use with the SEND command (see SEND for
  further details)


  1\b13\b3.\b.6\b62\b2.\b.  s\bse\ben\bnd\bd (\b(0\b0)\b)

  s\bse\ben\bnd\bd <\b<c\bca\bal\bll\bl>\b> [\b[<\b<c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Send a message to one or more callsigns
  s\bse\ben\bnd\bd R\bRR\bR <\b<c\bca\bal\bll\bl>\b> Send a message and ask for a read receipt
  s\bse\ben\bnd\bd C\bCO\bOP\bPY\bY <\b<m\bms\bsg\bgn\bno\bo>\b> <\b<c\bca\bal\bll\bl>\b> Send a copy of a  message to someone
  s\bse\ben\bnd\bd P\bPR\bRI\bIV\bVA\bAT\bTE\bE <\b<c\bca\bal\bll\bl>\b> Send a personal message
  s\bse\ben\bnd\bd N\bNO\bOP\bPR\bRI\bIV\bVA\bAT\bTE\bE <\b<c\bca\bal\bll\bl>\b> Send a message to all stations


  All the SEND commands will create a message which will be sent either
  to an individual callsign or to one of the 'bulletin' addresses.

  SEND <call> on its own acts as though you had typed SEND PRIVATE, that
  is it will mark the message as personal and send it to the cluster
  node that that callsign is connected to.

  You can have more than one callsign in all of the SEND commands.

  You can have multiple qualifiers so that you can have for example:-



         SEND RR COPY 123 PRIVATE G1TLH G0RDI




  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.

  SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP
  is an alias for SEND PRIVATE


  1\b13\b3.\b.6\b63\b3.\b.  s\bse\bet\bt/\b/a\bad\bdd\bdr\bre\bes\bss\bs (\b(0\b0)\b)

  s\bse\bet\bt/\b/a\bad\bdd\bdr\bre\bes\bss\bs <\b<y\byo\bou\bur\br_\b_a\bad\bdd\bdr\bre\bes\bss\bs>\b> Record your postal address


  Literally, record your address details on the cluster.


  1\b13\b3.\b.6\b64\b4.\b.  s\bse\bet\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be (\b(0\b0)\b)

  s\bse\bet\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be Allow announce messages


  Allow announce messages to arrive at your terminal.


  1\b13\b3.\b.6\b65\b5.\b.  s\bse\bet\bt/\b/a\bar\brc\bcl\blu\bus\bst\bte\ber\br (\b(5\b5)\b)

  s\bse\bet\bt/\b/a\bar\brc\bcl\blu\bus\bst\bte\ber\br <\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 an AR-
  Cluster type node


  Set the node_call as an AR-Cluster type node


  1\b13\b3.\b.6\b66\b6.\b.  s\bse\bet\bt/\b/b\bba\bad\bdd\bdx\bx (\b(8\b8)\b)

  s\bse\bet\bt/\b/b\bba\bad\bdd\bdx\bx <\b<c\bca\bal\bll\bl>\b> Stop words we do not wish to see in the callsign
  field of a dx spot being propagated


  Setting a word as 'baddx' will prevent spots with that word in the
  callsign field of a DX spot from going any further. They will not be
  displayed and they will not be sent onto other nodes.

  The word must be wriiten in full, no wild cards are allowed eg:-



         set/baddx FORSALE VIDEO FR0G




  To allow a word again, use the following command ...

         unset/baddx VIDEO





  1\b13\b3.\b.6\b67\b7.\b.  s\bse\bet\bt/\b/b\bba\bad\bdn\bno\bod\bde\be (\b(6\b6)\b)

  s\bse\bet\bt/\b/b\bba\bad\bdn\bno\bod\bde\be <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> Stop spots from this node_call being
  propagated


  Setting a callsign as a 'badnode' will prevent spots from that node
  going any further. They will not be displayed and they will not be
  sent onto other nodes.

  The call can be a full or partial call (or a prefix), eg:-



         set/badnode K1TTT




  will stop anything from K1TTT (including any SSID's)



         unset/badnode K1TTT




  will allow spots from him again.

  Use with extreme care. This command may well be superceded by
  FILTERing.


  1\b13\b3.\b.6\b68\b8.\b.  s\bse\bet\bt/\b/b\bba\bad\bds\bsp\bpo\bot\btt\bte\ber\br (\b(8\b8)\b)

  s\bse\bet\bt/\b/b\bba\bad\bds\bsp\bpo\bot\btt\bte\ber\br <\b<c\bca\bal\bll\bl>\b> Stop spots from this callsign being propagated


  Setting a callsign as a 'badspotter' will prevent spots from this
  callsign going any further. They will not be displayed and they will
  not be sent onto other nodes.

  The call must be written in full, no wild cards are allowed eg:-



         set/badspotter VE2STN




  will stop anything from VE2STN. If you want SSIDs as well then you
  must enter them specifically.



         unset/badspotter VE2STN


  will allow spots from him again.

  Use with extreme care. This command may well be superceded by
  FILTERing.


  1\b13\b3.\b.6\b69\b9.\b.  s\bse\bet\bt/\b/b\bbe\bee\bep\bp (\b(0\b0)\b)

  s\bse\bet\bt/\b/b\bbe\bee\bep\bp Add beeps to terminal messages


  Add a beep to DX and other terminal messages.


  1\b13\b3.\b.7\b70\b0.\b.  s\bse\bet\bt/\b/c\bcl\blx\bx (\b(5\b5)\b)

  s\bse\bet\bt/\b/c\bcl\blx\bx <\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 CLX type
  node


  Set the node_call as a CLX type node


  1\b13\b3.\b.7\b71\b1.\b.  s\bse\bet\bt/\b/d\bde\beb\bbu\bug\bg (\b(9\b9)\b)

  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>


  1\b13\b3.\b.7\b72\b2.\b.  s\bse\bet\bt/\b/d\bdx\bx (\b(0\b0)\b)

  s\bse\bet\bt/\b/d\bdx\bxAllow DX messages to arrive at your terminal


  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
  type node


  Set the node_call as a DXNet type node


  1\b13\b3.\b.7\b75\b5.\b.  s\bse\bet\bt/\b/e\bec\bch\bho\bo (\b(0\b0)\b)

  s\bse\bet\bt/\b/e\bec\bch\bho\bo Make the cluster echo your input


  If you are connected via a telnet session, different implimentations
  of telnet handle echo differently depending on whether you are
  connected via port 23 or some other port. You can use this command to
  change the setting appropriately.

  You can remove the echo with the _\bu_\bn_\bs_\be_\bt_\b/_\be_\bc_\bh_\bo command

  The setting is stored in your user profile.

  YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.


  1\b13\b3.\b.7\b76\b6.\b.  s\bse\bet\bt/\b/h\bhe\ber\bre\be (\b(0\b0)\b)

  s\bse\bet\bt/\b/h\bhe\ber\bre\be Set the here flag


  Let others on the cluster know you are here by only displaying your
  callsign.  If you are away from your terminal you can use the
  _\bu_\bn_\bs_\be_\bt_\b/_\bh_\be_\br_\be command to let people know you are away.  This simply puts
  brackets around your callsign to indicate you are not available.


  1\b13\b3.\b.7\b77\b7.\b.  s\bse\bet\bt/\b/h\bho\bom\bme\ben\bno\bod\bde\be (\b(0\b0)\b)

  s\bse\bet\bt/\b/h\bho\bom\bme\ben\bno\bod\bde\be <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> Set your home cluster


  Tell the cluster system where you normally connect to. Any Messages
  sent to you will normally find their way there should you not be
  connected.  eg:-



         SET/HOMENODE gb7djk





  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


  Set the hop count for a particular type of broadcast for a node.

  This command allows you to set up special hop counts for a node for
  currently: announce, spots, wwv and wcy broadcasts.



       eg:
         set/hops gb7djk ann 10
         set/hops gb7mbc spots 20




  Set SHOW/HOPS for information on what is already set. This command
  creates a filter and works in conjunction with the filter system.


  1\b13\b3.\b.7\b79\b9.\b.  s\bse\bet\bt/\b/i\bis\bso\bol\bla\bat\bte\be (\b(9\b9)\b)

  s\bse\bet\bt/\b/i\bis\bso\bol\bla\bat\bte\be <\b<n\bno\bod\bde\be c\bca\bal\bll\bl>\b> Isolate a node from the rest of the network



  Connect a node to your system in such a way that you are a full
  protocol member of its network and can see all spots on it, but
  nothing either leaks out from it nor goes back into from the rest of
  the nodes connected to you.

  You can potentially connect several nodes in this way.

  You can see which nodes are isolated with the show/isolate (1)
  command.

  You can remove the isolation with the command unset/isolate.


  1\b13\b3.\b.8\b80\b0.\b.  s\bse\bet\bt/\b/l\bla\ban\bng\bgu\bua\bag\bge\be (\b(0\b0)\b)

  s\bse\bet\bt/\b/l\bla\ban\bng\bgu\bua\bag\bge\be <\b<l\bla\ban\bng\bgu\bua\bag\bge\be>\b> Set the language you wish to use


  You can select the language that you want the cluster to use.
  Currently the languages available are _\be_\bn (English) and _\bn_\bl (Dutch).


  1\b13\b3.\b.8\b81\b1.\b.  s\bse\bet\bt/\b/l\blo\boc\bca\bat\bti\bio\bon\bn (\b(0\b0)\b)

  s\bse\bet\bt/\b/l\blo\boc\bca\bat\bti\bio\bon\bn <\b<l\bla\bat\bt a\ban\bnd\bd l\blo\bon\bng\bg>\b> Set your latitude and longitude


  You can set your latitude and longitude manually or alternatively use
  the _\bs_\be_\bt_\b/_\bq_\br_\ba command which will do the conversion for you.



         set/location 54 04 N 2 02 E






  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


  In order to get accurate headings and such like you must tell the
  system what your latitude and longitude is. If you have not yet done a
  SET/QRA then this command will set your QRA locator for you. For
  example:-



         SET/LOCATION 52 22 N 0 57 E





  1\b13\b3.\b.8\b83\b3.\b.  s\bse\bet\bt/\b/l\blo\bog\bgi\bin\bni\bin\bnf\bfo\bo (\b(0\b0)\b)

  s\bse\bet\bt/\b/l\blo\bog\bgi\bin\bni\bin\bnf\bfo\bo Show logins and logouts of nodes and users


  Show users and nodes when they log in and out of the local cluster.
  You can stop these messages by using the _\bu_\bn_\bs_\be_\bt_\b/_\bl_\bo_\bg_\bi_\bn_\bi_\bn_\bf_\bo command.


  1\b13\b3.\b.8\b84\b4.\b.  s\bse\bet\bt/\b/l\blo\boc\bck\bko\bou\but\bt (\b(9\b9)\b)

  s\bse\bet\bt/\b/l\blo\boc\bck\bko\bou\but\bt <\b<c\bca\bal\bll\bl>\b> Stop a callsign connecting to the cluster


  You can show who is locked out with the _\bs_\bh_\bo_\bw_\b/_\bl_\bo_\bc_\bk_\bo_\bu_\bt command.  To
  allow the user to connect again, use the _\bu_\bn_\bs_\be_\bt_\b/_\bl_\bo_\bc_\bk_\bo_\bu_\bt command.


  1\b13\b3.\b.8\b85\b5.\b.  s\bse\bet\bt/\b/n\bna\bam\bme\be (\b(0\b0)\b)

  s\bse\bet\bt/\b/n\bna\bam\bme\be <\b<y\byo\bou\bur\br_\b_n\bna\bam\bme\be>\b> Set your name


  Tell the cluster what your name is, eg:-



         set/name Dirk





  1\b13\b3.\b.8\b86\b6.\b.  s\bse\bet\bt/\b/n\bno\bod\bde\be (\b(9\b9)\b)

  s\bse\bet\bt/\b/n\bno\bod\bde\be <\b<c\bca\bal\bll\bl>\b> [\b[<\b<c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Make the callsign an AK1A cluster


  Tell the system that the call(s) are to be treated as AK1A cluster and
  fed PC Protocol rather normal user commands.

  From version 1.41 you can also set the following types of cluster



         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.


  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)

  s\bse\bet\bt/\b/o\bob\bbs\bsc\bco\bou\bun\bnt\bt <\b<c\bco\bou\bun\bnt\bt>\b> <\b<n\bno\bod\bde\be c\bca\bal\bll\bl>\b> Set the 'pump-up' obsolescence
  counter


  From version 1.35 onwards neighbouring nodes are pinged at regular
  intervals (see SET/PINGINTERVAL), usually 300 seconds or 5 minutes.
  There is a 'pump-up' counter which is decremented on every outgoing
  ping and then reset to the 'obscount' value on every incoming ping.
  The default value of this parameter is 2.

  What this means is that a neighbouring node will be pinged twice at
  (default) 300 second intervals and if no reply has been heard just
  before what would be the third attempt, that node is disconnected.

  If a ping is heard then the obscount is reset to the full value. Using
  default values, if a node has not responded to a ping within 15
  minutes, it is disconnected.
  1\b13\b3.\b.8\b88\b8.\b.  s\bse\bet\bt/\b/p\bpa\bag\bge\be (\b(0\b0)\b)

  s\bse\bet\bt/\b/p\bpa\bag\bge\be <\b<n\bn>\b> Set the number of lines per page


  Tell the system how many lines you wish on a page when the number of
  lines of output from a command is more than this. The default is 20.
  Setting it explicitly to 0 will disable paging.



         SET/PAGE 30
         SET/PAGE 0




  The setting is stored in your user profile.



  1\b13\b3.\b.8\b89\b9.\b.  s\bse\bet\bt/\b/p\bpa\bas\bss\bsw\bwo\bor\brd\bd (\b(9\b9)\b)

  s\bse\bet\bt/\b/p\bpa\bas\bss\bsw\bwo\bor\brd\bd <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> <\b<s\bst\btr\bri\bin\bng\bg>\b> Set a users password


  The password for a user can only be set by a full sysop. The string
  can contain any characters but any spaces are removed (you can type in
  spaces - but they won't appear in the password). You can see the
  result with STAT/USER.  The password is the usual 30 character baycom
  type password.


  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
  nodes


  As from version 1.35 all neighbouring nodes are pinged at regular
  intervals in order to determine the rolling quality of the link and,
  in future, to affect routing decisions. The default interval is 300
  secs or 5 minutes.

  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
  seconds for numbers greater than that.

  This is used also to help determine when a link is down at the far end
  (as certain cluster software doesn't always notice), see SET/OBSCOUNT
  for more information.


  1\b13\b3.\b.9\b91\b1.\b.  s\bse\bet\bt/\b/p\bpr\bri\biv\bvi\bil\ble\beg\bge\be (\b(9\b9)\b)

  s\bse\bet\bt/\b/p\bpr\bri\biv\bvi\bil\ble\beg\bge\be <\b<n\bn>\b> <\b<c\bca\bal\bll\bl>\b> [\b[<\b<c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Set the privilege level on a
  call


  Set the privilege level on a callsign. The privilege levels that
  pertain to commands are as default:-




    0 - normal user
    1 - allow remote nodes normal user RCMDs
    5 - various privileged commands (including shutdown, but not disc-
        connect), the normal level for another node.
    8 - more privileged commands (including disconnect)
    9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
        LEVEL.




  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.


  1\b13\b3.\b.9\b92\b2.\b.  s\bse\bet\bt/\b/s\bsp\bpi\bid\bde\ber\br (\b(5\b5)\b)

  s\bse\bet\bt/\b/s\bsp\bpi\bid\bde\ber\br <\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 DXSpider
  type node


  Set the node_call as a DXSpider type node


  1\b13\b3.\b.9\b93\b3.\b.  s\bse\bet\bt/\b/s\bsy\bys\bs_\b_q\bqr\bra\ba (\b(9\b9)\b)

  s\bse\bet\bt/\b/s\bsy\bys\bs_\b_q\bqr\bra\ba <\b<l\blo\boc\bca\bat\bto\bor\br>\b> Set your cluster QRA locator


  1\b13\b3.\b.9\b94\b4.\b.  s\bse\bet\bt/\b/q\bqr\bra\ba (\b(0\b0)\b)

  s\bse\bet\bt/\b/q\bqr\bra\ba <\b<l\blo\boc\bca\bat\bto\bor\br>\b> Set your QRA locator


  Tell the system what your QRA (or Maidenhead) locator is. If you have
  not done a SET/LOCATION then your latitude and longitude will be set
  roughly correctly (assuming your locator is correct ;-). For example:-



         SET/QRA JO02LQ





  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


  Tell the system where your are.  For example:-



         set/qth East Dereham, Norfolk





  1\b13\b3.\b.9\b96\b6.\b.  s\bse\bet\bt/\b/t\bta\bal\blk\bk (\b(0\b0)\b)

  s\bse\bet\bt/\b/t\bta\bal\blk\bk Allow talk messages to be seen at your console


  Allow talk messages to arrive at your console.  You can switch off
  talks with the _\bu_\bn_\bs_\be_\bt_\b/_\bt_\ba_\bl_\bk command.


  1\b13\b3.\b.9\b97\b7.\b.  s\bse\bet\bt/\b/w\bwc\bcy\by (\b(0\b0)\b)

  s\bse\bet\bt/\b/w\bwc\bcy\by Allow WCY messages to be seen at your console


  Allow WCY information to be seen at your console.  You can switch off
  WCY messages with the _\bu_\bn_\bs_\be_\bt_\b/_\bw_\bc_\by command.


  1\b13\b3.\b.9\b98\b8.\b.  s\bse\bet\bt/\b/w\bww\bwv\bv (\b(0\b0)\b)

  s\bse\bet\bt/\b/w\bww\bwv\bv Allow WWV messages to be seen at your console


  Allow WWV information to be seen at your console.  You can switch off
  WWV messages with the _\bu_\bn_\bs_\be_\bt_\b/_\bw_\bw_\bv command.


  1\b13\b3.\b.9\b99\b9.\b.  s\bse\bet\bt/\b/w\bwx\bx (\b(0\b0)\b)

  s\bse\bet\bt/\b/w\bwx\bx Allow WX messages to be seen at your console


  Allow WX information to be seen at your console.  You can switch off
  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


  Display all the bad dx callsigns in the system, see SET/BADDX for more
  information.


  1\b13\b3.\b.1\b10\b01\b1.\b.  s\bsh\bho\bow\bw/\b/b\bba\bad\bdn\bno\bod\bde\be (\b(6\b6)\b)

  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


  Display all the bad spotter's callsigns in the system, see
  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)

  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\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:-




       on <band>       - eg 160m 20m 2m 23cm 6mm
       on <region>     - eg hf vhf uhf shf      (see SHOW/BANDS)

       <number>        - the number of spots you want
       <from>-<to>     - <from> spot no <to> spot no in
                         the selected list

       <prefix>        - for a spotted callsign beginning with <prefix>
       *<suffix>       - for a spotted callsign ending in <suffix>
       *<string>*      - for a spotted callsign containing <string>

       day <number>    - starting <number> days ago
       day <from>-<to> - <from> days <to> days ago

       info <text>     - any spots containing <text> in the info or remarks

       by <call>       - any spots spotted by <call> (spotter <call>
                               is the same).

       qsl             - this automatically looks for any qsl info on the call
                         held in the spot database.

       iota [<iota>]   - If the iota island number is missing it will
                         look for the string iota and anything which looks like
                         an iota island number. If you specify then it will look
                         for that island.

       qra [<locator>] - this will look for the specific locator if
                         you specify one or else anything that looks like a locator.




  e.g.




          SH/DX 9m0
          SH/DX on 20m info iota
          SH/DX 9a on vhf day 30
          SH/DX rf1p qsl
          SH/DX iota
          SH/DX iota eu-064
          SH/DX qra jn86

  1\b13\b3.\b.1\b10\b05\b5.\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


  This command takes the <prefix> (which can be a full or partial
  callsign if desired), looks up which internal country number it is and
  then displays all the spots as per SH/DX for that country.

  The options for SHOW/DX also apply to this command.  e.g.




          SH/DXCC G
          SH/DXCC W on 20m info iota





  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)

  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


  SHOW/FILES on its own will show you a list of the various fileareas
  available on the system. To see the contents of a particular file area
  type:-



          SH/FILES <filearea>




  where <filearea> is the name of the filearea you want to see the
  contents of.

  You can also use shell globbing characters like '*' and '?' in a
  string to see a selection of files in a filearea eg:-



          SH/FILES bulletins arld*




  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)

  s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br Show the filters you have set


  Show the contents of all the filters that are set by you. This command
  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)

  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)

  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


  This command shows the hop counts set up for a node. You can specify
  which category you want to see. If you leave the category out then all
  the categories will be listed.


  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)

  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)

  s\bsh\bho\bow\bw/\b/l\blo\boc\bck\bko\bou\but\bt Show a list of excluded callsigns


  Show a list of callsigns that have been excluded (locked out) of the
  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)

  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


  This command outputs a short section of the system log.  On its own it
  will output a general logfile.  With the optional callsign it will
  show output from the log associated with that callsign.


  1\b13\b3.\b.1\b11\b13\b3.\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


  Show the Moon rise and set times for a (list of) prefixes or
  callsigns, together with the azimuth and elevation of the sun
  currently at those locations.

  If you don't specify any prefixes or callsigns, it will show the times
  for your QTH (assuming you have set it with either SET/LOCATION or
  SET/QRA), together with the current azimuth and elevation.

  In addition, it will show the gain or loss dB relative to the nominal
  distance of 385,000Km due to the ellipsoidal nature of the orbit.

  If all else fails it will show the Moonrise and set times for the node
  that you are connected to.

  For example:-





    SH/MOON
    SH/MOON G1TLH W5UN





  1\b13\b3.\b.1\b11\b14\b4.\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>


  This command allow you to estimate the likelihood of you contacting a
  station with the prefix you have specified. The output assumes a
  modest power of 20dBW and receiver sensitivity of -123dBm (about
  0.15muV/10dB SINAD)

  The result predicts the most likely operating frequencies and signal
  levels for high frequency (shortwave) radio propagation paths on
  specified days of the year and hours of the day. It is most useful for
  paths between 250 km and 6000 km, but can be used with reduced
  accuracy for paths shorter or longer than this.

  The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
  used to predict the MUF given the predicted flux, day of the year,
  hour of the day and geographic coordinates of the transmitter and
  receiver. This routine is reasonably accurate for the purposes here,
  with a claimed RMS error of 3.8 MHz, but much smaller and less complex
  than the programs used by major shortwave broadcasting organizations,
  such as the Voice of America.

  The command will display some header information detailing its
  assumptions, together with the locations, latitude and longitudes and
  bearings. It will then show UTC (UT), local time at the other end
  (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
  (Zen) and the likely signal strengths. Then for each frequency for
  which the system thinks there is a likelihood of a circuit it prints a
  value.

  The value is currently a likely S meter reading based on the
  conventional 6dB / S point scale. If the value has a '+' appended it
  means that it is 1/2 an S point stronger. If the value is preceeded by
  an 'm' it means that there is likely to be much fading and by an 's'
  that the signal is likely to be noisy.

  By default SHOW/MUF will show the next two hours worth of data. You
  can specify anything up to 24 hours worth of data by appending the no
  of hours required after the prefix. For example:-



         SH/MUF W




  produces:








    RxSens: -123 dBM SFI: 159   R: 193   Month: 10   Day: 21
    Power :   20 dBW    Distance:  6283 km    Delay: 22.4 ms
    Location                       Lat / Long           Azim
    East Dereham, Norfolk          52 41 N 0 57 E         47
    United-States-W                43 0 N 87 54 W        299
    UT LT  MUF Zen  1.8  3.5  7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
    18 23 11.5 -35  mS0+ mS2   S3
    19  0 11.2 -41  mS0+ mS2   S3




  indicating that you will have weak, fading circuits on top band and
  80m but usable signals on 40m (about S3).

  inputing:-



         SH/MUF W 24




  will get you the above display, but with the next 24 hours worth of
  propagation data.



         SH/MUF W L 24
         SH/MUF W 24 Long




  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.


  1\b13\b3.\b.1\b11\b15\b5.\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


  Show the type and version (if connected) of the nodes specified on the
  command line. If no callsigns are specified then a sorted list of all
  the non-user callsigns known to the system will be displayed.


  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)

  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


  This command takes the <callsign> (which can be a full or partial
  callsign or a prefix), looks up which internal country number it is
  and then displays all the relevant prefixes for that country together
  with the internal country no, the CQ and ITU regions.

  See also SHOW/DXCC





  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)

  s\bsh\bho\bow\bw/\b/p\bpr\bro\bog\bgr\bra\bam\bm Show the locations of all the included program modules


  Show the name and location where every program module was load from.
  This is useful for checking where you think you have loaded a .pm file
  from.


  1\b13\b3.\b.1\b11\b18\b8.\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


  This is a multipurpose command that allows you either to calculate the
  distance and bearing between two locators or (if only one locator is
  given on the command line) the distance and beraing from your station
  to the locator. For example:-



       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
  character locators.

  It is also possible to convert a latitude and longitude to a locator
  by using this command with a latitude and longitude as an argument,
  for example:-



       SH/QRA 52 41 N 0 58 E





  1\b13\b3.\b.1\b11\b19\b9.\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


  This command queries the QRZ callbook server on the internet and
  returns any information available for that callsign. This service is
  provided for users of this software by http://www.qrz.com


  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)

  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>


  This command allows you to see to which node the callsigns specified
  are connected. It is a sort of inverse sh/config.



    sh/route n2tly





  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)

  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


  Show the tracking data from your location to the satellite of your
  choice from now on for the next few hours.

  If you use this command without a satellite name it will display a
  list of all the satellites known currently to the system.

  If you give a name then you can obtain tracking data of all the passes
  that start and finish 5 degrees below the horizon. As default it will
  give information for the next three hours for every five minute
  period.

  You can alter the number of hours and the step size, within certain
  limits.

  Each pass in a period is separated with a row of '-----' characters

  So for example:-



       SH/SAT AO-10
       SH/SAT FENGYUN1 12 2





  1\b13\b3.\b.1\b12\b22\b2.\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


  Show the sun rise and set times for a (list of) prefixes or callsigns,
  together with the azimuth and elevation of the sun currently at those
  locations.

  If you don't specify any prefixes or callsigns, it will show the times
  for your QTH (assuming you have set it with either SET/LOCATION or
  SET/QRA), together with the current azimuth and elevation.

  If all else fails it will show the sunrise and set times for the node
  that you are connected to.

  For example:-



         SH/SUN
         SH/SUN G1TLH K9CW ZS





  1\b13\b3.\b.1\b12\b23\b3.\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


  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\b12\b24\b4.\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


  Display the most recent WCY information that has been received by the
  system


  1\b13\b3.\b.1\b12\b25\b5.\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\b26\b6.\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


  Shutdown the cluster and disconnect all the users.  If you have Spider
  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)

  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


  This is a very simple yet powerful command for the sysop.  It allows
  you to issue commands as if you were a different user.  This is very
  useful for the kind of things that users seem to always get wrong..
  like home_node for example.


  1\b13\b3.\b.1\b12\b28\b8.\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


  Show the internal status of a database descriptor.

  Depending on your privilege level you will see more or less
  information.  This command is unlikely to be of much use to anyone
  other than a sysop.




  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)

  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


  Show the internal status of the channel object either for the channel
  that you are on or else for the callsign that you asked for.

  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)

  s\bst\bta\bat\bt/\b/m\bms\bsg\bg <\b<m\bms\bsg\bgn\bno\bo>\b> Show the status of a message


  This command shows the internal status of a message and includes
  information such as to whom it has been forwarded, its size, origin
  etc etc.


  1\b13\b3.\b.1\b13\b31\b1.\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


  Shows the full contents of a user record including all the secret
  flags and stuff.

  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)

  s\bsy\bys\bso\bop\bp Regain your privileges if you login remotely


  The system automatically reduces your privilege level to that of a
  normal user if you login in remotely. This command allows you to
  regain your normal privilege level. It uses the normal system: five
  numbers are returned that are indexes into the character array that is
  your assigned password (see SET/PASSWORD). The indexes start from
  zero.

  You are expected to return a string which contains the characters
  required in the correct order. You may intersperse those characters
  with others to obscure your reply for any watchers. For example (and
  these values are for explanation :-):



         password = 012345678901234567890123456789
         > sysop
         22 10 15 17 3




  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.


  1\b13\b3.\b.1\b13\b33\b3.\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>
  t\bta\bal\blk\bk <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> >\b> <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> [\b[<\b<t\bte\bex\bxt\bt>\b>]\b] Send a text message to
  <callsign> via <node_call>


  Send a short message to any other station that is visible on the
  cluster system. You can send it to anyone you can see with a
  SHOW/CONFIGURATION command, they don't have to be connected locally.

  The second form of TALK is used when other cluster nodes are connected
  with restricted information. This usually means that they don't send
  the user information usually associated with logging on and off the
  cluster.

  If you know that G3JNB is likely to be present on GB7TLH, but you can
  only see GB7TLH in the SH/C list but with no users, then you would use
  the second form of the talk message.

  If you want to have a ragchew with someone you can leave the text
  message out and the system will go into 'Talk' mode. What this means
  is that a short message is sent to the recipient telling them that you
  are in a 'Talking' frame of mind and then you just type - everything
  you send will go to the station that you asked for.

  All the usual announcements, spots and so on will still come out on
  your terminal.

  If you want to do something (such as send a spot) you precede the
  normal command with a '/' character, eg:-



          /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
          /HELP talk




  To leave talk mode type:



          /EX





  1\b13\b3.\b.1\b13\b34\b4.\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


  Type out the contents of a file in a filearea. So, for example, in
  filearea 'bulletins' you want to look at file 'arld051' you would
  enter:-


          TYPE bulletins/arld051




  See also SHOW/FILES to see what fileareas are available and a list of
  content.


  1\b13\b3.\b.1\b13\b35\b5.\b.  w\bwh\bho\bo (\b(0\b0)\b)

  w\bwh\bho\bo Show who is physically connected locally


  This is a quick listing that shows which callsigns are connected and
  what sort of connection they have


  1\b13\b3.\b.1\b13\b36\b6.\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\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)

  w\bwx\bx s\bsy\bys\bso\bop\bp <\b<t\bte\bex\bxt\bt>\b> Send a weather message to other clusters only


  Send a weather message only to other cluster nodes and not to general
  users.