X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Fadminmanual.sgml;h=2267f36bed26207c246c6a056a4cc841b5be2c5c;hb=0fcb7df9b5f6b17605f07d965e71d8bc4dee09a0;hp=9222966b76a6c2e7a168001e9e62b2fc7ef13205;hpb=8b3550e37fbfc539cdd10472d10f92ae0135f4b7;p=spider.git diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 9222966b..2267f36b 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -1813,3311 +1813,4 @@ Restart your Spider software The DXSpider command set -

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

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

-Create an 'accept this announce' line for a filter. - -An accept filter line means that if the announce matches this filter it is -passed onto the user. See HELP FILTERS for more info. Please read this -to understand how filters work - it will save a lot of grief later on. - -You can use any of the following things in this line:- - - - info eg: iota or qsl - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - wx 1 filter WX announces - dest 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 (extended for sysops) (8) - -

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

-This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- - - - accept/ann by G,M,2 - accept/ann input node_default by G,M,2 - accept/ann user_default by G,M,2 - - -accept/route (8) - -

- -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 the callsign of the thingy - call_dxcc eg: 61,62 (from eg: sh/pre G) - call_itu - call_zone - origin really the interface it came in on - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - - -

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

- -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. - -Please read the following section carefully. Though it looks similar, -reformatting, corrections, and hopefully clarifications have been added. - -You can use any of the following things in this line:- - - -Filters for the station being spotted: - call - call G --> G1AAA, GJ2BBB, GU3CCC, etc will be spotted - call K --> K1XX, K1XXX will be spotted - W1XX, W1XXX will NOT be spotted - call PA --> PA3EZL will be spotted - PB2FG will NOT be spotted - - call_dxcc - call_dxcc G --> G1AAA will be spotted - GU1AAA will NOT be spotted (different country) - call_dxcc K --> K1XX, W1XX will be spotted (same country) - call_dxcc 139 --> PA3EZL and PB2FG will be spotted - - call_itu - call_zone - -Filters for the callsign of the station doing the spotting: - by - by G --> spots from G1AAA, GJ2BBB, GU3CCC, etc will be spotted - by K --> spots from K1XX, K1XXX will be spotted - spots from W1XX, W1XXX will NOT be spotted - - by_dxcc - by_dxcc G --> spots from G1AAA will be spotted - spots from GU1AAA will NOT be spotted (different -country) - by_dxcc K --> spots from K1XX, W1XX will be spotted (same country) - by_dxcc 139 --> spots from PA3EZL or PB2FG will be spotted - - by_itu - by_zone - -Filters for the callsign of the "node" doing the spotting: - origin - origin K --> spots from a node starting with K will be spotted - spots from a node starting with KK will NOT be spotted - spots from a node starting with W will NOT be spotted - -Filters for the callsign of the connected node or user (channel) doing the spotting: - channel - channel W1HR --> spots from the connected node W1HR will be spotted - channel K1QX --> spots from the connected user K1QX will be spotted - - info eg: iota or qsl - freq eg: 0/30000 or hf or hf/cw or 6m,4m,2m - on same as 'freq' - - - -

-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 (extended for sysops) (8) - -

- -accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version - - -

-This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- - - - accept/spot db0sue-7 1 by_zone 14,15,16 - accept/spot node_default all - set/hops node_default 10 - - accept/spot user_default by G,M,2 - - -accept/wcy (0) - -

- -accept/wcy [0-9] <pattern> set an accept WCY filter - - -

-It is unlikely that you will want to do this, but if you do then you can -filter on the following fields:- - - - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - - -

-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 (extended for sysops) (8) - -

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

-This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- - - - accept/wcy node_default all - set/hops node_default 10 - - -accept/wwv (0) - -

- -accept/wwv [0-9] <pattern> Set an accept WWV filter - - -

-It is unlikely that you will want to do this, but if you do then you can -filter on the following fields:- - - - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - - -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 (extended for sysops) (8) - -

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

-This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- - - - accept/wwv db0sue-7 1 by_zone 4 - accept/wwv node_default all - set/hops node_default 10 - - accept/wwv user_default by W,K - - -announce (0) - -

- -announce <text> Send an announcement to local users - - -

-Send an announcement to LOCAL users only, where <text> is the text -of the announcement you wish to broadcast. 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 (0) - -

- -announce full <text> Send an announcement cluster wide - - -

-This command will send your announcement across the whole cluster -network. - - -announce sysop (5) - -

- -announce sysop <text> - - -

-Send an announcement to Sysops only - -apropos (0) - -

- -apropos <string> Search the help database - - -

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

- -bye Exit from the cluster - - -

-This will disconnect you from the cluster - -catchup (5) - -

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

-When you send messages the fact that you have forwarded it to another node -is remembered so that it isn't sent again. When you have a new partner -node and you add their callsign to your /spider/msg/forward.pl file, all -outstanding non-private messages will be forwarded to them. This may well -be ALL the non-private messages. You can prevent this by using these -commmands:- - - - catchup GB7DJK all - catchup GB7DJK 300 301 302 303 500-510 - - -and to undo what you have just done:- - - - uncatchup GB7DJK all - uncatchup GB7DJK 300 301 302 303 500-510 - - -which will arrange for them to be forward candidates again. - -Order is not important. - -clear/announce (8) - -

- -clear/announce <callsign> [input] [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 (8) - -

- -clear/route <callsign> [input] [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 (0) - -

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

-This command allows you to clear (remove) a line in a spot filter or to -remove the whole filter. - -If you have a filter:- - - - acc/spot 1 on hf/cw - acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) - - -and you say:- - - - clear/spot 1 - - -you will be left with:- - - - acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) - - -If you do: - - - clear/spot all - - -the filter will be completely removed. - -clear/spots (extended for sysops) (8) - -

- -clear/spots <callsign> [input] [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 (0) - -

- -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 (extended for sysops) (8) - -

- -clear/wcy <callsign> [input] [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 (0) - -

- -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 (extended for sysops) (8) - -

- -clear/wwv <callsign> [input] [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 (5) - -

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

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

- -dbavail Show a list of all the databases in the system - - -

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

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

-DBCREATE allows you to define a database in the system. It doesn't actually -create anything, just defines it. - -The databases that are created are simple DB_File hash databases, they are -therefore already 'indexed'. - -You can define a local database with the first form of the command eg: - - DBCREATE oblast - -You can also chain databases with the addition of the 'chain' keyword. -This will search each database one after the other. A typical example -is: - - DBCREATE sdx_qsl chain sql_ad - -No checking is done to see if the any of the chained databases exist, in -fact it is usually better to do the above statement first then do each of -the chained databases. - -Databases can exist offsite. To define a database that lives on another -node do: - - DBCREATE buckmaster remote gb7dxc - -Remote databases cannot be chained; however, the last database in a -a chain can be a remote database eg: - - DBCREATE qsl chain gb7dxc - -To see what databases have been defined do: - - DBAVAIL (or it will have been aliased to SHOW/COMMAND) - -It would be normal for you to add an entry into your local Aliases file -to allow people to use the 'SHOW/<dbname>' style syntax. So you would -need to add a line like:- - - - 's' => [ - .. - .. - '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', - .. - .. - ], - - -to allow - - SH/BUCK g1tlh - -to work as they may be used to. - -See DBIMPORT for the importing of existing AK1A format data to databases. -See DBSHOW for generic database enquiry - -dbimport (9) - -

- -dbimport <dbname> Import AK1A data into a database - - -

-If you want to import or update data in bulk to a database you can use -this command. It will either create or update entries into an existing -database. For example:- - - DBIMPORT oblast /tmp/OBLAST.FUL - -will import the standard OBLAST database that comes with AK1A into the -oblast database held locally. - -dbremove (9) - -

- -dbremove <dbname> Delete a database - - -

-DBREMOVE will completely remove a database entry and also delete any data -file that is associated with it. - -There is no warning, no comeback, no safety net. - -For example: - - DBREMOVE oblast - -will remove the oblast database from the system and it will also remove -the associated datafile. - -I repeat: - -There is no warning, no comeback, no safety net. - -You have been warned. - -dbshow (0) - -

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

-This is the generic user interface to the database to the database system. -It is expected that the sysop will add an entry to the local Aliases file -so that users can use the more familiar AK1A style of enquiry such as: - - - SH/BUCK G1TLH - - -but if he hasn't and the database really does exist (use DBAVAIL or -SHOW/COMMAND to find out) you can do the same thing with: - - - DBSHOW buck G1TLH - - - -debug (9) - -

- -debug Set the cluster program into debug mode - - -

-Executing this command will only have an effect if you are running the cluster -in debug mode i.e. - - - perl -d cluster.pl - - -It will interrupt the cluster just after the debug command has finished. - -delete/user (9) - -

- -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! - -demonstrate (9) - -

- -demonstrate <call> <command> Demonstrate a command to another user - - -

-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. - -directory (0) - -

- -directory List messages -directory all List all messages -directory own List your own messages -directory new List all new messages -directory to <call> List all messages to <call> -directory from <call> List all messages from <call> -directory subject <string> List all messages with <string> -in subject -directory <nn> List last <nn> messages -directory <from>-<to> List messages <from> message <to> message - - -

-List the messages in the messages directory. - -If there is a 'p' one space after the message number then it is a -personal message. If there is a '-' between the message number and the -'p' then this indicates that the message has been read. - -You can use shell escape characters such as '*' and '?' in the <call> -fields. - -You can combine some of the various directory commands together eg:- - - - DIR TO G1TLH 5 -or - DIR SUBJECT IOTA 200-250 - - -You can abbreviate all the commands to one letter and use ak1a syntax:- - - - DIR/T G1* 10 - DIR/S QSL 10-100 5 - - - -directory (extended for sysops) (5) - -

-Works just like the user command except that sysops can see ALL messages. - -disconnect (8) - -

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

-Disconnect any <call> connected locally - -dx (0) - -

- -dx [by <call>] <freq> <call> <remarks> Send a DX spot - - -

-This is how you send a DX Spot to other users. You can, in fact, now -enter the <freq> and the <call> either way round. - - - DX FR0G 144.600 - DX 144.600 FR0G - DX 144600 FR0G - - -will all give the same result. You can add some remarks to the end -of the command and they will be added to the spot. - - - DX FR0G 144600 this is a test - - -You can credit someone else by saying:- - - - DX by G1TLH FR0G 144.600 he isn't on the cluster - - -The <freq> is compared against the available bands set up in the -cluster. See SHOW/BANDS for more information. - -export (9) - -

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

-Export a message to a file. This command can only be executed on a local -console with a fully privileged user. The file produced will be in a form -ready to be imported back into the cluster by placing it in the import -directory (/spider/msg/import). - -This command cannot overwrite an existing file. This is to provide some -measure of security. Any files written will owned by the same user as the -main cluster, otherwise you can put the new files anywhere the cluster can -access. For example:- - - EXPORT 2345 /tmp/a - -export_users (9) - -

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

-Export the users database to a file in ascii format. If no filename -is given then it will export the file to /spider/data/user_asc. - -If the file already exists it will be renamed to <filename>.o. In fact -up to 5 generations of the file can be kept each one with an extra 'o' on the -suffix. - -BE WARNED: this will write to any file you have write access to. No check is -made on the filename (if any) that you specify. - -filtering (0) - -

- -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 (8) - -

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

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

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

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

- -help <cmd> Get help on a command - - -

-All commands can be abbreviated, so SHOW/DX can be abbreviated -to SH/DX, ANNOUNCE can be shortened to AN and so on. - -Look at the APROPOS <string> command which will search the help database -for the <string> you specify and give you a list of likely commands -to look at with HELP. - -init (5) - -

- -init <node call> Re-initialise a link to an AK1A compatible node - - -

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

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

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

- -kill <msgno> [<msgno> ...] Remove or erase a message from -the system -kill from <call> Remove all messages from a callsign -kill to <call> Remove all messages to a callsign - - -

-You can get rid of any message to or originating from your callsign using -this command. You can remove more than one message at a time. - -As a sysop you can kill any message on the system. - -kill full (5) - -

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

-Delete a message (usually a 'bulletin') from the whole cluster system. - -This uses the subject field, so any messages that have exactly the same subject -will be deleted. Beware! - -kill/expunge (6) - -

- -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 (0) - -

- -links Show which nodes are physically connected - - -

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

- -load/aliases Reload the command alias table - - -

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

- -load/badmsg Reload the bad message table - - -

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

- -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 (9) - -

- -load/bands Reload the band limits table - - -

-Reload the /spider/data/bands.pl file if you have changed it manually whilst -the cluster is running. - -load/cmd_cache (9) - -

- -load/cmd_cache Reload the automatic command cache - - -

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

- -load/forward Reload the msg forwarding routing table - - -Reload the /spider/msg/forward.pl file if you have changed it -manually whilst the cluster is running. - -load/messages (9) - -

- -load/messages Reload the system messages file - - -

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

- -load/prefixes Reload the prefix table - - -

-Reload the /spider/data/prefix_data.pl file if you have changed it manually -whilst the cluster is running. - -merge (5) - -

- -merge <node> [<no spots>/<no wwv>] Ask for the -latest spots and WWV - - -

-MERGE allows you to bring your spot and wwv database up to date. By default -it will request the last 10 spots and 5 WWVs from the node you select. The -node must be connected locally. - -You can request any number of spots or wwv and although they will be appended -to your databases they will not duplicate any that have recently been added -(the last 2 days for spots and last month for WWV data). - -msg (9) - -

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

-Alter message parameters like To, From, Subject, whether private or bulletin -or return receipt (RR) is required or whether to keep this message from timing -out. - - - MSG TO - change TO callsign to - MSG FRom - change FROM callsign to - MSG PRrivate - set private flag - MSG NOPRrivate - unset private flag - MSG RR - set RR flag - MSG NORR - unset RR flag - MSG KEep - set the keep flag (message won't be deleted ever) - MSG NOKEep - unset the keep flag - MSG SUbject - change the subject to - MSG WAittime - remove any waitting time for this message - MSG NOREad - mark message as unread - MSG REad - 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 (8) - -

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

-Send some arbitrary text to a locally connected callsign. No processing is done on -the text. This command allows you to send PC Protocol to unstick things if problems -arise (messages get stuck etc). eg:- - - pc gb7djk PC33^GB7TLH^GB7DJK^400^ - -You can also use in the same way as a talk command to a connected user but -without any processing, added of "from <blah> to <blah>" or whatever. - - pc G1TLH Try doing that properly!!! - -ping (1) - -

- -ping <node> Check the link quality between nodes - - -

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

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

-This command allows you to send nearly any command to another DX Cluster -node that is connected to the system. - -Whether you get any output is dependant on a) whether the other system knows -that the node callsign of this cluster is in fact a node b) whether the -other system is allowing RCMDs from this node and c) whether you have -permission to send this command at all. - -read (0) - -

- -read Read the next unread personal message addressed to you -read <msgno> Read the specified message - - -

-You can read any messages that are sent as 'non-personal' and also any -message either sent by or sent to your callsign. - - -read (extended for sysops) (5) - -

- -read <msgno> Read a message on the system - - -

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

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

-Create an 'reject this announce' line for a filter. - -An reject filter line means that if the announce matches this filter it is -passed onto the user. See HELP FILTERS for more info. Please read this -to understand how filters work - it will save a lot of grief later on. - -You can use any of the following things in this line:- - - - info eg: iota or qsl - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - wx 1 filter WX announces - dest 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 (extended for sysops) (8) - -

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

-This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- - - - reject/ann by G,M,2 - reject/ann input node_default by G,M,2 - reject/ann user_default by G,M,2 - - -reject/route (8) - -

- -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 the callsign of the thingy - call_dxcc eg: 61,62 (from eg: sh/pre G) - call_itu - call_zone - origin really the interface it came in on - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - - -

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

- -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 eg: 0/30000 or hf or hf/cw or 6m,4m,2m - on same as 'freq' - call eg: G,PA,HB9 - info eg: iota or qsl - by - call_dxcc eg: 61,62 (from eg: sh/pre G) - call_itu - call_zone - by_dxcc - by_itu - by_zone - origin - channel - - -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 (extended for sysops) (8) - -

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

-This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- - - - reject/spot db0sue-7 1 by_zone 14,15,16 - reject/spot node_default all - set/hops node_default 10 - - reject/spot user_default by G,M,2 - - -reject/wcy (0) - -

- -reject/wcy [0-9] <pattern> Set a reject WCY filter - - -

-It is unlikely that you will want to do this, but if you do then you can -filter on the following fields:- - - - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - - -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 (extended for sysops) (8) - -

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

-This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- - - reject/wcy gb7djk all - -reject/wwv (0) - -

- -reject/wwv [0-9] <pattern> Set a reject WWV filter - - -

-It is unlikely that you will want to do this, but if you do then you can -filter on the following fields:- - - - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - - -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 (extended for sysops) (8) - -

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

This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- - - - reject/wwv db0sue-7 1 by_zone 4 - reject/wwv node_default all - - reject/wwv user_default by W - - -reply (0) - -

- -reply Reply (privately) to the last message that you have read -reply <msgno> Reply (privately) to the specified message -reply B <msgno> Reply as a Bulletin to the specified message -reply NOPrivate <msgno> Reply as a Bulletin to the specified -message -reply RR <msgno> Reply to the specified message with read -receipt - - -

-You can reply to a message and the subject will automatically have -"Re:" inserted in front of it, if it isn't already present. - -You can also use all the extra qualifiers such as RR, PRIVATE, -NOPRIVATE, B that you can use with the SEND command (see SEND -for further details) - -send (0) - -

- -send <call> [<call> ...] Send a message to -one or more callsigns -send RR <call> Send a message and ask for a read receipt -send COPY <msgno> <call> Send a copy of a message -to someone -send PRIVATE <call> Send a personal message -send NOPRIVATE <call> Send a message to all stations - - -

-All the SEND commands will create a message which will be sent either to -an individual callsign or to one of the 'bulletin' addresses. - -SEND <call> on its own acts as though you had typed SEND PRIVATE, that is -it will mark the message as personal and send it to the cluster node that -that callsign is connected to. - -You can have more than one callsign in all of the SEND commands. - -You can have multiple qualifiers so that you can have for example:- - - - SEND RR COPY 123 PRIVATE G1TLH G0RDI - - -which should send a copy of message 123 to G1TLH and G0RDI and you will -receive a read receipt when they have read the message. - -SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) -SP is an alias for SEND PRIVATE - -set/address (0) - -

- -set/address <your_address> Record your postal address - - -

-Literally, record your address details on the cluster. - -set/announce (0) - -

- -set/announce Allow announce messages - - -

-Allow announce messages to arrive at your terminal. - -set/arcluster (5) - -

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

-Set the node_call as an AR-Cluster type node - -set/baddx (8) - -

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

-Setting a word as 'baddx' will prevent spots with that word in the callsign -field of a DX spot from going any further. They will not be displayed and they -will not be sent onto other nodes. - -The word must be wriiten in full, no wild cards are allowed eg:- - - - set/baddx FORSALE VIDEO FR0G - - -To allow a word again, use the following command ... - - - unset/baddx VIDEO - - -set/badnode (6) - -

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

-Setting a callsign as a 'badnode' will prevent spots from that node -going any further. They will not be displayed and they will not be -sent onto other nodes. - -The call can be a full or partial call (or a prefix), eg:- - - - set/badnode K1TTT - - -will stop anything from K1TTT (including any SSID's) - - - unset/badnode K1TTT - - -will allow spots from him again. - -Use with extreme care. This command may well be superceded by FILTERing. - -set/badspotter (8) - -

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

-Setting a callsign as a 'badspotter' will prevent spots from this callsign -going any further. They will not be displayed and they will not be -sent onto other nodes. - -The call must be written in full, no wild cards are allowed eg:- - - - set/badspotter VE2STN - - -will stop anything from VE2STN. If you want SSIDs as well then you must -enter them specifically. - - - unset/badspotter VE2STN - - -will allow spots from him again. - -Use with extreme care. This command may well be superceded by FILTERing. - -set/badword (8) - -

- -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 (0) - -

- -set/beep Add beeps to terminal messages - - -

-Add a beep to DX and other terminal messages. - -set/bbs (5) - -

- -set/bbs <call> [<call>..]Make <call> a BBS - - -set/clx (5) - -

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

-Set the node_call as a CLX type node - -set/debug (9) - -

- -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/dx (0) - -

- -set/dxAllow DX messages to arrive at your terminal - - -

-You can stop DX messages with the unset/dx command - -set/dxgrid (0) - -

- -set/dxgridAllow grid squares on the end of DX messages - - -

-Some logging programs do not like the additional information at -the end of a DX spot. If this is the case, use the unset/dxgrid -command to remove the grid squares. - -set/dxnet (5) - -

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

-Set the node_call as a DXNet type node - -set/echo (0) - -

- -set/echo Make the cluster echo your input - - -

-If you are connected via a telnet session, different implimentations -of telnet handle echo differently depending on whether you are -connected via port 23 or some other port. You can use this command -to change the setting appropriately. - -You can remove the echo with the unset/echo command - -The setting is stored in your user profile. - -YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25. - -set/email (0) - -

- -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 (0) - -

- -set/here Set the here flag - - -

-Let others on the cluster know you are here by only displaying your -callsign. If you are away from your terminal you can use the unset/here -command to let people know you are away. This simply puts brackets -around your callsign to indicate you are not available. - -set/homenode (0) - -

- -set/homenode <node_call> Set your home cluster - - -

-Tell the cluster system where you normally connect to. Any Messages sent -to you will normally find their way there should you not be connected. -eg:- - - - SET/HOMENODE gb7djk - - -set/hops (8) - -

- -set/hops <node_call> ann|spots|wwv|wcy <n> -Set hop count - - -

-Set the hop count for a particular type of broadcast for a node. - -This command allows you to set up special hop counts for a node -for currently: announce, spots, wwv and wcy broadcasts. - - -eg: - set/hops gb7djk ann 10 - set/hops gb7mbc spots 20 - - -Set SHOW/HOPS for information on what is already set. This command -creates a filter and works in conjunction with the filter system. - -set/isolate (9) - -

- -set/isolate <node call> Isolate a node from the rest of the network - - -

-Connect a node to your system in such a way that you are a full protocol -member of its network and can see all spots on it, but nothing either leaks -out from it nor goes back into from the rest of the nodes connected to you. - -You can potentially connect several nodes in this way. - -You can see which nodes are isolated with the show/isolate (1) command. - -You can remove the isolation with the command unset/isolate. - -set/language (0) - -

- -set/language <language> Set the language you wish to use - - -

-You can select the language that you want the cluster to use. Currently -the languages available are en (English) and nl (Dutch). - -set/location (0) - -

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

-You can set your latitude and longitude manually or alternatively use the -set/qra command which will do the conversion for you. - - - set/location 54 04 N 2 02 E - - - -set/sys_location (9) - -

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

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

- -set/logininfo Show logins and logouts of nodes and users - - -

-Show users and nodes when they log in and out of the local cluster. You -can stop these messages by using the unset/logininfo command. - - -set/lockout (9) - -

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

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

- -set/name <your_name> Set your name - - -

-Tell the cluster what your name is, eg:- - - - set/name Dirk - - -set/node (9) - -

- -set/node <call> [<call> ...] Make the callsign an AK1A cluster - - -

-Tell the system that the call(s) are to be treated as AK1A cluster and -fed PC Protocol rather normal user commands. - -From version 1.41 you can also set the following types of cluster - - - set/spider - set/dxnet - set/clx - set/arcluster - - -To see what your nodes are set to, use the show/nodes command. - -set/obscount (9) - -

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

-From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see -SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up' -counter which is decremented on every outgoing ping and then reset to -the 'obscount' value on every incoming ping. The default value of this -parameter is 2. - -What this means is that a neighbouring node will be pinged twice at -(default) 300 second intervals and if no reply has been heard just before -what would be the third attempt, that node is disconnected. - -If a ping is heard then the obscount is reset to the full value. Using -default values, if a node has not responded to a ping within 15 minutes, -it is disconnected. - -set/page (0) - -

- -set/page <n> Set the number of lines per page - - -

-Tell the system how many lines you wish on a page when the number of lines -of output from a command is more than this. The default is 20. Setting it -explicitly to 0 will disable paging. - - - SET/PAGE 30 - SET/PAGE 0 - - -The setting is stored in your user profile. - -set/password (0) - -

- -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 (9) - -

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

-The password for a user can only be set by a full sysop. The string -can contain any characters. - -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 (9) - -

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

-As from version 1.35 all neighbouring nodes are pinged at regular intervals -in order to determine the rolling quality of the link and, in future, to -affect routing decisions. The default interval is 300 secs or 5 minutes. - -You can use this command to set a different interval. Please don't. - -But if you do the value you enter is treated as minutes up 60 and seconds -for numbers greater than that. - -This is used also to help determine when a link is down at the far end -(as certain cluster software doesn't always notice), see SET/OBSCOUNT -for more information. - -set/privilege (9) - -

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

-Set the privilege level on a callsign. The privilege levels that pertain -to commands are as default:- - - - 0 - normal user - 1 - allow remote nodes normal user RCMDs - 5 - various privileged commands (including shutdown, but not disc- - connect), the normal level for another node. - 8 - more privileged commands (including disconnect) - 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS - LEVEL. - - -If you are a sysop and you come in as a normal user on a remote connection -your privilege will automatically be set to 0. - -set/spider (5) - -

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

-Set the node_call as a DXSpider type node - -set/sys_qra (9) - -

- -set/sys_qra <locator> Set your cluster QRA locator - - -set/qra (0) - -

- -set/qra <locator> Set your QRA locator - - -

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

- -set/qth <your QTH> Set your QTH - - -

-Tell the system where your are. For example:- - - - set/qth East Dereham, Norfolk - - -set/register (9) - -

- -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 (0) - -

- -set/talk Allow talk messages to be seen at your console - - -

-Allow talk messages to arrive at your console. You can switch off -talks with the unset/talk command. - -set/wcy (0) - -

- -set/wcy Allow WCY messages to be seen at your console - - -

-Allow WCY information to be seen at your console. You can switch off -WCY messages with the unset/wcy command. - -set/wwv (0) - -

- -set/wwv Allow WWV messages to be seen at your console - - -

-Allow WWV information to be seen at your console. You can switch off -WWV messages with the unset/wwv command. - -set/wx (0) - -

- -set/wx Allow WX messages to be seen at your console - - -

-Allow WX information to be seen at your console. You can switch off -WX messages with the unset/wx command. - -show/baddx (1) - -

- -show/baddxShow all the bad dx calls in the system - - -

-Display all the bad dx callsigns in the system, see SET/BADDX -for more information. - -show/badnode (6) - -

- -show/badnode Show all the bad nodes in the system - - -

-Display all the bad node callsigns in the system, see SET/BADNODE -for more information. - -show/badspotter (1) - -

- -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 (1) - -

- -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 (0) - -

- -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 (0) - -

- -show/configuration/node Show all the nodes connected - - -

-Show all the nodes connected locally and the nodes they have connected. - -show/connect (1) - -

- -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 (0) - -

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

-This is very nearly the same as SHOW/TIME, the only difference the format -of the date string if no arguments are given. - -If no prefixes or callsigns are given then this command returns the local -time and UTC as the computer has it right now. If you give some prefixes -then it will show UTC and UTC + the local offset (not including DST) at -the prefixes or callsigns that you specify. - -show/debug (9) - -

- -show/debug Show what levels of debug you are logging - - -

-The levels can be set with set/debug - -show/dx (0) - -

- -show/dx [options] interrogate the spot database - - -

-If you just type SHOW/DX you will get the last so many spots -(sysop configurable, but usually 10). - -In addition you can add any number of these options in very nearly -any order to the basic SHOW/DX command, they are:- - - -on <band> - eg 160m 20m 2m 23cm 6mm -on <region> - eg hf vhf uhf shf (see SHOW/BANDS) - -<number> - the number of spots you want -<from>-<to> - <from> spot no <to> spot no in - the selected list - -<prefix> - for a spotted callsign beginning with <prefix> -*<suffix> - for a spotted callsign ending in <suffix> -*<string>* - for a spotted callsign containing <string> - -day <number> - starting <number> days ago -day <from>-<to> - <from> days <to> days ago - -info <text> - any spots containing <text> in the info or remarks - -by <call> - any spots spotted by <call> (spotter <call> - is the same). - -qsl - this automatically looks for any qsl info on the call - held in the spot database. - -iota [<iota>] - If the iota island number is missing it will - look for the string iota and anything which looks like - an iota island number. If you specify then it will look - for that island. - -qra [<locator>] - this will look for the specific locator if - you specify one or else anything that looks like a locator. - - -e.g. - - - SH/DX 9m0 - SH/DX on 20m info iota - SH/DX 9a on vhf day 30 - SH/DX rf1p qsl - SH/DX iota - SH/DX iota eu-064 - SH/DX qra jn86 - - -show/dxcc (0) - -

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

-This command takes the <prefix> (which can be a full or partial -callsign if desired), looks up which internal country number it is -and then displays all the spots as per SH/DX for that country. - -The options for SHOW/DX also apply to this command. -e.g. - - - SH/DXCC G - SH/DXCC W on 20m info iota - - -sh/dxstats (0) - -

- -sh/dxstats Show the DX Statistics for last 31 days - - -

-Show the total DX spots for the last 31 days - - -show/files (0) - -

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

-SHOW/FILES on its own will show you a list of the various fileareas -available on the system. To see the contents of a particular file -area type:- - - - SH/FILES <filearea> - - -where <filearea> is the name of the filearea you want to see the -contents of. - -You can also use shell globbing characters like '*' and '?' in a -string to see a selection of files in a filearea eg:- - - - SH/FILES bulletins arld* - - -See also TYPE - to see the contents of a file. - -show/filter (0) - -

- -show/filter Show the filters you have set - - -

-Show the contents of all the filters that are set by you. This command -displays all the filters set - for all the various categories. - -show/filter (extended for sysops) (5) - -

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

-A sysop can look at any filters that have been set. - -show/hfstats (0) - -

- -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 (0) - -

- -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 (8) - -

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

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

- -show/isolate Show a list of isolated nodes - - -

-Show which nodes are currently set to be isolated. - -show/lockout (9) - -

- -show/lockout Show a list of excluded callsigns - - -

-Show a list of callsigns that have been excluded (locked out) of the -cluster locally with the set/lockout command - -show/log (8) - -

- -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 (0) - -

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

-Show the Moon rise and set times for a (list of) prefixes or callsigns, -together with the azimuth and elevation of the sun currently at those -locations. - -If you don't specify any prefixes or callsigns, it will show the times for -your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), -together with the current azimuth and elevation. - -In addition, it will show the gain or loss dB relative to the nominal -distance of 385,000Km due to the ellipsoidal nature of the orbit. - -If all else fails it will show the Moonrise and set times for the node -that you are connected to. - -For example:- - - - SH/MOON - SH/MOON G1TLH W5UN - - -show/muf (0) - -

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

-This command allow you to estimate the likelihood of you contacting -a station with the prefix you have specified. The output assumes a modest -power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD) - -The result predicts the most likely operating frequencies and signal -levels for high frequency (shortwave) radio propagation paths on -specified days of the year and hours of the day. It is most useful for -paths between 250 km and 6000 km, but can be used with reduced accuracy -for paths shorter or longer than this. - -The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and -used to predict the MUF given the predicted flux, day of the year, -hour of the day and geographic coordinates of the transmitter and -receiver. This routine is reasonably accurate for the purposes here, -with a claimed RMS error of 3.8 MHz, but much smaller and less complex -than the programs used by major shortwave broadcasting organizations, -such as the Voice of America. - -The command will display some header information detailing its -assumptions, together with the locations, latitude and longitudes and -bearings. It will then show UTC (UT), local time at the other end -(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path -(Zen) and the likely signal strengths. Then for each frequency for which -the system thinks there is a likelihood of a circuit it prints a value. - -The value is currently a likely S meter reading based on the conventional -6dB / S point scale. If the value has a '+' appended it means that it is -1/2 an S point stronger. If the value is preceeded by an 'm' it means that -there is likely to be much fading and by an 's' that the signal is likely -to be noisy. - -By default SHOW/MUF will show the next two hours worth of data. You -can specify anything up to 24 hours worth of data by appending the no of -hours required after the prefix. For example:- - - - SH/MUF W - - -produces: - - - RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21 - Power : 20 dBW Distance: 6283 km Delay: 22.4 ms - Location Lat / Long Azim - East Dereham, Norfolk 52 41 N 0 57 E 47 - United-States-W 43 0 N 87 54 W 299 - UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0 - 18 23 11.5 -35 mS0+ mS2 S3 - 19 0 11.2 -41 mS0+ mS2 S3 - - -indicating that you will have weak, fading circuits on top band and -80m but usable signals on 40m (about S3). - -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 (0) - -

- -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 (0) - -

- -show/newconfiguration/node Show all the nodes connected locally - - -

-Show all the nodes connected to this node in the new format. - -show/node (1) - -

- -show/node [<node_call> ...] Show the type and version -number of nodes - - -

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

- -show/prefix <callsign> Interrogate the prefix database - - -

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

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

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

- -show/qra <locator> [<locator>] Show the distance -between locators -show/qra <lat> <long> Convert latitude and longitude to -a locator - - -

-This is a multipurpose command that allows you either to calculate the -distance and bearing between two locators or (if only one locator is -given on the command line) the distance and beraing from your station -to the locator. For example:- - - -SH/QRA IO92QL -SH/QRA JN06 IN73 - - -The first example will show the distance and bearing to the locator from -yourself, the second example will calculate the distance and bearing from -the first locator to the second. You can use 4 or 6 character locators. - -It is also possible to convert a latitude and longitude to a locator by -using this command with a latitude and longitude as an argument, for -example:- - - -SH/QRA 52 41 N 0 58 E - - -show/qrz (0) - -

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

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

- -show/registered [<prefix>[ Show the registered users - - -show/route (0) - -

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

-This command allows you to see to which node the callsigns specified are -connected. It is a sort of inverse sh/config. - - - sh/route n2tly - - -show/satellite (0) - -

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

-Show the tracking data from your location to the satellite of your choice -from now on for the next few hours. - -If you use this command without a satellite name it will display a list -of all the satellites known currently to the system. - -If you give a name then you can obtain tracking data of all the passes -that start and finish 5 degrees below the horizon. As default it will -give information for the next three hours for every five minute period. - -You can alter the number of hours and the step size, within certain -limits. - -Each pass in a period is separated with a row of '-----' characters - -So for example:- - - -SH/SAT AO-10 -SH/SAT FENGYUN1 12 2 - - -show/sun (0) - -

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

-Show the sun rise and set times for a (list of) prefixes or callsigns, -together with the azimuth and elevation of the sun currently at those -locations. - -If you don't specify any prefixes or callsigns, it will show the times for -your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), -together with the current azimuth and elevation. - -If all else fails it will show the sunrise and set times for the node -that you are connected to. - -For example:- - - - SH/SUN - SH/SUN G1TLH K9CW ZS - - -show/time (0) - -

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

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

- -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 (0) - -

- -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 (0) - -

- -show/wcy Show the last 10 WCY broadcasts -show/wcy <n> Show the last <n> WCY broadcasts - - -

-Display the most recent WCY information that has been received by the system - -show/wwv (0) - -

- -show/wwv Show the last 10 WWV broadcasts -show/wwv <n> Show the last <n> WWV broadcasts - - -

-Display the most recent WWV information that has been received by the system - - -shutdown (5) - -

- -shutdown Shutdown the cluster - - -

-Shutdown the cluster and disconnect all the users. If you have Spider -set to respawn in /etc/inittab it will of course restart. - -spoof (9) - -

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

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

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

-Show the internal status of a database descriptor. - -Depending on your privilege level you will see more or less information. -This command is unlikely to be of much use to anyone other than a sysop. - -stat/channel (5) - -

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

-Show the internal status of the channel object either for the channel that -you are on or else for the callsign that you asked for. - -Only the fields that are defined (in perl term) will be displayed. - -stat/msg (5) - -

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

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

-If no message number is given then the status of the message system is -displayed. - -stat/route_node (5) - -

- -stat/route_node <callsign> Show the data in a Route::Node object - - -stat/route_user (5) - -

- -stat/route_user <callsign> Show the data in a Route::User object - - -stat/user (5) - -

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

-Shows the full contents of a user record including all the secret flags -and stuff. - -Only the fields that are defined (in perl term) will be displayed. - -sysop (0) - -

- -sysop Regain your privileges if you login remotely - - -

-The system automatically reduces your privilege level to that of a -normal user if you login in remotely. This command allows you to -regain your normal privilege level. It uses the normal system: five -numbers are returned that are indexes into the character array that is -your assigned password (see SET/PASSWORD). The indexes start from -zero. - -You are expected to return a string which contains the characters -required in the correct order. You may intersperse those characters -with others to obscure your reply for any watchers. For example (and -these values are for explanation :-): - - - password = 012345678901234567890123456789 - > sysop - 22 10 15 17 3 - - -you type:- - - - aa2bbbb0ccc5ddd7xxx3n - or 2 0 5 7 3 - or 20573 - - -They will all match. If there is no password you will still be offered -numbers but nothing will happen when you input a string. Any match is -case sensitive. - -talk (0) - -

- -talk <callsign> Enter talk mode with <callsign> -talk <callsign> <text> Send a text message to <callsign> -talk <callsign> > <node_call> [<text>] -Send a text message to <callsign> via <node_call> - - -

-Send a short message to any other station that is visible on the cluster -system. You can send it to anyone you can see with a SHOW/CONFIGURATION -command, they don't have to be connected locally. - -The second form of TALK is used when other cluster nodes are connected -with restricted information. This usually means that they don't send -the user information usually associated with logging on and off the cluster. - -If you know that G3JNB is likely to be present on GB7TLH, but you can only -see GB7TLH in the SH/C list but with no users, then you would use the -second form of the talk message. - -If you want to have a ragchew with someone you can leave the text message -out and the system will go into 'Talk' mode. What this means is that a -short message is sent to the recipient telling them that you are in a 'Talking' -frame of mind and then you just type - everything you send will go to the -station that you asked for. - -All the usual announcements, spots and so on will still come out on your -terminal. - -If you want to do something (such as send a spot) you precede the normal -command with a '/' character, eg:- - - - /DX 14001 G1TLH What's a B class licensee doing on 20m CW? - /HELP talk - - -To leave talk mode type: - - - /EX - - -type (0) - -

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

-Type out the contents of a file in a filearea. So, for example, in -filearea 'bulletins' you want to look at file 'arld051' you would -enter:- - - - TYPE bulletins/arld051 - - -See also SHOW/FILES to see what fileareas are available and a -list of content. - -who (0) - -

- -who Show who is physically connected locally - - -

-This is a quick listing that shows which callsigns are connected and -what sort of connection they have - -wx (0) - -

- -wx <text> Send a weather message to local users -wx full <text> Send a weather message to all cluster users - - -

-Weather messages can sometimes be useful if you are experiencing an extreme -that may indicate enhanced conditions - -wx (enhanced for sysops) (5) - -

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

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