From: g0vgs Date: Sun, 28 Jan 2001 13:25:17 +0000 (+0000) Subject: Add section on mail to manual. Added adminmanual-12.html X-Git-Tag: R_1_47_PRE1~15 X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=commitdiff_plain;h=8945b9430ce1c821384e59ea10d06bc561750702;p=spider.git Add section on mail to manual. Added adminmanual-12.html --- diff --git a/html/adminmanual-1.html b/html/adminmanual-1.html index bb9dff66..500b6364 100644 --- a/html/adminmanual-1.html +++ b/html/adminmanual-1.html @@ -15,8 +15,6 @@ Previous

1. Installation (Original version by Iain Phillips, G0RDI)

-

Last modified: 26 January 2001 by Ian Maude, G0VGS -

1.1 Introduction

diff --git a/html/adminmanual-10.html b/html/adminmanual-10.html index cf3f5130..e8ad28f7 100644 --- a/html/adminmanual-10.html +++ b/html/adminmanual-10.html @@ -2,7 +2,7 @@ - The DXSpider Installation and Administration Manual : CVS + The DXSpider Installation and Administration Manual : Information, files and useful programs @@ -13,99 +13,323 @@ Previous Contents
-

10. CVS

+

10. Information, files and useful programs

-

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

-

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

10.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 banner +that is sent to the user on login. This is know as a "message of the day" +or "motd". To set this up, simply create a file in /spider/data called motd +and edit it to say whatever you want. It is purely a text file and will be +sent automatically to anyone logging in to the cluster.

-

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

10.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 the user advising them +of the fact. This message lives in the /spider/data directory and is called +"offline". Simply create the file and edit it to say whatever you wish. +This file will be sent to a user attempting to log into the cluster when +DXSpider is not actually running.

-

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

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

-

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

+
+show/files
+
+
+

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

-

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

+
+type news
+
+
+

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

-

First login as the user sysop. Next you need to connect to the CVS -repository. You do this with the command below ... +

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 +bulletins. Now copy any OPDX or similar bulletins into it. These +can be listed by the user in the same way as above using the show/files +command with an extension for the bulletins directory you have just created, +like this ....

+

-cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login 
+show/files bulletins
-

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

-

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

An example would look like this ....

-

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

+
+sh/files
+bulletins      DIR 20-Dec-1999 1715Z news          1602 14-Dec-1999 1330Z
+
+
+

You can see that in the files area (basically the packclus directory) there is a +file called news and a directory called bulletins. 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 +news you would simply issue the command ....

+

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

This command is all on one line. +

+

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

-

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

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

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

-

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

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

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

-

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

10.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 something like this ... 

-tar cvfz /tmp/s.tgz spider
-cd /
-tar xvfzp /tmp/s.tgz
+
+#!/usr/bin/perl
+
+# provide some standard aliases for commands for terminally
+# helpless ak1a user (helpless in the sense that they never
+# read nor understand help files)
+
+# This file is automagically reloaded if its modification time is 
+# later than the one stored in CmdAlias.pm
+
+# PLEASE make this file consistant with reality! (the patterns MUST
+# match the filenames!)
+
+# Don't alter this file, copy it into the local_cmd tree and modify it.
+# This file will be replaced everytime I issue a new release.
+
+# You only need to put aliases in here for commands that don't work as
+# you desire naturally, e.g sh/dx on its own just works as you expect
+# so you need not add it as an alias.
+
+
+
+package CmdAlias;
+
+%alias = (
+    '?' => [
+          '^\?', 'apropos', 'apropos',
+        ],
+    'a' => [
+          '^ann.*/full', 'announce full', 'announce', 
+          '^ann.*/sysop', 'announce sysop', 'announce',
+          '^ann.*/(.*)$', 'announce $1', 'announce',
+        ],
+        'b' => [
+        ],
+        'c' => [
+        ],
+        'd' => [
+          '^del', 'kill', 'kill',
+          '^del\w*/fu', 'kill full', 'kill',
+          '^di\w*/a\w*', 'directory all', 'directory',
+          '^di\w*/b\w*', 'directory bulletins', 'directory',
+          '^di\w*/n\w*', 'directory new', 'directory',
+          '^di\w*/o\w*', 'directory own', 'directory',
+          '^di\w*/s\w*', 'directory subject', 'directory',
+          '^di\w*/t\w*', 'directory to', 'directory',
+          '^di\w*/f\w*', 'directory from', 'directory',
+          '^di\w*/(\d+)', 'directory $1', 'directory',
+        ],
+        'e' => [
+        ],
+        'f' => [
+        ],
+        'g' => [
+        ],
+        'h' => [
+        ],
+        'i' => [
+        ],
+        'j' => [
+        ],
+        'k' => [
+        ],
+        'l' => [
+          '^l$', 'directory', 'directory',
+          '^ll$', 'directory', 'directory',
+          '^ll/(\d+)', 'directory $1', 'directory',
+        ],
+        'm' => [
+        ],
+        'n' => [
+          '^news', 'type news', 'type',
+        ],
+        'o' => [
+        ],
+        'p' => [
+        ],
+        'q' => [
+          '^q', 'bye', 'bye',
+        ],
+        'r' => [        
+          '^r$', 'read', 'read',
+          '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
+        ],
+        's' => [
+          '^s/p$', 'send', 'send',
+          '^sb$', 'send noprivate', 'send',
+          '^set/home$', 'set/homenode', 'set/homenode',
+          '^set/nobe', 'unset/beep', 'unset/beep',
+          '^set/nohe', 'unset/here', 'unset/here',
+          '^set/noan', 'unset/announce', 'unset/announce',
+          '^set/nodx', 'unset/dx', 'unset/dx',
+          '^set/nota', 'unset/talk', 'unset/talk',
+          '^set/noww', 'unset/wwv', 'unset/wwv',
+          '^set/nowx', 'unset/wx', 'unset/wx',
+          '^sh$', 'show', 'show',
+          '^sh\w*/buck', 'dbshow buck', 'dbshow',
+          '^sh\w*/bu', 'show/files bulletins', 'show/files',
+          '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
+          '^sh\w*/c$', 'show/configuration', 'show/configuration',
+          '^sh\w*/com', 'dbavail', 'dbavail',
+          '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
+          '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
+          '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
+          '^sh\w*/email', 'dbshow email', 'dbshow',
+          '^sh\w*/hftest', 'dbshow hftest', 'dbshow',
+          '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
+          '^sh\w*/qsl', 'dbshow qsl', 'dbshow',
+          '^sh\w*/tnc', 'who', 'who',
+          '^sh\w*/up', 'show/cluster', 'show/cluster',
+          '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
+          '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
+          '^sp$', 'send', 'send',
+        
+    ],
+        't' => [
+          '^ta$', 'talk', 'talk',
+          '^t$', 'talk', 'talk',
+        ],
+        'u' => [
+        ],
+        'v' => [
+        ],
+        'w' => [
+          '^wx/full', 'wx full', 'wx',
+          '^wx/sysop', 'wx sysop', 'wx',
+        ],
+        'x' => [
+        ],
+        'y' => [
+        ],
+        'z' => [
+        ],
+)
-

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

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

-

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

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

10.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 and colour for spots, +announces etc. To use this program, simply use console.pl instead of client.pl. +

+

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

+

10.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 export command from the cluster prompt +as the sysop. For example ...

-

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

+
+export 5467 /spider/perl/keps.in
+
+
+

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

Now login to a VT as sysop and cd /spider/perl. There is a command in +the perl directory called convkeps.pl. All we need to do now is +convert the file like so ...

-

Now the magic part! From now on when you want to update, simply connect to the -Internet and then, as the user sysop ... +

+
+./convkeps.pl keps.in
+
+
+

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

-cd /spider
-cvs -z3 update -d
+load/keps
-

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

That is it! the kepler data has been updated.

-

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

Next diff --git a/html/adminmanual-11.html b/html/adminmanual-11.html index e08773e3..06051d2f 100644 --- a/html/adminmanual-11.html +++ b/html/adminmanual-11.html @@ -2,2207 +2,113 @@ - The DXSpider Installation and Administration Manual : The DXSpider command set + The DXSpider Installation and Administration Manual : CVS + -Next +Next Previous Contents
-

11. The DXSpider command set

+

11. CVS

-

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

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

-

11.1 accept/announce (0) -

- -

accept/announce [0-9] <pattern> Set an accept filter -line for announce -

-

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

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

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

-

-
-  info <string>            eg: iota or qsl
-  by <prefixes>            eg: G,M,2         
-  origin <prefixes>
-  origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
-  origin_itu <numbers>
-  origin_zone <numbers>
-  by_dxcc <numbers>
-  by_itu <numbers>
-  by_zone <numbers>
-  channel <prefixes>
-  wx 1                     filter WX announces
-  dest <prefixes>          eg: 6MUK,WDX      (distros)
-
-
-

some examples:- -

-

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

or -

-

-
-  acc/ann by G,M,2 
-
-
-

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

-

-
-  acc/ann all
-
-
-

but this probably for advanced users... -

-

11.2 accept/announce (extended for sysops) (8) -

- -

accept/announce <call> [input] [0-9]<pattern> Announce filter sysop version -

-

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

-

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

-

11.3 accept/spots (0) -

- -

accept/announce [0-9] <pattern> Set an accept filter line for spots -

-

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

-

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

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

-

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

-

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

some examples:- -

-

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

You can use the tag 'all' to accept everything, eg: -

-

-
-  acc/spot 3 all
-
-
-

but this probably for advanced users... -

-

11.4 accept/spots (extended for sysops) (8) -

- -

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 the -default for nodes and users eg:- -

-

-
-  accept/spot db0sue-7 1 by_zone 14,15,16
-  accept/spot node_default all
-  set/hops node_default 10
-
-  accept/spot user_default by G,M,2
-
-
-

-

11.5 accept/wcy (0) -

- -

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 can -filter on the following fields:- -

-

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

-

There are no examples because WCY Broadcasts only come from one place and -you either want them or not (see UNSET/WCY if you don't want them). -

This command is really provided for future use. -

See HELP FILTER for information. -

-

11.6 accept/wcy (extended for sysops) (8) -

- -

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 the -default for nodes and users eg:- -

-

-
-  accept/wcy node_default all
-  set/hops node_default 10
-
-
-

-

11.7 accept/wwv (0) -

- -

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 can -filter on the following fields:- -

-

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

for example -

-

-
-  accept/wwv by_zone 4
-
-
-

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

See HELP FILTER for information. -

-

11.8 accept/wwv (extended for sysops) (8) -

- -

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 the -default for nodes and users eg:- -

-

-
-  accept/wwv db0sue-7 1 by_zone 4
-  accept/wwv node_default all
-  set/hops node_default 10
-
-  accept/wwv user_default by W,K
-
-
-

-

11.9 announce (0) -

- -

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 -

-

11.10 announce full (0) -

- -

announce full <text> Send an announcement cluster wide -

-

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

-

-

11.11 announce sysop (5) -

- -

announce sysop <text> -

-

Send an announcement to Sysops only -

-

11.12 apropos (0) -

- -

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

-

11.13 bye (0) -

- -

bye Exit from the cluster -

-

This will disconnect you from the cluster -

-

11.14 catchup (5) -

- -

catchup <node_call> All|[<msgno> ...] Mark a message as sent -

-

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

-

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

and to undo what you have just done:- -

-

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

which will arrange for them to be forward candidates again. -

Order is not important. -

-

11.15 clear/spots (0) -

- -

clear/spots [1|all] Clear a spot filter line -

-

This command allows you to clear (remove) a line in a spot filter or to -remove the whole filter. -

If you have a filter:- -

-

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

and you say:- -

-

-
-  clear/spot 1
-
-
-

you will be left with:- -

-

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

If you do: -

-

-
-  clear/spot all
-
-
-

the filter will be completely removed. -

-

-

11.16 connect (5) -

- -

connect <callsign> Start a connection to another DX Cluster -

-

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

-

11.17 dbavail (0) -

- -

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

-

11.18 dbcreate (9) -

- -

dbcreate <name> Create a database entry
-dbcreate <name> chain <name> [<name>..] Create a chained database entry
-dbcreate <name> remote <node> Create a remote database -entry
 -

-

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

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

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

DBCREATE oblast -

You can also chain databases with the addition of the 'chain' keyword. -This will search each database one after the other. A typical example -is: -

DBCREATE sdx_qsl chain sql_ad -

No checking is done to see if the any of the chained databases exist, in -fact it is usually better to do the above statement first then do each of -the chained databases. -

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

DBCREATE buckmaster remote gb7dxc -

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

DBCREATE qsl chain gb7dxc -

To see what databases have been defined do: -

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

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

-

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

to allow -

SH/BUCK g1tlh -

to work as they may be used to. -

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

-

11.19 dbimport (9) -

- -

dbimport <dbname> Import AK1A data into a database -

-

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

DBIMPORT oblast /tmp/OBLAST.FUL -

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

-

11.20 dbremove (9) -

- -

dbremove <dbname> Delete a database -

-

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

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

For example: -

DBREMOVE oblast -

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

I repeat: -

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

You have been warned. -

-

11.21 dbshow (0) -

- -

dbshow <dbname> <key> Display an entry, if it exists, in a database -

-

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

-

-
-  SH/BUCK G1TLH
-
-
-

but if he hasn't and the database really does exist (use DBAVAIL or -SHOW/COMMAND to find out) you can do the same thing with: -

-

-
-  DBSHOW buck G1TLH
-
-
-

-

-

11.22 debug (9) -

- -

debug Set the cluster program into debug mode -

-

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

-

-
-        perl -d cluster.pl
-
-
-

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

-

11.23 directory (0) -

- -

directory List messages
directory all List all 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. -

If there is a 'p' one space after the message number then it is a -personal message. If there is a '-' between the message number and the -'p' then this indicates that the message has been read. -

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

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

-

-
-   DIR TO G1TLH 5
-or 
-   DIR SUBJECT IOTA 200-250
-
-
-

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

-

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

-

-

11.24 directory (extended for sysops) (5) -

- -

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

-

11.25 disconnect (8) -

- -

disconnect <call> [<call> ...] Disconnect a user or node -

-

Disconnect any <call> connected locally -

-

11.26 dx (0) -

- -

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 -enter the <freq> and the <call> either way round. -

-

-
-   DX FR0G 144.600
-   DX 144.600 FR0G
-   DX 144600 FR0G 
-
-
-

will all give the same result. You can add some remarks to the end -of the command and they will be added to the spot. -

-

-
-   DX FR0G 144600 this is a test
-
-
-

You can credit someone else by saying:- -

-

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

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

-

11.27 export (9) -

- -

export <msgno> <filename> Export a message to a file -

-

Export a message to a file. This command can only be executed on a local -console with a fully privileged user. The file produced will be in a form -ready to be imported back into the cluster by placing it in the import -directory (/spider/msg/import). -

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

EXPORT 2345 /tmp/a -

-

11.28 export_users (9) -

- -

export_users [<filename>] Export the users database to ascii -

-

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

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

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

-

11.29 forward/latlong (8) -

- -

forward/latlong <node_call> Send latitude and longitude information to another cluster -

-

This command sends all the latitude and longitude information that your -cluster is holding against callsigns. One advantage of recieving this -information is that more locator information is held by you. This -means that more locators are given on the DX line assuming you have -set/dxgrid enabled. This could be a LOT of information though, so -it is not recommended on slow links. -

-

11.30 forward/opername (1) -

- -

forward/opername <call> Send out information on this <call> to all clusters -

-

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

-

11.31 help (0) -

- -

help <cmd> Get help on a command -

-

All commands can be abbreviated, so SHOW/DX can be abbreviated -to SH/DX, ANNOUNCE can be shortened to AN and so on. -

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

-

11.32 init (5) -

- -

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 -that has got confused, usually by a protocol loop of some kind. It may -work - but you usually will be better off simply disconnecting it (or -better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your -node>). -

Best of luck - you will need it. -

-

11.33 kill (0) -

- -

kill <msgno> [<msgno> ..] Delete a message from the local system -

-

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

-

11.34 kill (5) -

- -

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 using -this command. You can remove more than one message at a time. -

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

-

11.35 kill full (5) -

- -

kill full <msgno> [<msgno>] Delete a message from the whole cluster -

-

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

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

-

11.36 links (0) -

- -

links Show which nodes are physically connected -

-

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

-

-

11.37 load/aliases (9) -

- -

load/aliases Reload the command alias table -

-

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

-

-

11.38 load/baddx (9) -

- -

load/baddx Reload the bad DX table -

-

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

-

11.39 load/badmsg (9) -

- -

load/badmsg Reload the bad message table -

-

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

-

11.40 load/badwords (9) -

- -

load/badwords Reload the badwords file -

-

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

-

11.41 load/bands (9) -

- -

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

-

11.42 load/cmd_cache (9) -

- -

load/cmd_cache Reload the automatic command cache -

-

Normally, if you change a command file in the cmd or local_cmd tree it will -automatially be picked up by the cluster program. Sometimes it can get confused -if you are doing a lot of moving commands about or delete a command in the -local_cmd tree and want to use the normal one again. Execute this command to -reset everything back to the state it was just after a cluster restart. -

-

11.43 load/forward (9) -

- -

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

-

11.44 load/messages (9) -

- -

load/messages Reload the system messages file -

-

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

unknown message 'xxxx' in lang 'en' -

-

11.45 load/prefixes (9) -

- -

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

-

11.46 merge (5) -

- -

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 default -it will request the last 10 spots and 5 WWVs from the node you select. The -node must be connected locally. -

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

-

11.47 msg (9) -

- -

msg <cmd> <msgno> [data ...] Alter various message parameters -

-

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

-

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

You can look at the status of a message by using:- -

STAT/MSG <msgno> -

This will display more information on the message than DIR does. -

-

11.48 pc (8) -

- -

pc <call> <text> Send text (eg PC Protocol) to <call> -

-

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

pc gb7djk PC33^GB7TLH^GB7DJK^400^ -

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

pc G1TLH Try doing that properly!!! -

-

11.49 ping (1) -

- -

ping <node> Check the link quality between nodes -

-

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

-

-

11.50 rcmd (1) -

- -

rcmd <node call> <cmd> Send a command to another DX cluster -

-

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

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

-

11.51 read (0) -

- -

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 -message either sent by or sent to your callsign. -

-

-

11.52 read (extended for sysops) (5) -

- -

read <msgno> Read a message on the system -

-

As a sysop you may read any message on the system -

-

11.53 reject/announce -

- -

reject/announce [0-9] <pattern> Set a reject filter -for announce -

-

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

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

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

-

-
-  info <string>            eg: iota or qsl
-  by <prefixes>            eg: G,M,2         
-  origin <prefixes>
-  origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
-  origin_itu <numbers>
-  origin_zone <numbers>
-  by_dxcc <numbers>
-  by_itu <numbers>
-  by_zone <numbers>
-  channel <prefixes>
-  wx 1                     filter WX announces
-  dest <prefixes>          eg: 6MUK,WDX      (distros)
-
-
-

some examples:- -

-

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

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

-

-
-  rej/ann all
-
-
-

but this probably for advanced users... -

-

11.54 reject/announce (extended for sysops) (8) -

- -

reject/announce <call> [input] [0-9] <pattern> Announce filter sysop version -

-

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

-

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

-

11.55 reject/spots (0) -

- -

reject/spots [0-9] <pattern> Set a reject filter line for spots -

-

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

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

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

-

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

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

some examples:- -

-

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

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

-

-
-  rej/spot 3 all
-
-
-

but this probably for advanced users... -

-

11.56 reject/spots (extended for sysops) (8) -

- -

reject/spots <call> [input] [0-9] <pattern> -Reject spot filter sysop version -

-

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

-

-
-  reject/spot db0sue-7 1 by_zone 14,15,16
-  reject/spot node_default all
-  set/hops node_default 10
-
-  reject/spot user_default by G,M,2
-
-
-

-

11.57 reject/wcy (0) -

- -

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 can -filter on the following fields:- -

-

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

There are no examples because WCY Broadcasts only come from one place and -you either want them or not (see UNSET/WCY if you don't want them). -

This command is really provided for future use. -

See HELP FILTER for information. -

-

11.58 reject/wcy (extended for sysops) (8) -

- -

reject/wcy <call> [input] [0-9] <pattern> -WCY reject filter sysop version -

-

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

reject/wcy gb7djk all -

-

11.59 reject/wwv (0) -

- -

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 can -filter on the following fields:- -

-

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

for example -

-

-
-  reject/wwv by_zone 14,15,16
-
-
-

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

See HELP FILTER for information. -

-

11.60 reject/wwv (extended for sysops) (8) -

- -

reject/wwv <call> [input] [0-9] <pattern> -WWV reject filter sysop version -

-

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

-

-
-  reject/wwv db0sue-7 1 by_zone 4
-  reject/wwv node_default all
-
-  reject/wwv user_default by W
-
-
-

-

11.61 reply (0) -

- -

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 -"Re:" inserted in front of it, if it isn't already present. -

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

-

11.62 send (0) -

- -

send <call> [<call> ...] Send a message to one or more callsigns
-send RR <call> Send a message and ask for a read receipt
-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 to -an individual callsign or to one of the 'bulletin' addresses. -

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

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

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

-

-
-  SEND RR COPY 123 PRIVATE G1TLH G0RDI
-
-
-

which should send a copy of message 123 to G1TLH and G0RDI and you will -receive a read receipt when they have read the message. -

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

-

11.63 set/address (0) -

- -

set/address <your_address> Record your postal address -

-

Literally, record your address details on the cluster. -

-

11.64 set/announce (0) -

- -

set/announce Allow announce messages -

-

Allow announce messages to arrive at your terminal. -

-

11.65 set/arcluster (5) -

- -

set/arcluster <node_call> [<node_call> ...] Make -the node_call an AR-Cluster type node -

-

Set the node_call as an AR-Cluster type node -

-

11.66 set/baddx (8) -

- -

set/baddx <call> Stop words we do not wish to see in the callsign field -of a dx spot being propagated -

-

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

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

-

-
-  set/baddx FORSALE VIDEO FR0G 
-
-
-

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

-

-
-  unset/baddx VIDEO
-
-
-

-

11.67 set/badnode (6) -

- -

set/badnode <node_call> Stop spots from this node_call -being propagated -

-

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

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

-

-
-  set/badnode K1TTT 
-
-
-

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

-

-
-  unset/badnode K1TTT
-
-
-

will allow spots from him again. -

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

-

11.68 set/badspotter (8) -

- -

set/badspotter <call> Stop spots from this callsign being propagated -

-

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

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

-

-
-  set/badspotter VE2STN 
-
-
-

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

-

-
-  unset/badspotter VE2STN
-
-
-

will allow spots from him again. -

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

-

11.69 set/beep (0) -

- -

set/beep Add beeps to terminal messages -

-

Add a beep to DX and other terminal messages. -

-

11.70 set/clx (5) -

- -

set/clx <node_call> [<node_call> ...] Make -the node_call a CLX type node -

-

Set the node_call as a CLX type node -

-

11.71 set/debug (9) -

- -

set/debug <name> Add a debug level to the debug set -

-

You can remove this level with unset/debug <name> -

-

11.72 set/dx (0) -

- -

set/dxAllow DX messages to arrive at your terminal -

-

You can stop DX messages with the unset/dx command -

-

11.73 set/dxgrid (0) -

- -

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 unset/dxgrid -command to remove the grid squares. -

-

11.74 set/dxnet (5) -

- -

set/dxnet <node_call> [<node_call> ...] Make -the node_call a DXNet type node -

-

Set the node_call as a DXNet type node -

-

11.75 set/echo (0) -

- -

set/echo Make the cluster echo your input -

-

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

You can remove the echo with the 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. -

-

11.76 set/here (0) -

- -

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 unset/here -command to let people know you are away. This simply puts brackets -around your callsign to indicate you are not available. -

-

11.77 set/homenode (0) -

- -

set/homenode <node_call> Set your home cluster -

-

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

-

-
-  SET/HOMENODE gb7djk
-
-
-

-

11.78 set/hops (8) -

- -

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

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

-

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

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

-

11.79 set/isolate (9) -

- -

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 protocol -member of its network and can see all spots on it, but nothing either leaks -out from it nor goes back into from the rest of the nodes connected to you. -

You can potentially connect several nodes in this way. -

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

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

-

11.80 set/language (0) -

- -

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 en (English) and nl (Dutch). -

-

11.81 set/location (0) -

- -

set/location <lat and long> Set your latitude and longitude -

-

You can set your latitude and longitude manually or alternatively use the -set/qra command which will do the conversion for you. -

-

-
-  set/location 54 04 N 2 02 E
-
-
-

-

-

11.82 set/sys_location (9) -

- -

set/sys_location <lat & long> Set your cluster latitude and longitude -

-

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

-

-
-  SET/LOCATION 52 22 N 0 57 E
-
-
-

-

11.83 set/logininfo (0) -

- -

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 unset/logininfo command. -

-

-

11.84 set/lockout (9) -

- -

set/lockout <call> Stop a callsign connecting to the cluster -

-

You can show who is locked out with the show/lockout command. -To allow the user to connect again, use the unset/lockout command. -

-

11.85 set/name (0) -

- -

set/name <your_name> Set your name -

-

Tell the cluster what your name is, eg:- -

-

-
-  set/name Dirk
-
-
-

-

11.86 set/node (9) -

- -

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 -fed PC Protocol rather normal user commands. -

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

-

-
-  set/spider
-  set/dxnet
-  set/clx
-  set/arcluster
-
-
-

To see what your nodes are set to, use the show/nodes command. -

-

11.87 set/obscount (9) -

- -

set/obscount <count> <node call> Set the 'pump-up' obsolescence counter -

-

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

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

If a ping is heard then the obscount is reset to the full value. Using -default values, if a node has not responded to a ping within 15 minutes, -it is disconnected. -

-

11.88 set/page (0) -

- -

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 lines -of output from a command is more than this. The default is 20. Setting it -explicitly to 0 will disable paging. -

-

-
-  SET/PAGE 30
-  SET/PAGE 0
-
-
-

The setting is stored in your user profile. -

-

-

11.89 set/password (9) -

- -

set/password <callsign> <string> Set a users password -

-

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

-

11.90 set/pinginterval (9) -

- -

set/pinginterval <time> <node call> Set the ping time to neighbouring nodes -

-

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

You can use this command to set a different interval. Please don't. -

But if you do the value you enter is treated as minutes up 60 and seconds -for numbers greater than that. -

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

-

11.91 set/privilege (9) -

- -

set/privilege <n> <call> [<call> ...] Set the privilege level on a call -

-

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

-

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

If you are a sysop and you come in as a normal user on a remote connection -your privilege will automatically be set to 0. -

-

11.92 set/spider (5) -

- -

set/spider <node_call> [<node_call> ...] Make -the node_call a DXSpider type node -

-

Set the node_call as a DXSpider type node -

-

11.93 set/sys_qra (9) -

- -

set/sys_qra <locator> Set your cluster QRA locator -

-

11.94 set/qra (0) -

- -

set/qra <locator> Set your QRA locator -

-

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

-

-
-  SET/QRA JO02LQ
-
-
-

-

11.95 set/qth (0) -

- -

set/qth <your QTH> Set your QTH -

-

Tell the system where your are. For example:- -

-

-
-  set/qth East Dereham, Norfolk
-
-
-

-

11.96 set/talk (0) -

- -

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 unset/talk command. -

-

11.97 set/wcy (0) -

- -

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 unset/wcy command. -

-

11.98 set/wwv (0) -

- -

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 unset/wwv command. -

-

11.99 set/wx (0) -

- -

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 unset/wx command. -

-

11.100 show/baddx (1) -

- -

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

-

11.101 show/badnode (6) -

- -

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

-

11.102 show/badspotter (1) -

- -

show/badspotterShow all the bad spotters in the system -

-

Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER -for more information. -

-

11.103 show/date (0) -

- -

show/date [<prefix>|<callsign>] Show -the local time -

-

This is very nearly the same as SHOW/TIME, the only difference the format -of the date string if no arguments are given. -

If no prefixes or callsigns are given then this command returns the local -time and UTC as the computer has it right now. If you give some prefixes -then it will show UTC and UTC + the local offset (not including DST) at -the prefixes or callsigns that you specify. -

-

11.104 show/dx (0) -

- -

show/dx [options] interrogate the spot database -

-

If you just type SHOW/DX you will get the last so many spots -(sysop configurable, but usually 10). -

In addition you can add any number of these options in very nearly -any order to the basic SHOW/DX command, they are:- -

-

-
-   
-on <band>       - eg 160m 20m 2m 23cm 6mm
-on <region>     - eg hf vhf uhf shf      (see SHOW/BANDS)
-   
-<number>        - the number of spots you want
-<from>-<to>     - <from> spot no <to> spot no in 
-                  the selected list
-   
-<prefix>        - for a spotted callsign beginning with <prefix>
-*<suffix>       - for a spotted callsign ending in <suffix>
-*<string>*      - for a spotted callsign containing <string>
-   
-day <number>    - starting <number> days ago
-day <from>-<to> - <from> days <to> days ago
-   
-info <text>     - any spots containing <text> in the info or remarks
-   
-by <call>       - any spots spotted by <call> (spotter <call> 
-                        is the same).
-
-qsl             - this automatically looks for any qsl info on the call
-                  held in the spot database.
-
-iota [<iota>]   - If the iota island number is missing it will 
-                  look for the string iota and anything which looks like 
-                  an iota island number. If you specify then it will look 
-                  for that island.
-
-qra [<locator>] - this will look for the specific locator if 
-                  you specify one or else anything that looks like a locator.
-
-
-

e.g. -

-

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

-

11.105 show/dxcc (0) -

- -

show/dxcc <prefix> Interrogate the spot database by country -

-

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

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

-

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

-

11.106 show/files (0) -

- -

show/files [<filearea> [<string>]] List -the contents of a filearea -

-

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

-

-
-   SH/FILES <filearea>
-
-
-

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

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

-

-
-   SH/FILES bulletins arld*
-
-
-

See also TYPE - to see the contents of a file. -

-

11.107 show/filter (0) -

- -

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

-

11.108 show/filter (extended for sysops) (5) -

- -

show/filter <callsign> Show the filters set by <callsign> -

-

A sysop can look at any filters that have been set. -

-

11.109 show/hops (8) -

- -

show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a node -

-

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

-

11.110 show/isolate (1) -

- -

show/isolate Show a list of isolated nodes +

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

-

Show which nodes are currently set to be isolated. +

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

-

11.111 show/lockout (9) -

- -

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 set/lockout command -

-

11.112 show/moon (0) -

- -

show/moon [<prefix>|<callsign>] Show moon -rise and set times -

-

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

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

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

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

For example:- -

-

-
-  SH/MOON
-  SH/MOON G1TLH W5UN
-
-
-

-

11.113 show/muf (0) -

- -

show/muf <prefix> [<hours>][long] Show -the likely propagation to <prefix> -

-

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

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

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

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

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

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

-

-
-  SH/MUF W
-
-
-

produces: -

-

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

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

inputing:- -

-

-
-  SH/MUF W 24
-
-
-

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

-

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

Gives you an estimate of the long path propagation characterics. It -should be noted that the figures will probably not be very useful, nor -terrible accurate, but it is included for completeness. -

-

11.114 show/node (1) -

- -

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 -command line. If no callsigns are specified then a sorted list of all -the non-user callsigns known to the system will be displayed. -

-

11.115 show/prefix (0) -

- -

show/prefix <callsign> Interrogate the prefix database -

-

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

See also SHOW/DXCC -

-

-

11.116 show/program (5) -

- -

show/program Show the locations of all the included program modules -

-

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

-

11.117 show/qra (0) -

- -

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 -distance and bearing between two locators or (if only one locator is -given on the command line) the distance and beraing from your station -to the locator. For example:- -

-

-
-SH/QRA IO92QL 
-SH/QRA JN06 IN73
-
-
-

The first example will show the distance and bearing to the locator from -yourself, the second example will calculate the distance and bearing from -the first locator to the second. You can use 4 or 6 character locators. -

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

-

-
-SH/QRA 52 41 N 0 58 E
-
-
-

-

11.118 show/qrz (0) -

- -

show/qrz <callsign> Show any callbook details on a callsign -

-

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

-

11.119 show/route (0) -

- -

show/route <callsign> Show the route to <callsign> -

-

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

-

-
-  sh/route n2tly
-
-
-

-

11.120 show/satellite (0) -

- -

show/satellite <name> [<hours> <interval>] -Show satellite tracking data -

-

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

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

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

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

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

So for example:- +

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

-

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

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

-

11.121 show/sun (0) -

- -

show/sun [<prefix>|<callsign>] Show -sun rise and set times +

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

-

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

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

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

For example:- +

First login as the user sysop. Next you need to connect to the CVS +repository. You do this with the command below ...

-

-  SH/SUN
-  SH/SUN G1TLH K9CW ZS
+cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
-
-

-

11.122 show/time (0) -

- -

show/time [<prefix>|<callsign>] Show -the local time -

-

If no prefixes or callsigns are given then this command returns the local -time and UTC as the computer has it right now. If you give some prefixes -then it will show UTC and UTC + the local offset (not including DST) at -the prefixes or callsigns that you specify. -

-

11.123 show/wcy (0) -

- -

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 -

-

11.124 show/wwv (0) -

- -

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

-

-

11.125 shutdown (5) -

- -

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

-

11.126 spoof (9) -

- -

spoof <callsign> <command> Run commands as another user -

-

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

-

11.127 stat/db (5) -

- -

stat/db <dbname> Show the status of a database -

-

Show the internal status of a database descriptor. -

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

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

-

11.128 stat/channel (5) -

- -

stat/channel <callsign> Show the status of a channel on the cluster -

-

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

Only the fields that are defined (in perl term) will be displayed. -

-

11.129 stat/msg (5) -

- -

stat/msg <msgno> Show the status of a message -

-

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

-

11.130 stat/user (5) -

- -

stat/user <callsign> Show the full status of a user -

-

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

Only the fields that are defined (in perl term) will be displayed. +

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

-

11.131 sysop (0) -

- -

sysop Regain your privileges if you login remotely -

-

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

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

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

-

-  password = 012345678901234567890123456789
-  > sysop
-  22 10 15 17 3
+cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
-
-

you type:- +

This command is all on one line.

-

-
- aa2bbbb0ccc5ddd7xxx3n
- or 2 0 5 7 3
- or 20573
-
-
-

They will all match. If there is no password you will still be offered -numbers but nothing will happen when you input a string. Any match is -case sensitive. +

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

-

11.132 talk (0) -

- -

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

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

-

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

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

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

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

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

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

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

-   /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
-   /HELP talk
+tar cvfz /tmp/s.tgz spider
+cd /
+tar xvfzp /tmp/s.tgz
-

To leave talk mode type: +

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

-

-
-   /EX
-
-
+

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

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

-

11.133 type (0) -

- -

type <filearea>/<name> Look at a file in one of the fileareas +

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

-

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

Now the magic part! From now on when you want to update, simply connect to the +Internet and then, as the user sysop ... 

-   TYPE bulletins/arld051
+cd /spider
+cvs -z3 update -d
-

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

-

11.134 who (0) -

- -

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 -

-

11.135 wx (0) -

- -

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 -

-

11.136 wx (enhanced for sysops) (5) -

- -

wx sysop <text> Send a weather message to other clusters only -

-

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

+

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

+

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

-Next +Next Previous Contents diff --git a/html/adminmanual-12.html b/html/adminmanual-12.html new file mode 100644 index 00000000..bc59b2cf --- /dev/null +++ b/html/adminmanual-12.html @@ -0,0 +1,2209 @@ + + + + + The DXSpider Installation and Administration Manual : The DXSpider command set + + + + + +Next +Previous +Contents +
+

12. 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 commands that are useful +for a sysop. These are listed below in alphabetical order. The number in +brackets following the command name is the permissions level needed to use +the command. +

+

12.1 accept/announce (0) +

+ +

accept/announce [0-9] <pattern> Set an accept filter +line for announce +

+

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

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

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

+

+
+  info <string>            eg: iota or qsl
+  by <prefixes>            eg: G,M,2         
+  origin <prefixes>
+  origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
+  origin_itu <numbers>
+  origin_zone <numbers>
+  by_dxcc <numbers>
+  by_itu <numbers>
+  by_zone <numbers>
+  channel <prefixes>
+  wx 1                     filter WX announces
+  dest <prefixes>          eg: 6MUK,WDX      (distros)
+
+
+

some examples:- +

+

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

or +

+

+
+  acc/ann by G,M,2 
+
+
+

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

+

+
+  acc/ann all
+
+
+

but this probably for advanced users... +

+

12.2 accept/announce (extended for sysops) (8) +

+ +

accept/announce <call> [input] [0-9]<pattern> Announce filter sysop version +

+

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

+

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

+

12.3 accept/spots (0) +

+ +

accept/announce [0-9] <pattern> Set an accept filter line for spots +

+

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

+

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

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

+

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

+

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

some examples:- +

+

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

You can use the tag 'all' to accept everything, eg: +

+

+
+  acc/spot 3 all
+
+
+

but this probably for advanced users... +

+

12.4 accept/spots (extended for sysops) (8) +

+ +

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 the +default for nodes and users eg:- +

+

+
+  accept/spot db0sue-7 1 by_zone 14,15,16
+  accept/spot node_default all
+  set/hops node_default 10
+
+  accept/spot user_default by G,M,2
+
+
+

+

12.5 accept/wcy (0) +

+ +

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 can +filter on the following fields:- +

+

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

+

There are no examples because WCY Broadcasts only come from one place and +you either want them or not (see UNSET/WCY if you don't want them). +

This command is really provided for future use. +

See HELP FILTER for information. +

+

12.6 accept/wcy (extended for sysops) (8) +

+ +

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 the +default for nodes and users eg:- +

+

+
+  accept/wcy node_default all
+  set/hops node_default 10
+
+
+

+

12.7 accept/wwv (0) +

+ +

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 can +filter on the following fields:- +

+

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

for example +

+

+
+  accept/wwv by_zone 4
+
+
+

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

See HELP FILTER for information. +

+

12.8 accept/wwv (extended for sysops) (8) +

+ +

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 the +default for nodes and users eg:- +

+

+
+  accept/wwv db0sue-7 1 by_zone 4
+  accept/wwv node_default all
+  set/hops node_default 10
+
+  accept/wwv user_default by W,K
+
+
+

+

12.9 announce (0) +

+ +

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 +

+

12.10 announce full (0) +

+ +

announce full <text> Send an announcement cluster wide +

+

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

+

+

12.11 announce sysop (5) +

+ +

announce sysop <text> +

+

Send an announcement to Sysops only +

+

12.12 apropos (0) +

+ +

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

+

12.13 bye (0) +

+ +

bye Exit from the cluster +

+

This will disconnect you from the cluster +

+

12.14 catchup (5) +

+ +

catchup <node_call> All|[<msgno> ...] Mark a message as sent +

+

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

+

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

and to undo what you have just done:- +

+

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

which will arrange for them to be forward candidates again. +

Order is not important. +

+

12.15 clear/spots (0) +

+ +

clear/spots [1|all] Clear a spot filter line +

+

This command allows you to clear (remove) a line in a spot filter or to +remove the whole filter. +

If you have a filter:- +

+

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

and you say:- +

+

+
+  clear/spot 1
+
+
+

you will be left with:- +

+

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

If you do: +

+

+
+  clear/spot all
+
+
+

the filter will be completely removed. +

+

+

12.16 connect (5) +

+ +

connect <callsign> Start a connection to another DX Cluster +

+

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

+

12.17 dbavail (0) +

+ +

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

+

12.18 dbcreate (9) +

+ +

dbcreate <name> Create a database entry
+dbcreate <name> chain <name> [<name>..] Create a chained database entry
+dbcreate <name> remote <node> Create a remote database +entry
 +

+

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

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

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

DBCREATE oblast +

You can also chain databases with the addition of the 'chain' keyword. +This will search each database one after the other. A typical example +is: +

DBCREATE sdx_qsl chain sql_ad +

No checking is done to see if the any of the chained databases exist, in +fact it is usually better to do the above statement first then do each of +the chained databases. +

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

DBCREATE buckmaster remote gb7dxc +

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

DBCREATE qsl chain gb7dxc +

To see what databases have been defined do: +

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

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

+

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

to allow +

SH/BUCK g1tlh +

to work as they may be used to. +

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

+

12.19 dbimport (9) +

+ +

dbimport <dbname> Import AK1A data into a database +

+

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

DBIMPORT oblast /tmp/OBLAST.FUL +

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

+

12.20 dbremove (9) +

+ +

dbremove <dbname> Delete a database +

+

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

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

For example: +

DBREMOVE oblast +

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

I repeat: +

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

You have been warned. +

+

12.21 dbshow (0) +

+ +

dbshow <dbname> <key> Display an entry, if it exists, in a database +

+

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

+

+
+  SH/BUCK G1TLH
+
+
+

but if he hasn't and the database really does exist (use DBAVAIL or +SHOW/COMMAND to find out) you can do the same thing with: +

+

+
+  DBSHOW buck G1TLH
+
+
+

+

+

12.22 debug (9) +

+ +

debug Set the cluster program into debug mode +

+

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

+

+
+        perl -d cluster.pl
+
+
+

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

+

12.23 directory (0) +

+ +

directory List messages
directory all List all 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. +

If there is a 'p' one space after the message number then it is a +personal message. If there is a '-' between the message number and the +'p' then this indicates that the message has been read. +

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

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

+

+
+   DIR TO G1TLH 5
+or 
+   DIR SUBJECT IOTA 200-250
+
+
+

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

+

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

+

+

12.24 directory (extended for sysops) (5) +

+ +

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

+

12.25 disconnect (8) +

+ +

disconnect <call> [<call> ...] Disconnect a user or node +

+

Disconnect any <call> connected locally +

+

12.26 dx (0) +

+ +

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 +enter the <freq> and the <call> either way round. +

+

+
+   DX FR0G 144.600
+   DX 144.600 FR0G
+   DX 144600 FR0G 
+
+
+

will all give the same result. You can add some remarks to the end +of the command and they will be added to the spot. +

+

+
+   DX FR0G 144600 this is a test
+
+
+

You can credit someone else by saying:- +

+

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

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

+

12.27 export (9) +

+ +

export <msgno> <filename> Export a message to a file +

+

Export a message to a file. This command can only be executed on a local +console with a fully privileged user. The file produced will be in a form +ready to be imported back into the cluster by placing it in the import +directory (/spider/msg/import). +

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

EXPORT 2345 /tmp/a +

+

12.28 export_users (9) +

+ +

export_users [<filename>] Export the users database to ascii +

+

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

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

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

+

12.29 forward/latlong (8) +

+ +

forward/latlong <node_call> Send latitude and longitude information to another cluster +

+

This command sends all the latitude and longitude information that your +cluster is holding against callsigns. One advantage of recieving this +information is that more locator information is held by you. This +means that more locators are given on the DX line assuming you have +set/dxgrid enabled. This could be a LOT of information though, so +it is not recommended on slow links. +

+

12.30 forward/opername (1) +

+ +

forward/opername <call> Send out information on this <call> to all clusters +

+

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

+

12.31 help (0) +

+ +

help <cmd> Get help on a command +

+

All commands can be abbreviated, so SHOW/DX can be abbreviated +to SH/DX, ANNOUNCE can be shortened to AN and so on. +

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

+

12.32 init (5) +

+ +

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 +that has got confused, usually by a protocol loop of some kind. It may +work - but you usually will be better off simply disconnecting it (or +better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your +node>). +

Best of luck - you will need it. +

+

12.33 kill (0) +

+ +

kill <msgno> [<msgno> ..] Delete a message from the local system +

+

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

+

12.34 kill (5) +

+ +

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 using +this command. You can remove more than one message at a time. +

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

+

12.35 kill full (5) +

+ +

kill full <msgno> [<msgno>] Delete a message from the whole cluster +

+

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

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

+

12.36 links (0) +

+ +

links Show which nodes are physically connected +

+

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

+

+

12.37 load/aliases (9) +

+ +

load/aliases Reload the command alias table +

+

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

+

+

12.38 load/baddx (9) +

+ +

load/baddx Reload the bad DX table +

+

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

+

12.39 load/badmsg (9) +

+ +

load/badmsg Reload the bad message table +

+

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

+

12.40 load/badwords (9) +

+ +

load/badwords Reload the badwords file +

+

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

+

12.41 load/bands (9) +

+ +

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

+

12.42 load/cmd_cache (9) +

+ +

load/cmd_cache Reload the automatic command cache +

+

Normally, if you change a command file in the cmd or local_cmd tree it will +automatially be picked up by the cluster program. Sometimes it can get confused +if you are doing a lot of moving commands about or delete a command in the +local_cmd tree and want to use the normal one again. Execute this command to +reset everything back to the state it was just after a cluster restart. +

+

12.43 load/forward (9) +

+ +

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

+

12.44 load/messages (9) +

+ +

load/messages Reload the system messages file +

+

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

unknown message 'xxxx' in lang 'en' +

+

12.45 load/prefixes (9) +

+ +

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

+

12.46 merge (5) +

+ +

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 default +it will request the last 10 spots and 5 WWVs from the node you select. The +node must be connected locally. +

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

+

12.47 msg (9) +

+ +

msg <cmd> <msgno> [data ...] Alter various message parameters +

+

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

+

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

You can look at the status of a message by using:- +

STAT/MSG <msgno> +

This will display more information on the message than DIR does. +

+

12.48 pc (8) +

+ +

pc <call> <text> Send text (eg PC Protocol) to <call> +

+

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

pc gb7djk PC33^GB7TLH^GB7DJK^400^ +

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

pc G1TLH Try doing that properly!!! +

+

12.49 ping (1) +

+ +

ping <node> Check the link quality between nodes +

+

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

+

+

12.50 rcmd (1) +

+ +

rcmd <node call> <cmd> Send a command to another DX cluster +

+

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

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

+

12.51 read (0) +

+ +

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 +message either sent by or sent to your callsign. +

+

+

12.52 read (extended for sysops) (5) +

+ +

read <msgno> Read a message on the system +

+

As a sysop you may read any message on the system +

+

12.53 reject/announce +

+ +

reject/announce [0-9] <pattern> Set a reject filter +for announce +

+

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

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

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

+

+
+  info <string>            eg: iota or qsl
+  by <prefixes>            eg: G,M,2         
+  origin <prefixes>
+  origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
+  origin_itu <numbers>
+  origin_zone <numbers>
+  by_dxcc <numbers>
+  by_itu <numbers>
+  by_zone <numbers>
+  channel <prefixes>
+  wx 1                     filter WX announces
+  dest <prefixes>          eg: 6MUK,WDX      (distros)
+
+
+

some examples:- +

+

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

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

+

+
+  rej/ann all
+
+
+

but this probably for advanced users... +

+

12.54 reject/announce (extended for sysops) (8) +

+ +

reject/announce <call> [input] [0-9] <pattern> Announce filter sysop version +

+

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

+

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

+

12.55 reject/spots (0) +

+ +

reject/spots [0-9] <pattern> Set a reject filter line for spots +

+

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

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

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

+

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

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

some examples:- +

+

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

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

+

+
+  rej/spot 3 all
+
+
+

but this probably for advanced users... +

+

12.56 reject/spots (extended for sysops) (8) +

+ +

reject/spots <call> [input] [0-9] <pattern> +Reject spot filter sysop version +

+

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

+

+
+  reject/spot db0sue-7 1 by_zone 14,15,16
+  reject/spot node_default all
+  set/hops node_default 10
+
+  reject/spot user_default by G,M,2
+
+
+

+

12.57 reject/wcy (0) +

+ +

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 can +filter on the following fields:- +

+

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

There are no examples because WCY Broadcasts only come from one place and +you either want them or not (see UNSET/WCY if you don't want them). +

This command is really provided for future use. +

See HELP FILTER for information. +

+

12.58 reject/wcy (extended for sysops) (8) +

+ +

reject/wcy <call> [input] [0-9] <pattern> +WCY reject filter sysop version +

+

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

reject/wcy gb7djk all +

+

12.59 reject/wwv (0) +

+ +

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 can +filter on the following fields:- +

+

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

for example +

+

+
+  reject/wwv by_zone 14,15,16
+
+
+

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

See HELP FILTER for information. +

+

12.60 reject/wwv (extended for sysops) (8) +

+ +

reject/wwv <call> [input] [0-9] <pattern> +WWV reject filter sysop version +

+

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

+

+
+  reject/wwv db0sue-7 1 by_zone 4
+  reject/wwv node_default all
+
+  reject/wwv user_default by W
+
+
+

+

12.61 reply (0) +

+ +

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 +"Re:" inserted in front of it, if it isn't already present. +

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

+

12.62 send (0) +

+ +

send <call> [<call> ...] Send a message to one or more callsigns
+send RR <call> Send a message and ask for a read receipt
+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 to +an individual callsign or to one of the 'bulletin' addresses. +

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

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

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

+

+
+  SEND RR COPY 123 PRIVATE G1TLH G0RDI
+
+
+

which should send a copy of message 123 to G1TLH and G0RDI and you will +receive a read receipt when they have read the message. +

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

+

12.63 set/address (0) +

+ +

set/address <your_address> Record your postal address +

+

Literally, record your address details on the cluster. +

+

12.64 set/announce (0) +

+ +

set/announce Allow announce messages +

+

Allow announce messages to arrive at your terminal. +

+

12.65 set/arcluster (5) +

+ +

set/arcluster <node_call> [<node_call> ...] Make +the node_call an AR-Cluster type node +

+

Set the node_call as an AR-Cluster type node +

+

12.66 set/baddx (8) +

+ +

set/baddx <call> Stop words we do not wish to see in the callsign field +of a dx spot being propagated +

+

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

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

+

+
+  set/baddx FORSALE VIDEO FR0G 
+
+
+

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

+

+
+  unset/baddx VIDEO
+
+
+

+

12.67 set/badnode (6) +

+ +

set/badnode <node_call> Stop spots from this node_call +being propagated +

+

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

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

+

+
+  set/badnode K1TTT 
+
+
+

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

+

+
+  unset/badnode K1TTT
+
+
+

will allow spots from him again. +

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

+

12.68 set/badspotter (8) +

+ +

set/badspotter <call> Stop spots from this callsign being propagated +

+

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

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

+

+
+  set/badspotter VE2STN 
+
+
+

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

+

+
+  unset/badspotter VE2STN
+
+
+

will allow spots from him again. +

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

+

12.69 set/beep (0) +

+ +

set/beep Add beeps to terminal messages +

+

Add a beep to DX and other terminal messages. +

+

12.70 set/clx (5) +

+ +

set/clx <node_call> [<node_call> ...] Make +the node_call a CLX type node +

+

Set the node_call as a CLX type node +

+

12.71 set/debug (9) +

+ +

set/debug <name> Add a debug level to the debug set +

+

You can remove this level with unset/debug <name> +

+

12.72 set/dx (0) +

+ +

set/dxAllow DX messages to arrive at your terminal +

+

You can stop DX messages with the unset/dx command +

+

12.73 set/dxgrid (0) +

+ +

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 unset/dxgrid +command to remove the grid squares. +

+

12.74 set/dxnet (5) +

+ +

set/dxnet <node_call> [<node_call> ...] Make +the node_call a DXNet type node +

+

Set the node_call as a DXNet type node +

+

12.75 set/echo (0) +

+ +

set/echo Make the cluster echo your input +

+

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

You can remove the echo with the 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. +

+

12.76 set/here (0) +

+ +

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 unset/here +command to let people know you are away. This simply puts brackets +around your callsign to indicate you are not available. +

+

12.77 set/homenode (0) +

+ +

set/homenode <node_call> Set your home cluster +

+

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

+

+
+  SET/HOMENODE gb7djk
+
+
+

+

12.78 set/hops (8) +

+ +

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

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

+

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

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

+

12.79 set/isolate (9) +

+ +

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 protocol +member of its network and can see all spots on it, but nothing either leaks +out from it nor goes back into from the rest of the nodes connected to you. +

You can potentially connect several nodes in this way. +

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

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

+

12.80 set/language (0) +

+ +

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 en (English) and nl (Dutch). +

+

12.81 set/location (0) +

+ +

set/location <lat and long> Set your latitude and longitude +

+

You can set your latitude and longitude manually or alternatively use the +set/qra command which will do the conversion for you. +

+

+
+  set/location 54 04 N 2 02 E
+
+
+

+

+

12.82 set/sys_location (9) +

+ +

set/sys_location <lat & long> Set your cluster latitude and longitude +

+

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

+

+
+  SET/LOCATION 52 22 N 0 57 E
+
+
+

+

12.83 set/logininfo (0) +

+ +

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 unset/logininfo command. +

+

+

12.84 set/lockout (9) +

+ +

set/lockout <call> Stop a callsign connecting to the cluster +

+

You can show who is locked out with the show/lockout command. +To allow the user to connect again, use the unset/lockout command. +

+

12.85 set/name (0) +

+ +

set/name <your_name> Set your name +

+

Tell the cluster what your name is, eg:- +

+

+
+  set/name Dirk
+
+
+

+

12.86 set/node (9) +

+ +

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 +fed PC Protocol rather normal user commands. +

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

+

+
+  set/spider
+  set/dxnet
+  set/clx
+  set/arcluster
+
+
+

To see what your nodes are set to, use the show/nodes command. +

+

12.87 set/obscount (9) +

+ +

set/obscount <count> <node call> Set the 'pump-up' obsolescence counter +

+

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

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

If a ping is heard then the obscount is reset to the full value. Using +default values, if a node has not responded to a ping within 15 minutes, +it is disconnected. +

+

12.88 set/page (0) +

+ +

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 lines +of output from a command is more than this. The default is 20. Setting it +explicitly to 0 will disable paging. +

+

+
+  SET/PAGE 30
+  SET/PAGE 0
+
+
+

The setting is stored in your user profile. +

+

+

12.89 set/password (9) +

+ +

set/password <callsign> <string> Set a users password +

+

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

+

12.90 set/pinginterval (9) +

+ +

set/pinginterval <time> <node call> Set the ping time to neighbouring nodes +

+

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

You can use this command to set a different interval. Please don't. +

But if you do the value you enter is treated as minutes up 60 and seconds +for numbers greater than that. +

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

+

12.91 set/privilege (9) +

+ +

set/privilege <n> <call> [<call> ...] Set the privilege level on a call +

+

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

+

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

If you are a sysop and you come in as a normal user on a remote connection +your privilege will automatically be set to 0. +

+

12.92 set/spider (5) +

+ +

set/spider <node_call> [<node_call> ...] Make +the node_call a DXSpider type node +

+

Set the node_call as a DXSpider type node +

+

12.93 set/sys_qra (9) +

+ +

set/sys_qra <locator> Set your cluster QRA locator +

+

12.94 set/qra (0) +

+ +

set/qra <locator> Set your QRA locator +

+

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

+

+
+  SET/QRA JO02LQ
+
+
+

+

12.95 set/qth (0) +

+ +

set/qth <your QTH> Set your QTH +

+

Tell the system where your are. For example:- +

+

+
+  set/qth East Dereham, Norfolk
+
+
+

+

12.96 set/talk (0) +

+ +

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 unset/talk command. +

+

12.97 set/wcy (0) +

+ +

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 unset/wcy command. +

+

12.98 set/wwv (0) +

+ +

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 unset/wwv command. +

+

12.99 set/wx (0) +

+ +

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 unset/wx command. +

+

12.100 show/baddx (1) +

+ +

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

+

12.101 show/badnode (6) +

+ +

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

+

12.102 show/badspotter (1) +

+ +

show/badspotterShow all the bad spotters in the system +

+

Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER +for more information. +

+

12.103 show/date (0) +

+ +

show/date [<prefix>|<callsign>] Show +the local time +

+

This is very nearly the same as SHOW/TIME, the only difference the format +of the date string if no arguments are given. +

If no prefixes or callsigns are given then this command returns the local +time and UTC as the computer has it right now. If you give some prefixes +then it will show UTC and UTC + the local offset (not including DST) at +the prefixes or callsigns that you specify. +

+

12.104 show/dx (0) +

+ +

show/dx [options] interrogate the spot database +

+

If you just type SHOW/DX you will get the last so many spots +(sysop configurable, but usually 10). +

In addition you can add any number of these options in very nearly +any order to the basic SHOW/DX command, they are:- +

+

+
+   
+on <band>       - eg 160m 20m 2m 23cm 6mm
+on <region>     - eg hf vhf uhf shf      (see SHOW/BANDS)
+   
+<number>        - the number of spots you want
+<from>-<to>     - <from> spot no <to> spot no in 
+                  the selected list
+   
+<prefix>        - for a spotted callsign beginning with <prefix>
+*<suffix>       - for a spotted callsign ending in <suffix>
+*<string>*      - for a spotted callsign containing <string>
+   
+day <number>    - starting <number> days ago
+day <from>-<to> - <from> days <to> days ago
+   
+info <text>     - any spots containing <text> in the info or remarks
+   
+by <call>       - any spots spotted by <call> (spotter <call> 
+                        is the same).
+
+qsl             - this automatically looks for any qsl info on the call
+                  held in the spot database.
+
+iota [<iota>]   - If the iota island number is missing it will 
+                  look for the string iota and anything which looks like 
+                  an iota island number. If you specify then it will look 
+                  for that island.
+
+qra [<locator>] - this will look for the specific locator if 
+                  you specify one or else anything that looks like a locator.
+
+
+

e.g. +

+

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

+

12.105 show/dxcc (0) +

+ +

show/dxcc <prefix> Interrogate the spot database by country +

+

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

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

+

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

+

12.106 show/files (0) +

+ +

show/files [<filearea> [<string>]] List +the contents of a filearea +

+

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

+

+
+   SH/FILES <filearea>
+
+
+

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

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

+

+
+   SH/FILES bulletins arld*
+
+
+

See also TYPE - to see the contents of a file. +

+

12.107 show/filter (0) +

+ +

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

+

12.108 show/filter (extended for sysops) (5) +

+ +

show/filter <callsign> Show the filters set by <callsign> +

+

A sysop can look at any filters that have been set. +

+

12.109 show/hops (8) +

+ +

show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a node +

+

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

+

12.110 show/isolate (1) +

+ +

show/isolate Show a list of isolated nodes +

+

Show which nodes are currently set to be isolated. +

+

12.111 show/lockout (9) +

+ +

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 set/lockout command +

+

12.112 show/moon (0) +

+ +

show/moon [<prefix>|<callsign>] Show moon +rise and set times +

+

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

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

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

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

For example:- +

+

+
+  SH/MOON
+  SH/MOON G1TLH W5UN
+
+
+

+

12.113 show/muf (0) +

+ +

show/muf <prefix> [<hours>][long] Show +the likely propagation to <prefix> +

+

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

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

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

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

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

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

+

+
+  SH/MUF W
+
+
+

produces: +

+

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

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

inputing:- +

+

+
+  SH/MUF W 24
+
+
+

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

+

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

Gives you an estimate of the long path propagation characterics. It +should be noted that the figures will probably not be very useful, nor +terrible accurate, but it is included for completeness. +

+

12.114 show/node (1) +

+ +

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 +command line. If no callsigns are specified then a sorted list of all +the non-user callsigns known to the system will be displayed. +

+

12.115 show/prefix (0) +

+ +

show/prefix <callsign> Interrogate the prefix database +

+

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

See also SHOW/DXCC +

+

+

12.116 show/program (5) +

+ +

show/program Show the locations of all the included program modules +

+

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

+

12.117 show/qra (0) +

+ +

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 +distance and bearing between two locators or (if only one locator is +given on the command line) the distance and beraing from your station +to the locator. For example:- +

+

+
+SH/QRA IO92QL 
+SH/QRA JN06 IN73
+
+
+

The first example will show the distance and bearing to the locator from +yourself, the second example will calculate the distance and bearing from +the first locator to the second. You can use 4 or 6 character locators. +

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

+

+
+SH/QRA 52 41 N 0 58 E
+
+
+

+

12.118 show/qrz (0) +

+ +

show/qrz <callsign> Show any callbook details on a callsign +

+

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

+

12.119 show/route (0) +

+ +

show/route <callsign> Show the route to <callsign> +

+

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

+

+
+  sh/route n2tly
+
+
+

+

12.120 show/satellite (0) +

+ +

show/satellite <name> [<hours> <interval>] +Show satellite tracking data +

+

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

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

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

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

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

So for example:- +

+

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

+

12.121 show/sun (0) +

+ +

show/sun [<prefix>|<callsign>] Show +sun rise and set times +

+

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

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

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

For example:- +

+

+
+  SH/SUN
+  SH/SUN G1TLH K9CW ZS
+
+
+

+

12.122 show/time (0) +

+ +

show/time [<prefix>|<callsign>] Show +the local time +

+

If no prefixes or callsigns are given then this command returns the local +time and UTC as the computer has it right now. If you give some prefixes +then it will show UTC and UTC + the local offset (not including DST) at +the prefixes or callsigns that you specify. +

+

12.123 show/wcy (0) +

+ +

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 +

+

12.124 show/wwv (0) +

+ +

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

+

+

12.125 shutdown (5) +

+ +

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

+

12.126 spoof (9) +

+ +

spoof <callsign> <command> Run commands as another user +

+

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

+

12.127 stat/db (5) +

+ +

stat/db <dbname> Show the status of a database +

+

Show the internal status of a database descriptor. +

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

+

12.128 stat/channel (5) +

+ +

stat/channel <callsign> Show the status of a channel on the cluster +

+

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

Only the fields that are defined (in perl term) will be displayed. +

+

12.129 stat/msg (5) +

+ +

stat/msg <msgno> Show the status of a message +

+

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

+

12.130 stat/user (5) +

+ +

stat/user <callsign> Show the full status of a user +

+

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

Only the fields that are defined (in perl term) will be displayed. +

+

12.131 sysop (0) +

+ +

sysop Regain your privileges if you login remotely +

+

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

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

+

+
+  password = 012345678901234567890123456789
+  > sysop
+  22 10 15 17 3
+
+
+

you type:- +

+

+
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
+
+
+

They will all match. If there is no password you will still be offered +numbers but nothing will happen when you input a string. Any match is +case sensitive. +

+

12.132 talk (0) +

+ +

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

+

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

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

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

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

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

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

+

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

To leave talk mode type: +

+

+
+   /EX
+
+
+

+

12.133 type (0) +

+ +

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 +filearea 'bulletins' you want to look at file 'arld051' you would +enter:- +

+

+
+   TYPE bulletins/arld051
+
+
+

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

+

12.134 who (0) +

+ +

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 +

+

12.135 wx (0) +

+ +

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 +

+

12.136 wx (enhanced for sysops) (5) +

+ +

wx sysop <text> Send a weather message to other clusters only +

+

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

+

+

+

+Next +Previous +Contents + + diff --git a/html/adminmanual-9.html b/html/adminmanual-9.html index a002c013..48a6caa7 100644 --- a/html/adminmanual-9.html +++ b/html/adminmanual-9.html @@ -2,7 +2,7 @@ - The DXSpider Installation and Administration Manual : Information, files and useful programs + The DXSpider Installation and Administration Manual : Mail @@ -13,279 +13,38 @@ Previous Contents
-

9. Information, files and useful programs

- -

9.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 banner -that is sent to the user on login. This is know as a "message of the day" -or "motd". To set this up, simply create a file in /spider/data called motd -and edit it to say whatever you want. It is purely a text file and will be -sent automatically to anyone logging in to the cluster. -

-

9.2 Downtime message +

9. Mail

+ +

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

The cluster mail is automatically deleted after 30 days unless the sysop +sets the "keep" flag using the msg command. +

+

9.1 Personal mail

-

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

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.3 Other text messages +

9.2 Bulletin mail

-

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

-

-
-show/files
-
-
-

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

-

-
-type news
-
-
-

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 -bulletins. Now copy any OPDX or similar bulletins into it. These -can be listed by the user in the same way as above using the show/files -command with an extension for the bulletins directory you have just created, -like this .... -

-

-
-show/files bulletins
-
-
+

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

-

An example would look like this .... +

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

-

-
-sh/files
-bulletins      DIR 20-Dec-1999 1715Z news          1602 14-Dec-1999 1330Z
-
-
-

You can see that in the files area (basically the packclus directory) there is a -file called news and a directory called bulletins. 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 -news you would simply issue the command .... -

-

-
-type news
-
-
-

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

-

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

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

-

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

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

-

9.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 something like this ... -

-

-
-
-#!/usr/bin/perl
-
-# provide some standard aliases for commands for terminally
-# helpless ak1a user (helpless in the sense that they never
-# read nor understand help files)
-
-# This file is automagically reloaded if its modification time is 
-# later than the one stored in CmdAlias.pm
-
-# PLEASE make this file consistant with reality! (the patterns MUST
-# match the filenames!)
-
-# Don't alter this file, copy it into the local_cmd tree and modify it.
-# This file will be replaced everytime I issue a new release.
-
-# You only need to put aliases in here for commands that don't work as
-# you desire naturally, e.g sh/dx on its own just works as you expect
-# so you need not add it as an alias.
-
-
-
-package CmdAlias;
-
-%alias = (
-    '?' => [
-          '^\?', 'apropos', 'apropos',
-        ],
-    'a' => [
-          '^ann.*/full', 'announce full', 'announce', 
-          '^ann.*/sysop', 'announce sysop', 'announce',
-          '^ann.*/(.*)$', 'announce $1', 'announce',
-        ],
-        'b' => [
-        ],
-        'c' => [
-        ],
-        'd' => [
-          '^del', 'kill', 'kill',
-          '^del\w*/fu', 'kill full', 'kill',
-          '^di\w*/a\w*', 'directory all', 'directory',
-          '^di\w*/b\w*', 'directory bulletins', 'directory',
-          '^di\w*/n\w*', 'directory new', 'directory',
-          '^di\w*/o\w*', 'directory own', 'directory',
-          '^di\w*/s\w*', 'directory subject', 'directory',
-          '^di\w*/t\w*', 'directory to', 'directory',
-          '^di\w*/f\w*', 'directory from', 'directory',
-          '^di\w*/(\d+)', 'directory $1', 'directory',
-        ],
-        'e' => [
-        ],
-        'f' => [
-        ],
-        'g' => [
-        ],
-        'h' => [
-        ],
-        'i' => [
-        ],
-        'j' => [
-        ],
-        'k' => [
-        ],
-        'l' => [
-          '^l$', 'directory', 'directory',
-          '^ll$', 'directory', 'directory',
-          '^ll/(\d+)', 'directory $1', 'directory',
-        ],
-        'm' => [
-        ],
-        'n' => [
-          '^news', 'type news', 'type',
-        ],
-        'o' => [
-        ],
-        'p' => [
-        ],
-        'q' => [
-          '^q', 'bye', 'bye',
-        ],
-        'r' => [        
-          '^r$', 'read', 'read',
-          '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
-        ],
-        's' => [
-          '^s/p$', 'send', 'send',
-          '^sb$', 'send noprivate', 'send',
-          '^set/home$', 'set/homenode', 'set/homenode',
-          '^set/nobe', 'unset/beep', 'unset/beep',
-          '^set/nohe', 'unset/here', 'unset/here',
-          '^set/noan', 'unset/announce', 'unset/announce',
-          '^set/nodx', 'unset/dx', 'unset/dx',
-          '^set/nota', 'unset/talk', 'unset/talk',
-          '^set/noww', 'unset/wwv', 'unset/wwv',
-          '^set/nowx', 'unset/wx', 'unset/wx',
-          '^sh$', 'show', 'show',
-          '^sh\w*/buck', 'dbshow buck', 'dbshow',
-          '^sh\w*/bu', 'show/files bulletins', 'show/files',
-          '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
-          '^sh\w*/c$', 'show/configuration', 'show/configuration',
-          '^sh\w*/com', 'dbavail', 'dbavail',
-          '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
-          '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
-          '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
-          '^sh\w*/email', 'dbshow email', 'dbshow',
-          '^sh\w*/hftest', 'dbshow hftest', 'dbshow',
-          '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
-          '^sh\w*/qsl', 'dbshow qsl', 'dbshow',
-          '^sh\w*/tnc', 'who', 'who',
-          '^sh\w*/up', 'show/cluster', 'show/cluster',
-          '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
-          '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
-          '^sp$', 'send', 'send',
-        
-    ],
-        't' => [
-          '^ta$', 'talk', 'talk',
-          '^t$', 'talk', 'talk',
-        ],
-        'u' => [
-        ],
-        'v' => [
-        ],
-        'w' => [
-          '^wx/full', 'wx full', 'wx',
-          '^wx/sysop', 'wx sysop', 'wx',
-        ],
-        'x' => [
-        ],
-        'y' => [
-        ],
-        'z' => [
-        ],
-)
-
-
-

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

-

9.5 Forward.pl +

9.3 Forward.pl

DXSpider receives all and any mail sent to it without any alterations needed @@ -354,7 +113,70 @@ only be sent to the UK links and not to PA4AB-14.

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

-

9.6 Distribution lists +

+

9.4 The msg command +

+ +

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

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

+

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

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

+

9.5 Message status +

+ +

You can check on a message from within the cluster by using 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 ... +

+

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

+

9.6 Filtering mail +

+ +

This is described in the section on Other filters so I will not +duplicate it here. +

+

9.7 Distribution lists

Distribution lists are simply a list of users to send certain types of @@ -372,16 +194,6 @@ qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX

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

-

9.7 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 and colour for spots, -announces etc. To use this program, simply use console.pl instead of client.pl. -

-

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

9.8 BBS interface

@@ -394,42 +206,6 @@ the interface is one-way. Make sure you only send mail to the clusters that want it by using the Forward.pl file very carefully.

-

9.9 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 export command from the cluster prompt -as the sysop. For example ... -

-

-
-export 5467 /spider/perl/keps.in
-
-
-

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

Now login to a VT as sysop and cd /spider/perl. There is a command in -the perl directory called convkeps.pl. All we need to do now is -convert the file like so ... -

-

-
-./convkeps.pl keps.in
-
-
-

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

-

-
-load/keps
-
-
-

That is it! the kepler data has been updated. -

-

Next Previous diff --git a/html/adminmanual.html b/html/adminmanual.html index b7446d2f..3a815cff 100644 --- a/html/adminmanual.html +++ b/html/adminmanual.html @@ -15,7 +15,7 @@ Contents

The DXSpider Installation and Administration Manual

-

Ian Maude, G0VGS, (ianmaude@btinternet.com)

Version 1.30 January 2001 +

Ian Maude, G0VGS, (ianmaude@btinternet.com)

Version 1.31 January 2001

A reference for SysOps of the DXSpider DXCluster program.
@@ -84,162 +84,172 @@ Contents
  • 8.3 Filtering words from text fields in Announce, Talk and DX spots

    -

    9. Information, files and useful programs

    +

    9. Mail

    -

    10. CVS

    +

    10. Information, files and useful programs

    + + +

    +

    11. CVS

    -

    11. The DXSpider command set

    +

    12. The DXSpider command set

    Next diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 07c72386..da942c37 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -6,7 +6,7 @@ The DXSpider Installation and Administration Manual <author>Ian Maude, G0VGS, (ianmaude@btinternet.com) -<date>Version 1.30 January 2001 +<date>Version 1.31 January 2001 <abstract> A reference for SysOps of the DXSpider DXCluster program. </abstract> @@ -18,9 +18,6 @@ A reference for SysOps of the DXSpider DXCluster program. <sect>Installation (Original version by Iain Phillips, G0RDI) -<P> -Last modified: 26 January 2001 by Ian Maude, G0VGS - <sect1>Introduction <P> @@ -1312,6 +1309,199 @@ are just examples :-) <P> You can reload the file from the cluster prompt as sysop with load/badwords. +<sect>Mail + +<P> +DXSpider deals seamlessly with standard AK1A type mail. It supports both +personal and bulletin mail and the sysop has additional commands to ensure +that mail gets to where it is meant. DXSpider will send mail almost +immediately, assuming that the target is on line. However, only one +mail message is dealt with at any one time. If a mail message is already +being sent or recieved, then the new message will be queued until it has +finished. + +The cluster mail is automatically deleted after 30 days unless the sysop +sets the "keep" flag using the <em>msg</em> command. + +<sect1>Personal mail + +<P> +Personal mail is sent using the <em>sp</em> command. This is actually the +default method of sending mail and so a simple <em>s</em> for send will do. +A full list of the send commands and options is in the <em>command set</em> +section, so I will not duplicate them here. + +<sect1>Bulletin mail + +<P> +Bulletin mail is sent by using the <em>sb</em> command. This is one of the +most common mistakes users make when sending mail. They send a bulletin +mail with <em>s</em> or <em>sp</em> instead of <em>sb</em> and of course +the message never leaves the cluster. This can be rectified by the sysop +by using the <em>msg</em> command. + +<P>Bulletin addresses can be set using the Forward.pl file. + +<sect1>Forward.pl + +<P> +DXSpider receives all and any mail sent to it without any alterations needed +in files. Because personal and bulletin mail are treated differently, there +is no need for a list of accepted bulletin addresses. It is necessary, however, +to tell the program which links accept which bulletins. For example, it is +pointless sending bulletins addresses to "UK" to any links other than UK +ones. The file that does this is called forward.pl and lives in /spider/msg. +At default, like other spider files it is named forward.pl.issue. Rename it +to forward.pl and edit the file to match your requirements. +The format is below ... + +<tscreen><verb> +# +# this is an example message forwarding file for the system +# +# The format of each line is as follows +# +# type to/from/at pattern action destinations +# P/B/F T/F/A regex I/F [ call [, call ...] ] +# +# type: P - private, B - bulletin (msg), F - file (ak1a bull) +# to/from/at: T - to field, F - from field, A - home bbs, O - origin +# pattern: a perl regex on the field requested +# action: I - ignore, F - forward +# destinations: a reference to an array containing node callsigns +# +# if it is non-private and isn't in here then it won't get forwarded +# +# Currently only type B msgs are affected by this code. +# +# The list is read from the top down, the first pattern that matches +# causes the action to be taken. +# +# The pattern can be undef or 0 in which case it will always be selected +# for the action specified +# +# If the BBS list is undef or 0 and the action is 'F' (and it matches the +# pattern) then it will always be forwarded to every node that doesn't have +# it (I strongly recommend you don't use this unless you REALLY mean it, if +# you allow a new link with this on EVERY bull will be forwarded immediately +# on first connection) +# + +package DXMsg; + +@forward = ( +'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ], +'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ], +'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ], +'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], +); +</verb></tscreen> + +Simply insert a bulletin address and state in the brackets where you wish +that mail to go. For example, you can see here that mail sent to "UK" will +only be sent to the UK links and not to PA4AB-14. + +<P> +To force the cluster to reread the file use load/forward + + +<sect1>The msg command + +<P> +The <em>msg</em> command is a very powerful and flexible tool for the +sysop. It allows the sysop to alter to and from fields and make other +changes to manage the cluster mail. + +Here is a full list of the various options ... + +<tscreen><verb> + MSG TO <msgno> <call> - change TO callsign to <call> + MSG FRom <msgno> <call> - change FROM callsign to <call> + MSG PRrivate <msgno> - set private flag + MSG NOPRrivate <msgno> - unset private flag + MSG RR <msgno> - set RR flag + MSG NORR <msgno> - unset RR flag + MSG KEep <msgno> - set the keep flag (message won't be deleted ever) + MSG NOKEep <msgno> - unset the keep flag + MSG SUbject <msgno> <new> - change the subject to <new> + MSG WAittime <msgno> - remove any waiting time for this message + MSG NOREad <msgno> - mark message as unread + MSG REad <msgno> - mark message as read + MSG QUeue - queue any outstanding bulletins + MSG QUeue 1 - queue any outstanding private messages +</verb></tscreen> + +These commands are simply typed from within the cluster as the sysop user. + +<sect1>Message status + +<P> +You can check on a message from within the cluster by using the command +<em>stat/msg</em>. 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 ... + +<tscreen><verb> +G0VGS de GB7MBC 28-Jan-2001 1308Z > +stat/msg 6869 + From: GB7DJK + Msg Time: 26-Jan-2001 1302Z + Msgno: 6869 + Origin: GB7DJK + Size: 8012 + Subject: AMSAT 2line KEPS 01025.AMSAT + To: UK +Got it Nodes: GB7BAA, GB7ADX + Private: 0 +Read Confirm: 0 + Times read: 0 +G0VGS de GB7MBC 28-Jan-2001 1308Z > +</verb></tscreen> + +<sect1>Filtering mail + +<P> +This is described in the section on <em>Other filters</em> so I will not +duplicate it here. + +<sect1>Distribution lists + +<P> +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 <em>distro</em>. You +put any distibution lists in here. For example, here is a file called +SYSOP.pl that caters for the UK sysops. + +<tscreen><verb> +qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX + GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH + GB7DXK GB7DXI GB7DXS) +</verb></tscreen> + +Any mail sent to "sysop" would only be sent to the callsigns in this list. + +<sect1>BBS interface + +<P> +Spider provides a simple BBS interface. No input is required from the sysop +of the cluster at all. The BBS simply sets the cluster as a BBS and pushes +any required mail to the cluster. No mail can flow from Spider to the BBS, +the interface is one-way. + +<P> +Please be careful not to flood the cluster network with unnecessary mail. +Make sure you only send mail to the clusters that want it by using the +Forward.pl file very carefully. + <sect>Information, files and useful programs <sect1>MOTD @@ -1577,92 +1767,6 @@ You can create aliases for commands at will. Beware though, these may not always turn out as you think. Care is needed and you need to test the results once you have set an alias. -<sect1>Forward.pl - -<P> -DXSpider receives all and any mail sent to it without any alterations needed -in files. Because personal and bulletin mail are treated differently, there -is no need for a list of accepted bulletin addresses. It is necessary, however, -to tell the program which links accept which bulletins. For example, it is -pointless sending bulletins addresses to "UK" to any links other than UK -ones. The file that does this is called forward.pl and lives in /spider/msg. -At default, like other spider files it is named forward.pl.issue. Rename it -to forward.pl and edit the file to match your requirements. -The format is below ... - -<tscreen><verb> -# -# this is an example message forwarding file for the system -# -# The format of each line is as follows -# -# type to/from/at pattern action destinations -# P/B/F T/F/A regex I/F [ call [, call ...] ] -# -# type: P - private, B - bulletin (msg), F - file (ak1a bull) -# to/from/at: T - to field, F - from field, A - home bbs, O - origin -# pattern: a perl regex on the field requested -# action: I - ignore, F - forward -# destinations: a reference to an array containing node callsigns -# -# if it is non-private and isn't in here then it won't get forwarded -# -# Currently only type B msgs are affected by this code. -# -# The list is read from the top down, the first pattern that matches -# causes the action to be taken. -# -# The pattern can be undef or 0 in which case it will always be selected -# for the action specified -# -# If the BBS list is undef or 0 and the action is 'F' (and it matches the -# pattern) then it will always be forwarded to every node that doesn't have -# it (I strongly recommend you don't use this unless you REALLY mean it, if -# you allow a new link with this on EVERY bull will be forwarded immediately -# on first connection) -# - -package DXMsg; - -@forward = ( -'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ], -'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], -'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ], -'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], -'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], -'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], -'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], -'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], -'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], -'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ], -'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ], -); -</verb></tscreen> - -Simply insert a bulletin address and state in the brackets where you wish -that mail to go. For example, you can see here that mail sent to "UK" will -only be sent to the UK links and not to PA4AB-14. - -<P> -To force the cluster to reread the file use load/forward - -<sect1>Distribution lists - -<P> -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 <em>distro</em>. You -put any distibution lists in here. For example, here is a file called -SYSOP.pl that caters for the UK sysops. - -<tscreen><verb> -qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX - GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH - GB7DXK GB7DXI GB7DXS) -</verb></tscreen> - -Any mail sent to "sysop" would only be sent to the callsigns in this list. - <sect1>Console.pl <P> @@ -1674,19 +1778,6 @@ announces etc. To use this program, simply use console.pl instead of client.pl. To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the file with your favourite editor. -<sect1>BBS interface - -<P> -Spider provides a simple BBS interface. No input is required from the sysop -of the cluster at all. The BBS simply sets the cluster as a BBS and pushes -any required mail to the cluster. No mail can flow from Spider to the BBS, -the interface is one-way. - -<P> -Please be careful not to flood the cluster network with unnecessary mail. -Make sure you only send mail to the clusters that want it by using the -Forward.pl file very carefully. - <sect1>Updating kepler data <P> diff --git a/txt/adminmanual.txt b/txt/adminmanual.txt index 98aa9af5..bc8263bc 100644 --- a/txt/adminmanual.txt +++ b/txt/adminmanual.txt @@ -1,6 +1,6 @@ The DXSpider Installation and Administration Manual Ian Maude, G0VGS, (ianmaude@btinternet.com) - Version 1.30 January 2001 + Version 1.31 January 2001 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -113,167 +113,172 @@ 8.2 Filtering DX callouts (Depricated) 8.3 Filtering words from text fields in Announce, Talk and DX spots - 9. Information, files and useful programs + 9. Mail - 9.1 MOTD - 9.2 Downtime message - 9.3 Other text messages - 9.4 The Aliases file - 9.5 Forward.pl - 9.6 Distribution lists - 9.7 Console.pl + 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 - 9.9 Updating kepler data - - 10. CVS - - 11. The DXSpider command set - - 11.1 accept/announce (0) - 11.2 accept/announce (extended for sysops) (8) - 11.3 accept/spots (0) - 11.4 accept/spots (extended for sysops) (8) - 11.5 accept/wcy (0) - 11.6 accept/wcy (extended for sysops) (8) - 11.7 accept/wwv (0) - 11.8 accept/wwv (extended for sysops) (8) - 11.9 announce (0) - 11.10 announce full (0) - 11.11 announce sysop (5) - 11.12 apropos (0) - 11.13 bye (0) - 11.14 catchup (5) - 11.15 clear/spots (0) - 11.16 connect (5) - 11.17 dbavail (0) - 11.18 dbcreate (9) - 11.19 dbimport (9) - 11.20 dbremove (9) - 11.21 dbshow (0) - 11.22 debug (9) - 11.23 directory (0) - 11.24 directory (extended for sysops) (5) - 11.25 disconnect (8) - 11.26 dx (0) - 11.27 export (9) - 11.28 export_users (9) - 11.29 forward/latlong (8) - 11.30 forward/opername (1) - 11.31 help (0) - 11.32 init (5) - 11.33 kill (0) - 11.34 kill (5) - 11.35 kill full (5) - 11.36 links (0) - 11.37 load/aliases (9) - 11.38 load/baddx (9) - 11.39 load/badmsg (9) - 11.40 load/badwords (9) - 11.41 load/bands (9) - 11.42 load/cmd_cache (9) - 11.43 load/forward (9) - 11.44 load/messages (9) - 11.45 load/prefixes (9) - 11.46 merge (5) - 11.47 msg (9) - 11.48 pc (8) - 11.49 ping (1) - 11.50 rcmd (1) - 11.51 read (0) - 11.52 read (extended for sysops) (5) - 11.53 reject/announce - 11.54 reject/announce (extended for sysops) (8) - 11.55 reject/spots (0) - 11.56 reject/spots (extended for sysops) (8) - 11.57 reject/wcy (0) - 11.58 reject/wcy (extended for sysops) (8) - 11.59 reject/wwv (0) - 11.60 reject/wwv (extended for sysops) (8) - 11.61 reply (0) - 11.62 send (0) - 11.63 set/address (0) - 11.64 set/announce (0) - 11.65 set/arcluster (5) - 11.66 set/baddx (8) - 11.67 set/badnode (6) - 11.68 set/badspotter (8) - 11.69 set/beep (0) - 11.70 set/clx (5) - 11.71 set/debug (9) - 11.72 set/dx (0) - 11.73 set/dxgrid (0) - 11.74 set/dxnet (5) - 11.75 set/echo (0) - 11.76 set/here (0) - 11.77 set/homenode (0) - 11.78 set/hops (8) - 11.79 set/isolate (9) - 11.80 set/language (0) - 11.81 set/location (0) - 11.82 set/sys_location (9) - 11.83 set/logininfo (0) - 11.84 set/lockout (9) - 11.85 set/name (0) - 11.86 set/node (9) - 11.87 set/obscount (9) - 11.88 set/page (0) - 11.89 set/password (9) - 11.90 set/pinginterval (9) - 11.91 set/privilege (9) - 11.92 set/spider (5) - 11.93 set/sys_qra (9) - 11.94 set/qra (0) - 11.95 set/qth (0) - 11.96 set/talk (0) - 11.97 set/wcy (0) - 11.98 set/wwv (0) - 11.99 set/wx (0) - 11.100 show/baddx (1) - 11.101 show/badnode (6) - 11.102 show/badspotter (1) - 11.103 show/date (0) - 11.104 show/dx (0) - 11.105 show/dxcc (0) - 11.106 show/files (0) - 11.107 show/filter (0) - 11.108 show/filter (extended for sysops) (5) - 11.109 show/hops (8) - 11.110 show/isolate (1) - 11.111 show/lockout (9) - 11.112 show/moon (0) - 11.113 show/muf (0) - 11.114 show/node (1) - 11.115 show/prefix (0) - 11.116 show/program (5) - 11.117 show/qra (0) - 11.118 show/qrz (0) - 11.119 show/route (0) - 11.120 show/satellite (0) - 11.121 show/sun (0) - 11.122 show/time (0) - 11.123 show/wcy (0) - 11.124 show/wwv (0) - 11.125 shutdown (5) - 11.126 spoof (9) - 11.127 stat/db (5) - 11.128 stat/channel (5) - 11.129 stat/msg (5) - 11.130 stat/user (5) - 11.131 sysop (0) - 11.132 talk (0) - 11.133 type (0) - 11.134 who (0) - 11.135 wx (0) - 11.136 wx (enhanced for sysops) (5) + + 10. Information, files and useful programs + + 10.1 MOTD + 10.2 Downtime message + 10.3 Other text messages + 10.4 The Aliases file + 10.5 Console.pl + 10.6 Updating kepler data + + 11. CVS + + 12. The DXSpider command set + + 12.1 accept/announce (0) + 12.2 accept/announce (extended for sysops) (8) + 12.3 accept/spots (0) + 12.4 accept/spots (extended for sysops) (8) + 12.5 accept/wcy (0) + 12.6 accept/wcy (extended for sysops) (8) + 12.7 accept/wwv (0) + 12.8 accept/wwv (extended for sysops) (8) + 12.9 announce (0) + 12.10 announce full (0) + 12.11 announce sysop (5) + 12.12 apropos (0) + 12.13 bye (0) + 12.14 catchup (5) + 12.15 clear/spots (0) + 12.16 connect (5) + 12.17 dbavail (0) + 12.18 dbcreate (9) + 12.19 dbimport (9) + 12.20 dbremove (9) + 12.21 dbshow (0) + 12.22 debug (9) + 12.23 directory (0) + 12.24 directory (extended for sysops) (5) + 12.25 disconnect (8) + 12.26 dx (0) + 12.27 export (9) + 12.28 export_users (9) + 12.29 forward/latlong (8) + 12.30 forward/opername (1) + 12.31 help (0) + 12.32 init (5) + 12.33 kill (0) + 12.34 kill (5) + 12.35 kill full (5) + 12.36 links (0) + 12.37 load/aliases (9) + 12.38 load/baddx (9) + 12.39 load/badmsg (9) + 12.40 load/badwords (9) + 12.41 load/bands (9) + 12.42 load/cmd_cache (9) + 12.43 load/forward (9) + 12.44 load/messages (9) + 12.45 load/prefixes (9) + 12.46 merge (5) + 12.47 msg (9) + 12.48 pc (8) + 12.49 ping (1) + 12.50 rcmd (1) + 12.51 read (0) + 12.52 read (extended for sysops) (5) + 12.53 reject/announce + 12.54 reject/announce (extended for sysops) (8) + 12.55 reject/spots (0) + 12.56 reject/spots (extended for sysops) (8) + 12.57 reject/wcy (0) + 12.58 reject/wcy (extended for sysops) (8) + 12.59 reject/wwv (0) + 12.60 reject/wwv (extended for sysops) (8) + 12.61 reply (0) + 12.62 send (0) + 12.63 set/address (0) + 12.64 set/announce (0) + 12.65 set/arcluster (5) + 12.66 set/baddx (8) + 12.67 set/badnode (6) + 12.68 set/badspotter (8) + 12.69 set/beep (0) + 12.70 set/clx (5) + 12.71 set/debug (9) + 12.72 set/dx (0) + 12.73 set/dxgrid (0) + 12.74 set/dxnet (5) + 12.75 set/echo (0) + 12.76 set/here (0) + 12.77 set/homenode (0) + 12.78 set/hops (8) + 12.79 set/isolate (9) + 12.80 set/language (0) + 12.81 set/location (0) + 12.82 set/sys_location (9) + 12.83 set/logininfo (0) + 12.84 set/lockout (9) + 12.85 set/name (0) + 12.86 set/node (9) + 12.87 set/obscount (9) + 12.88 set/page (0) + 12.89 set/password (9) + 12.90 set/pinginterval (9) + 12.91 set/privilege (9) + 12.92 set/spider (5) + 12.93 set/sys_qra (9) + 12.94 set/qra (0) + 12.95 set/qth (0) + 12.96 set/talk (0) + 12.97 set/wcy (0) + 12.98 set/wwv (0) + 12.99 set/wx (0) + 12.100 show/baddx (1) + 12.101 show/badnode (6) + 12.102 show/badspotter (1) + 12.103 show/date (0) + 12.104 show/dx (0) + 12.105 show/dxcc (0) + 12.106 show/files (0) + 12.107 show/filter (0) + 12.108 show/filter (extended for sysops) (5) + 12.109 show/hops (8) + 12.110 show/isolate (1) + 12.111 show/lockout (9) + 12.112 show/moon (0) + 12.113 show/muf (0) + 12.114 show/node (1) + 12.115 show/prefix (0) + 12.116 show/program (5) + 12.117 show/qra (0) + 12.118 show/qrz (0) + 12.119 show/route (0) + 12.120 show/satellite (0) + 12.121 show/sun (0) + 12.122 show/time (0) + 12.123 show/wcy (0) + 12.124 show/wwv (0) + 12.125 shutdown (5) + 12.126 spoof (9) + 12.127 stat/db (5) + 12.128 stat/channel (5) + 12.129 stat/msg (5) + 12.130 stat/user (5) + 12.131 sysop (0) + 12.132 talk (0) + 12.133 type (0) + 12.134 who (0) + 12.135 wx (0) + 12.136 wx (enhanced for sysops) (5) ______________________________________________________________________ 11.. IInnssttaallllaattiioonn ((OOrriiggiinnaall vveerrssiioonn bbyy IIaaiinn PPhhiilllliippss,, GG00RRDDII)) - Last modified: 26 January 2001 by Ian Maude, G0VGS - - 11..11.. IInnttrroodduuccttiioonn This section describes the installation of DX Spider v1.35 on a RedHat @@ -322,12 +327,15 @@ the above list as the earliest versions usable. + 11..22.. PPrreeppaarraattiioonn I will assume that you have already downloaded the latest tarball of the DXSpider software and are ready to install it. I am assuming version 1.35 for this section but of course you would use the latest version. + + Login as root and create a user to run the cluster under. _U_N_D_E_R _N_O _C_I_R_C_U_M_S_T_A_N_C_E_S _U_S_E _R_O_O_T _A_S _T_H_I_S _U_S_E_R_!. I am going to use the name _s_y_s_o_p. You can call it anything you wish. Depending on your security @@ -385,6 +393,7 @@ 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 @@ -393,10 +402,9 @@ - - # chown -R sysop.spider spider - # find . -type d -exec chmod 2775 {} \; - # find . -type f -exec chmod 775 {} \; + # chown -R sysop.spider spider + # find . -type d -exec chmod 2775 {} \; + # find . -type f -exec chmod 775 {} \; @@ -452,8 +460,6 @@ There appears to be an extra slash in there. However this has to be there for the file to work so leave it in. - - PPLLEEAASSEE UUSSEE CCAAPPIITTAALL LLEETTTTEERRSS FFOORR CCAALLLLSSIIGGNNSS @@ -526,7 +532,7 @@ - G0VGS de GB7MBC 19-Nov-1999 2150Z > + G0VGS de GB7MBC 19-Nov-1999 2150Z > @@ -586,13 +592,11 @@ 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 + spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet @@ -654,14 +658,10 @@ any major differences at the moment, it allows for compatibility. The 4 types are ... - - - - - set/node (AK1A type) - set/spider - set/dxnet - set/clx + set/node (AK1A type) + set/spider + set/dxnet + set/clx @@ -1833,9 +1833,244 @@ load/badwords. - 99.. IInnffoorrmmaattiioonn,, ffiilleess aanndd uusseeffuull pprrooggrraammss + 99.. MMaaiill + + DXSpider deals seamlessly with standard AK1A type mail. It supports + both personal and bulletin mail and the sysop has additional commands + to ensure that mail gets to where it is meant. DXSpider will send + mail almost immediately, assuming that the target is on line. + However, only one mail message is dealt with at any one time. If a + mail message is already being sent or recieved, then the new message + will be queued until it has finished. + + The cluster mail is automatically deleted after 30 days unless the + sysop sets the "keep" flag using the _m_s_g command. + + 99..11.. PPeerrssoonnaall mmaaiill + + Personal mail is sent using the _s_p 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 _c_o_m_m_a_n_d _s_e_t + section, so I will not duplicate them here. + + + 99..22.. BBuulllleettiinn mmaaiill + + Bulletin mail is sent by using the _s_b command. This is one of the + most common mistakes users make when sending mail. They send a + bulletin mail with _s or _s_p instead of _s_b and of course the message + never leaves the cluster. This can be rectified by the sysop by using + the _m_s_g command. + + + Bulletin addresses can be set using the Forward.pl file. + + + 99..33.. FFoorrwwaarrdd..ppll + + DXSpider receives all and any mail sent to it without any alterations + needed in files. Because personal and bulletin mail are treated + differently, there is no need for a list of accepted bulletin + addresses. It is necessary, however, to tell the program which links + accept which bulletins. For example, it is pointless sending + bulletins addresses to "UK" to any links other than UK ones. The file + that does this is called forward.pl and lives in /spider/msg. At + default, like other spider files it is named forward.pl.issue. Rename + it to forward.pl and edit the file to match your requirements. The + format is below ... + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + # + # this is an example message forwarding file for the system + # + # The format of each line is as follows + # + # type to/from/at pattern action destinations + # P/B/F T/F/A regex I/F [ call [, call ...] ] + # + # type: P - private, B - bulletin (msg), F - file (ak1a bull) + # to/from/at: T - to field, F - from field, A - home bbs, O - origin + # pattern: a perl regex on the field requested + # action: I - ignore, F - forward + # destinations: a reference to an array containing node callsigns + # + # if it is non-private and isn't in here then it won't get forwarded + # + # Currently only type B msgs are affected by this code. + # + # The list is read from the top down, the first pattern that matches + # causes the action to be taken. + # + # The pattern can be undef or 0 in which case it will always be selected + # for the action specified + # + # If the BBS list is undef or 0 and the action is 'F' (and it matches the + # pattern) then it will always be forwarded to every node that doesn't have + # it (I strongly recommend you don't use this unless you REALLY mean it, if + # you allow a new link with this on EVERY bull will be forwarded immediately + # on first connection) + # + + package DXMsg; + + @forward = ( + ); + + + + + Simply insert a bulletin address and state in the brackets where you + wish that mail to go. For example, you can see here that mail sent to + "UK" will only be sent to the UK links and not to PA4AB-14. + + + To force the cluster to reread the file use load/forward + + + + 99..44.. TThhee mmssgg ccoommmmaanndd + + The _m_s_g command is a very powerful and flexible tool for the sysop. + It allows the sysop to alter to and from fields and make other changes + to manage the cluster mail. + + Here is a full list of the various options ... + + + + + + + + + + + + MSG TO <msgno> <call> - change TO callsign to <call> + MSG FRom <msgno> <call> - change FROM callsign to <call> + MSG PRrivate <msgno> - set private flag + MSG NOPRrivate <msgno> - unset private flag + MSG RR <msgno> - set RR flag + MSG NORR <msgno> - unset RR flag + MSG KEep <msgno> - set the keep flag (message won't be deleted ever) + MSG NOKEep <msgno> - unset the keep flag + MSG SUbject <msgno> <new> - change the subject to <new> + MSG WAittime <msgno> - remove any waiting time for this message + MSG NOREad <msgno> - mark message as unread + MSG REad <msgno> - mark message as read + MSG QUeue - queue any outstanding bulletins + MSG QUeue 1 - queue any outstanding private messages + + + + + These commands are simply typed from within the cluster as the sysop + user. + + + 99..55.. MMeessssaaggee ssttaattuuss + + You can check on a message from within the cluster by using the + command _s_t_a_t_/_m_s_g. 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 ... - 99..11.. MMOOTTDD + + + G0VGS de GB7MBC 28-Jan-2001 1308Z > + stat/msg 6869 + From: GB7DJK + Msg Time: 26-Jan-2001 1302Z + Msgno: 6869 + Origin: GB7DJK + Size: 8012 + Subject: AMSAT 2line KEPS 01025.AMSAT + To: UK + Got it Nodes: GB7BAA, GB7ADX + Private: 0 + Read Confirm: 0 + Times read: 0 + G0VGS de GB7MBC 28-Jan-2001 1308Z > + + + + + + 99..66.. FFiilltteerriinngg mmaaiill + + This is described in the section on _O_t_h_e_r _f_i_l_t_e_r_s so I will not + duplicate it here. + + + 99..77.. DDiissttrriibbuuttiioonn lliissttss + + 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 _d_i_s_t_r_o. You put + any distibution lists in here. For example, here is a file called + SYSOP.pl that caters for the UK sysops. + + + qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX + GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH + GB7DXK GB7DXI GB7DXS) + + + + + Any mail sent to "sysop" would only be sent to the callsigns in this + list. + + + 99..88.. BBBBSS iinntteerrffaaccee + + Spider provides a simple BBS interface. No input is required from the + sysop of the cluster at all. The BBS simply sets the cluster as a BBS + and pushes any required mail to the cluster. No mail can flow from + Spider to the BBS, the interface is one-way. + + + Please be careful not to flood the cluster network with unnecessary + mail. Make sure you only send mail to the clusters that want it by + using the Forward.pl file very carefully. + + + 1100.. IInnffoorrmmaattiioonn,, ffiilleess aanndd uusseeffuull pprrooggrraammss + + 1100..11.. MMOOTTDD 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 @@ -1846,7 +2081,7 @@ to the cluster. - 99..22.. DDoowwnnttiimmee mmeessssaaggee + 1100..22.. DDoowwnnttiimmee mmeessssaaggee 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 @@ -1857,7 +2092,7 @@ actually running. - 99..33.. OOtthheerr tteexxtt mmeessssaaggeess + 1100..33.. OOtthheerr tteexxtt mmeessssaaggeess 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 @@ -1875,8 +2110,6 @@ They can be read by the user by typing the command .... - - type news @@ -1912,6 +2145,7 @@ + You can see that in the files area (basically the packclus directory) there is a file called _n_e_w_s and a directory called _b_u_l_l_e_t_i_n_s. You can also see that dates they were created. In the case of the file _n_e_w_s, @@ -1930,21 +2164,33 @@ - show/files bulletins - opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z - opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z - opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z - opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z - opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z - opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z - opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z - opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z - opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z - opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z - opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z - opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z - opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z - Press Enter to continue, A to abort (16 lines) > + + + + + + + + + + + + + show/files bulletins + opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z + opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z + opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z + opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z + opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z + opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z + opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z + opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z + opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z + opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z + opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z + opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z + opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z + Press Enter to continue, A to abort (16 lines) > @@ -1974,7 +2220,7 @@ The page length will of course depend on what you have it set to! - 99..44.. TThhee AAlliiaasseess ffiillee + 1100..44.. TThhee AAlliiaasseess ffiillee 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 @@ -1996,54 +2242,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - #!/usr/bin/perl # provide some standard aliases for commands for terminally @@ -2186,90 +2384,7 @@ the results once you have set an alias. - 99..55.. FFoorrwwaarrdd..ppll - - DXSpider receives all and any mail sent to it without any alterations - needed in files. Because personal and bulletin mail are treated - differently, there is no need for a list of accepted bulletin - addresses. It is necessary, however, to tell the program which links - accept which bulletins. For example, it is pointless sending - bulletins addresses to "UK" to any links other than UK ones. The file - that does this is called forward.pl and lives in /spider/msg. At - default, like other spider files it is named forward.pl.issue. Rename - it to forward.pl and edit the file to match your requirements. The - format is below ... - - - - # - # this is an example message forwarding file for the system - # - # The format of each line is as follows - # - # type to/from/at pattern action destinations - # P/B/F T/F/A regex I/F [ call [, call ...] ] - # - # type: P - private, B - bulletin (msg), F - file (ak1a bull) - # to/from/at: T - to field, F - from field, A - home bbs, O - origin - # pattern: a perl regex on the field requested - # action: I - ignore, F - forward - # destinations: a reference to an array containing node callsigns - # - # if it is non-private and isn't in here then it won't get forwarded - # - # Currently only type B msgs are affected by this code. - # - # The list is read from the top down, the first pattern that matches - # causes the action to be taken. - # - # The pattern can be undef or 0 in which case it will always be selected - # for the action specified - # - # If the BBS list is undef or 0 and the action is 'F' (and it matches the - # pattern) then it will always be forwarded to every node that doesn't have - # it (I strongly recommend you don't use this unless you REALLY mean it, if - # you allow a new link with this on EVERY bull will be forwarded immediately - # on first connection) - # - - package DXMsg; - - @forward = ( - ); - - - - - Simply insert a bulletin address and state in the brackets where you - wish that mail to go. For example, you can see here that mail sent to - "UK" will only be sent to the UK links and not to PA4AB-14. - - - To force the cluster to reread the file use load/forward - - - 99..66.. DDiissttrriibbuuttiioonn lliissttss - - 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 _d_i_s_t_r_o. You put - any distibution lists in here. For example, here is a file called - SYSOP.pl that caters for the UK sysops. - - - - qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX - GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH - GB7DXK GB7DXI GB7DXS) - - - - - Any mail sent to "sysop" would only be sent to the callsigns in this - list. - - - 99..77.. CCoonnssoollee..ppll + 1100..55.. CCoonnssoollee..ppll In later versions of Spider a simple console program is provided for the sysop. This has a type ahead buffer with line editing facilities @@ -2281,20 +2396,7 @@ edit the file with your favourite editor. - 99..88.. BBBBSS iinntteerrffaaccee - - Spider provides a simple BBS interface. No input is required from the - sysop of the cluster at all. The BBS simply sets the cluster as a BBS - and pushes any required mail to the cluster. No mail can flow from - Spider to the BBS, the interface is one-way. - - - Please be careful not to flood the cluster network with unnecessary - mail. Make sure you only send mail to the clusters that want it by - using the Forward.pl file very carefully. - - - 99..99.. UUppddaattiinngg kkeepplleerr ddaattaa + 1100..66.. UUppddaattiinngg kkeepplleerr ddaattaa Spider has a powerful and flexible show/satellite command. In order for this to be accurate, the kepler data has to be updated regularly. @@ -2308,6 +2410,8 @@ export 5467 /spider/perl/keps.in + + would export message number 5467 as a file called keps.in in the /spider/perl directory. @@ -2335,7 +2439,8 @@ - 1100.. CCVVSS + + 1111.. CCVVSS CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held at Sourceforge. This means that it is possible to update your @@ -2440,6 +2545,8 @@ Now the magic part! From now on when you want to update, simply connect to the Internet and then, as the user _s_y_s_o_p ... + + cd /spider cvs -z3 update -d @@ -2455,7 +2562,7 @@ You will find any changes documented in the /spider/Changes file. - 1111.. TThhee DDXXSSppiiddeerr ccoommmmaanndd sseett + 1122.. TThhee DDXXSSppiiddeerr ccoommmmaanndd sseett Below is a complete list of commands available from the cluster prompt. Most maintenance tasks are automatic but there are some @@ -2464,7 +2571,8 @@ is the permissions level needed to use the command. - 1111..11.. aacccceepptt//aannnnoouunnccee ((00)) + + 1122..11.. aacccceepptt//aannnnoouunnccee ((00)) aacccceepptt//aannnnoouunnccee [[00--99]] <<ppaatttteerrnn>> Set an accept filter line for announce @@ -2506,6 +2614,7 @@ + or @@ -2528,7 +2637,8 @@ but this probably for advanced users... - 1111..22.. aacccceepptt//aannnnoouunnccee ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + + 1122..22.. aacccceepptt//aannnnoouunnccee ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) aacccceepptt//aannnnoouunnccee <<ccaallll>> [[iinnppuutt]] [[00--99]]<<ppaatttteerrnn>> Announce filter sysop version @@ -2547,7 +2657,7 @@ - 1111..33.. aacccceepptt//ssppoottss ((00)) + 1122..33.. aacccceepptt//ssppoottss ((00)) aacccceepptt//aannnnoouunnccee [[00--99]] <<ppaatttteerrnn>> Set an accept filter line for spots @@ -2563,28 +2673,19 @@ - - - - - - - - - - freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m - on <range> same as 'freq' - call <prefixes> eg: G,PA,HB9 - info <string> eg: iota or qsl - by <prefixes> - call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G) - call_itu <numbers> - call_zone <numbers> - by_dxcc <numbers> - by_itu <numbers> - by_zone <numbers> - origin <prefixes> - channel <prefixes> + freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m + on <range> same as 'freq' + call <prefixes> eg: G,PA,HB9 + info <string> eg: iota or qsl + by <prefixes> + call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G) + call_itu <numbers> + call_zone <numbers> + by_dxcc <numbers> + by_itu <numbers> + by_zone <numbers> + origin <prefixes> + channel <prefixes> @@ -2603,9 +2704,6 @@ acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) - - - You can use the tag 'all' to accept everything, eg: @@ -2618,7 +2716,7 @@ but this probably for advanced users... - 1111..44.. aacccceepptt//ssppoottss ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 1122..44.. aacccceepptt//ssppoottss ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) aacccceepptt//ssppoottss <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> Spot filter sysop version @@ -2638,7 +2736,7 @@ - 1111..55.. aacccceepptt//wwccyy ((00)) + 1122..55.. aacccceepptt//wwccyy ((00)) aacccceepptt//wwccyy [[00--99]] <<ppaatttteerrnn>> set an accept WCY filter @@ -2671,7 +2769,8 @@ See HELP FILTER for information. - 1111..66.. aacccceepptt//wwccyy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + + 1122..66.. aacccceepptt//wwccyy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) aacccceepptt//wwccyy <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> WCY filter sysop version @@ -2688,7 +2787,7 @@ - 1111..77.. aacccceepptt//wwwwvv ((00)) + 1122..77.. aacccceepptt//wwwwvv ((00)) aacccceepptt//wwwwvv [[00--99]] <<ppaatttteerrnn>> Set an accept WWV filter @@ -2698,21 +2797,15 @@ - - - - - - - by <prefixes> eg: G,M,2 - origin <prefixes> - origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G) - origin_itu <numbers> - origin_zone <numbers> - by_dxcc <numbers> - by_itu <numbers> - by_zone <numbers> - channel <prefixes> + by <prefixes> eg: G,M,2 + origin <prefixes> + origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G) + origin_itu <numbers> + origin_zone <numbers> + by_dxcc <numbers> + by_itu <numbers> + by_zone <numbers> + channel <prefixes> @@ -2732,7 +2825,7 @@ See HELP FILTER for information. - 1111..88.. aacccceepptt//wwwwvv ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 1122..88.. aacccceepptt//wwwwvv ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) aacccceepptt//wwwwvv <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> WWV filter sysop version @@ -2742,17 +2835,18 @@ - accept/wwv db0sue-7 1 by_zone 4 - accept/wwv node_default all - set/hops node_default 10 - accept/wwv user_default by W,K + accept/wwv db0sue-7 1 by_zone 4 + accept/wwv node_default all + set/hops node_default 10 + + accept/wwv user_default by W,K - 1111..99.. aannnnoouunnccee ((00)) + 1122..99.. aannnnoouunnccee ((00)) aannnnoouunnccee <<tteexxtt>> Send an announcement to local users @@ -2761,7 +2855,7 @@ the announcement you wish to broadcast - 1111..1100.. aannnnoouunnccee ffuullll ((00)) + 1122..1100.. aannnnoouunnccee ffuullll ((00)) aannnnoouunnccee ffuullll <<tteexxtt>> Send an announcement cluster wide @@ -2770,7 +2864,8 @@ network. - 1111..1111.. aannnnoouunnccee ssyyssoopp ((55)) + + 1122..1111.. aannnnoouunnccee ssyyssoopp ((55)) aannnnoouunnccee ssyyssoopp <<tteexxtt>> @@ -2778,7 +2873,7 @@ Send an announcement to Sysops only - 1111..1122.. aapprrooppooss ((00)) + 1122..1122.. aapprrooppooss ((00)) aapprrooppooss <<ssttrriinngg>> Search the help database @@ -2787,7 +2882,7 @@ print the names of all the commands that may be relevant. - 1111..1133.. bbyyee ((00)) + 1122..1133.. bbyyee ((00)) bbyyee Exit from the cluster @@ -2795,7 +2890,7 @@ This will disconnect you from the cluster - 1111..1144.. ccaattcchhuupp ((55)) + 1122..1144.. ccaattcchhuupp ((55)) ccaattcchhuupp <<nnooddee__ccaallll>> AAllll||[[<<mmssggnnoo>> ......]] Mark a message as sent @@ -2807,8 +2902,6 @@ This may well be ALL the non-private messages. You can prevent this by using these commmands:- - - catchup GB7DJK all catchup GB7DJK 300 301 302 303 500-510 @@ -2830,12 +2923,11 @@ Order is not important. - 1111..1155.. cclleeaarr//ssppoottss ((00)) + 1122..1155.. cclleeaarr//ssppoottss ((00)) cclleeaarr//ssppoottss [[11||aallll]] Clear a spot filter line - This command allows you to clear (remove) a line in a spot filter or to remove the whole filter. @@ -2880,7 +2972,7 @@ - 1111..1166.. ccoonnnneecctt ((55)) + 1122..1166.. ccoonnnneecctt ((55)) ccoonnnneecctt <<ccaallllssiiggnn>> Start a connection to another DX Cluster @@ -2892,7 +2984,7 @@ cluster <callsign>. - 1111..1177.. ddbbaavvaaiill ((00)) + 1122..1177.. ddbbaavvaaiill ((00)) ddbbaavvaaiill Show a list of all the databases in the system @@ -2901,8 +2993,7 @@ defined in the system. It is also aliased to SHOW/COMMAND. - - 1111..1188.. ddbbccrreeaattee ((99)) + 1122..1188.. ddbbccrreeaattee ((99)) ddbbccrreeaattee <<nnaammee>> Create a database entry ddbbccrreeaattee <<nnaammee>> cchhaaiinn <<nnaammee>> [[<<nnaammee>>....]] Create a chained database @@ -2942,6 +3033,7 @@ To see what databases have been defined do: + DBAVAIL (or it will have been aliased to SHOW/COMMAND) It would be normal for you to add an entry into your local Aliases @@ -2967,12 +3059,11 @@ to work as they may be used to. - See DBIMPORT for the importing of existing AK1A format data to databases. See DBSHOW for generic database enquiry - 1111..1199.. ddbbiimmppoorrtt ((99)) + 1122..1199.. ddbbiimmppoorrtt ((99)) ddbbiimmppoorrtt <<ddbbnnaammee>> Import AK1A data into a database @@ -2987,7 +3078,7 @@ oblast database held locally. - 1111..2200.. ddbbrreemmoovvee ((99)) + 1122..2200.. ddbbrreemmoovvee ((99)) ddbbrreemmoovvee <<ddbbnnaammee>> Delete a database @@ -3008,10 +3099,11 @@ There is no warning, no comeback, no safety net. + You have been warned. - 1111..2211.. ddbbsshhooww ((00)) + 1122..2211.. ddbbsshhooww ((00)) ddbbsshhooww <<ddbbnnaammee>> <<kkeeyy>> Display an entry, if it exists, in a database @@ -3033,15 +3125,14 @@ - - DBSHOW buck G1TLH + DBSHOW buck G1TLH - 1111..2222.. ddeebbuugg ((99)) + 1122..2222.. ddeebbuugg ((99)) ddeebbuugg Set the cluster program into debug mode @@ -3060,7 +3151,7 @@ finished. - 1111..2233.. ddiirreeccttoorryy ((00)) + 1122..2233.. ddiirreeccttoorryy ((00)) ddiirreeccttoorryy List messages ddiirreeccttoorryy oowwnn List your own messages @@ -3074,6 +3165,7 @@ List the messages in the messages directory. + If there is a 'p' one space after the message number then it is a personal message. If there is a '-' between the message number and the @@ -3100,13 +3192,17 @@ DIR/S QSL 10-100 5 - 1111..2244.. ddiirreeccttoorryy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) + + + + + 1122..2244.. ddiirreeccttoorryy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) Works just like the user command except that sysops can see ALL messages. - 1111..2255.. ddiissccoonnnneecctt ((88)) + 1122..2255.. ddiissccoonnnneecctt ((88)) ddiissccoonnnneecctt <<ccaallll>> [[<<ccaallll>> ......]] Disconnect a user or node @@ -3114,7 +3210,7 @@ Disconnect any <call> connected locally - 1111..2266.. ddxx ((00)) + 1122..2266.. ddxx ((00)) ddxx [[bbyy <<ccaallll>>]] <<ffrreeqq>> <<ccaallll>> <<rreemmaarrkkss>> Send a DX spot @@ -3136,7 +3232,7 @@ - DX FR0G 144600 this is a test + DX FR0G 144600 this is a test @@ -3154,7 +3250,7 @@ cluster. See SHOW/BANDS for more information. - 1111..2277.. eexxppoorrtt ((99)) + 1122..2277.. eexxppoorrtt ((99)) eexxppoorrtt <<mmssggnnoo>> <<ffiilleennaammee>> Export a message to a file @@ -3172,7 +3268,7 @@ EXPORT 2345 /tmp/a - 1111..2288.. eexxppoorrtt__uusseerrss ((99)) + 1122..2288.. eexxppoorrtt__uusseerrss ((99)) eexxppoorrtt__uusseerrss [[<<ffiilleennaammee>>]] Export the users database to ascii @@ -3188,7 +3284,7 @@ check is made on the filename (if any) that you specify. - 1111..2299.. ffoorrwwaarrdd//llaattlloonngg ((88)) + 1122..2299.. ffoorrwwaarrdd//llaattlloonngg ((88)) ffoorrwwaarrdd//llaattlloonngg <<nnooddee__ccaallll>> Send latitude and longitude information to another cluster @@ -3202,7 +3298,7 @@ so it is not recommended on slow links. - 1111..3300.. ffoorrwwaarrdd//ooppeerrnnaammee ((11)) + 1122..3300.. ffoorrwwaarrdd//ooppeerrnnaammee ((11)) ffoorrwwaarrdd//ooppeerrnnaammee <<ccaallll>> Send out information on this <call> to all clusters @@ -3214,7 +3310,7 @@ available. - 1111..3311.. hheellpp ((00)) + 1122..3311.. hheellpp ((00)) hheellpp <<ccmmdd>> Get help on a command @@ -3227,7 +3323,7 @@ commands to look at with HELP. - 1111..3322.. iinniitt ((55)) + 1122..3322.. iinniitt ((55)) iinniitt <<nnooddee ccaallll>> Re-initialise a link to an AK1A compatible node @@ -3241,7 +3337,7 @@ Best of luck - you will need it. - 1111..3333.. kkiillll ((00)) + 1122..3333.. kkiillll ((00)) kkiillll <<mmssggnnoo>> [[<<mmssggnnoo>> ....]] Delete a message from the local system @@ -3251,7 +3347,7 @@ the sysop). - 1111..3344.. kkiillll ((55)) + 1122..3344.. kkiillll ((55)) kkiillll <<mmssggnnoo>> [[<<mmssggnnoo>> ......]] Remove or erase a message from the system kkiillll ffrroomm <<ccaallll>> Remove all messages from a callsign @@ -3264,18 +3360,17 @@ As a sysop you can kill any message on the system. - 1111..3355.. kkiillll ffuullll ((55)) + 1122..3355.. kkiillll ffuullll ((55)) kkiillll ffuullll <<mmssggnnoo>> [[<<mmssggnnoo>>]] Delete a message from the whole cluster - Delete a message (usually a 'bulletin') from the whole cluster system. This uses the subject field, so any messages that have exactly the same subject will be deleted. Beware! - 1111..3366.. lliinnkkss ((00)) + 1122..3366.. lliinnkkss ((00)) lliinnkkss Show which nodes are physically connected @@ -3285,7 +3380,7 @@ - 1111..3377.. llooaadd//aalliiaasseess ((99)) + 1122..3377.. llooaadd//aalliiaasseess ((99)) llooaadd//aalliiaasseess Reload the command alias table @@ -3296,9 +3391,7 @@ - - - 1111..3388.. llooaadd//bbaaddddxx ((99)) + 1122..3388.. llooaadd//bbaaddddxx ((99)) llooaadd//bbaaddddxx Reload the bad DX table @@ -3308,7 +3401,7 @@ if spotted, will not be passed on. FR0G and TEST are classic examples. - 1111..3399.. llooaadd//bbaaddmmssgg ((99)) + 1122..3399.. llooaadd//bbaaddmmssgg ((99)) llooaadd//bbaaddmmssgg Reload the bad message table @@ -3320,7 +3413,7 @@ deleted on receipt. - 1111..4400.. llooaadd//bbaaddwwoorrddss ((99)) + 1122..4400.. llooaadd//bbaaddwwoorrddss ((99)) llooaadd//bbaaddwwoorrddss Reload the badwords file @@ -3334,7 +3427,10 @@ ignored. - 1111..4411.. llooaadd//bbaannddss ((99)) + + + + 1122..4411.. llooaadd//bbaannddss ((99)) llooaadd//bbaannddss Reload the band limits table @@ -3343,7 +3439,7 @@ whilst the cluster is running. - 1111..4422.. llooaadd//ccmmdd__ccaacchhee ((99)) + 1122..4422.. llooaadd//ccmmdd__ccaacchhee ((99)) llooaadd//ccmmdd__ccaacchhee Reload the automatic command cache @@ -3356,7 +3452,7 @@ was just after a cluster restart. - 1111..4433.. llooaadd//ffoorrwwaarrdd ((99)) + 1122..4433.. llooaadd//ffoorrwwaarrdd ((99)) llooaadd//ffoorrwwaarrdd Reload the msg forwarding routing table @@ -3364,7 +3460,7 @@ whilst the cluster is running. - 1111..4444.. llooaadd//mmeessssaaggeess ((99)) + 1122..4444.. llooaadd//mmeessssaaggeess ((99)) llooaadd//mmeessssaaggeess Reload the system messages file @@ -3377,7 +3473,7 @@ unknown message 'xxxx' in lang 'en' - 1111..4455.. llooaadd//pprreeffiixxeess ((99)) + 1122..4455.. llooaadd//pprreeffiixxeess ((99)) llooaadd//pprreeffiixxeess Reload the prefix table @@ -3386,7 +3482,7 @@ manually whilst the cluster is running. - 1111..4466.. mmeerrggee ((55)) + 1122..4466.. mmeerrggee ((55)) mmeerrggee <<nnooddee>> [[<<nnoo ssppoottss>>//<<nnoo wwwwvv>>]] Ask for the latest spots and WWV @@ -3400,8 +3496,7 @@ recently been added (the last 2 days for spots and last month for WWV data). - - 1111..4477.. mmssgg ((99)) + 1122..4477.. mmssgg ((99)) mmssgg <<ccmmdd>> <<mmssggnnoo>> [[ddaattaa ......]] Alter various message parameters @@ -3437,7 +3532,7 @@ This will display more information on the message than DIR does. - 1111..4488.. ppcc ((88)) + 1122..4488.. ppcc ((88)) ppcc <<ccaallll>> <<tteexxtt>> Send text (eg PC Protocol) to <call> @@ -3456,7 +3551,7 @@ pc G1TLH Try doing that properly!!! - 1111..4499.. ppiinngg ((11)) + 1122..4499.. ppiinngg ((11)) ppiinngg <<nnooddee>> Check the link quality between nodes @@ -3467,9 +3562,7 @@ is output to the console in seconds. Any visible cluster node can be PINGed. - - - 1111..5500.. rrccmmdd ((11)) + 1122..5500.. rrccmmdd ((11)) rrccmmdd <<nnooddee ccaallll>> <<ccmmdd>> Send a command to another DX cluster @@ -3483,7 +3576,7 @@ whether you have permission to send this command at all. - 1111..5511.. rreeaadd ((00)) + 1122..5511.. rreeaadd ((00)) rreeaadd Read the next unread personal message addressed to you rreeaadd <<mmssggnnoo>> Read the specified message @@ -3494,9 +3587,7 @@ - - - 1111..5522.. rreeaadd ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) + 1122..5522.. rreeaadd ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) rreeaadd <<mmssggnnoo>> Read a message on the system @@ -3504,7 +3595,7 @@ As a sysop you may read any message on the system - 1111..5533.. rreejjeecctt//aannnnoouunnccee + 1122..5533.. rreejjeecctt//aannnnoouunnccee rreejjeecctt//aannnnoouunnccee [[00--99]] <<ppaatttteerrnn>> Set a reject filter for announce @@ -3536,6 +3627,7 @@ + some examples:- @@ -3557,11 +3649,12 @@ but this probably for advanced users... - 1111..5544.. rreejjeecctt//aannnnoouunnccee ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 1122..5544.. rreejjeecctt//aannnnoouunnccee ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) rreejjeecctt//aannnnoouunnccee <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> Announce filter sysop version + This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:- @@ -3575,7 +3668,7 @@ - 1111..5555.. rreejjeecctt//ssppoottss ((00)) + 1122..5555.. rreejjeecctt//ssppoottss ((00)) rreejjeecctt//ssppoottss [[00--99]] <<ppaatttteerrnn>> Set a reject filter line for spots @@ -3591,19 +3684,29 @@ - freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m - on <range> same as 'freq' - call <prefixes> eg: G,PA,HB9 - info <string> eg: iota or qsl - by <prefixes> - call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G) - call_itu <numbers> - call_zone <numbers> - by_dxcc <numbers> - by_itu <numbers> - by_zone <numbers> - origin <prefixes> - channel <prefixes> + + + + + + + + + + + freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m + on <range> same as 'freq' + call <prefixes> eg: G,PA,HB9 + info <string> eg: iota or qsl + by <prefixes> + call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G) + call_itu <numbers> + call_zone <numbers> + by_dxcc <numbers> + by_itu <numbers> + by_zone <numbers> + origin <prefixes> + channel <prefixes> @@ -3628,7 +3731,7 @@ - rej/spot 3 all + rej/spot 3 all @@ -3636,7 +3739,7 @@ but this probably for advanced users... - 1111..5566.. rreejjeecctt//ssppoottss ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 1122..5566.. rreejjeecctt//ssppoottss ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) rreejjeecctt//ssppoottss <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> Reject spot filter sysop version @@ -3657,7 +3760,7 @@ - 1111..5577.. rreejjeecctt//wwccyy ((00)) + 1122..5577.. rreejjeecctt//wwccyy ((00)) rreejjeecctt//wwccyy [[00--99]] <<ppaatttteerrnn>> Set a reject WCY filter @@ -3689,18 +3792,19 @@ See HELP FILTER for information. - 1111..5588.. rreejjeecctt//wwccyy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 1122..5588.. rreejjeecctt//wwccyy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) rreejjeecctt//wwccyy <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> WCY reject filter sysop version + This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:- reject/wcy gb7djk all - 1111..5599.. rreejjeecctt//wwwwvv ((00)) + 1122..5599.. rreejjeecctt//wwwwvv ((00)) rreejjeecctt//wwwwvv [[00--99]] <<ppaatttteerrnn>> Set a reject WWV filter @@ -3722,7 +3826,6 @@ - for example @@ -3738,7 +3841,7 @@ See HELP FILTER for information. - 1111..6600.. rreejjeecctt//wwwwvv ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 1122..6600.. rreejjeecctt//wwwwvv ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) rreejjeecctt//wwwwvv <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> WWV reject filter sysop version @@ -3758,9 +3861,7 @@ - - - 1111..6611.. rreeppllyy ((00)) + 1122..6611.. rreeppllyy ((00)) rreeppllyy Reply (privately) to the last message that you have read rreeppllyy <<mmssggnnoo>> Reply (privately) to the specified message @@ -3777,7 +3878,7 @@ further details) - 1111..6622.. sseenndd ((00)) + 1122..6622.. sseenndd ((00)) sseenndd <<ccaallll>> [[<<ccaallll>> ......]] Send a message to one or more callsigns sseenndd RRRR <<ccaallll>> Send a message and ask for a read receipt @@ -3811,7 +3912,7 @@ is an alias for SEND PRIVATE - 1111..6633.. sseett//aaddddrreessss ((00)) + 1122..6633.. sseett//aaddddrreessss ((00)) sseett//aaddddrreessss <<yyoouurr__aaddddrreessss>> Record your postal address @@ -3819,14 +3920,15 @@ Literally, record your address details on the cluster. - 1111..6644.. sseett//aannnnoouunnccee ((00)) + 1122..6644.. sseett//aannnnoouunnccee ((00)) sseett//aannnnoouunnccee Allow announce messages Allow announce messages to arrive at your terminal. - 1111..6655.. sseett//aarrcclluusstteerr ((55)) + + 1122..6655.. sseett//aarrcclluusstteerr ((55)) sseett//aarrcclluusstteerr <<nnooddee__ccaallll>> [[<<nnooddee__ccaallll>> ......]] Make the node_call an AR- Cluster type node @@ -3835,7 +3937,7 @@ Set the node_call as an AR-Cluster type node - 1111..6666.. sseett//bbaaddddxx ((88)) + 1122..6666.. sseett//bbaaddddxx ((88)) sseett//bbaaddddxx <<ccaallll>> Stop words we do not wish to see in the callsign field of a dx spot being propagated @@ -3856,15 +3958,13 @@ To allow a word again, use the following command ... - - unset/baddx VIDEO - 1111..6677.. sseett//bbaaddnnooddee ((66)) + 1122..6677.. sseett//bbaaddnnooddee ((66)) sseett//bbaaddnnooddee <<nnooddee__ccaallll>> Stop spots from this node_call being propagated @@ -3898,7 +3998,7 @@ FILTERing. - 1111..6688.. sseett//bbaaddssppootttteerr ((88)) + 1122..6688.. sseett//bbaaddssppootttteerr ((88)) sseett//bbaaddssppootttteerr <<ccaallll>> Stop spots from this callsign being propagated @@ -3924,15 +4024,13 @@ unset/badspotter VE2STN - - will allow spots from him again. Use with extreme care. This command may well be superceded by FILTERing. - 1111..6699.. sseett//bbeeeepp ((00)) + 1122..6699.. sseett//bbeeeepp ((00)) sseett//bbeeeepp Add beeps to terminal messages @@ -3940,7 +4038,7 @@ Add a beep to DX and other terminal messages. - 1111..7700.. sseett//ccllxx ((55)) + 1122..7700.. sseett//ccllxx ((55)) sseett//ccllxx <<nnooddee__ccaallll>> [[<<nnooddee__ccaallll>> ......]] Make the node_call a CLX type node @@ -3949,7 +4047,7 @@ Set the node_call as a CLX type node - 1111..7711.. sseett//ddeebbuugg ((99)) + 1122..7711.. sseett//ddeebbuugg ((99)) sseett//ddeebbuugg <<nnaammee>> Add a debug level to the debug set @@ -3957,8 +4055,7 @@ You can remove this level with unset/debug <name> - - 1111..7722.. sseett//ddxx ((00)) + 1122..7722.. sseett//ddxx ((00)) sseett//ddxxAllow DX messages to arrive at your terminal @@ -3966,7 +4063,7 @@ You can stop DX messages with the _u_n_s_e_t_/_d_x command - 1111..7733.. sseett//ddxxggrriidd ((00)) + 1122..7733.. sseett//ddxxggrriidd ((00)) sseett//ddxxggrriiddAllow grid squares on the end of DX messages @@ -3976,7 +4073,7 @@ to remove the grid squares. - 1111..7744.. sseett//ddxxnneett ((55)) + 1122..7744.. sseett//ddxxnneett ((55)) sseett//ddxxnneett <<nnooddee__ccaallll>> [[<<nnooddee__ccaallll>> ......]] Make the node_call a DXNet type node @@ -3985,7 +4082,7 @@ Set the node_call as a DXNet type node - 1111..7755.. sseett//eecchhoo ((00)) + 1122..7755.. sseett//eecchhoo ((00)) sseett//eecchhoo Make the cluster echo your input @@ -4002,7 +4099,7 @@ YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25. - 1111..7766.. sseett//hheerree ((00)) + 1122..7766.. sseett//hheerree ((00)) sseett//hheerree Set the here flag @@ -4013,7 +4110,7 @@ brackets around your callsign to indicate you are not available. - 1111..7777.. sseett//hhoommeennooddee ((00)) + 1122..7777.. sseett//hhoommeennooddee ((00)) sseett//hhoommeennooddee <<nnooddee__ccaallll>> Set your home cluster @@ -4024,13 +4121,13 @@ - SET/HOMENODE gb7djk + SET/HOMENODE gb7djk - 1111..7788.. sseett//hhooppss ((88)) + 1122..7788.. sseett//hhooppss ((88)) sseett//hhooppss <<nnooddee__ccaallll>> aannnn||ssppoottss||wwwwvv||wwccyy <<nn>> Set hop count @@ -4053,11 +4150,12 @@ creates a filter and works in conjunction with the filter system. - 1111..7799.. sseett//iissoollaattee ((99)) + 1122..7799.. sseett//iissoollaattee ((99)) sseett//iissoollaattee <<nnooddee ccaallll>> Isolate a node from the rest of the network + Connect a node to your system in such a way that you are a full protocol member of its network and can see all spots on it, but nothing either leaks out from it nor goes back into from the rest of @@ -4071,7 +4169,7 @@ You can remove the isolation with the command unset/isolate. - 1111..8800.. sseett//llaanngguuaaggee ((00)) + 1122..8800.. sseett//llaanngguuaaggee ((00)) sseett//llaanngguuaaggee <<llaanngguuaaggee>> Set the language you wish to use @@ -4080,7 +4178,7 @@ Currently the languages available are _e_n (English) and _n_l (Dutch). - 1111..8811.. sseett//llooccaattiioonn ((00)) + 1122..8811.. sseett//llooccaattiioonn ((00)) sseett//llooccaattiioonn <<llaatt aanndd lloonngg>> Set your latitude and longitude @@ -4090,14 +4188,14 @@ - set/location 54 04 N 2 02 E + set/location 54 04 N 2 02 E - 1111..8822.. sseett//ssyyss__llooccaattiioonn ((99)) + 1122..8822.. sseett//ssyyss__llooccaattiioonn ((99)) sseett//ssyyss__llooccaattiioonn <<llaatt && lloonngg>> Set your cluster latitude and longitude @@ -4115,7 +4213,7 @@ - 1111..8833.. sseett//llooggiinniinnffoo ((00)) + 1122..8833.. sseett//llooggiinniinnffoo ((00)) sseett//llooggiinniinnffoo Show logins and logouts of nodes and users @@ -4124,8 +4222,7 @@ You can stop these messages by using the _u_n_s_e_t_/_l_o_g_i_n_i_n_f_o command. - - 1111..8844.. sseett//lloocckkoouutt ((99)) + 1122..8844.. sseett//lloocckkoouutt ((99)) sseett//lloocckkoouutt <<ccaallll>> Stop a callsign connecting to the cluster @@ -4134,7 +4231,7 @@ allow the user to connect again, use the _u_n_s_e_t_/_l_o_c_k_o_u_t command. - 1111..8855.. sseett//nnaammee ((00)) + 1122..8855.. sseett//nnaammee ((00)) sseett//nnaammee <<yyoouurr__nnaammee>> Set your name @@ -4149,13 +4246,14 @@ - 1111..8866.. sseett//nnooddee ((99)) + 1122..8866.. sseett//nnooddee ((99)) sseett//nnooddee <<ccaallll>> [[<<ccaallll>> ......]] Make the callsign an AK1A cluster Tell the system that the call(s) are to be treated as AK1A cluster and fed PC Protocol rather normal user commands. + From version 1.41 you can also set the following types of cluster @@ -4171,7 +4269,7 @@ To see what your nodes are set to, use the _s_h_o_w_/_n_o_d_e_s command. - 1111..8877.. sseett//oobbssccoouunntt ((99)) + 1122..8877.. sseett//oobbssccoouunntt ((99)) sseett//oobbssccoouunntt <<ccoouunntt>> <<nnooddee ccaallll>> Set the 'pump-up' obsolescence counter @@ -4190,9 +4288,7 @@ If a ping is heard then the obscount is reset to the full value. Using default values, if a node has not responded to a ping within 15 minutes, it is disconnected. - - - 1111..8888.. sseett//ppaaggee ((00)) + 1122..8888.. sseett//ppaaggee ((00)) sseett//ppaaggee <<nn>> Set the number of lines per page @@ -4213,7 +4309,7 @@ - 1111..8899.. sseett//ppaasssswwoorrdd ((99)) + 1122..8899.. sseett//ppaasssswwoorrdd ((99)) sseett//ppaasssswwoorrdd <<ccaallllssiiggnn>> <<ssttrriinngg>> Set a users password @@ -4225,7 +4321,7 @@ type password. - 1111..9900.. sseett//ppiinnggiinntteerrvvaall ((99)) + 1122..9900.. sseett//ppiinnggiinntteerrvvaall ((99)) sseett//ppiinnggiinntteerrvvaall <<ttiimmee>> <<nnooddee ccaallll>> Set the ping time to neighbouring nodes @@ -4246,7 +4342,7 @@ for more information. - 1111..9911.. sseett//pprriivviilleeggee ((99)) + 1122..9911.. sseett//pprriivviilleeggee ((99)) sseett//pprriivviilleeggee <<nn>> <<ccaallll>> [[<<ccaallll>> ......]] Set the privilege level on a call @@ -4257,13 +4353,14 @@ - 0 - normal user - 1 - allow remote nodes normal user RCMDs - 5 - various privileged commands (including shutdown, but not disc- - connect), the normal level for another node. - 8 - more privileged commands (including disconnect) - 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS - LEVEL. + + 0 - normal user + 1 - allow remote nodes normal user RCMDs + 5 - various privileged commands (including shutdown, but not disc- + connect), the normal level for another node. + 8 - more privileged commands (including disconnect) + 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS + LEVEL. @@ -4272,7 +4369,7 @@ connection your privilege will automatically be set to 0. - 1111..9922.. sseett//ssppiiddeerr ((55)) + 1122..9922.. sseett//ssppiiddeerr ((55)) sseett//ssppiiddeerr <<nnooddee__ccaallll>> [[<<nnooddee__ccaallll>> ......]] Make the node_call a DXSpider type node @@ -4281,14 +4378,12 @@ Set the node_call as a DXSpider type node - 1111..9933.. sseett//ssyyss__qqrraa ((99)) + 1122..9933.. sseett//ssyyss__qqrraa ((99)) sseett//ssyyss__qqrraa <<llooccaattoorr>> Set your cluster QRA locator - - - 1111..9944.. sseett//qqrraa ((00)) + 1122..9944.. sseett//qqrraa ((00)) sseett//qqrraa <<llooccaattoorr>> Set your QRA locator @@ -4305,7 +4400,7 @@ - 1111..9955.. sseett//qqtthh ((00)) + 1122..9955.. sseett//qqtthh ((00)) sseett//qqtthh <<yyoouurr QQTTHH>> Set your QTH @@ -4320,7 +4415,7 @@ - 1111..9966.. sseett//ttaallkk ((00)) + 1122..9966.. sseett//ttaallkk ((00)) sseett//ttaallkk Allow talk messages to be seen at your console @@ -4329,7 +4424,7 @@ talks with the _u_n_s_e_t_/_t_a_l_k command. - 1111..9977.. sseett//wwccyy ((00)) + 1122..9977.. sseett//wwccyy ((00)) sseett//wwccyy Allow WCY messages to be seen at your console @@ -4338,7 +4433,7 @@ WCY messages with the _u_n_s_e_t_/_w_c_y command. - 1111..9988.. sseett//wwwwvv ((00)) + 1122..9988.. sseett//wwwwvv ((00)) sseett//wwwwvv Allow WWV messages to be seen at your console @@ -4347,14 +4442,16 @@ WWV messages with the _u_n_s_e_t_/_w_w_v command. - 1111..9999.. sseett//wwxx ((00)) + 1122..9999.. sseett//wwxx ((00)) sseett//wwxx 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 _u_n_s_e_t_/_w_x command. - 1111..110000.. sshhooww//bbaaddddxx ((11)) + + + 1122..110000.. sshhooww//bbaaddddxx ((11)) sshhooww//bbaaddddxxShow all the bad dx calls in the system @@ -4363,7 +4460,7 @@ information. - 1111..110011.. sshhooww//bbaaddnnooddee ((66)) + 1122..110011.. sshhooww//bbaaddnnooddee ((66)) sshhooww//bbaaddnnooddee Show all the bad nodes in the system @@ -4372,7 +4469,7 @@ more information. - 1111..110022.. sshhooww//bbaaddssppootttteerr ((11)) + 1122..110022.. sshhooww//bbaaddssppootttteerr ((11)) sshhooww//bbaaddssppootttteerrShow all the bad spotters in the system @@ -4381,7 +4478,7 @@ SET/BADSPOTTER for more information. - 1111..110033.. sshhooww//ddaattee ((00)) + 1122..110033.. sshhooww//ddaattee ((00)) sshhooww//ddaattee [[<<pprreeffiixx>>||<<ccaallllssiiggnn>>]] Show the local time @@ -4395,7 +4492,7 @@ including DST) at the prefixes or callsigns that you specify. - 1111..110044.. sshhooww//ddxx ((00)) + 1122..110044.. sshhooww//ddxx ((00)) sshhooww//ddxx [[ooppttiioonnss]] interrogate the spot database @@ -4409,46 +4506,35 @@ + on <band> - eg 160m 20m 2m 23cm 6mm + on <region> - eg hf vhf uhf shf (see SHOW/BANDS) + <number> - the number of spots you want + <from>-<to> - <from> spot no <to> spot no in + the selected list + <prefix> - for a spotted callsign beginning with <prefix> + *<suffix> - for a spotted callsign ending in <suffix> + *<string>* - for a spotted callsign containing <string> + day <number> - starting <number> days ago + day <from>-<to> - <from> days <to> days ago + info <text> - any spots containing <text> in the info or remarks + by <call> - any spots spotted by <call> (spotter <call> + is the same). + qsl - this automatically looks for any qsl info on the call + held in the spot database. + iota [<iota>] - If the iota island number is missing it will + look for the string iota and anything which looks like + an iota island number. If you specify then it will look + for that island. - - - - on <band> - eg 160m 20m 2m 23cm 6mm - on <region> - eg hf vhf uhf shf (see SHOW/BANDS) - - <number> - the number of spots you want - <from>-<to> - <from> spot no <to> spot no in - the selected list - - <prefix> - for a spotted callsign beginning with <prefix> - *<suffix> - for a spotted callsign ending in <suffix> - *<string>* - for a spotted callsign containing <string> - - day <number> - starting <number> days ago - day <from>-<to> - <from> days <to> days ago - - info <text> - any spots containing <text> in the info or remarks - - by <call> - any spots spotted by <call> (spotter <call> - is the same). - - qsl - this automatically looks for any qsl info on the call - held in the spot database. - - iota [<iota>] - If the iota island number is missing it will - look for the string iota and anything which looks like - an iota island number. If you specify then it will look - for that island. - - qra [<locator>] - this will look for the specific locator if - you specify one or else anything that looks like a locator. + qra [<locator>] - this will look for the specific locator if + you specify one or else anything that looks like a locator. @@ -4466,11 +4552,7 @@ SH/DX iota eu-064 SH/DX qra jn86 - - - - - 1111..110055.. sshhooww//ddxxcccc ((00)) + 1122..110055.. sshhooww//ddxxcccc ((00)) sshhooww//ddxxcccc <<pprreeffiixx>> Interrogate the spot database by country @@ -4484,16 +4566,14 @@ + SH/DXCC G + SH/DXCC W on 20m info iota - SH/DXCC G - SH/DXCC W on 20m info iota - - - 1111..110066.. sshhooww//ffiilleess ((00)) + 1122..110066.. sshhooww//ffiilleess ((00)) sshhooww//ffiilleess [[<<ffiilleeaarreeaa>> [[<<ssttrriinngg>>]]]] List the contents of a filearea @@ -4525,7 +4605,7 @@ See also TYPE - to see the contents of a file. - 1111..110077.. sshhooww//ffiilltteerr ((00)) + 1122..110077.. sshhooww//ffiilltteerr ((00)) sshhooww//ffiilltteerr Show the filters you have set @@ -4534,15 +4614,14 @@ displays all the filters set - for all the various categories. - 1111..110088.. sshhooww//ffiilltteerr ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) + 1122..110088.. sshhooww//ffiilltteerr ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) sshhooww//ffiilltteerr <<ccaallllssiiggnn>> Show the filters set by <callsign> - A sysop can look at any filters that have been set. - 1111..110099.. sshhooww//hhooppss ((88)) + 1122..110099.. sshhooww//hhooppss ((88)) sshhooww//hhooppss <<nnooddee__ccaallll>> [[aannnn||ssppoottss||wwccyy||wwwwvv||]] Show the hop counts for a node @@ -4552,7 +4631,8 @@ which category you want to see. If you leave the category out then all the categories will be listed. - 1111..111100.. sshhooww//iissoollaattee ((11)) + + 1122..111100.. sshhooww//iissoollaattee ((11)) sshhooww//iissoollaattee Show a list of isolated nodes @@ -4560,7 +4640,7 @@ Show which nodes are currently set to be isolated. - 1111..111111.. sshhooww//lloocckkoouutt ((99)) + 1122..111111.. sshhooww//lloocckkoouutt ((99)) sshhooww//lloocckkoouutt Show a list of excluded callsigns @@ -4569,7 +4649,7 @@ cluster locally with the _s_e_t_/_l_o_c_k_o_u_t command - 1111..111122.. sshhooww//mmoooonn ((00)) + 1122..111122.. sshhooww//mmoooonn ((00)) sshhooww//mmoooonn [[<<pprreeffiixx>>||<<ccaallllssiiggnn>>]] Show moon rise and set times @@ -4599,12 +4679,11 @@ - 1111..111133.. sshhooww//mmuuff ((00)) + 1122..111133.. sshhooww//mmuuff ((00)) sshhooww//mmuuff <<pprreeffiixx>> [[<<hhoouurrss>>]][[lloonngg]] Show the likely propagation to <prefix> - This command allow you to estimate the likelihood of you contacting a station with the prefix you have specified. The output assumes a modest power of 20dBW and receiver sensitivity of -123dBm (about @@ -4671,7 +4750,6 @@ inputing:- - SH/MUF W 24 @@ -4682,10 +4760,8 @@ - - - SH/MUF W L 24 - SH/MUF W 24 Long + SH/MUF W L 24 + SH/MUF W 24 Long @@ -4695,7 +4771,7 @@ terrible accurate, but it is included for completeness. - 1111..111144.. sshhooww//nnooddee ((11)) + 1122..111144.. sshhooww//nnooddee ((11)) sshhooww//nnooddee [[<<nnooddee__ccaallll>> ......]] Show the type and version number of nodes @@ -4705,7 +4781,7 @@ the non-user callsigns known to the system will be displayed. - 1111..111155.. sshhooww//pprreeffiixx ((00)) + 1122..111155.. sshhooww//pprreeffiixx ((00)) sshhooww//pprreeffiixx <<ccaallllssiiggnn>> Interrogate the prefix database @@ -4719,7 +4795,7 @@ - 1111..111166.. sshhooww//pprrooggrraamm ((55)) + 1122..111166.. sshhooww//pprrooggrraamm ((55)) sshhooww//pprrooggrraamm Show the locations of all the included program modules @@ -4729,7 +4805,7 @@ from. - 1111..111177.. sshhooww//qqrraa ((00)) + 1122..111177.. sshhooww//qqrraa ((00)) sshhooww//qqrraa <<llooccaattoorr>> [[<<llooccaattoorr>>]] Show the distance between locators sshhooww//qqrraa <<llaatt>> <<lloonngg>> Convert latitude and longitude to a locator @@ -4740,8 +4816,6 @@ given on the command line) the distance and beraing from your station to the locator. For example:- - - SH/QRA IO92QL SH/QRA JN06 IN73 @@ -4765,7 +4839,7 @@ - 1111..111188.. sshhooww//qqrrzz ((00)) + 1122..111188.. sshhooww//qqrrzz ((00)) sshhooww//qqrrzz <<ccaallllssiiggnn>> Show any callbook details on a callsign @@ -4775,7 +4849,7 @@ provided for users of this software by http://www.qrz.com - 1111..111199.. sshhooww//rroouuttee ((00)) + 1122..111199.. sshhooww//rroouuttee ((00)) sshhooww//rroouuttee <<ccaallllssiiggnn>> Show the route to <callsign> @@ -4791,7 +4865,7 @@ - 1111..112200.. sshhooww//ssaatteelllliittee ((00)) + 1122..112200.. sshhooww//ssaatteelllliittee ((00)) sshhooww//ssaatteelllliittee <<nnaammee>> [[<<hhoouurrss>> <<iinntteerrvvaall>>]] Show satellite tracking data @@ -4816,6 +4890,7 @@ So for example:- + SH/SAT AO-10 SH/SAT FENGYUN1 12 2 @@ -4823,7 +4898,7 @@ - 1111..112211.. sshhooww//ssuunn ((00)) + 1122..112211.. sshhooww//ssuunn ((00)) sshhooww//ssuunn [[<<pprreeffiixx>>||<<ccaallllssiiggnn>>]] Show sun rise and set times @@ -4850,7 +4925,7 @@ - 1111..112222.. sshhooww//ttiimmee ((00)) + 1122..112222.. sshhooww//ttiimmee ((00)) sshhooww//ttiimmee [[<<pprreeffiixx>>||<<ccaallllssiiggnn>>]] Show the local time @@ -4861,7 +4936,7 @@ including DST) at the prefixes or callsigns that you specify. - 1111..112233.. sshhooww//wwccyy ((00)) + 1122..112233.. sshhooww//wwccyy ((00)) sshhooww//wwccyy Show the last 10 WCY broadcasts sshhooww//wwccyy <<nn>> Show the last <n> WCY broadcasts @@ -4871,7 +4946,9 @@ system - 1111..112244.. sshhooww//wwwwvv ((00)) + + + 1122..112244.. sshhooww//wwwwvv ((00)) sshhooww//wwwwvv Show the last 10 WWV broadcasts sshhooww//wwwwvv <<nn>> Show the last <n> WWV broadcasts @@ -4882,7 +4959,7 @@ - 1111..112255.. sshhuuttddoowwnn ((55)) + 1122..112255.. sshhuuttddoowwnn ((55)) sshhuuttddoowwnn Shutdown the cluster @@ -4891,7 +4968,7 @@ set to respawn in /etc/inittab it will of course restart. - 1111..112266.. ssppooooff ((99)) + 1122..112266.. ssppooooff ((99)) ssppooooff <<ccaallllssiiggnn>> <<ccoommmmaanndd>> Run commands as another user @@ -4902,7 +4979,7 @@ like home_node for example. - 1111..112277.. ssttaatt//ddbb ((55)) + 1122..112277.. ssttaatt//ddbb ((55)) ssttaatt//ddbb <<ddbbnnaammee>> Show the status of a database @@ -4914,7 +4991,7 @@ other than a sysop. - 1111..112288.. ssttaatt//cchhaannnneell ((55)) + 1122..112288.. ssttaatt//cchhaannnneell ((55)) ssttaatt//cchhaannnneell <<ccaallllssiiggnn>> Show the status of a channel on the cluster @@ -4925,7 +5002,7 @@ Only the fields that are defined (in perl term) will be displayed. - 1111..112299.. ssttaatt//mmssgg ((55)) + 1122..112299.. ssttaatt//mmssgg ((55)) ssttaatt//mmssgg <<mmssggnnoo>> Show the status of a message @@ -4935,7 +5012,9 @@ etc etc. - 1111..113300.. ssttaatt//uusseerr ((55)) + + + 1122..113300.. ssttaatt//uusseerr ((55)) ssttaatt//uusseerr <<ccaallllssiiggnn>> Show the full status of a user @@ -4946,9 +5025,7 @@ Only the fields that are defined (in perl term) will be displayed. - - - 1111..113311.. ssyyssoopp ((00)) + 1122..113311.. ssyyssoopp ((00)) ssyyssoopp Regain your privileges if you login remotely @@ -4990,7 +5067,7 @@ case sensitive. - 1111..113322.. ttaallkk ((00)) + 1122..113322.. ttaallkk ((00)) ttaallkk <<ccaallllssiiggnn>> Enter talk mode with <callsign> ttaallkk <<ccaallllssiiggnn>> <<tteexxtt>> Send a text message to <callsign> @@ -5002,6 +5079,7 @@ cluster system. You can send it to anyone you can see with a SHOW/CONFIGURATION command, they don't have to be connected locally. + The second form of TALK is used when other cluster nodes are connected with restricted information. This usually means that they don't send the user information usually associated with logging on and off the @@ -5041,7 +5119,7 @@ - 1111..113333.. ttyyppee ((00)) + 1122..113333.. ttyyppee ((00)) ttyyppee <<ffiilleeaarreeaa>>//<<nnaammee>> Look at a file in one of the fileareas @@ -5061,16 +5139,14 @@ content. - 1111..113344.. wwhhoo ((00)) + 1122..113344.. wwhhoo ((00)) wwhhoo Show who is physically connected locally This is a quick listing that shows which callsigns are connected and what sort of connection they have - - - 1111..113355.. wwxx ((00)) + 1122..113355.. wwxx ((00)) wwxx <<tteexxtt>> Send a weather message to local users wwxx ffuullll <<tteexxtt>> Send a weather message to all cluster users @@ -5080,7 +5156,7 @@ extreme that may indicate enhanced conditions - 1111..113366.. wwxx ((eennhhaanncceedd ffoorr ssyyssooppss)) ((55)) + 1122..113366.. wwxx ((eennhhaanncceedd ffoorr ssyyssooppss)) ((55)) wwxx ssyyssoopp <<tteexxtt>> Send a weather message to other clusters only @@ -5126,16 +5202,6 @@ - - - - - - - - - -