X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-10.html;h=f7ba1e56ba3b191e1f44e39be2ff5f081803b8bd;hb=8b89a9f5ce05bee89e83d68a75da9e73f560ee67;hp=5b030d16313f7185d5af430e9c7e82acfa10f87e;hpb=e1f91307fae936112a25ed7ce08f47214ecec766;p=spider.git diff --git a/html/adminmanual-10.html b/html/adminmanual-10.html index 5b030d16..f7ba1e56 100644 --- a/html/adminmanual-10.html +++ b/html/adminmanual-10.html @@ -2,42 +2,346 @@
-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. +
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.
-
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... +
+
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
+
+
++
accept/route <call> [0-9] <pattern> Set an 'accept' filter line for routing
+
+
Create an 'accept this routing PC Protocol' line for a filter. +
+
An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter +it is passed thru that interface. See HELP FILTERING 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:- +
+
+
+ call <prefixes> the callsign of the thingy
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes> really the interface it came in on
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+
+
++
some examples:- +
+
+
+ acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
+ acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
+
+
++
You can use the tag 'all' to accept everything eg: +
+
+
+ acc/route all
+
+
++
accept/spots [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... +
+
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
+
+
++
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. +
+
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
+
+
++
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. +
+
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
+
+
++
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. If you do not wish to receive +announces, use the set/noannounce command. Any announces made by +a sysop will override set/noannounce. +
+
announce full <text> Send an announcement cluster wide
+
+
This command will send your announcement across the whole cluster +network. +
+
+
announce sysop <text>
Send an announcement to Sysops only
-
connect <callsign> Start a connection to another DX Cluster
+
apropos <string> Search the help database
-
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>. +
Search the help database for <string> (it isn't case sensitive), +and print the names of all the commands that may be relevant.
+
bye Exit from the cluster
-
This will disconnect you from the cluster +
+
<node_call> All [<msgno> ...] Mark a message as sent
+
catchup <node_call> All|[<msgno> ...] Mark a message as sent
When you send messages the fact that you have forwarded it to another node is remembered so that it isn't sent again. When you have a new partner @@ -45,19 +349,148 @@ 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:- -
catch GB7DJK all -catch GB7DJK 300 301 302 303 +
+
+
+ catchup GB7DJK all
+ catchup GB7DJK 300 301 302 303 500-510
+
+
and to undo what you have just done:- -
uncatch GB7DJK all -uncatch GB7DJK 300 301 302 303 +
+
+
+ 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. +
+
clear/announce [input] <callsign> [0-9|all] Clear an announce filter line
+
+
A sysop can clear an input or normal output filter for a user or the +node_default or user_default. +
+
clear/route [input] ^lt;callsign> [0-9|all] Clear a route filter line
+
+
This command allows you to clear (remove) a line in a route filter or to +remove the whole filter. +
see CLEAR/SPOTS for a more detailed explanation. +
A sysop can clear an input or normal output filter for a user or the +node_default or user_default. +
+
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. +
+
clear/spots [input] <callsign> [0-9|all] Clear a spot filter line
-
A sysop can clear an input or normal output filter for a user or the +node_default or user_default. +
+
clear/wcy [1|all] Clear a WCY filter line
+
+
This command allows you to clear (remove) a line in a WCY filter or to +remove the whole filter. +
see CLEAR/SPOTS for a more detailed explanation. +
+
clear/wcy [input] <callsign> [0-9|all] Clear a WCY filter line
+
+
A sysop can clear an input or normal output filter for a user or the +node_default or user_default. +
+
clear/wwv [1|all] Clear a WWV filter line
+
+
This command allows you to clear (remove) a line in a WWV filter or to +remove the whole filter. +
see CLEAR/SPOTS for a more detailed explanation. +
+
clear/wwv [input] <callsign> [0-9|all] Clear a WWV filter line
+
+
A sysop can clear an input or normal output filter for a user or the +node_default or user_default. +
+
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>. +
+
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. +
+
dbcreate <name> Create a database entry
+dbcreate <name> remote <node> Create a remote 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. @@ -101,7 +534,7 @@ need to add a line like:-
See DBIMPORT for the importing of existing AK1A format data to databases. See DBSHOW for generic database enquiry
-
dbimport <dbname> Import AK1A data into a database
@@ -113,7 +546,7 @@ database. For example:-
will import the standard OBLAST database that comes with AK1A into the oblast database held locally.
-
dbremove <dbname> Delete a database
@@ -129,7 +562,31 @@ the associated datafile.
There is no warning, no comeback, no safety net.
You have been warned.
-
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
+
+
++
+
debug Set the cluster program into debug mode
@@ -144,34 +601,254 @@ in debug mode i.e.
It will interrupt the cluster just after the debug command has finished.
-
Works just like the user command except that sysops can see ALL messages. +
delete/user <callsign> Delete a user from the User Database
-
This command will completely remove a one or more users from the database. +
There is NO SECOND CHANCE. +
It goes without saying that you should use this command CAREFULLY! +
+
disconnect <call> [<call> ...] Disconnect a user or node
+
demonstrate <call> <command> Demonstrate a command to another user
-
Disconnect any <call> connected locally +
This command is provided so that sysops can demonstrate commands to +other users. It runs a command as though that user had typed it in and +then sends the output to that user, together with the command that +caused it. +
+
+
+ DEMO g7brn sh/dx iota oc209
+ DEMO g1tlh set/here
+
+
+Note that this command is similar to SPOOF and will have the same side +effects. Commands are run at the privilege of the user which is being +demonstrated to.
-
export <msgno> <filename> Export a message to a file
+
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:-
-
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 +
+
+ 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
+
+
++
+
Works just like the user command except that sysops can see ALL messages. +
+
disconnect <call> [<call> ...] Disconnect a user or node
+
+
Disconnect any <call> connected locally +
+
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. +
+
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 +
+
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. +
+
filtering Filtering things in DXSpider
+
+
There are a number of things you can filter in the DXSpider system. They +all use the same general mechanism. +
In general terms you can create a 'reject' or an 'accept' filter which +can have up to 10 lines in it. You do this using, for example:- +
accept/spots ..... +reject/spots ..... +
where ..... are the specific commands for that type of filter. There +are filters for spots, wwv, announce, wcy and (for sysops) +connects. See each different accept or reject command reference for +more details. +
There is also a command to clear out one or more lines in a filter and +one to show you what you have set. They are:- +
clear/spots 1 +clear/spots all +
and +
show/filter +
There is clear/xxxx command for each type of filter. +
For now we are going to use spots for the examples, but you can apply +the principles to all types of filter. +
There are two main types of filter 'accept' or 'reject'; which you use +depends entirely on how you look at the world and what is least +writing to achieve what you want. Each filter has 10 lines (of any +length) which are tried in order. If a line matches then the action +you have specified is taken (ie reject means ignore it and accept +means gimme it). +
The important thing to remember is that if you specify a 'reject' +filter (all the lines in it say 'reject/spots' (for instance) then if +a spot comes in that doesn't match any of the lines then you will get +it BUT if you specify an 'accept' filter then any spots that don't +match are dumped. For example if I have a one line accept filter:- +
accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16) +
then automatically you will ONLY get VHF spots from or to CQ zones 14 +15 and 16. If you set a reject filter like: +
reject/spots on hf/cw +
Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA +and will work it even on CW then you could say:- +
reject/spots on hf/cw and not info iota +
But in that case you might only be interested in iota and say:- +
accept/spots not on hf/cw or info iota +
which is exactly the same. You should choose one or the other until +you are confortable with the way it works. Yes, you can mix them +(actually you can have an accept AND a reject on the same line) but +don't try this at home until you can analyse the results that you get +without ringing up the sysop for help. +
You can arrange your filter lines into logical units, either for your +own understanding or simply convenience. I have one set frequently:- +
reject/spots 1 on hf/cw +reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16) +
What this does is to ignore all HF CW spots (being a class B I can't +read any CW and couldn't possibly be interested in HF :-) and also +rejects any spots on VHF which don't either originate or spot someone +in Europe. +
This is an exmaple where you would use the line number (1 and 2 in +this case), if you leave the digit out, the system assumes '1'. Digits +'0'-'9' are available. +
You can leave the word 'and' out if you want, it is implied. You can +use any number of brackets to make the 'expression' as you want +it. There are things called precedence rules working here which mean +that you will NEED brackets in a situation like line 2 because, +without it, will assume:- +
(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16 +
annoying, but that is the way it is. If you use OR - use +brackets. Whilst we are here CASE is not important. 'And BY_Zone' is +just 'and by_zone'. +
If you want to alter your filter you can just redefine one or more +lines of it or clear out one line. For example:- +
reject/spots 1 on hf/ssb +
or +
clear/spots 1 +
To remove the filter in its entirty:- +
clear/spots all +
There are similar CLEAR commands for the other filters:- +
clear/announce +clear/wcy +clear/wwv +
ADVANCED USERS:- +
Once you are happy with the results you get, you may like to experiment. +
my example that filters hf/cw spots and accepts vhf/uhf spots from EU +can be written with a mixed filter, eg: +
rej/spot on hf/cw +acc/spot on 0/30000 +acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16) +
each filter slot actually has a 'reject' slot and an 'accept' +slot. The reject slot is executed BEFORE the accept slot. +
It was mentioned earlier that after a reject test that doesn't match, +the default for following tests is 'accept', the reverse is true for +'accept'. In the example what happens is that the reject is executed +first, any non hf/cw spot is passed to the accept line, which lets +thru everything else on HF. +
The next filter line lets through just VHF/UHF spots from EU. +
+
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. +
+
forward/opername <call> Send out information on this <call> to all clusters
@@ -180,7 +857,18 @@ access. For example:-
be broadcast in PC41 protocol packets. This information is Name, QTH, Location
and Homenode. PC41s are only sent for the information that is available.
-
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. +
+
init <node call> Re-initialise a link to an AK1A compatible node
@@ -192,7 +880,16 @@ better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
node>).
Best of luck - you will need it.
-
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). +
+
As a sysop you can kill any message on the system.
-
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!
-
+ Deleting a message using the normal KILL commands only marks that message
+for deletion. The actual deletion only happens later (usually two days later).
+ The KILL EXPUNGE command causes the message to be truly deleted more or less
+immediately.
+ It otherwise is used in the same way as the KILL command.
+
+
+
+ This is a quick listing that shows which links are connected and
+some information about them. See WHO for a list of all connections.
+
+
+
+ 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.
+
+
+ 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.
+
+
+ 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.
+
+
+ Reload the /spider/data/bands.pl file if you have changed it manually whilst
+the cluster is running.
+
+
+ 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.
+
+ Reload the /spider/msg/forward.pl file if you have changed it
+manually whilst the cluster is running.
+
+
+ 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'
+
+
+ Reload the /spider/data/prefix_data.pl file if you have changed it manually
+whilst the cluster is running.
+
+
+ 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).
+
+
+ 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.
+
+ 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.
+
+
+ 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!!!
+
+
+ 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.
+
+
+
+ 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.
+
+
+ You can read any messages that are sent as 'non-personal' and also any
+message either sent by or sent to your callsign.
+
+
+
+ As a sysop you may read any message on the system
+
+
+ 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:-
+
+ some examples:-
+
+ You can use the tag 'all' to reject everything eg:
+
+ but this probably for advanced users...
+
+
+ This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+
+
+ Create an 'reject this routing PC Protocol' line for a filter.
+
+ An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
+it is NOT passed thru that interface. See HELP FILTERING 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:-
+
+
+ some examples:-
+
+
+ You can use the tag 'all' to reject everything eg:
+
+
+
+ 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:-
+
+ 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:-
+
+ You can use the tag 'all' to reject everything eg:
+
+ but this probably for advanced users...
+
+
+ This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+
+
+ It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+
+ 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.
+
+
+ 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
+
+
+ It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+
+ for example
+
+ is probably the only useful thing to do (which will only show WWV broadcasts
+by stations in the US).
+ See HELP FILTER for information.
+
+
+ This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+
+
+ 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)
+
+
+ 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:-
+
+ 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
+
+
+ Literally, record your address details on the cluster.
+
+
+ Allow announce messages to arrive at your terminal.
+
+
+ Set the node_call as an AR-Cluster type node
+
+
+ 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:-
+
+ To allow a word again, use the following command ...
+
+
+
+ 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:-
+
+ will stop anything from K1TTT (including any SSID's)
+
+ will allow spots from him again.
+ Use with extreme care. This command may well be superceded by FILTERing.
+
+
+ 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:-
+
+ will stop anything from VE2STN. If you want SSIDs as well then you must
+enter them specifically.
+
+ will allow spots from him again.
+ Use with extreme care. This command may well be superceded by FILTERing.
+
+
+ Setting a word as a 'badword' will prevent things like spots,
+announces or talks with this word in the the text part from going any
+further. They will not be displayed and they will not be sent onto
+other nodes.
+ The word must be written in full, no wild cards are allowed eg:-
+ set/badword annihilate annihilated annihilation
+ will stop anything with these words in the text.
+ unset/badword annihilated
+ will allow text with this word again.
+
+
+
+ Add a beep to DX and other terminal messages.
+
+
+
+ Set the node_call as a CLX type node
+
+
+ You can choose to log several different levels. The levels are
+ chan
+state
+msg
+cron
+connect
+ You can show what levels you are logging with the show/debug
+command.
+ You can remove a debug level with unset/debug <name>
+
+
+ You can stop DX messages with the unset/dx command
+
+
+ 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.
+
+
+ Set the node_call as a DXNet type node
+
+
+ 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.
+
+
+ If any personal messages come in for your callsign then you can use
+these commands to control whether they are forwarded onto your email
+address. To enable the forwarding do something like:-
+ SET/EMAIL mike.tubby@somewhere.com
+ You can have more than one email address (each one separated by a space).
+Emails are forwarded to all the email addresses you specify.
+ You can disable forwarding by:-
+ UNSET/EMAIL
+
+
+ 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.
+
+
+ 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 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.
+
+ Set SHOW/HOPS for information on what is already set. This command
+creates a filter and works in conjunction with the filter system.
+
+
+ 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.
+
+
+ You can select the language that you want the cluster to use. Currently
+the languages available are en (English) and nl (Dutch).
+
+
+ You can set your latitude and longitude manually or alternatively use the
+set/qra command which will do the conversion for you.
+
+
+
+
+ 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:-
+
+
+
+ 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.
+
+
+
+ You can show who is locked out with the show/lockout command.
+To allow the user to connect again, use the unset/lockout command.
+
+
+ Tell the cluster what your name is, eg:-
+
+
+
+ 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
+
+ To see what your nodes are set to, use the show/nodes command.
+
+
+ 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.
+
+
+ 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.
+
+ The setting is stored in your user profile.
+
+
+ This command only works for a 'telnet' user (currently). It will
+only work if you have a password already set. This initial password
+can only be set by the sysop.
+ When you execute this command it will ask you for your old password,
+then ask you to type in your new password twice (to make sure you
+get it right). You may or may not see the data echoed on the screen
+as you type, depending on the type of telnet client you have.
+
+
+ The password for a user can only be set by a full sysop. The string
+can contain any characters.
+ The way this field is used depends on context. If it is being used in
+the SYSOP command context then you are offered 5 random numbers and you
+have to supply the corresponding letters. This is now mainly for ax25
+connections.
+ If it is being used on incoming telnet connections then, if a password
+is set or the:
+ set/var $main::passwdreq = 1
+ command is executed in the startup script, then a password prompt is
+given after the normal 'login: ' prompt.
+ The command "unset/password" is provided to allow a sysop to remove a
+users password completely in case a user forgets or loses their password.
+
+
+ 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.
+
+
+ Set the privilege level on a callsign. The privilege levels that pertain
+to commands are as default:-
+
+ 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.
+
+
+ Set the node_call as a DXSpider type node
+
+
+
+ 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:-
+
+
+
+ Tell the system where your are. For example:-
+
+
+
+ Registration is a concept that you can switch on by executing the
+ set/var $main::regreq = 1
+ command (usually in your startup file)
+ If a user is NOT registered then, firstly, instead of the normal
+motd file (/spider/data/motd) being sent to the user at startup, the
+user is sent the motd_nor file instead. Secondly, the non registered
+user only has READ-ONLY access to the node. The non-registered user
+cannot use DX, ANN etc.
+ The only exception to this is that a non-registered user can TALK or
+SEND messages to the sysop.
+ To unset a user use the 'unset/register' command
+
+
+ Allow talk messages to arrive at your console. You can switch off
+talks with the unset/talk command.
+
+
+ Allow WCY information to be seen at your console. You can switch off
+WCY messages with the unset/wcy command.
+
+
+ Allow WWV information to be seen at your console. You can switch off
+WWV messages with the unset/wwv command.
+
+
+ Allow WX information to be seen at your console. You can switch off
+WX messages with the unset/wx command.
+
+
+ Display all the bad dx callsigns in the system, see SET/BADDX
+for more information.
+
+
+ Display all the bad node callsigns in the system, see SET/BADNODE
+for more information.
+
+
+ Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
+for more information.
+
+
+ Display all the bad words in the system, see SET/BADWORD
+for more information.
+
+
+ This command allows you to see all the users that can be seen
+and the nodes to which they are connected. With the optional node,
+you can specify a particular node to look at.
+ This command is normally abbreviated to: sh/c
+ BE WARNED: the list that is returned can be VERY long
+
+
+ Show all the nodes connected locally and the nodes they have connected.
+
+
+ This command shows information on all the active connections known to
+the node. This command gives slightly more information than WHO.
+
+
+ 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.
+
+
+ The levels can be set with set/debug
+
+
+ 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:-
+
+ e.g.
+
+
+
+ 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.
+
+
+
+ Show the total DX spots for the last 31 days
+
+
+
- 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.
+ 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:-
- 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.
+ 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:-
+
+ See also TYPE - to see the contents of a file.
-
- 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.
+ Show the contents of all the filters that are set by you. This command
+displays all the filters set - for all the various categories.
-
- 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.
+ A sysop can look at any filters that have been set.
-
- Reload the /spider/data/bands.pl file if you have changed it manually whilst
-the cluster is running.
+ Show the HF DX spots breakdown by band for the last 31 days
-
- 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.
+ Show the HF DX Spotter table for your country for the last 31 days
- Reload the /spider/msg/forward.pl file if you have changed it
-manually whilst the cluster is running.
+
- 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.
+
+
- 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'
+ Show which nodes are currently set to be isolated.
-
- Reload the /spider/data/prefix_data.pl file if you have changed it manually whilst
-the cluster is running.
+ Show a list of callsigns that have been excluded (locked out) of the
+cluster locally with the set/lockout command
-
- 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).
+ This command outputs a short section of the system log. On its own
+it will output a general logfile. With the optional callsign it will
+show output from the log associated with that callsign.
-
- 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.
+
+ 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:-
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.
-
+ 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:-
- 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!!!
+ produces:
+
+ indicating that you will have weak, fading circuits on top band and
+80m but usable signals on 40m (about S3).
+ inputting:-
+
+ will get you the above display, but with the next 24 hours worth of
+propagation data.
+
+ 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.
-
+ This command allows you to see all the users that can be seen
+and the nodes to which they are connected.
+ This command produces essentially the same information as
+SHOW/CONFIGURATION except that it shows all the duplication of
+any routes that might be present It also uses a different format
+which may not take up quite as much space if you don't have any
+loops.
+ BE WARNED: the list that is returned can be VERY long
+
+
- This command is used to estimate the quality of the link to another cluster.
-The time returned is the length of time taken for a PC51 to go to another
-cluster and be returned.
- Any visible cluster node can be PINGed.
+ Show all the nodes connected to this node in the new format.
-
- 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.
+ 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.
-
+ 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
- As a sysop you may read any message on the system
-
- You can remove this level with unset/debug <name>
+ 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.
-
- 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.
+ 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:-
+
+ 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:-
+
+
-
- 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
+ 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
-
- You can show who is locked out with the show/lockout (9) command.
- To allow the user to connect again, use the command unset/lockout
-
-
- 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
+ This command allows you to see to which node the callsigns specified are
+connected. It is a sort of inverse sh/config.
+ To see what your nodes are set to, use the show/nodes command.
-
-
- 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.
+
-
+ 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:-
- 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.
+
-
- Set the privilege level on a callsign. The privilege levels that pertain
-to commands are as default:-
+
+ 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:-
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.
-
- 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.
+ 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.
-
- Show the VHF DX spots breakdown by band for the last 31 days
+
+
+ Show the VHF DX Spotter table for your country for the last 31 days
-
- 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.
+ Display the most recent WCY information that has been received by the system
+
+
- Display the most recent WWV information that has been received by the system
+
+
+ Shutdown the cluster and disconnect all the users. If you have Spider
set to respawn in /etc/inittab it will of course restart.
-
- 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.
- Only the fields that are defined (in perl term) will be displayed.
- 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.
- If no message number is given then the status of the message system is
+displayed.
+
+
+
+ Only the fields that are defined (in perl term) will be displayed.
+
+ 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 :-):
+
+ you type:-
+
+ 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.
+
+
+ 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:-
+
+ To leave talk mode type:
+
+
+
+ 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:-
+
+ See also SHOW/FILES to see what fileareas are available and a
+list of content.
+
+
+ This is a quick listing that shows which callsigns are connected and
+what sort of connection they have
+
+
+ Weather messages can sometimes be useful if you are experiencing an extreme
+that may indicate enhanced conditions
+
+
+ Send a weather message only to other cluster nodes and not to general users.
+
kill <msgno> [<msgno> ...] Remove or erase a message from the system
@@ -203,320 +900,1600 @@ node>).
this command. You can remove more than one message at a time.
10.14 kill full (5)
-
+kill full <msgno> [<msgno>] Delete a message from the whole cluster
10.46 kill full (5)
+
+kill full <msgno> [<msgno>] Delete a message from the whole cluster
+10.15 load/aliases (9)
+
10.47 kill/expunge (6)
+
+
+kill/expunge <msgno> [<msgno>..]Expunge a message
+10.48 links (0)
+
+
+links Show which nodes are physically connected
+10.49 load/aliases (9)
+
+
+load/aliases Reload the command alias table
+10.50 load/badmsg (9)
+
+
+load/badmsg Reload the bad message table
+10.51 load/badwords (9)
+
+
+load/badwords Reload the bad words table
+10.52 load/bands (9)
+
+
+load/bands Reload the band limits table
+10.53 load/cmd_cache (9)
+
+
+load/cmd_cache Reload the automatic command cache
+10.54 load/forward (9)
+
+
+load/forward Reload the msg forwarding routing table
+10.55 load/messages (9)
+
+
+load/messages Reload the system messages file
+10.56 load/prefixes (9)
+
+
+load/prefixes Reload the prefix table
+10.57 merge (5)
+
+
+merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
+10.58 msg (9)
+
+
+msg <cmd> <msgno> [data ...] Alter various message parameters
+
+
+
+ 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
+
+10.59 pc (8)
+
+
+pc <call> <text> Send text (eg PC Protocol) to <call>
+10.60 ping (1)
+
+
+ping <node> Check the link quality between nodes
+10.61 rcmd (1)
+
+
+rcmd <node call> <cmd> Send a command to another DX cluster
+10.62 read (0)
+
+
+read Read the next unread personal message addressed to you
+
+read <msgno> Read the specified message10.63 read (extended for sysops) (5)
+
+
+read <msgno> Read a message on the system
+10.64 reject/announce
+
+
+reject/announce [0-9] <pattern> Set a reject filter
+for announce
+
+
+
+ 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)
+
+
+
+
+ rej/ann by_zone 14,15,16 and not by G,M,2
+
+
+
+
+ rej/ann all
+
+10.65 reject/announce (extended for sysops) (8)
+
+
+reject/announce <call> [input] [0-9] <pattern> Announce filter sysop version
+
+
+
+ reject/ann by G,M,2
+ reject/ann input node_default by G,M,2
+ reject/ann user_default by G,M,2
+
+10.66 reject/route (8)
+
+
+reject/route <call> [0-9] <pattern> Set an 'reject' filter line for routing
+
+
+
+ call <prefixes> the callsign of the thingy
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes> really the interface it came in on
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+
+
+
+
+ rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
+
+
+
+
+ rej/route all (equiv to [very] restricted mode)
+
+10.67 reject/spots (0)
+
+
+reject/spots [0-9] <pattern> Set a reject filter line for spots
+
+
+
+ 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>
+
+
+
+
+ rej/spot 1 on hf
+ rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+
+ rej/spot 3 all
+
+10.68 reject/spots (extended for sysops) (8)
+
+
+reject/spots <call> [input] [0-9] <pattern>
+Reject spot filter sysop version
+
+
+
+ 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
+
+10.69 reject/wcy (0)
+
+
+reject/wcy [0-9] <pattern> Set a reject WCY filter
+
+
+
+ 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>
+
+10.70 reject/wcy (extended for sysops) (8)
+
+
+reject/wcy <call> [input] [0-9] <pattern>
+WCY reject filter sysop version
+10.71 reject/wwv (0)
+
+
+reject/wwv [0-9] <pattern> Set a reject WWV filter
+
+
+
+ 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>
+
+
+
+
+ reject/wwv by_zone 14,15,16
+
+10.72 reject/wwv (extended for sysops) (8)
+
+
+reject/wwv <call> [input] [0-9] <pattern>
+WWV reject filter sysop version
+
+
+
+ reject/wwv db0sue-7 1 by_zone 4
+ reject/wwv node_default all
+
+ reject/wwv user_default by W
+
+10.73 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 receipt10.74 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
+
+
+ SEND RR COPY 123 PRIVATE G1TLH G0RDI
+
+10.75 set/address (0)
+
+
+set/address <your_address> Record your postal address
+10.76 set/announce (0)
+
+
+set/announce Allow announce messages
+10.77 set/arcluster (5)
+
+
+set/arcluster <node_call> [<node_call> ...] Make
+the node_call an AR-Cluster type node
+10.78 set/baddx (8)
+
+
+set/baddx <call> Stop words we do not wish to see in the callsign field
+of a dx spot being propagated
+
+
+
+ set/baddx FORSALE VIDEO FR0G
+
+
+
+
+ unset/baddx VIDEO
+
+10.79 set/badnode (6)
+
+
+set/badnode <node_call> Stop spots from this node_call
+being propagated
+
+
+
+ set/badnode K1TTT
+
+
+
+
+ unset/badnode K1TTT
+
+10.80 set/badspotter (8)
+
+
+set/badspotter <call> Stop spots from this callsign being propagated
+
+
+
+ set/badspotter VE2STN
+
+
+
+
+ unset/badspotter VE2STN
+
+10.81 set/badword (8)
+
+
+set/badword <word> Stop things with this word being propogated
+10.82 set/beep (0)
+
+
+set/beep Add beeps to terminal messages
+10.83 set/bbs (5)
+
+
+set/bbs <call> [<call>..]Make <call> a BBS
+10.84 set/clx (5)
+
+
+set/clx <node_call> [<node_call> ...] Make
+the node_call a CLX type node
+10.85 set/debug (9)
+
+
+set/debug <name> Add a debug level to the debug set
+10.86 set/dx (0)
+
+
+set/dxAllow DX messages to arrive at your terminal
+10.87 set/dxgrid (0)
+
+
+set/dxgridAllow grid squares on the end of DX messages
+10.88 set/dxnet (5)
+
+
+set/dxnet <node_call> [<node_call> ...] Make
+the node_call a DXNet type node
+10.89 set/echo (0)
+
+
+set/echo Make the cluster echo your input
+10.90 set/email (0)
+
+
+set/email <email_address> Set email address(es) and forward your personals
+10.91 set/here (0)
+
+
+set/here Set the here flag
+10.92 set/homenode (0)
+
+
+set/homenode <node_call> Set your home cluster
+
+
+
+ SET/HOMENODE gb7djk
+
+10.93 set/hops (8)
+
+
+set/hops <node_call> ann|spots|wwv|wcy <n>
+Set hop count
+
+
+
+eg:
+ set/hops gb7djk ann 10
+ set/hops gb7mbc spots 20
+
+10.94 set/isolate (9)
+
+
+set/isolate <node call> Isolate a node from the rest of the network
+10.95 set/language (0)
+
+
+set/language <language> Set the language you wish to use
+10.96 set/location (0)
+
+
+set/location <lat and long> Set your latitude and longitude
+
+
+
+ set/location 54 04 N 2 02 E
+
+10.97 set/sys_location (9)
+
+
+set/sys_location <lat & long> Set your cluster latitude and longitude
+
+
+
+ SET/LOCATION 52 22 N 0 57 E
+
+10.98 set/logininfo (0)
+
+
+set/logininfo Show logins and logouts of nodes and users
+10.99 set/lockout (9)
+
+
+set/lockout <call> Stop a callsign connecting to the cluster
+10.100 set/name (0)
+
+
+set/name <your_name> Set your name
+
+
+
+ set/name Dirk
+
+10.101 set/node (9)
+
+
+set/node <call> [<call> ...] Make the callsign an AK1A cluster
+
+
+
+ set/spider
+ set/dxnet
+ set/clx
+ set/arcluster
+
+10.102 set/obscount (9)
+
+
+set/obscount <count> <node call> Set the 'pump-up' obsolescence counter
+10.103 set/page (0)
+
+
+set/page <n> Set the number of lines per page
+
+
+
+ SET/PAGE 30
+ SET/PAGE 0
+
+10.104 set/password (0)
+
+
+set/password Set your own password
+10.105 set/password (9)
+
+
+set/password <callsign> <string> Set a users password
+10.106 set/pinginterval (9)
+
+
+set/pinginterval <time> <node call> Set the ping time to neighbouring nodes
+10.107 set/privilege (9)
+
+
+set/privilege <n> <call> [<call> ...] Set the privilege level on a call
+
+
+
+ 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.
+
+10.108 set/spider (5)
+
+
+set/spider <node_call> [<node_call> ...] Make
+the node_call a DXSpider type node
+10.109 set/sys_qra (9)
+
+
+set/sys_qra <locator> Set your cluster QRA locator
+10.110 set/qra (0)
+
+
+set/qra <locator> Set your QRA locator
+
+
+
+ SET/QRA JO02LQ
+
+10.111 set/qth (0)
+
+
+set/qth <your QTH> Set your QTH
+
+
+
+ set/qth East Dereham, Norfolk
+
+10.112 set/register (9)
+
+
+set/register <call> Mark a user as registered
+10.113 set/talk (0)
+
+
+set/talk Allow talk messages to be seen at your console
+10.114 set/wcy (0)
+
+
+set/wcy Allow WCY messages to be seen at your console
+10.115 set/wwv (0)
+
+
+set/wwv Allow WWV messages to be seen at your console
+10.116 set/wx (0)
+
+
+set/wx Allow WX messages to be seen at your console
+10.117 show/baddx (1)
+
+
+show/baddxShow all the bad dx calls in the system
+10.118 show/badnode (6)
+
+
+show/badnode Show all the bad nodes in the system
+10.119 show/badspotter (1)
+
+
+show/badspotter Show all the bad spotters in the system
+10.120 show/badword (1)
+
+
+show/badword Show all the bad words in the system
+10.121 show/configuration (0)
+
+
+show/configuration [<node>] Show all visible nodes and their users
+10.122 show/configuration/node (0)
+
+
+show/configuration/node Show all the nodes connected
+10.123 show/connect (1)
+
+
+show/connect Show all the active connections
+10.124 show/date (0)
+
+
+show/date [<prefix>|<callsign>] Show
+the local time
+10.125 show/debug (9)
+
+
+show/debug Show what levels of debug you are logging
+10.126 show/dx (0)
+
+
+show/dx [options] interrogate the spot database
+
+
+
+
+on <band> - eg 160m 20m 2m 23cm 6mm
+on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
+
+<number> - the number of spots you want
+<from>-<to> - <from> spot no <to> spot no in
+ the selected list
+
+<prefix> - for a spotted callsign beginning with <prefix>
+*<suffix> - for a spotted callsign ending in <suffix>
+*<string>* - for a spotted callsign containing <string>
+
+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.
+
+
+
+
+
+ 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
+
+10.127 show/dxcc (0)
+
+
+show/dxcc <prefix> Interrogate the spot database by country
+
+
+
+
+ SH/DXCC G
+ SH/DXCC W on 20m info iota
+
+10.128 sh/dxstats (0)
+
+
+sh/dxstats Show the DX Statistics for last 31 days
+10.129 show/files (0)
-load/aliases Reload the command alias table
+show/files [<filearea> [<string>]] List
+the contents of a filearea
10.16 load/baddx (9)
-
-
-load/baddx Reload the bad DX table
+
+
+ SH/FILES <filearea>
+
+
+
+
+ SH/FILES bulletins arld*
+
+10.17 load/badmsg (9)
+
10.130 show/filter (0)
-load/badmsg Reload the bad message table
+show/filter Show the filters you have set
10.18 load/badwords (9)
+
10.131 show/filter (extended for sysops) (5)
-load/badwords Reload the badwords file
+show/filter <callsign> Show the filters set by <callsign>
10.19 load/bands (9)
+
10.132 show/hfstats (0)
-load/bands Reload the band limits table
+show/hfstats Show the HF DX Statistics for last 31 days
10.20 load/cmd_cache (9)
+
10.133 show/hftable (0)
-load/cmd_cache Reload the automatic command cache
+show/hftable Show the HF DX Spotter Table for your country
10.21 load/forward (9)
+
10.134 show/hops (8)
-load/forward Reload the msg forwarding routing table
-show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a node
10.22 load/messages (9)
+
10.135 show/isolate (1)
-load/messages Reload the system messages file
+show/isolate Show a list of isolated nodes
10.23 load/prefixes (9)
+
10.136 show/lockout (9)
-load/prefixes Reload the prefix table
+show/lockout Show a list of excluded callsigns
10.24 merge (5)
+
10.137 show/log (8)
-merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
+show/log [<callsign>] Show excerpts from the system log
10.25 msg (9)
+
10.138 show/moon (0)
-msg <cmd> <msgno> [data ...] Alter various message parameters
-show/moon [<prefix>|<callsign>] Show moon
+rise and set times
+
-
- 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
+ SH/MOON
+ SH/MOON G1TLH W5UN
10.26 pc (8)
+
10.139 show/muf (0)
-pc <call> <text> Send text (eg PC Protocol) to <call>
+show/muf <prefix> [<hours>][long] Show
+the likely propagation to <prefix>
+
+
+
+ SH/MUF W
+
+
+
+
+ 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
+
+
+
+
+ SH/MUF W 24
+
+
+
+
+ SH/MUF W L 24
+ SH/MUF W 24 Long
+
+10.27 ping (1)
+
10.140 show/newconfiguration (0)
+
+
+show/newconfiguration [<node>] Show all the nodes and users visible
+10.141 show/newconfiguration/node (0)
-ping <node> Send a ping command to another cluster node
+show/newconfiguration/node Show all the nodes connected locally
10.28 rcmd (1)
+
10.142 show/node (1)
-rcmd <node call> <cmd> Send a command to another DX cluster
+show/node [<node_call> ...] Show the type and version
+number of nodes
10.29 read (5)
+
10.143 show/prefix (0)
-read <msgno> Read a message on the system
+show/prefix <callsign> Interrogate the prefix database
+10.30 set/debug (9)
+
10.144 show/program (5)
-set/debug <name> Add a debug level to the debug set
+show/program Show the locations of all the included program modules
10.31 set/isolate (9)
+
10.145 show/qra (0)
-set/isolate <node call> Isolate a node from the rest of the network
+show/qra <locator> [<locator>] Show the distance
+between locators
+show/qra <lat> <long> Convert latitude and longitude to a locator
+
+
+SH/QRA IO92QL
+SH/QRA JN06 IN73
+
+
+
+SH/QRA 52 41 N 0 58 E
+
+10.32 set/sys_location (9)
+
10.146 show/qrz (0)
-set/sys_location <lat & long> Set your cluster latitude and longitude
+show/qrz <callsign> Show any callbook details on a callsign
10.33 set/lockout (9)
+
10.147 show/registered (9)
-set/lockout <call> Stop a callsign connecting to the cluster
+show/registered [<prefix>[ Show the registered users
10.34 set/node (9)
+
10.148 show/route (0)
-set/node <call> [<call> ...] Make the callsign an AK1A cluster
+show/route <callsign> Show the route to <callsign>
-set/spider
-set/dxnet
-set/clx
-set/arcluster
+ sh/route n2tly
-10.35 set/obscount (9)
-
-
-set/obscount <count> <node call> Set the 'pump-up' obscelence counter
-10.36 set/pinginterval (9)
+
10.149 show/satellite (0)
-set/pinginterval <time> <node call> Set the ping time to neighbouring nodes
+show/satellite <name> [<hours> <interval>]
+Show satellite tracking data
+
+
+SH/SAT AO-10
+SH/SAT FENGYUN1 12 2
+
+10.37 set/privilege (9)
+
10.150 show/sun (0)
-set/privilege <n> <call> [<call> ...] Set the privilege level on a call
-show/sun [<prefix>|<callsign>] Show
+sun rise and set times
+
-
- 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.
+ SH/SUN
+ SH/SUN G1TLH K9CW ZS
10.38 set/password (9)
+
10.151 show/time (0)
-set/password <callsign> <string> Set a users password
+show/time [<prefix>|<callsign>] Show
+the local time
10.39 set/sys_qra (9)
+
10.152 show/vhfstats (0)
-set/sys_qra <locator> Set your cluster QRA locator
+show/vhfstats Show the VHF DX Statistics for last 31 days
10.40 show/call (1)
+
10.153 show/vhftable (0)
-show/call Show any callbook details on a program
-This command queries an international callbook server on the internet
-and returns any information available for that callsign.
+show/vhftable Show the VHF DX Spotter Table for your country
+10.41 show/program (5)
+
10.154 show/wcy (0)
-show/program Show the locations of all the included program modules
+show/wcy Show the last 10 WCY broadcasts
+show/wcy <n> Show the last <n> WCY broadcasts10.155 show/wwv (0)
+
+
+show/wwv Show the last 10 WWV broadcasts
+show/wwv <n> Show the last <n> WWV broadcasts10.42 shutdown (5)
+
10.156 shutdown (5)
shutdown Shutdown the cluster
@@ -524,7 +2501,7 @@ is useful for checking where you think you have loaded a .pm file from.
10.43 spoof (9)
+
10.157 spoof (9)
spoof <callsign> <command> Run commands as another user
@@ -534,7 +2511,7 @@ 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.
10.44 stat/db (5)
+
10.158 stat/db (5)
stat/db <dbname> Show the status of a database
@@ -543,7 +2520,7 @@ example.
10.45 stat/channel (5)
+
10.159 stat/channel (5)
stat/channel <callsign> Show the status of a channel on the cluster
@@ -552,7 +2529,7 @@ This command is unlikely to be of much use to anyone other than a sysop.
you are on or else for the callsign that you asked for.
10.46 stat/msg (5)
+
10.160 stat/msg (5)
stat/msg <msgno> Show the status of a message
@@ -560,7 +2537,20 @@ you are on or else for the callsign that you asked for.
10.47 stat/user (5)
+
10.161 stat/route_node (5)
+
+
+stat/route_node <callsign> Show the data in a Route::Node object
+10.162 stat/route_user (5)
+
+
+stat/route_user <callsign> Show the data in a Route::User object
+10.163 stat/user (5)
stat/user <callsign> Show the full status of a user
@@ -569,6 +2559,124 @@ such as to whom it has been forwarded, its size, origin etc etc.
and stuff.
10.164 sysop (0)
+
+
+sysop Regain your privileges if you login remotely
+
+
+
+ password = 012345678901234567890123456789
+ > sysop
+ 22 10 15 17 3
+
+
+
+
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
+
+10.165 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>
+
+
+ /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
+ /HELP talk
+
+
+
+
+ /EX
+
+10.166 type (0)
+
+
+type <filearea>/<name> Look at a file in one of the fileareas
+
+
+
+ TYPE bulletins/arld051
+
+10.167 who (0)
+
+
+who Show who is physically connected locally
+10.168 wx (0)
+
+
+wx <text> Send a weather message to local users
+
+wx full <text> Send a weather message to all cluster users10.169 wx (enhanced for sysops) (5)
+
+
+wx sysop <text> Send a weather message to other clusters only
+