- The DXSpider Installation and Administration Manual
+ The DXSpider Administration Manual v1.47
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.47 (Revision 1.30), April 2001
+
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
- 1. Installation (Original version by Iain Philipps, G0RDI)
-
- 1.1 Introduction
- 1.2 Preparation
- 1.3 Installing the software
- 1.4 Setting callsigns etc
- 1.5 Starting up for the first time
- 1.6 The Client program
-
- 2. Quick installation guide (Linux version)
-
- 3. Configuration
+ 1. Hop control
- 3.1 Allowing ax25 connects from users
- 3.2 Allowing telnet connects from users
- 3.3 Setting up telnet connects (from 1.47 onwards)
- 3.4 Setting up for AGW Engine (1.47 onwards)
- 3.5 Setting up node connects
- 3.6 Connection scripts
- 3.7 Starting the connection
- 3.8 Telnet echo
+ 1.1 Basic hop control
+ 1.2 Isolating networks
- 4. Automating things
+ 2. Filtering (Old Style upto v1.44)
- 4.1 Autostarting the cluster
- 4.2 The crontab file
+ 2.1 Spots
+ 2.2 Announcements
+ 2.3 WWV
- 5. Hop control
+ 3. Filtering (New Style v1.45 and later)
- 5.1 Basic hop control
- 5.2 Isolating networks
+ 3.1 General filter rules
+ 3.2 Types of filter
+ 3.3 Filter options
+ 3.4 Default filters
+ 3.5 Advanced filtering
- 6. Filtering (Old Style upto v1.44)
+ 4. Other filters
- 6.1 Spots
- 6.2 Announcements
- 6.3 WWV
+ 4.1 Filtering Mail
+ 4.2 Filtering DX callouts (Depricated)
+ 4.3 Filtering words from text fields in Announce, Talk and DX spots
- 7. Filtering (New Style v1.45 and later)
+ 5. Mail
- 7.1 General filter rules
- 7.2 Types of filter
- 7.3 Filter options
- 7.4 Default filters
- 7.5 Advanced filtering
+ 5.1 Personal mail
+ 5.2 Bulletin mail
+ 5.3 Forward.pl
+ 5.4 The msg command
+ 5.5 Message status
+ 5.6 Filtering mail
+ 5.7 Distribution lists
+ 5.8 BBS interface
- 8. Other filters
+ 6. Databases
- 8.1 Filtering Mail
- 8.2 Filtering DX callouts (Depricated)
- 8.3 Filtering words from text fields in Announce, Talk and DX spots
+ 6.1 Creating databases
+ 6.2 Importing databases
+ 6.3 Checking available databases
+ 6.4 Looking up databases
+ 6.5 Removing databases
- 9. Mail
+ 7. Information, files and useful programs
- 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
+ 7.1 MOTD
+ 7.2 Downtime message
+ 7.3 Other text messages
+ 7.4 The Aliases file
+ 7.5 Console.pl
+ 7.6 Updating kepler data
+ 7.7 The QRZ callbook
- 10. Databases
+ 8. CVS
- 10.1 Creating databases
- 10.2 Importing databases
- 10.3 Checking available databases
- 10.4 Looking up databases
- 10.5 Removing databases
+ 9. The DXSpider command set
- 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
- 11.7 The QRZ callbook
-
- 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/configuration (0)
- 13.104 show/configuration/node (0)
- 13.105 show/connect (1)
- 13.106 show/date (0)
- 13.107 show/debug (9)
- 13.108 show/dx (0)
- 13.109 show/dxcc (0)
- 13.110 show/files (0)
- 13.111 show/filter (0)
- 13.112 show/filter (extended for sysops) (5)
- 13.113 show/hops (8)
- 13.114 show/isolate (1)
- 13.115 show/lockout (9)
- 13.116 show/log (8)
- 13.117 show/moon (0)
- 13.118 show/muf (0)
- 13.119 show/node (1)
- 13.120 show/prefix (0)
- 13.121 show/program (5)
- 13.122 show/qra (0)
- 13.123 show/qrz (0)
- 13.124 show/route (0)
- 13.125 show/satellite (0)
- 13.126 show/sun (0)
- 13.127 show/time (0)
- 13.128 show/wcy (0)
- 13.129 show/wwv (0)
- 13.130 shutdown (5)
- 13.131 spoof (9)
- 13.132 stat/db (5)
- 13.133 stat/channel (5)
- 13.134 stat/msg (5)
- 13.135 stat/user (5)
- 13.136 sysop (0)
- 13.137 talk (0)
- 13.138 type (0)
- 13.139 who (0)
- 13.140 wx (0)
- 13.141 wx (enhanced for sysops) (5)
+ 9.1 accept/announce (0)
+ 9.2 accept/announce (extended for sysops) (8)
+ 9.3 accept/spots (0)
+ 9.4 accept/spots (extended for sysops) (8)
+ 9.5 accept/wcy (0)
+ 9.6 accept/wcy (extended for sysops) (8)
+ 9.7 accept/wwv (0)
+ 9.8 accept/wwv (extended for sysops) (8)
+ 9.9 announce (0)
+ 9.10 announce full (0)
+ 9.11 announce sysop (5)
+ 9.12 apropos (0)
+ 9.13 bye (0)
+ 9.14 catchup (5)
+ 9.15 clear/spots (0)
+ 9.16 connect (5)
+ 9.17 dbavail (0)
+ 9.18 dbcreate (9)
+ 9.19 dbimport (9)
+ 9.20 dbremove (9)
+ 9.21 dbshow (0)
+ 9.22 debug (9)
+ 9.23 directory (0)
+ 9.24 directory (extended for sysops) (5)
+ 9.25 disconnect (8)
+ 9.26 dx (0)
+ 9.27 export (9)
+ 9.28 export_users (9)
+ 9.29 forward/latlong (8)
+ 9.30 forward/opername (1)
+ 9.31 help (0)
+ 9.32 init (5)
+ 9.33 kill (0)
+ 9.34 kill (5)
+ 9.35 kill full (5)
+ 9.36 links (0)
+ 9.37 load/aliases (9)
+ 9.38 load/baddx (9)
+ 9.39 load/badmsg (9)
+ 9.40 load/badwords (9)
+ 9.41 load/bands (9)
+ 9.42 load/cmd_cache (9)
+ 9.43 load/forward (9)
+ 9.44 load/messages (9)
+ 9.45 load/prefixes (9)
+ 9.46 merge (5)
+ 9.47 msg (9)
+ 9.48 pc (8)
+ 9.49 ping (1)
+ 9.50 rcmd (1)
+ 9.51 read (0)
+ 9.52 read (extended for sysops) (5)
+ 9.53 reject/announce
+ 9.54 reject/announce (extended for sysops) (8)
+ 9.55 reject/spots (0)
+ 9.56 reject/spots (extended for sysops) (8)
+ 9.57 reject/wcy (0)
+ 9.58 reject/wcy (extended for sysops) (8)
+ 9.59 reject/wwv (0)
+ 9.60 reject/wwv (extended for sysops) (8)
+ 9.61 reply (0)
+ 9.62 send (0)
+ 9.63 set/address (0)
+ 9.64 set/announce (0)
+ 9.65 set/arcluster (5)
+ 9.66 set/baddx (8)
+ 9.67 set/badnode (6)
+ 9.68 set/badspotter (8)
+ 9.69 set/beep (0)
+ 9.70 set/clx (5)
+ 9.71 set/debug (9)
+ 9.72 set/dx (0)
+ 9.73 set/dxgrid (0)
+ 9.74 set/dxnet (5)
+ 9.75 set/echo (0)
+ 9.76 set/here (0)
+ 9.77 set/homenode (0)
+ 9.78 set/hops (8)
+ 9.79 set/isolate (9)
+ 9.80 set/language (0)
+ 9.81 set/location (0)
+ 9.82 set/sys_location (9)
+ 9.83 set/logininfo (0)
+ 9.84 set/lockout (9)
+ 9.85 set/name (0)
+ 9.86 set/node (9)
+ 9.87 set/obscount (9)
+ 9.88 set/page (0)
+ 9.89 set/password (9)
+ 9.90 set/pinginterval (9)
+ 9.91 set/privilege (9)
+ 9.92 set/spider (5)
+ 9.93 set/sys_qra (9)
+ 9.94 set/qra (0)
+ 9.95 set/qth (0)
+ 9.96 set/talk (0)
+ 9.97 set/wcy (0)
+ 9.98 set/wwv (0)
+ 9.99 set/wx (0)
+ 9.100 show/baddx (1)
+ 9.101 show/badnode (6)
+ 9.102 show/badspotter (1)
+ 9.103 show/configuration (0)
+ 9.104 show/configuration/node (0)
+ 9.105 show/connect (1)
+ 9.106 show/date (0)
+ 9.107 show/debug (9)
+ 9.108 show/dx (0)
+ 9.109 show/dxcc (0)
+ 9.110 show/files (0)
+ 9.111 show/filter (0)
+ 9.112 show/filter (extended for sysops) (5)
+ 9.113 show/hops (8)
+ 9.114 show/isolate (1)
+ 9.115 show/lockout (9)
+ 9.116 show/log (8)
+ 9.117 show/moon (0)
+ 9.118 show/muf (0)
+ 9.119 show/node (1)
+ 9.120 show/prefix (0)
+ 9.121 show/program (5)
+ 9.122 show/qra (0)
+ 9.123 show/qrz (0)
+ 9.124 show/route (0)
+ 9.125 show/satellite (0)
+ 9.126 show/sun (0)
+ 9.127 show/time (0)
+ 9.128 show/wcy (0)
+ 9.129 show/wwv (0)
+ 9.130 shutdown (5)
+ 9.131 spoof (9)
+ 9.132 stat/db (5)
+ 9.133 stat/channel (5)
+ 9.134 stat/msg (5)
+ 9.135 stat/user (5)
+ 9.136 sysop (0)
+ 9.137 talk (0)
+ 9.138 type (0)
+ 9.139 who (0)
+ 9.140 wx (0)
+ 9.141 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\bli\bip\bpp\bps\bs,\b, G\bG0\b0R\bRD\bDI\bI)\b)
-
- 1\b1.\b.1\b1.\b. I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
-
- This section describes the installation of DX Spider v1.46 on a RedHat
- Linux Distribution. Wherever possible I will try to include
- differences for other distributions. I do not intend to try and cover
- the installation of Linux or the setup of the AX25 utilities. If you
- need help on this then read Iains original installation guide that
- comes with the Spider distribution.
-
-
- I am assuming a general knowledge of Linux and its commands. You
- 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. Earlier versions of
- Spider required perl 5.004, however it is now _\bS_\bT_\bR_\bO_\bN_\bG_\bL_\bY recommended
- that you use at least version 5.005_03 as this is the version being
- used in the development of Spider.
-
-
- In addition to the standard Red Hat distribution you will require the
- following modules from http://www.cpan.org/CPAN.html ...
-
-
-
- +\bo Data-Dumper-2.101.tar.gz
-
- +\bo TimeDate-1.10.tar.gz
-
- +\bo IO-1.20.tar.gz (for perl 5.00403 and lower)
-
- +\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.46 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.46.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 any file in /spider/perl, they are overwritten with every
- release. Any files or commands you place in /spider/local or
- /spider/local_cmd will automagically be used in preference to the ones
- in /spider/perl EVEN while the cluster is running!
-
-
- Save the new file and change directory to ../perl ....
-
-
-
- $ 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.46
- 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/src. Now issue the following command ...
-
- $ ./client
-
-
-
-
-
- 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.
-
-
- 1\b1.\b.6\b6.\b. T\bTh\bhe\be C\bCl\bli\bie\ben\bnt\bt p\bpr\bro\bog\bgr\bra\bam\bm
-
- In earlier versions of Spider, all the processes were Perl scripts.
- This was fine but with a lot of users your computer memory would soon
- 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.
-
-
-
- 2\b2.\b. Q\bQu\bui\bic\bck\bk i\bin\bns\bst\bta\bal\bll\bla\bat\bti\bio\bon\bn g\bgu\bui\bid\bde\be (\b(L\bLi\bin\bnu\bux\bx v\bve\ber\brs\bsi\bio\bon\bn)\b)
-
- This section is designed for experienced Spider sysops who want to
- install Spider from scratch. It is simply a check list of things that
- need to be done without any explanations. The name in brackets at the
- end of each line is the user that should be doing that process.
-
-
- +\bo Login as root
-
- +\bo Get the additional CPAN modules and install them (root)
-
- +\bo Create the "sysop" user and set a password (root)
-
- +\bo Put the Spider tarball in sysop and untar it (root)
-
- +\bo ln -s sysop/spider /spider (root)
-
- +\bo groupadd -g 251 spider (root)
-
- +\bo Add any more users you need to the group entry in /etc/group (root)
-
- +\bo Set the permissions on the spider tree (root)
-
- +\bo Fix permissions on ax25_call and netrom_call (root)
-
- +\bo Login as the sysop user
-
- +\bo cd to /spider (sysop)
-
- +\bo mkdir local (sysop)
-
- +\bo mkdir local_cmd (sysop)
-
- +\bo cp perl/DXVars.pm.issue local/DXVars.pm (sysop)
-
- +\bo cd to /spider/local and edit DXVars to set your details (sysop)
-
- +\bo cd ../perl (sysop)
-
- +\bo ./create_sysop.pl (sysop)
-
- +\bo ./cluster.pl (sysop)
-
- Spider should now be running and you should be able to login using the
- client program.
-
-
- +\bo Login as root
-
- +\bo Enter the correct line in ax25d.conf (root)
-
- +\bo Enter the correct line in /etc/services (root)
-
- +\bo Enter the correct line in /etc/inetd.conf (root)
-
- +\bo killall -HUP inetd (root)
-
- Spider should now be able to accept logins via telnet, netrom and
- ax25.
-
-
- +\bo Login as sysop
-
- +\bo Start the cluster (sysop)
-
- +\bo set/node and type for links (sysop)
-
- +\bo Write any connect scripts (sysop)
-
- +\bo Edit /spider/crontab as required (sysop)
-
- +\bo Edit any other files as necessary (sysop)
-
- +\bo Set filters, hops and forwarding files (sysop)
-
- +\bo Login as root
-
- +\bo Enter the correct line in /etc/inittab (root)
-
-
- 3\b3.\b. C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
-
-
-
-
- 3\b3.\b.1\b1.\b. A\bAl\bll\blo\bow\bwi\bin\bng\bg a\bax\bx2\b25\b5 c\bco\bon\bnn\bne\bec\bct\bts\bs f\bfr\bro\bom\bm u\bus\bse\ber\brs\bs
-
- As stated previously, the aim of this document is not to tell you how
- 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
-
-
-
-
- or, if you wish your users to be able to use SSID's on their callsigns
- ..
-
-
-
- default * * * * * * - sysop /spider/src/client client %s ax25
-
-
-
-
- For most purposes this is not desirable. The only time you probably
- will need this is when you need to allow other cluster nodes that are
- using SSID's in. In this case it would probably be better to use the
- first example and then add a specific line for that node like this:
-
-
-
- GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25
- default * * * * * * - sysop /spider/src/client client %u ax25
-
-
-
-
-
- 3\b3.\b.2\b2.\b. A\bAl\bll\blo\bow\bwi\bin\bng\bg t\bte\bel\bln\bne\bet\bt c\bco\bon\bnn\bne\bec\bct\bts\bs f\bfr\bro\bom\bm u\bus\bse\ber\brs\bs
-
-
- From version 1.47 there is a new (more efficient) way of doing this
- (see next section) but, if you prefer, the method of doing it
- described here will continue to work just fine.
-
-
- Allowing telnet connections is quite simple. Firstly you need to add
- a line in /etc/services to allow connections to a port number, like
- this ....
-
-
-
- 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
-
-
-
- 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/src. You can test that spider is
- accepting telnet logins by issuing the following command ....
-
-
-
- ./client 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 t\bte\bel\bln\bne\bet\bt c\bco\bon\bnn\bne\bec\bct\bts\bs (\b(f\bfr\bro\bom\bm 1\b1.\b.4\b47\b7 o\bon\bnw\bwa\bar\brd\bds\bs)\b)
-
- From version 1.47 you can choose to allow the perl cluster.pl program
- to allow connections directly (i.e. not via the /spider/src/client
- interface program). If you are using Windows then this is the only
- method available of allowing incoming telnet connections.
-
-
- To do this you need first to remove any line that you may previously
- have set up in /etc/inetd.conf. Remember to:-
-
-
-
- killall -HUP inetd
-
-
-
-
-
- to make the change happen...
-
-
- Having done that, you need to copy the file _\b/_\bs_\bp_\bi_\bd_\be_\br_\b/_\bp_\be_\br_\bl_\b/_\bL_\bi_\bs_\bt_\be_\bn_\be_\br_\bs_\b._\bp_\bm
- to _\b/_\bs_\bp_\bi_\bd_\be_\br_\b/_\bl_\bo_\bc_\ba_\bl and then edit it. You will need to uncomment the line
- containing "0.0.0.0" and select the correct port to listen on. So that
- it looks like this:-
- @listen = (
- ["0.0.0.0", 8000],
- );
-
-
-
-
-
- As standard, the listener will listen on all interfaces
- simultaneously. If you require more control than this, you can
- specify each interface individually:-
-
-
-
- @listen = (
- ["gb7baa.dxcluster.net", 8000],
- ["44.131.16.2", 6300],
- );
-
-
-
-
-
- This will only be successful if the IP addresses on each interface are
- static. If you are using some kind of dynamic IP addressing then the
- 'default' method is the only one that will work.
-
-
- Restart the cluster.pl program to enable the listener.
-
-
- One important difference with the internal listener is that no echoing
- is done by the cluster program. Users will need to set 'local-echo' on
- in their telnet clients if it isn't set automatically (as per the
- standards). Needless to say this will probably only apply to Windows
- users.
-
-
- 3\b3.\b.4\b4.\b. S\bSe\bet\btt\bti\bin\bng\bg u\bup\bp f\bfo\bor\br A\bAG\bGW\bW E\bEn\bng\bgi\bin\bne\be (\b(1\b1.\b.4\b47\b7 o\bon\bnw\bwa\bar\brd\bds\bs)\b)
-
- AGW Engine is a Windows based ax25 stack. You can connect to an AGW
- engine from Linux as well as Windows based machines.
-
-
- In order to enable access to an AGW Engine you need to copy
- _\b/_\bs_\bp_\bi_\bd_\be_\br_\b/_\bp_\be_\br_\bl_\b/_\bA_\bG_\bW_\bC_\bo_\bn_\bn_\be_\bc_\bt_\b._\bp_\bm to _\b/_\bs_\bp_\bi_\bd_\be_\br_\b/_\bl_\bo_\bc_\ba_\bl and edit it. Specifically
- you must:-
-
-
- +\bo set $enable to 1.
-
- +\bo set $login and $passwd to the values set up in your AGW
- installation. If you haven't set any there, then you should not
- touch these values.
-
- +\bo You can connect to a remote AGW engine (ie on some other machine)
- by changing $addr and $port appropriately.
-
- +\bo Restart the cluster.pl program
-
-
-
-
-
-
-
- 3\b3.\b.5\b5.\b. S\bSe\bet\btt\bti\bin\bng\bg u\bup\bp n\bno\bod\bde\be c\bco\bon\bnn\bne\bec\bct\bts\bs
-
- In order to allow cluster node connections, spider needs to know that
- the connecting callsign is a cluster node. This is the case whether
- 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. 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, cd to spider/src and issue the command ...
-
-
-
- ./client gb7baa (using the callsign you set as a node)
-
-
-
-
-
- You should get an initialisation string from DXSpider like this ...
-
-
-
- ./client gb7baa
- PC38^GB7MBC^~
-
- If the callsign you just set up as a cluster node is for an incoming
- connect, this is all that needs to be done. If the connection is to
- be outgoing then a connection script needs to be written.
-
-
- Sometimes you make a mistake... Honest, it does happen. If you want
- to make a node back to being a normal user, regardless of what type it
- is, do:
-
-
-
- unset/node gb7baa
-
-
-
-
-
- 3\b3.\b.6\b6.\b. C\bCo\bon\bnn\bne\bec\bct\bti\bio\bon\bn s\bsc\bcr\bri\bip\bpt\bts\bs
-
- Because DXSpider operates under Linux, connections can be made using
- just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all
- 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:-
-
-
-
- #\b# All lines starting with a # are ignored, as are completely blank
- lines.
-
-
- t\bti\bim\bme\beo\bou\but\bt
- timeout followed by a number is the number of seconds to wait
- for a command to complete. If there is no timeout specified in
- the script then the default is 60 seconds.
-
-
- a\bab\bbo\bor\brt\bt
- abort is a regular expression containing one or more strings to
- look for to abort a connection. This is a perl regular
- expression and is executed ignoring case.
-
-
- c\bco\bon\bnn\bne\bec\bct\bt
- connect followed by ax25, agw (for Windows users) or telnet and
- some type dependent information. In the case of a telnet
- connection, there can be up to two parameters. The first is the
- ip address or hostname of the computer you wish to connect to
- and the second is the port number you want to use (this can be
- left out if it is a normal telnet session). In the case of an
- ax25 session then this would normally be a call to ax25_call or
- netrom_call as in the example above. It is your responsibility
- to get your node and other ax25 parameters to work before going
- down this route!
-
-
- '\b' line in a chat type script. The words/phrases normally come in
- pairs, either can be empty. Each line reads input from the
- connection until it sees the string (or perl regular expression)
- contained in the left hand string. If the left hand string is
- empty then it doesn't read or wait for anything. The comparison
- is done ignoring case. When the left hand string has found what
- it is looking for (if it is) then the right hand string is sent
- to the connection. This process is repeated for every line of
- chat script.
-
-
- c\bcl\bli\bie\ben\bnt\bt
- client starts the connection, put the arguments you would want
- here if you were starting the client program manually. You only
- need this if the script has a different name to the callsign you
- are trying to connect to (i.e. you have a script called other
- which actually connects to GB7DJK-1 [instead of a script called
- gb7djk-1]).
-
-
- There are many possible ways to configure the script but here are
- three examples, one for a NETRom/AX25 connect, one for AGW engines and
- one for tcp/ip.
-
-
-
- timeout 60
- abort (Busy|Sorry|Fail)
- # don't forget to chmod 4775 netrom_call!
- connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
- # you can leave this out if you call the script 'gb7dxm'
- client gb7dxm ax25
-
-
-
-
-
-
-
-
- timeout 60
- abort (Busy|Sorry|Fail)
- # this does exactly the same as the previous example
- # the '1' is the AGW port number to connect thru for g1tlh
- connect agw 1 g1tlh
- # you can leave this out if you call the script 'gb7dxm'
- client gb7dxm ax25
-
-
-
-
-
-
-
-
- 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.7\b7.\b. S\bSt\bta\bar\brt\bti\bin\bng\bg t\bth\bhe\be c\bco\bon\bnn\bne\bec\bct\bti\bio\bon\bn
-
- You start the connection, from within a sysop enabled cluster login,
- by typing in the word _\bc_\bo_\bn_\bn_\be_\bc_\bt followed by a script name like this ....
-
-
-
- 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. From version 1.47 onwards, you will need to
- set/debug connect first. You should see something like this ...
-
-
-
- <- D G1TLH connect gb7djk-1
- -> D G1TLH connection to GB7DJK-1 started
- -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
- timeout set to 15
- CONNECT sort: telnet command: dirkl.tobit.co.uk
- CHAT "login" -> "gb7djk"
- received "
- Red Hat Linux release 5.1 (Manhattan)
- Kernel 2.0.35 on an i586
- "
- received "login: "
- sent "gb7djk"
- CHAT "word" -> "gb7djk"
- received "gb7djk"
- received "Password: "
- sent "gb7djk"
- Connected to GB7DJK-1, starting normal protocol
- <- O GB7DJK-1 telnet
- -> B GB7DJK-1 0
- GB7DJK-1 channel func state 0 -> init
- <- D GB7DJK-1
- <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1
- <- D GB7DJK-1 PC38^GB7DJK-1^~
- <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime
- 0 00:00^5447^~
- etc
-
-
-
-
-
- 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.8\b8.\b. T\bTe\bel\bln\bne\bet\bt e\bec\bch\bho\bo
-
- Cluster links in particular suffer greatly from the presence of telnet
- echo. This is caused by the telnet negotiation itself and can create
- 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 7300, 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 line works fine for RedHat distributions. It is also fine for
- SuSE up to 7.0. From Suse 7.1 you need to add runlevels 2 and 5 like
- this ...
-
-
-
- DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
-
-
-
-
-
- The line required for Slackware distributions is slightly different.
- My thanks to Aurelio, PA3EZL for this information.
-
-
-
- DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7
-
-
-
-
-
- This will automatically start DXSpider on tty7 (ALT-F7) on bootup and
- restart it should it crash for any reason.
-
-
- 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)
-
+ 1. Hop control
+ 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).
+ 1.1. Basic hop control
+ In /spider/data you will find a file called hop_table.pl. This is the
+ file that controls your hop count settings. It has a set of default
+ 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 ...
- # check every 10 minutes to see if gb7xxx is connected and if not
- # start a connect job going
- 0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx')
- 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 ...
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
+ running. If you alter the file during runtime, the command load/hops
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
+ 1.2. Isolating networks
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.
+ using the set/isolate <node_call> command.
The effect of this is to partition an isolated network completely from
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)
+ 2. Filtering (Old Style upto v1.44)
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
+ examples in the directories with the suffix .issue. 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
+ information. Outgoing filters are in the form CALLSIGN.pl and
+ incoming filters are in the form in_CALLSIGN.pl. Filters can be set
for both nodes and users.
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
+ are either going to write a filter to accept or to reject. 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
following sections.
- 6\b6.\b.1\b1.\b. S\bSp\bpo\bot\bts\bs
+ 2.1. Spots
The elements of the Spot filter are ....
- 6\b6.\b.2\b2.\b. A\bAn\bnn\bno\bou\bun\bnc\bce\bem\bme\ben\bnt\bts\bs
+ 2.2. Announcements
allow the posting of his Aurora Beacon.
- 6\b6.\b.3\b3.\b. W\bWW\bWV\bV
+ 2.3. WWV
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)
+ 3. Filtering (New Style v1.45 and later)
- 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
+ 3.1. General filter rules
Upto v1.44 it was not possible for the user to set their own filters.
From v1.45 though that has all changed. It is now possible to set
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
+ filters. These are accept, reject and clear. First we will look
generally at filtering. There are a number of things you can filter in
the DXSpider system. They all use the same general mechanism.
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
+ 3.2. Types of filter
- There are two main types of filter, _\ba_\bc_\bc_\be_\bp_\bt or _\br_\be_\bj_\be_\bc_\bt. You can use
+ There are two main types of filter, accept or reject. You can use
either to achieve the result you want dependent on your own preference
and which is more simple to do. It is pointless writing 8 lines of
reject filters when 1 accept filter would do the same thing! Each
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 filter ...
- then you will _\bO_\bN_\bL_\bY get VHF spots _\bf_\br_\bo_\bm or _\bt_\bo CQ zones 14, 15 and 16.
+ then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
If you set a reject filter like this ...
- Then you will get everything _\bE_\bX_\bC_\bE_\bP_\bT HF CW spots. You could make this
+ Then you will get everything EXCEPT HF CW spots. You could make this
single filter even more flexible. For example, if you are interested
in IOTA and will work it even on CW even though normally you are not
interested in CW, then you could say ...
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
+ above APART from those in zones 14, 15 and 16 (either spotted there or
originated there). If you did not have the brackets to separate the 2
sections, then Spider would read it logically from the front and see a
different expression entirely ...
- 7\b7.\b.3\b3.\b. F\bFi\bil\blt\bte\ber\br o\bop\bpt\bti\bio\bon\bns\bs
+ 3.3. Filter options
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
+ 3.4. Default filters
Sometimes all that is needed is a general rule for node connects.
This can be done with a node_default filter. This rule will always be
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
+ 3.5. Advanced filtering
Once you are happy with the results you get, you may like to
experiment.
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
+ said reject all HF spots in the CW section of the bands but accept all
+ others at HF. Also accept anything in VHF and above spotted in or by
+ operators in the zones 14, 15 and 16. Each filter slot actually has a
'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
the accept slot.
- 8\b8.\b. O\bOt\bth\bhe\ber\br f\bfi\bil\blt\bte\ber\brs\bs
+ 4. Other filters
- 8\b8.\b.1\b1.\b. F\bFi\bil\blt\bte\ber\bri\bin\bng\bg M\bMa\bai\bil\bl
+ 4.1. Filtering Mail
In the /spider/msg directory you will find a file called
badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
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)
+ 4.2. Filtering DX callouts (Depricated)
- _\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
+ From version 1.47, this method is replaced by the command set/baddx
In the same way as mail, there are some types of spot we do not wish
- 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
+ 4.3. Filtering words from text fields in Announce, Talk and DX spots
- Create a file in /spider/data called _\bb_\ba_\bd_\bw_\bo_\br_\bd_\bs. The format is quite
+ Create a file in /spider/data called badwords. The format is quite
simple. Lines beginning with # are ignored so comments can be added.
An example file is below ...
load/badwords.
- 9\b9.\b. M\bMa\bai\bil\bl
+ 5. Mail
DXSpider deals seamlessly with standard AK1A type mail. It supports
both personal and bulletin mail and the sysop has additional commands
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.
+ sysop sets the "keep" flag using the msg command.
- 9\b9.\b.1\b1.\b. P\bPe\ber\brs\bso\bon\bna\bal\bl m\bma\bai\bil\bl
+ 5.1. Personal mail
- 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
+ Personal mail is sent using the sp command. This is actually the
+ default method of sending mail and so a simple s for send will do. A
+ full list of the send commands and options is in the command set
section, so I will not duplicate them here.
- 9\b9.\b.2\b2.\b. B\bBu\bul\bll\ble\bet\bti\bin\bn m\bma\bai\bil\bl
+ 5.2. Bulletin mail
- Bulletin mail is sent by using the _\bs_\bb command. This is one of the
+ Bulletin mail is sent by using the sb command. This is one of the
most common mistakes users make when sending mail. They send a
- bulletin mail with _\bs or _\bs_\bp instead of _\bs_\bb and of course the message
+ bulletin mail with s or sp instead of sb and of course the message
never leaves the cluster. This can be rectified by the sysop by using
- the _\bm_\bs_\bg command.
+ the msg 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
+ 5.3. Forward.pl
DXSpider receives all and any mail sent to it without any alterations
needed in files. Because personal and bulletin mail are treated
- 9\b9.\b.4\b4.\b. T\bTh\bhe\be m\bms\bsg\bg c\bco\bom\bmm\bma\ban\bnd\bd
+ 5.4. The msg command
- The _\bm_\bs_\bg command is a very powerful and flexible tool for the sysop.
+ The msg command is a very powerful and flexible tool for the sysop.
It allows the sysop to alter to and from fields and make other changes
to manage the cluster mail.
user.
- 9\b9.\b.5\b5.\b. M\bMe\bes\bss\bsa\bag\bge\be s\bst\bta\bat\btu\bus\bs
+ 5.5. Message status
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
+ command stat/msg. This will give you additional information on the
message number including which nodes have received it, which node it
was received from and when etc. Here is an example of the output of
the command ...
- 9\b9.\b.6\b6.\b. F\bFi\bil\blt\bte\ber\bri\bin\bng\bg m\bma\bai\bil\bl
+ 5.6. Filtering mail
- This is described in the section on _\bO_\bt_\bh_\be_\br _\bf_\bi_\bl_\bt_\be_\br_\bs so I will not
+ This is described in the section on Other filters 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
+ 5.7. Distribution lists
Distribution lists are simply a list of users to send certain types of
mail to. An example of this is mail you only wish to send to other
- sysops. In /spider/msg there is a directory called _\bd_\bi_\bs_\bt_\br_\bo. You put
+ sysops. In /spider/msg there is a directory called distro. You put
any distibution lists in here. For example, here is a file called
SYSOP.pl that caters for the UK sysops.
list.
- 9\b9.\b.8\b8.\b. B\bBB\bBS\bS i\bin\bnt\bte\ber\brf\bfa\bac\bce\be
+ 5.8. BBS interface
Spider provides a simple BBS interface. No input is required from the
sysop of the cluster at all. The BBS simply sets the cluster as a BBS
using the Forward.pl file very carefully.
- 1\b10\b0.\b. D\bDa\bat\bta\bab\bba\bas\bse\bes\bs
+ 6. Databases
Spider allows the creation of local or remote databases. It supports
chained databases, allowing several different databases to be scanned
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
+ 6.1. Creating databases
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.
+ sent from the cluster prompt as the sysop user.
- To create a database you use the command _\bd_\bb_\bc_\br_\be_\ba_\bt_\be. It can be used in
+ To create a database you use the command dbcreate. It can be used in
3 different ways like so ..
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
+ 6.2. Importing databases
The only databases that Spider can currently import are the standard
AK1A databases such as OBLAST or the DB0SDX qsl and address database.
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
+ 6.3. Checking available databases
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
+ added. To do this use the dbavail command. This will output the
available databases. For example ...
- 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
+ 6.4. Looking up databases
- To look for information in a defined database, simply use the _\bd_\bb_\bs_\bh_\bo_\bw
+ To look for information in a defined database, simply use the dbshow
command, for example ...
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 ...
+ show 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
+ 6.5. Removing databases
- To delete an existing database you use the _\bd_\bb_\br_\be_\bm_\bo_\bv_\be command. For
+ To delete an existing database you use the dbremove command. For
example ...
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
+ 7. Information, files and useful programs
- 1\b11\b1.\b.1\b1.\b. M\bMO\bOT\bTD\bD
+ 7.1. MOTD
One of the more important things a cluster sysop needs to do is to get
information to his users. The simplest way to do this is to have a
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
+ 7.2. Downtime message
If for any reason the cluster is down, maybe for upgrade or
maintenance but the machine is still running, a message can be sent to
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
+ 7.3. Other text messages
You can set other text messages to be read by the user if they input
the file name. This could be for news items or maybe information for
new users. To set this up, make a directory under /spider called
- _\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
+ packclus. Under this directory you can create files called news or
+ newuser for example. In fact you can create files with any names you
like. These can be listed by the user with the command ....
- 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
+ If the file they want to read is called news. You could also set an
+ alias for this in the Alias file to allow them just to type news
You can also store other information in this directory, either
directly or nested under directories. One use for this would be to
store DX bulletins such as the OPDX bulletins. These can be listed
and read by the user. To keep things tidy, make a directory under
- /spider/packclus called _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn. Now copy any OPDX or similar
+ /spider/packclus called bulletin. Now copy any OPDX or similar
bulletins into it. These can be listed by the user in the same way as
- above using the _\bs_\bh_\bo_\bw_\b/_\bf_\bi_\bl_\be_\bs command with an extension for the bulletin
+ above using the show/files command with an extension for the bulletin
directory you have just created, like this ....
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. You can
- also see that dates they were created. In the case of the file _\bn_\be_\bw_\bs,
+ there is a file called news and a directory called bulletin. You can
+ also see that dates they were created. In the case of the file news,
you can also see the time it was last modified, a good clue as to
whether the file has been updated since you last read it. To read the
- file called _\bn_\be_\bw_\bs you would simply issue the command ....
+ file called news you would simply issue the command ....
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
+ 7.4. The Aliases file
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
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
+ 7.5. Console.pl
In later versions of Spider a simple console program is provided for
the sysop. This has a type ahead buffer with line editing facilities
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
+ 7.6. Updating kepler data
Spider has a powerful and flexible show/satellite command. In order
for this to be accurate, the kepler data has to be updated regularly.
In general, this data is available as an email or via cluster mail.
Updating it is simple. First you need to export the mail message as a
- file. You do this with the _\be_\bx_\bp_\bo_\br_\bt command from the cluster prompt as
+ file. You do this with the export command from the cluster prompt as
the sysop. For example ...
/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
+ the perl directory called convkeps.pl. All we need to do now is
convert the file like so ...
- 1\b11\b1.\b.7\b7.\b. T\bTh\bhe\be Q\bQR\bRZ\bZ c\bca\bal\bll\blb\bbo\boo\bok\bk
+ 7.7. The QRZ callbook
- The command _\bs_\bh_\b/_\bq_\br_\bz will only work once you have followed a few simple
+ The command sh/qrz will only work once you have followed a few simple
steps. First you need to get a user ID and password from qrz.com.
Simply go to the site and create one. Secondly you need to copy the
file /spider/perl/Internet.pm to /spider/local and alter it to match
proprieter of qrz.com for allowing this access.
- 1\b12\b2.\b. C\bCV\bVS\bS
+ 8. CVS
CVS stands for "Concurrent Versions System" and the CVS for DXSpider
is held at Sourceforge. This means that it is possible to update your
steps which are listed below ...
- First login as the user _\bs_\by_\bs_\bo_\bp. Next you need to connect to the CVS
+ First login as the user sysop. Next you need to connect to the CVS
repository. You do this with the command below ...
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 ...
+ connect to the Internet and then, as the user sysop ...
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
+ 9. The DXSpider command set
Below is a complete list of commands available from the cluster
prompt. Most maintenance tasks are automatic but there are some
is the permissions level needed to use the command.
- 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)
+ 9.1. accept/announce (0)
- 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
+ accept/announce [0-9] <pattern> Set an accept filter line for announce
Create an 'accept this announce' line for a filter.
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)
+ 9.2. accept/announce (extended for sysops) (8)
- 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
+ accept/announce <call> [input] [0-9]<pattern> Announce filter sysop
version
- 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)
+ 9.3. accept/spots (0)
- 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
+ accept/announce [0-9] <pattern> Set an accept filter line for spots
Create an 'accept this spot' line for a filter.
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)
+ 9.4. accept/spots (extended for sysops) (8)
- 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
+ accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
This version allows a sysop to set a filter for a callsign as well as
- 1\b13\b3.\b.5\b5.\b. a\bac\bcc\bce\bep\bpt\bt/\b/w\bwc\bcy\by (\b(0\b0)\b)
+ 9.5. accept/wcy (0)
- 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
+ accept/wcy [0-9] <pattern> set an accept WCY filter
It is unlikely that you will want to do this, but if you do then you
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)
+ 9.6. accept/wcy (extended for sysops) (8)
- 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
+ accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
This version allows a sysop to set a filter for a callsign as well as
- 1\b13\b3.\b.7\b7.\b. a\bac\bcc\bce\bep\bpt\bt/\b/w\bww\bwv\bv (\b(0\b0)\b)
+ 9.7. accept/wwv (0)
- 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
+ accept/wwv [0-9] <pattern> Set an accept WWV filter
It is unlikely that you will want to do this, but if you do then you
- 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)
+ 9.8. accept/wwv (extended for sysops) (8)
- 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
+ accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
This version allows a sysop to set a filter for a callsign as well as
- 1\b13\b3.\b.9\b9.\b. a\ban\bnn\bno\bou\bun\bnc\bce\be (\b(0\b0)\b)
+ 9.9. announce (0)
- a\ban\bnn\bno\bou\bun\bnc\bce\be <\b<t\bte\bex\bxt\bt>\b> Send an announcement to local users
+ announce <text> 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)
+ 9.10. announce full (0)
- 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
+ announce full <text> Send an announcement cluster wide
This command will send your announcement across the whole cluster
- 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)
+ 9.11. announce sysop (5)
- a\ban\bnn\bno\bou\bun\bnc\bce\be s\bsy\bys\bso\bop\bp <\b<t\bte\bex\bxt\bt>\b>
+ announce sysop <text>
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)
+ 9.12. apropos (0)
- a\bap\bpr\bro\bop\bpo\bos\bs <\b<s\bst\btr\bri\bin\bng\bg>\b> Search the help database
+ apropos <string> 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)
+ 9.13. bye (0)
- b\bby\bye\be Exit from the cluster
+ bye 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)
+ 9.14. catchup (5)
- 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
+ catchup <node_call> All|[<msgno> ...] Mark a message as sent
When you send messages the fact that you have forwarded it to another
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)
+ 9.15. clear/spots (0)
- 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
+ clear/spots [1|all] Clear a spot filter line
This command allows you to clear (remove) a line in a spot filter or
- 1\b13\b3.\b.1\b16\b6.\b. c\bco\bon\bnn\bne\bec\bct\bt (\b(5\b5)\b)
+ 9.16. connect (5)
- 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
+ connect <callsign> Start a connection to another DX Cluster
Start a connection process that will culminate in a new connection to
cluster <callsign>.
- 1\b13\b3.\b.1\b17\b7.\b. d\bdb\bba\bav\bva\bai\bil\bl (\b(0\b0)\b)
+ 9.17. dbavail (0)
- d\bdb\bba\bav\bva\bai\bil\bl Show a list of all the databases in the system
+ dbavail 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)
+ 9.18. dbcreate (9)
- 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
+ dbcreate <name> Create a database entry
+ dbcreate <name> chain <name> [<name>..] 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 <name> remote <node> Create a remote database entry
DBCREATE allows you to define a database in the system. It doesn't
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)
+ 9.19. dbimport (9)
- d\bdb\bbi\bim\bmp\bpo\bor\brt\bt <\b<d\bdb\bbn\bna\bam\bme\be>\b> Import AK1A data into a database
+ dbimport <dbname> Import AK1A data into a database
If you want to import or update data in bulk to a database you can use
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)
+ 9.20. dbremove (9)
- d\bdb\bbr\bre\bem\bmo\bov\bve\be <\b<d\bdb\bbn\bna\bam\bme\be>\b> Delete a database
+ dbremove <dbname> Delete a database
DBREMOVE will completely remove a database entry and also delete any
You have been warned.
- 1\b13\b3.\b.2\b21\b1.\b. d\bdb\bbs\bsh\bho\bow\bw (\b(0\b0)\b)
+ 9.21. dbshow (0)
- 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
+ dbshow <dbname> <key> Display an entry, if it exists, in a database
This is the generic user interface to the database to the database
- 1\b13\b3.\b.2\b22\b2.\b. d\bde\beb\bbu\bug\bg (\b(9\b9)\b)
+ 9.22. debug (9)
- d\bde\beb\bbu\bug\bg Set the cluster program into debug mode
+ debug Set the cluster program into debug mode
Executing this command will only have an effect if you are running the
finished.
- 1\b13\b3.\b.2\b23\b3.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by (\b(0\b0)\b)
+ 9.23. directory (0)
- 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
+ directory List messages
+ directory own List your own messages
+ directory new List all new messages
+ directory to <call> List all messages to <call>
+ directory from <call> List all messages from <call>
+ directory subject <string> List all messages with <string> in subject
+ directory <nn> List last <nn> messages
+ directory <from>-<to> List messages <from> message <to> message
List the messages in the messages directory.
- 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)
+ 9.24. directory (extended for sysops) (5)
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)
+ 9.25. disconnect (8)
- 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 <call> [<call> ...] 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)
+ 9.26. dx (0)
- 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
+ dx [by <call>] <freq> <call> <remarks> Send a DX spot
This is how you send a DX Spot to other users. You can, in fact, now
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)
+ 9.27. export (9)
- 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 <msgno> <filename> Export a message to a file
Export a message to a file. This command can only be executed on a
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)
+ 9.28. export_users (9)
- 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_users [<filename>] Export the users database to ascii
Export the users database to a file in ascii format. If no filename is
- 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)
+ 9.29. forward/latlong (8)
- 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
+ forward/latlong <node_call> Send latitude and longitude information to
another cluster
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,
+ have set/dxgrid 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)
+ 9.30. forward/opername (1)
- 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
+ forward/opername <call> Send out information on this <call> to all
clusters
available.
- 1\b13\b3.\b.3\b31\b1.\b. h\bhe\bel\blp\bp (\b(0\b0)\b)
+ 9.31. help (0)
- h\bhe\bel\blp\bp <\b<c\bcm\bmd\bd>\b> Get help on a command
+ help <cmd> Get help on a command
All commands can be abbreviated, so SHOW/DX can be abbreviated to
commands to look at with HELP.
- 1\b13\b3.\b.3\b32\b2.\b. i\bin\bni\bit\bt (\b(5\b5)\b)
+ 9.32. init (5)
- 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
+ init <node call> Re-initialise a link to an AK1A compatible node
This command attempts to re-initialise a link to a (usually) AK1A 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)
+ 9.33. kill (0)
- 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
+ kill <msgno> [<msgno> ..] Delete a message from the local system
Delete a message from the local system. You will only be able to
- 1\b13\b3.\b.3\b34\b4.\b. k\bki\bil\bll\bl (\b(5\b5)\b)
+ 9.34. kill (5)
- 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
+ kill <msgno> [<msgno> ...] Remove or erase a message from the system
+ kill from <call> Remove all messages from a callsign
+ kill to <call> Remove all messages to a callsign
You can get rid of any message to or originating from your callsign
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)
+ 9.35. kill full (5)
- 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
+ kill full <msgno> [<msgno>] Delete a message from the whole cluster
Delete a message (usually a 'bulletin') from the whole cluster system.
same subject will be deleted. Beware!
- 1\b13\b3.\b.3\b36\b6.\b. l\bli\bin\bnk\bks\bs (\b(0\b0)\b)
+ 9.36. links (0)
- l\bli\bin\bnk\bks\bs Show which nodes are physically connected
+ links Show which nodes are physically connected
This is a quick listing that shows which links are connected and some
- 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)
+ 9.37. load/aliases (9)
- l\blo\boa\bad\bd/\b/a\bal\bli\bia\bas\bse\bes\bs Reload the command alias table
+ load/aliases Reload the command alias table
Reload the /spider/cmd/Aliases file after you have editted it. You
- 1\b13\b3.\b.3\b38\b8.\b. l\blo\boa\bad\bd/\b/b\bba\bad\bdd\bdx\bx (\b(9\b9)\b)
+ 9.38. load/baddx (9)
- l\blo\boa\bad\bd/\b/b\bba\bad\bdd\bdx\bx Reload the bad DX table
+ load/baddx Reload the bad DX table
Reload the /spider/data/baddx.pl file if you have changed it manually
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)
+ 9.39. load/badmsg (9)
- l\blo\boa\bad\bd/\b/b\bba\bad\bdm\bms\bsg\bg Reload the bad message table
+ load/badmsg Reload the bad message table
Reload the /spider/msg/badmsg.pl file if you have changed it manually
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)
+ 9.40. load/badwords (9)
- l\blo\boa\bad\bd/\b/b\bba\bad\bdw\bwo\bor\brd\bds\bs Reload the badwords file
+ load/badwords Reload the badwords file
Reload the /spider/data/badwords file if you have changed it manually
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)
+ 9.41. load/bands (9)
- l\blo\boa\bad\bd/\b/b\bba\ban\bnd\bds\bs Reload the band limits table
+ load/bands Reload the band limits table
Reload the /spider/data/bands.pl file if you have changed it manually
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)
+ 9.42. load/cmd_cache (9)
- l\blo\boa\bad\bd/\b/c\bcm\bmd\bd_\b_c\bca\bac\bch\bhe\be Reload the automatic command cache
+ load/cmd_cache Reload the automatic command cache
Normally, if you change a command file in the cmd or local_cmd tree 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)
+ 9.43. load/forward (9)
- l\blo\boa\bad\bd/\b/f\bfo\bor\brw\bwa\bar\brd\bd Reload the msg forwarding routing table
+ load/forward Reload the msg forwarding routing table
Reload the /spider/msg/forward.pl file if you have changed 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)
+ 9.44. load/messages (9)
- l\blo\boa\bad\bd/\b/m\bme\bes\bss\bsa\bag\bge\bes\bs Reload the system messages file
+ load/messages Reload the system messages file
If you change the /spider/perl/Messages file (usually whilst
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)
+ 9.45. load/prefixes (9)
- l\blo\boa\bad\bd/\b/p\bpr\bre\bef\bfi\bix\bxe\bes\bs Reload the prefix table
+ load/prefixes 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)
+ 9.46. merge (5)
- 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 <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
MERGE allows you to bring your spot and wwv database up to date. By
data).
- 1\b13\b3.\b.4\b47\b7.\b. m\bms\bsg\bg (\b(9\b9)\b)
+ 9.47. msg (9)
- 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
+ msg <cmd> <msgno> [data ...] Alter various message parameters
Alter message parameters like To, From, Subject, whether private or
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)
+ 9.48. pc (8)
- p\bpc\bc <\b<c\bca\bal\bll\bl>\b> <\b<t\bte\bex\bxt\bt>\b> Send text (eg PC Protocol) to <call>
+ pc <call> <text> Send text (eg PC Protocol) to <call>
Send some arbitrary text to a locally connected callsign. No
pc G1TLH Try doing that properly!!!
- 1\b13\b3.\b.4\b49\b9.\b. p\bpi\bin\bng\bg (\b(1\b1)\b)
+ 9.49. ping (1)
- p\bpi\bin\bng\bg <\b<n\bno\bod\bde\be>\b> Check the link quality between nodes
+ ping <node> Check the link quality between nodes
his command allows you to send a frame to another cluster node on the
- 1\b13\b3.\b.5\b50\b0.\b. r\brc\bcm\bmd\bd (\b(1\b1)\b)
+ 9.50. rcmd (1)
- 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
+ rcmd <node call> <cmd> Send a command to another DX cluster
This command allows you to send nearly any command to another DX
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)
+ 9.51. read (0)
- 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
+ read Read the next unread personal message addressed to you
+ read <msgno> Read the specified message
You can read any messages that are sent as 'non-personal' and also any
- 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)
+ 9.52. read (extended for sysops) (5)
- r\bre\bea\bad\bd <\b<m\bms\bsg\bgn\bno\bo>\b> Read a message on the system
+ read <msgno> 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
+ 9.53. reject/announce
- 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
+ reject/announce [0-9] <pattern> Set a reject filter for announce
Create an 'reject this announce' line for a filter.
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)
+ 9.54. reject/announce (extended for sysops) (8)
- 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
+ reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
version
- 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)
+ 9.55. reject/spots (0)
- 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
+ reject/spots [0-9] <pattern> Set a reject filter line for spots
Create a 'reject this spot' line for a filter.
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)
+ 9.56. reject/spots (extended for sysops) (8)
- 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
+ reject/spots <call> [input] [0-9] <pattern> Reject spot filter sysop
version
- 1\b13\b3.\b.5\b57\b7.\b. r\bre\bej\bje\bec\bct\bt/\b/w\bwc\bcy\by (\b(0\b0)\b)
+ 9.57. reject/wcy (0)
- 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
+ reject/wcy [0-9] <pattern> Set a reject WCY filter
It is unlikely that you will want to do this, but if you do then you
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)
+ 9.58. reject/wcy (extended for sysops) (8)
- 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
+ reject/wcy <call> [input] [0-9] <pattern> WCY reject filter sysop
version
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)
+ 9.59. reject/wwv (0)
- 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
+ reject/wwv [0-9] <pattern> Set a reject WWV filter
It is unlikely that you will want to do this, but if you do then you
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)
+ 9.60. reject/wwv (extended for sysops) (8)
- 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
+ reject/wwv <call> [input] [0-9] <pattern> WWV reject filter sysop
version
- 1\b13\b3.\b.6\b61\b1.\b. r\bre\bep\bpl\bly\by (\b(0\b0)\b)
+ 9.61. reply (0)
- 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
+ reply Reply (privately) to the last message that you have read
+ reply <msgno> Reply (privately) to the specified message
+ reply B <msgno> Reply as a Bulletin to the specified message
+ reply NOPrivate <msgno> Reply as a Bulletin to the specified message
+ reply RR <msgno> Reply to the specified message with read receipt
You can reply to a message and the subject will automatically have
- 1\b13\b3.\b.6\b62\b2.\b. s\bse\ben\bnd\bd (\b(0\b0)\b)
+ 9.62. send (0)
- 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
+ send <call> [<call> ...] Send a message to one or more callsigns
+ send RR <call> Send a message and ask for a read receipt
+ send COPY <msgno> <call> Send a copy of a message to someone
+ send PRIVATE <call> Send a personal message
+ send NOPRIVATE <call> Send a message to all stations
All the SEND commands will create a message which will be sent either
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)
+ 9.63. set/address (0)
- 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
+ set/address <your_address> 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)
+ 9.64. set/announce (0)
- s\bse\bet\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be Allow announce messages
+ set/announce 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)
+ 9.65. set/arcluster (5)
- 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-
+ set/arcluster <node_call> [<node_call> ...] Make the node_call an AR-
Cluster type node
Set the node_call as an AR-Cluster type node
- 1\b13\b3.\b.6\b66\b6.\b. s\bse\bet\bt/\b/b\bba\bad\bdd\bdx\bx (\b(8\b8)\b)
+ 9.66. set/baddx (8)
- 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
+ set/baddx <call> Stop words we do not wish to see in the callsign
field of a dx spot being propagated
- 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)
+ 9.67. set/badnode (6)
- 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
+ set/badnode <node_call> Stop spots from this node_call being
propagated
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)
+ 9.68. set/badspotter (8)
- 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
+ set/badspotter <call> Stop spots from this callsign being propagated
Setting a callsign as a 'badspotter' will prevent spots from this
FILTERing.
- 1\b13\b3.\b.6\b69\b9.\b. s\bse\bet\bt/\b/b\bbe\bee\bep\bp (\b(0\b0)\b)
+ 9.69. set/beep (0)
- s\bse\bet\bt/\b/b\bbe\bee\bep\bp Add beeps to terminal messages
+ set/beep 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)
+ 9.70. set/clx (5)
- 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
+ set/clx <node_call> [<node_call> ...] 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)
+ 9.71. set/debug (9)
- 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
+ set/debug <name> Add a debug level to the debug set
You can choose to log several different levels. The levels are
chan state msg cron connect
- You can show what levels you are logging with the _\bs_\bh_\bo_\bw_\b/_\bd_\be_\bb_\bu_\bg command.
+ You can show what levels you are logging with the show/debug command.
You can remove a debug level with unset/debug <name>
- 1\b13\b3.\b.7\b72\b2.\b. s\bse\bet\bt/\b/d\bdx\bx (\b(0\b0)\b)
+ 9.72. set/dx (0)
- s\bse\bet\bt/\b/d\bdx\bxAllow DX messages to arrive at your terminal
+ set/dxAllow DX messages to arrive at your terminal
- You can stop DX messages with the _\bu_\bn_\bs_\be_\bt_\b/_\bd_\bx command
+ You can stop DX messages with the unset/dx 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)
+ 9.73. set/dxgrid (0)
- s\bse\bet\bt/\b/d\bdx\bxg\bgr\bri\bid\bdAllow grid squares on the end of DX messages
+ set/dxgridAllow 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
+ end of a DX spot. If this is the case, use the unset/dxgrid 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)
+ 9.74. set/dxnet (5)
- 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
+ set/dxnet <node_call> [<node_call> ...] 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)
+ 9.75. set/echo (0)
- s\bse\bet\bt/\b/e\bec\bch\bho\bo Make the cluster echo your input
+ set/echo Make the cluster echo your input
If you are connected via a telnet session, different implimentations
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
+ You can remove the echo with the unset/echo 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)
+ 9.76. set/here (0)
- s\bse\bet\bt/\b/h\bhe\ber\bre\be Set the here flag
+ set/here 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
+ unset/here 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)
+ 9.77. set/homenode (0)
- 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
+ set/homenode <node_call> Set your home cluster
Tell the cluster system where you normally connect to. Any Messages
- 1\b13\b3.\b.7\b78\b8.\b. s\bse\bet\bt/\b/h\bho\bop\bps\bs (\b(8\b8)\b)
+ 9.78. set/hops (8)
- 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/hops <node_call> ann|spots|wwv|wcy <n> Set hop count
Set the hop count for a particular type of broadcast for a node.
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)
+ 9.79. set/isolate (9)
- 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
+ set/isolate <node call> Isolate a node from the rest of the network
Connect a node to your system in such a way that you are a full
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)
+ 9.80. set/language (0)
- 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
+ set/language <language> 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).
+ Currently the languages available are en (English) and nl (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)
+ 9.81. set/location (0)
- 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
+ set/location <lat and long> 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.
+ the set/qra command which will do the conversion for you.
- 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)
+ 9.82. set/sys_location (9)
- 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
+ set/sys_location <lat & long> Set your cluster latitude and longitude
In order to get accurate headings and such like you must tell the
- 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)
+ 9.83. set/logininfo (0)
- s\bse\bet\bt/\b/l\blo\bog\bgi\bin\bni\bin\bnf\bfo\bo Show logins and logouts of nodes and users
+ set/logininfo 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.
+ You can stop these messages by using the unset/logininfo 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)
+ 9.84. set/lockout (9)
- 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
+ set/lockout <call> 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.
+ You can show who is locked out with the show/lockout command. To
+ allow the user to connect again, use the unset/lockout command.
- 1\b13\b3.\b.8\b85\b5.\b. s\bse\bet\bt/\b/n\bna\bam\bme\be (\b(0\b0)\b)
+ 9.85. set/name (0)
- 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
+ set/name <your_name> Set your name
Tell the cluster what your name is, eg:-
- 1\b13\b3.\b.8\b86\b6.\b. s\bse\bet\bt/\b/n\bno\bod\bde\be (\b(9\b9)\b)
+ 9.86. set/node (9)
- 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
+ set/node <call> [<call> ...] Make the callsign an AK1A cluster
Tell the system that the call(s) are to be treated as AK1A cluster and
- To see what your nodes are set to, use the _\bs_\bh_\bo_\bw_\b/_\bn_\bo_\bd_\be_\bs command.
+ To see what your nodes are set to, use the show/nodes 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)
+ 9.87. set/obscount (9)
- 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
+ set/obscount <count> <node call> Set the 'pump-up' obsolescence
counter
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)
+ 9.88. set/page (0)
- s\bse\bet\bt/\b/p\bpa\bag\bge\be <\b<n\bn>\b> Set the number of lines per page
+ set/page <n> Set the number of lines per page
Tell the system how many lines you wish on a page when the number of
- 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)
+ 9.89. set/password (9)
- 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
+ set/password <callsign> <string> Set a users password
The password for a user can only be set by a full sysop. The string
- 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)
+ 9.90. set/pinginterval (9)
- 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
+ set/pinginterval <time> <node call> Set the ping time to neighbouring
nodes
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)
+ 9.91. set/privilege (9)
- 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
+ set/privilege <n> <call> [<call> ...] Set the privilege level on a
call
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)
+ 9.92. set/spider (5)
- 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
+ set/spider <node_call> [<node_call> ...] 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)
+ 9.93. set/sys_qra (9)
- 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
+ set/sys_qra <locator> 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)
+ 9.94. set/qra (0)
- s\bse\bet\bt/\b/q\bqr\bra\ba <\b<l\blo\boc\bca\bat\bto\bor\br>\b> Set your QRA locator
+ set/qra <locator> Set your QRA locator
Tell the system what your QRA (or Maidenhead) locator is. If you have
- 1\b13\b3.\b.9\b95\b5.\b. s\bse\bet\bt/\b/q\bqt\bth\bh (\b(0\b0)\b)
+ 9.95. set/qth (0)
- s\bse\bet\bt/\b/q\bqt\bth\bh <\b<y\byo\bou\bur\br Q\bQT\bTH\bH>\b> Set your QTH
+ set/qth <your QTH> Set your QTH
Tell the system where your are. For example:-
- 1\b13\b3.\b.9\b96\b6.\b. s\bse\bet\bt/\b/t\bta\bal\blk\bk (\b(0\b0)\b)
+ 9.96. set/talk (0)
- s\bse\bet\bt/\b/t\bta\bal\blk\bk Allow talk messages to be seen at your console
+ set/talk 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.
+ talks with the unset/talk command.
- 1\b13\b3.\b.9\b97\b7.\b. s\bse\bet\bt/\b/w\bwc\bcy\by (\b(0\b0)\b)
+ 9.97. set/wcy (0)
- s\bse\bet\bt/\b/w\bwc\bcy\by Allow WCY messages to be seen at your console
+ set/wcy 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.
+ WCY messages with the unset/wcy command.
- 1\b13\b3.\b.9\b98\b8.\b. s\bse\bet\bt/\b/w\bww\bwv\bv (\b(0\b0)\b)
+ 9.98. set/wwv (0)
- s\bse\bet\bt/\b/w\bww\bwv\bv Allow WWV messages to be seen at your console
+ set/wwv 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.
+ WWV messages with the unset/wwv command.
- 1\b13\b3.\b.9\b99\b9.\b. s\bse\bet\bt/\b/w\bwx\bx (\b(0\b0)\b)
+ 9.99. set/wx (0)
- s\bse\bet\bt/\b/w\bwx\bx Allow WX messages to be seen at your console
+ set/wx 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.
+ WX messages with the unset/wx 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)
+ 9.100. show/baddx (1)
- s\bsh\bho\bow\bw/\b/b\bba\bad\bdd\bdx\bxShow all the bad dx calls in the system
+ show/baddxShow 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)
+ 9.101. show/badnode (6)
- s\bsh\bho\bow\bw/\b/b\bba\bad\bdn\bno\bod\bde\be Show all the bad nodes in the system
+ show/badnode 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)
+ 9.102. show/badspotter (1)
- s\bsh\bho\bow\bw/\b/b\bba\bad\bds\bsp\bpo\bot\btt\bte\ber\br Show all the bad spotters in the system
+ show/badspotter Show 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/c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn (\b(0\b0)\b)
+ 9.103. show/configuration (0)
- s\bsh\bho\bow\bw/\b/c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn [\b[<\b<n\bno\bod\bde\be>\b>]\b] Show all visible nodes and their users
+ show/configuration [<node>] Show all visible nodes and their users
This command allows you to see all the users that can be seen and the
- nodes to which they are connected. With the optional _\bn_\bo_\bd_\be, you can
+ nodes to which they are connected. With the optional node, you can
specify a particular node to look at.
This command is normally abbreviated to: sh/c
BE WARNED: the list that is returned can be VERY long
- 1\b13\b3.\b.1\b10\b04\b4.\b. s\bsh\bho\bow\bw/\b/c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn/\b/n\bno\bod\bde\be (\b(0\b0)\b)
+ 9.104. show/configuration/node (0)
- s\bsh\bho\bow\bw/\b/c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn/\b/n\bno\bod\bde\be Show all the nodes connected
+ show/configuration/node Show all the nodes connected
Show all the nodes connected locally and the nodes they have
connected.
- 1\b13\b3.\b.1\b10\b05\b5.\b. s\bsh\bho\bow\bw/\b/c\bco\bon\bnn\bne\bec\bct\bt (\b(1\b1)\b)
+ 9.105. show/connect (1)
- s\bsh\bho\bow\bw/\b/c\bco\bon\bnn\bne\bec\bct\bt Show all the active connections
+ show/connect Show all the active connections
This command shows information on all the active connections known to
the node. This command gives slightly more information than WHO.
- 1\b13\b3.\b.1\b10\b06\b6.\b. s\bsh\bho\bow\bw/\b/d\bda\bat\bte\be (\b(0\b0)\b)
+ 9.106. show/date (0)
- 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
+ show/date [<prefix>|<callsign>] Show the local time
This is very nearly the same as SHOW/TIME, the only difference the
including DST) at the prefixes or callsigns that you specify.
- 1\b13\b3.\b.1\b10\b07\b7.\b. s\bsh\bho\bow\bw/\b/d\bde\beb\bbu\bug\bg (\b(9\b9)\b)
+ 9.107. show/debug (9)
- s\bsh\bho\bow\bw/\b/d\bde\beb\bbu\bug\bg Show what levels of debug you are logging
+ show/debug Show what levels of debug you are logging
- The levels can be set with _\bs_\be_\bt_\b/_\bd_\be_\bb_\bu_\bg
+ The levels can be set with set/debug
- 1\b13\b3.\b.1\b10\b08\b8.\b. s\bsh\bho\bow\bw/\b/d\bdx\bx (\b(0\b0)\b)
+ 9.108. show/dx (0)
- s\bsh\bho\bow\bw/\b/d\bdx\bx [\b[o\bop\bpt\bti\bio\bon\bns\bs]\b] interrogate the spot database
+ show/dx [options] interrogate the spot database
If you just type SHOW/DX you will get the last so many spots (sysop
- 1\b13\b3.\b.1\b10\b09\b9.\b. s\bsh\bho\bow\bw/\b/d\bdx\bxc\bcc\bc (\b(0\b0)\b)
+ 9.109. show/dxcc (0)
- 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
+ show/dxcc <prefix> Interrogate the spot database by country
This command takes the <prefix> (which can be a full or partial
- 1\b13\b3.\b.1\b11\b10\b0.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\ble\bes\bs (\b(0\b0)\b)
+ 9.110. show/files (0)
- 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 [<filearea> [<string>]] List the contents of a filearea
SHOW/FILES on its own will show you a list of the various fileareas
- 1\b13\b3.\b.1\b11\b11\b1.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br (\b(0\b0)\b)
+ 9.111. show/filter (0)
- s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br Show the filters you have set
+ show/filter 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\b11\b12\b2.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(5\b5)\b)
+ 9.112. show/filter (extended for sysops) (5)
- 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>
+ show/filter <callsign> Show the filters set by <callsign>
A sysop can look at any filters that have been set.
- 1\b13\b3.\b.1\b11\b13\b3.\b. s\bsh\bho\bow\bw/\b/h\bho\bop\bps\bs (\b(8\b8)\b)
+ 9.113. show/hops (8)
- 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
+ show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a
node
the categories will be listed.
- 1\b13\b3.\b.1\b11\b14\b4.\b. s\bsh\bho\bow\bw/\b/i\bis\bso\bol\bla\bat\bte\be (\b(1\b1)\b)
+ 9.114. show/isolate (1)
- s\bsh\bho\bow\bw/\b/i\bis\bso\bol\bla\bat\bte\be Show a list of isolated nodes
+ show/isolate Show a list of isolated nodes
Show which nodes are currently set to be isolated.
- 1\b13\b3.\b.1\b11\b15\b5.\b. s\bsh\bho\bow\bw/\b/l\blo\boc\bck\bko\bou\but\bt (\b(9\b9)\b)
+ 9.115. show/lockout (9)
- s\bsh\bho\bow\bw/\b/l\blo\boc\bck\bko\bou\but\bt Show a list of excluded callsigns
+ show/lockout 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
+ cluster locally with the set/lockout command
- 1\b13\b3.\b.1\b11\b16\b6.\b. s\bsh\bho\bow\bw/\b/l\blo\bog\bg (\b(8\b8)\b)
+ 9.116. show/log (8)
- s\bsh\bho\bow\bw/\b/l\blo\bog\bg [\b[<\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b>]\b] Show excerpts from the system log
+ show/log [<callsign>] Show excerpts from the system log
This command outputs a short section of the system log. On its own it
show output from the log associated with that callsign.
- 1\b13\b3.\b.1\b11\b17\b7.\b. s\bsh\bho\bow\bw/\b/m\bmo\boo\bon\bn (\b(0\b0)\b)
+ 9.117. show/moon (0)
- 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/moon [<prefix>|<callsign>] Show moon rise and set times
Show the Moon rise and set times for a (list of) prefixes or
- 1\b13\b3.\b.1\b11\b18\b8.\b. s\bsh\bho\bow\bw/\b/m\bmu\buf\bf (\b(0\b0)\b)
+ 9.118. show/muf (0)
- 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
+ show/muf <prefix> [<hours>][long] Show the likely propagation to
<prefix>
terrible accurate, but it is included for completeness.
- 1\b13\b3.\b.1\b11\b19\b9.\b. s\bsh\bho\bow\bw/\b/n\bno\bod\bde\be (\b(1\b1)\b)
+ 9.119. show/node (1)
- 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/node [<node_call> ...] Show the type and version number of nodes
Show the type and version (if connected) of the nodes specified on the
the non-user callsigns known to the system will be displayed.
- 1\b13\b3.\b.1\b12\b20\b0.\b. s\bsh\bho\bow\bw/\b/p\bpr\bre\bef\bfi\bix\bx (\b(0\b0)\b)
+ 9.120. show/prefix (0)
- 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
+ show/prefix <callsign> Interrogate the prefix database
This command takes the <callsign> (which can be a full or partial
See also SHOW/DXCC
- 1\b13\b3.\b.1\b12\b21\b1.\b. s\bsh\bho\bow\bw/\b/p\bpr\bro\bog\bgr\bra\bam\bm (\b(5\b5)\b)
+ 9.121. show/program (5)
- s\bsh\bho\bow\bw/\b/p\bpr\bro\bog\bgr\bra\bam\bm Show the locations of all the included program modules
+ show/program Show the locations of all the included program modules
Show the name and location where every program module was load from.
from.
- 1\b13\b3.\b.1\b12\b22\b2.\b. s\bsh\bho\bow\bw/\b/q\bqr\bra\ba (\b(0\b0)\b)
+ 9.122. show/qra (0)
- 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
+ show/qra <locator> [<locator>] Show the distance between locators
+ show/qra <lat> <long> Convert latitude and longitude to a locator
This is a multipurpose command that allows you either to calculate the
- 1\b13\b3.\b.1\b12\b23\b3.\b. s\bsh\bho\bow\bw/\b/q\bqr\brz\bz (\b(0\b0)\b)
+ 9.123. show/qrz (0)
- 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
+ show/qrz <callsign> Show any callbook details on a callsign
This command queries the QRZ callbook server on the internet and
provided for users of this software by http://www.qrz.com
- 1\b13\b3.\b.1\b12\b24\b4.\b. s\bsh\bho\bow\bw/\b/r\bro\bou\but\bte\be (\b(0\b0)\b)
+ 9.124. show/route (0)
- 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>
+ show/route <callsign> Show the route to <callsign>
This command allows you to see to which node the callsigns specified
- 1\b13\b3.\b.1\b12\b25\b5.\b. s\bsh\bho\bow\bw/\b/s\bsa\bat\bte\bel\bll\bli\bit\bte\be (\b(0\b0)\b)
+ 9.125. show/satellite (0)
- 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
+ show/satellite <name> [<hours> <interval>] Show satellite tracking
data
- 1\b13\b3.\b.1\b12\b26\b6.\b. s\bsh\bho\bow\bw/\b/s\bsu\bun\bn (\b(0\b0)\b)
+ 9.126. show/sun (0)
- 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/sun [<prefix>|<callsign>] Show sun rise and set times
Show the sun rise and set times for a (list of) prefixes or callsigns,
- 1\b13\b3.\b.1\b12\b27\b7.\b. s\bsh\bho\bow\bw/\b/t\bti\bim\bme\be (\b(0\b0)\b)
+ 9.127. show/time (0)
- 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
+ show/time [<prefix>|<callsign>] Show the local time
If no prefixes or callsigns are given then this command returns the
including DST) at the prefixes or callsigns that you specify.
- 1\b13\b3.\b.1\b12\b28\b8.\b. s\bsh\bho\bow\bw/\b/w\bwc\bcy\by (\b(0\b0)\b)
+ 9.128. show/wcy (0)
- 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
+ show/wcy Show the last 10 WCY broadcasts
+ show/wcy <n> 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\b29\b9.\b. s\bsh\bho\bow\bw/\b/w\bww\bwv\bv (\b(0\b0)\b)
+ 9.129. show/wwv (0)
- 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
+ show/wwv Show the last 10 WWV broadcasts
+ show/wwv <n> Show the last <n> WWV broadcasts
Display the most recent WWV information that has been received by the
- 1\b13\b3.\b.1\b13\b30\b0.\b. s\bsh\bhu\but\btd\bdo\bow\bwn\bn (\b(5\b5)\b)
+ 9.130. shutdown (5)
- s\bsh\bhu\but\btd\bdo\bow\bwn\bn Shutdown the cluster
+ shutdown 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\b13\b31\b1.\b. s\bsp\bpo\boo\bof\bf (\b(9\b9)\b)
+ 9.131. spoof (9)
- 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
+ spoof <callsign> <command> Run commands as another user
This is a very simple yet powerful command for the sysop. It allows
like home_node for example.
- 1\b13\b3.\b.1\b13\b32\b2.\b. s\bst\bta\bat\bt/\b/d\bdb\bb (\b(5\b5)\b)
+ 9.132. stat/db (5)
- s\bst\bta\bat\bt/\b/d\bdb\bb <\b<d\bdb\bbn\bna\bam\bme\be>\b> Show the status of a database
+ stat/db <dbname> Show the status of a database
Show the internal status of a database descriptor.
- 1\b13\b3.\b.1\b13\b33\b3.\b. s\bst\bta\bat\bt/\b/c\bch\bha\ban\bnn\bne\bel\bl (\b(5\b5)\b)
+ 9.133. stat/channel (5)
- 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
+ stat/channel <callsign> Show the status of a channel on the cluster
Show the internal status of the channel object either for the channel
Only the fields that are defined (in perl term) will be displayed.
- 1\b13\b3.\b.1\b13\b34\b4.\b. s\bst\bta\bat\bt/\b/m\bms\bsg\bg (\b(5\b5)\b)
+ 9.134. stat/msg (5)
- s\bst\bta\bat\bt/\b/m\bms\bsg\bg <\b<m\bms\bsg\bgn\bno\bo>\b> Show the status of a message
+ stat/msg <msgno> Show the status of a message
This command shows the internal status of a message and includes
etc etc.
- 1\b13\b3.\b.1\b13\b35\b5.\b. s\bst\bta\bat\bt/\b/u\bus\bse\ber\br (\b(5\b5)\b)
+ 9.135. stat/user (5)
- 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
+ stat/user <callsign> Show the full status of a user
Shows the full contents of a user record including all the secret
Only the fields that are defined (in perl term) will be displayed.
- 1\b13\b3.\b.1\b13\b36\b6.\b. s\bsy\bys\bso\bop\bp (\b(0\b0)\b)
+ 9.136. sysop (0)
- s\bsy\bys\bso\bop\bp Regain your privileges if you login remotely
+ sysop Regain your privileges if you login remotely
The system automatically reduces your privilege level to that of a
case sensitive.
- 1\b13\b3.\b.1\b13\b37\b7.\b. t\bta\bal\blk\bk (\b(0\b0)\b)
+ 9.137. talk (0)
- 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
+ talk <callsign> Enter talk mode with <callsign>
+ talk <callsign> <text> Send a text message to <callsign>
+ talk <callsign> > <node_call> [<text>] Send a text message to
<callsign> via <node_call>
- 1\b13\b3.\b.1\b13\b38\b8.\b. t\bty\byp\bpe\be (\b(0\b0)\b)
+ 9.138. type (0)
- 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 <filearea>/<name> Look at a file in one of the fileareas
Type out the contents of a file in a filearea. So, for example, in
content.
- 1\b13\b3.\b.1\b13\b39\b9.\b. w\bwh\bho\bo (\b(0\b0)\b)
+ 9.139. who (0)
- w\bwh\bho\bo Show who is physically connected locally
+ who 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\b14\b40\b0.\b. w\bwx\bx (\b(0\b0)\b)
+ 9.140. wx (0)
- 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
+ wx <text> Send a weather message to local users
+ wx full <text> 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\b14\b41\b1.\b. w\bwx\bx (\b(e\ben\bnh\bha\ban\bnc\bce\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(5\b5)\b)
+ 9.141. wx (enhanced for sysops) (5)
- w\bwx\bx s\bsy\bys\bso\bop\bp <\b<t\bte\bex\bxt\bt>\b> Send a weather message to other clusters only
+ wx sysop <text> Send a weather message to other clusters only
Send a weather message only to other cluster nodes and not to general
projects / spider.git / blobdiff