X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-9.html;h=3d5a8ea8727d3034e87b452412672fccd2c8aee2;hb=99da9d68a4fee5b30fa90b679a9e015add2b75c9;hp=508d1d323217ee397bfa50b0ca65747c0a8f5928;hpb=c42f6d2e451d149bd3ee9059ed8a9a4589c47f6d;p=spider.git diff --git a/html/adminmanual-9.html b/html/adminmanual-9.html index 508d1d32..3d5a8ea8 100644 --- a/html/adminmanual-9.html +++ b/html/adminmanual-9.html @@ -2,388 +2,2666 @@
-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 +
+
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. +
+
bye Exit from the cluster
+
+
This will disconnect you from the cluster +
+
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. +
+
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> 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 +
+
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. +
+
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. +
+
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
+
+
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. +
+
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! +
+
+
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
+
+
++
+
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
+
+
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. +
+
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
+
+
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. +
+
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). +
+
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. +
+
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! +
+
kill/expunge <msgno> [<msgno>..]Expunge a message
+
+
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. +
+
+
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. +
+
+
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. +
+
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. +
+
load/badwords Reload the bad words table
+
+
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. +
+
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. +
+
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. +
+
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. +
+
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' +
+
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. +
+
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). +
+
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. +
+
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!!! +
+
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. +
+
+
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. +
+
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. +
+
+
read <msgno> Read a message on the system
+
+
As a sysop you may read any message on the system +
+
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... +
+
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
+
+
++
reject/route <call> [0-9] <pattern> Set an 'reject' filter line for routing
+
+
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:- +
+
+
+ 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:- +
+
+
+ rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
+
+
++
You can use the tag 'all' to reject everything eg: +
+
+
+ rej/route all (equiv to [very] restricted mode)
+
+
++
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... +
+
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
+
+
++
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. +
+
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 +
+
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. +
+
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
+
+
++
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) +
+
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 +
+
set/address <your_address> Record your postal address
+
+
Literally, record your address details on the cluster. +
+
set/announce Allow announce messages
+
+
Allow announce messages to arrive at your terminal. +
+
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 +
+
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
+
+
++
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. +
+
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. +
+
set/badword <word> Stop things with this word being propogated
+
+
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. +
+
+
set/beep Add beeps to terminal messages
+
+
Add a beep to DX and other terminal messages. +
+
set/bbs <call> [<call>..]Make <call> a BBS
+
+
set/clx <node_call> [<node_call> ...] Make
+the node_call a CLX type node
+
+
Set the node_call as a CLX type node +
+
set/debug <name> Add a debug level to the debug set
+
+
You can choose to log several different levels. The levels are +
chan +state +msg +cron +connect +
You can show what levels you are logging with the show/debug +command. +
You can remove a debug level with unset/debug <name> +
+
set/dxAllow DX messages to arrive at your terminal
+
+
You can stop DX messages with the unset/dx command +
+
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. +
+
set/dxnet <node_call> [<node_call> ...] Make
+the node_call a DXNet type node
+
+
Set the node_call as a DXNet type node +
+
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. +
+
set/email <email_address> Set email address(es) and forward your personals
+
+
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 +
+
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. +
+
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
+
+
++
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. +
+
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. +
+
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). +
+
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
+
+
++
+
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
+
+
++
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. +
+
+
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. +
+
set/name <your_name> Set your name
+
+
Tell the cluster what your name is, eg:- +
+
+
+ set/name Dirk
+
+
++
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. +
+
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. +
+
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. +
+
set/password Set your own password
+
+
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. +
+
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. +
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. +
+
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. +
+
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. +
+
set/spider <node_call> [<node_call> ...] Make
+the node_call a DXSpider type node
+
+
Set the node_call as a DXSpider type node +
+
set/sys_qra <locator> Set your cluster QRA locator
+
+
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
+
+
++
set/qth <your QTH> Set your QTH
+
+
Tell the system where your are. For example:- +
+
+
+ set/qth East Dereham, Norfolk
+
+
++
set/register <call> Mark a user as registered
+
+
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 +
+
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. +
+
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. +
+
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. +
+
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. +
+
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. +
+
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. +
+
show/badspotter Show all the bad spotters in the system
+
+
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER +for more information. +
+
show/badword Show all the bad words in the system
+
+
Display all the bad words in the system, see SET/BADWORD +for more information. +
+
show/configuration [<node>] Show all visible nodes and their users
+
+
This command allows you to see all the users that can be seen +and the nodes to which they are connected. With the optional 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/configuration/node Show all the nodes connected
+
+
Show all the nodes connected locally and the nodes they have connected. +
+
show/connect Show all the active connections
+
+
This command shows information on all the active connections known to +the node. This command gives slightly more information than WHO. +
+
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. +
+
show/debug Show what levels of debug you are logging
+
+
The levels can be set with set/debug +
+
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
+
+
++
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
+
+
++
sh/dxstats Show the DX Statistics for last 31 days
+
+
Show the total DX spots for the last 31 days +
+
+
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. +
+
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. +
+
show/filter <callsign> Show the filters set by <callsign>
+
+
A sysop can look at any filters that have been set. +
+
show/hfstats Show the HF DX Statistics for last 31 days
+
+
Show the HF DX spots breakdown by band for the last 31 days +
+
show/hftable Show the HF DX Spotter Table for your country
+
+
Show the HF DX Spotter table for your country for the last 31 days +
+
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. +
+
show/isolate Show a list of isolated nodes
+
+
Show which nodes are currently set to be isolated. +
+
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 +
+
show/log [<callsign>] Show excerpts from the system log
+
+
This command outputs a short section of the system log. On its own +it will output a general logfile. With the optional callsign it will +show output from the log associated with that callsign. +
+
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
+
+
++
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). +
inputting:- +
+
+
+ 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. +
+
show/newconfiguration [<node>] Show all the nodes and users visible
+
+
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 +
+
show/newconfiguration/node Show all the nodes connected locally
+
+
Show all the nodes connected to this node in the new format. +
+
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. +
+
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 +
+
+
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. +
+
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. +
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
+
+
++
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 +
+
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. +
show/registered [<prefix>[ Show the registered users
-
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/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.
-show/files
+ sh/route n2tly
-They can be read by the user by typing the command .... +
+
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:-
-type news
+SH/SAT AO-10
+SH/SAT FENGYUN1 12 2
-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/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:-
-show/files bulletins
+ SH/SUN
+ SH/SUN G1TLH K9CW ZS
-
An example would look like this .... +
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. +
+
show/vhfstats Show the VHF DX Statistics for last 31 days
+
+
Show the VHF DX spots breakdown by band for the last 31 days +
+
show/vhftable Show the VHF DX Spotter Table for your country
+
+
Show the VHF DX Spotter table for your country for the last 31 days +
+
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 +
+
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 +
+
+
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. +
+
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. +
+
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. +
+
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. +
+
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. +
+
If no message number is given then the status of the message system is +displayed. +
+
stat/route_node <callsign> Show the data in a Route::Node object
+
+
stat/route_user <callsign> Show the data in a Route::User object
+
+
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. +
+
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 :-):
-sh/files
-bulletins DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
+ password = 012345678901234567890123456789
+ > sysop
+ 22 10 15 17 3
-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 .... +
you type:-
-type news
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
-To look what is in the bulletins directory you issue the command .... +
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. +
+
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:-
-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) >
+ /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
+ /HELP talk
-You can now read any file in this directory using the type command, like this .... +
To leave talk mode type:
-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) >
+ /EX
-The page length will of course depend on what you have it set to!
-
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 ... +
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. +
+
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 +
+
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 +
+
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. -
-
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 = (
-'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) ],
-);
-
-
-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 -
-
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 distro. 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. -
-
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. +
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. +
-
To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the -file with your favourite editor.