\r
<sect>The DXSpider command set\r
\r
-<P>\r
-Below is a complete list of commands available from the cluster prompt.\r
-Most maintenance tasks are automatic but there are some commands that are useful\r
-for a sysop. These are listed below in alphabetical order. The number in\r
-brackets following the command name is the permissions level needed to use\r
-the command\r
-\r
-<sect1>accept/announce (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>accept/announce [0-9] <pattern></bf> Set an accept filter\r
- line for announce\r
-</tt>\r
-\r
-<P>\r
-Create an 'accept this announce' line for a filter.\r
-\r
-An accept filter line means that if the announce matches this filter it is\r
-passed onto the user. See HELP FILTERS for more info. Please read this\r
-to understand how filters work - it will save a lot of grief later on.\r
-\r
-You can use any of the following things in this line:-\r
-\r
-<tscreen><verb>\r
- info <string> eg: iota or qsl\r
- by <prefixes> eg: G,M,2\r
- origin <prefixes>\r
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)\r
- origin_itu <numbers>\r
- origin_zone <numbers>\r
- by_dxcc <numbers>\r
- by_itu <numbers>\r
- by_zone <numbers>\r
- channel <prefixes>\r
- wx 1 filter WX announces\r
- dest <prefixes> eg: 6MUK,WDX (distros)\r
-</verb></tscreen>\r
-\r
-some examples:-\r
-\r
-<tscreen><verb>\r
- acc/ann dest 6MUK\r
- acc/ann 2 by_zone 14,15,16\r
- (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)\r
-</verb></tscreen>\r
-\r
-or\r
-\r
-<tscreen><verb>\r
- acc/ann by G,M,2 \r
-</verb></tscreen>\r
-\r
-This filter would only allow announces that were posted buy UK stations. \r
-You can use the tag 'all' to accept everything eg:\r
-\r
-<tscreen><verb>\r
- acc/ann all\r
-</verb></tscreen>\r
-\r
-but this probably for advanced users...\r
-\r
-<sect1>accept/announce (extended for sysops) (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>accept/announce <call> [input] [0-9]<pattern></bf> Announce filter sysop version\r
-</tt>\r
-\r
-<P>\r
-This version allows a sysop to set a filter for a callsign as well as the\r
-default for nodes and users eg:-\r
-\r
-<tscreen><verb>\r
- accept/ann by G,M,2\r
- accept/ann input node_default by G,M,2\r
- accept/ann user_default by G,M,2\r
-</verb></tscreen>\r
-\r
-<sect1>accept/route (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>accept/route <call> [0-9] <pattern></bf> Set an 'accept' filter line for routing\r
-</tt>\r
-\r
-<P>\r
-Create an 'accept this routing PC Protocol' line for a filter. \r
-\r
-<P>\r
-An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter\r
-it is passed thru that interface. See HELP FILTERING for more info. Please read this\r
-to understand how filters work - it will save a lot of grief later on.\r
-\r
-<P>\r
-You can use any of the following things in this line:-\r
-\r
-<tscreen><verb>\r
- call <prefixes> the callsign of the thingy\r
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)\r
- call_itu <numbers>\r
- call_zone <numbers>\r
- origin <prefixes> really the interface it came in on\r
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)\r
- origin_itu <numbers>\r
- origin_zone <numbers>\r
-</verb></tscreen>\r
-\r
-<P>\r
-some examples:-\r
-\r
-<tscreen><verb>\r
- acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)\r
- acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)\r
-</verb></tscreen>\r
-\r
-<P>\r
-You can use the tag 'all' to accept everything eg:\r
-\r
-<tscreen><verb>\r
- acc/route all\r
-</verb></tscreen>\r
-\r
-<sect1>accept/spots (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>accept/spots [0-9] <pattern></bf> Set an accept filter \r
-line for spots\r
-</tt>\r
-\r
-<P>\r
-Create an 'accept this spot' line for a filter.\r
-\r
-<P>\r
-An accept filter line means that if the spot matches this filter it is\r
-passed onto the user. See HELP FILTERS for more info. Please read this\r
-to understand how filters work - it will save a lot of grief later on.\r
-\r
-Please read the following section carefully. Though it looks similar,\r
-reformatting, corrections, and hopefully clarifications have been added.\r
-\r
-You can use any of the following things in this line:-\r
-\r
-<tscreen><verb>\r
-Filters for the station being spotted:\r
- call <letters of the prefix, but NOT country inclusive>\r
- call G --> G1AAA, GJ2BBB, GU3CCC, etc will be spotted\r
- call K --> K1XX, K1XXX will be spotted\r
- W1XX, W1XXX will NOT be spotted\r
- call PA --> PA3EZL will be spotted\r
- PB2FG will NOT be spotted\r
-\r
- call_dxcc <numbers or prefixes>\r
- call_dxcc G --> G1AAA will be spotted\r
- GU1AAA will NOT be spotted (different country)\r
- call_dxcc K --> K1XX, W1XX will be spotted (same country)\r
- call_dxcc 139 --> PA3EZL and PB2FG will be spotted\r
-\r
- call_itu <numbers>\r
- call_zone <numbers>\r
-\r
-Filters for the callsign of the station doing the spotting:\r
- by <letters of the prefix, but NOT country inclusive>\r
- by G --> spots from G1AAA, GJ2BBB, GU3CCC, etc will be spotted\r
- by K --> spots from K1XX, K1XXX will be spotted\r
- spots from W1XX, W1XXX will NOT be spotted\r
-\r
- by_dxcc <numbers or prefixes>\r
- by_dxcc G --> spots from G1AAA will be spotted\r
- spots from GU1AAA will NOT be spotted (different\r
-country)\r
- by_dxcc K --> spots from K1XX, W1XX will be spotted (same country)\r
- by_dxcc 139 --> spots from PA3EZL or PB2FG will be spotted\r
-\r
- by_itu <numbers>\r
- by_zone <numbers>\r
-\r
-Filters for the callsign of the "node" doing the spotting:\r
- origin <letters of the prefix, but NOT country inclusive>\r
- origin K --> spots from a node starting with K will be spotted\r
- spots from a node starting with KK will NOT be spotted\r
- spots from a node starting with W will NOT be spotted\r
-\r
-Filters for the callsign of the connected node or user (channel) doing the spotting:\r
- channel <prefixes>\r
- channel W1HR --> spots from the connected node W1HR will be spotted\r
- channel K1QX --> spots from the connected user K1QX will be spotted\r
-\r
- info <string> eg: iota or qsl\r
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m\r
- on <range> same as 'freq'\r
-\r
-</verb></tscreen>\r
-\r
-<P>\r
-For frequencies, you can use any of the band names defined in\r
-SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -\r
-thus: hf/ssb. You can also just have a simple range like: 0/30000 -\r
-this is more efficient than saying simply: freq HF (but don't get\r
-too hung up about that)\r
-\r
-some examples:-\r
-\r
-<tscreen><verb>\r
- acc/spot 1 on hf/cw\r
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)\r
-</verb></tscreen>\r
-\r
-You can use the tag 'all' to accept everything, eg:\r
-\r
-<tscreen><verb>\r
- acc/spot 3 all\r
-</verb></tscreen>\r
-\r
-but this probably for advanced users...\r
-\r
-<sect1>accept/spots (extended for sysops) (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>accept/spots <call> [input] [0-9] <pattern></bf> Spot filter sysop version\r
-</tt>\r
-\r
-<P>\r
-This version allows a sysop to set a filter for a callsign as well as the\r
-default for nodes and users eg:-\r
-\r
-<tscreen><verb>\r
- accept/spot db0sue-7 1 by_zone 14,15,16\r
- accept/spot node_default all\r
- set/hops node_default 10\r
-\r
- accept/spot user_default by G,M,2\r
-</verb></tscreen>\r
-\r
-<sect1>accept/wcy (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>accept/wcy [0-9] <pattern></bf> set an accept WCY filter\r
-</tt>\r
-\r
-<P>\r
-It is unlikely that you will want to do this, but if you do then you can\r
-filter on the following fields:-\r
-\r
-<tscreen><verb>\r
- by <prefixes> eg: G,M,2 \r
- origin <prefixes>\r
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)\r
- origin_itu <numbers>\r
- origin_zone <numbers>\r
- by_dxcc <numbers>\r
- by_itu <numbers>\r
- by_zone <numbers>\r
- channel <prefixes>\r
-</verb></tscreen>\r
-\r
-<P>\r
-There are no examples because WCY Broadcasts only come from one place and\r
-you either want them or not (see UNSET/WCY if you don't want them).\r
-\r
-This command is really provided for future use.\r
-\r
-See HELP FILTER for information.\r
-\r
-<sect1>accept/wcy (extended for sysops) (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>accept/wcy <call> [input] [0-9] <pattern></bf>\r
-WCY filter sysop version\r
-</tt>\r
-\r
-<P>\r
-This version allows a sysop to set a filter for a callsign as well as the\r
-default for nodes and users eg:-\r
-\r
-<tscreen><verb>\r
- accept/wcy node_default all\r
- set/hops node_default 10\r
-</verb></tscreen>\r
-\r
-<sect1>accept/wwv (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>accept/wwv [0-9] <pattern></bf> Set an accept WWV filter\r
-</tt>\r
-\r
-<P>\r
-It is unlikely that you will want to do this, but if you do then you can\r
-filter on the following fields:-\r
-\r
-<tscreen><verb>\r
- by <prefixes> eg: G,M,2 \r
- origin <prefixes>\r
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)\r
- origin_itu <numbers>\r
- origin_zone <numbers>\r
- by_dxcc <numbers>\r
- by_itu <numbers>\r
- by_zone <numbers>\r
- channel <prefixes>\r
-</verb></tscreen>\r
-\r
-for example \r
-\r
-<tscreen><verb>\r
- accept/wwv by_zone 4\r
-</verb></tscreen>\r
-\r
-is probably the only useful thing to do (which will only show WWV broadcasts\r
-by stations in the US).\r
-\r
-See HELP FILTER for information.\r
-\r
-<sect1>accept/wwv (extended for sysops) (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>accept/wwv <call> [input] [0-9] <pattern></bf>\r
-WWV filter sysop version\r
-</tt>\r
-\r
-<P>\r
-This version allows a sysop to set a filter for a callsign as well as the\r
-default for nodes and users eg:-\r
-\r
-<tscreen><verb>\r
- accept/wwv db0sue-7 1 by_zone 4\r
- accept/wwv node_default all\r
- set/hops node_default 10\r
-\r
- accept/wwv user_default by W,K\r
-</verb></tscreen>\r
-\r
-<sect1>announce (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>announce <text></bf> Send an announcement to local users\r
-</tt>\r
-\r
-<P>\r
-Send an announcement to LOCAL users only, where <text> is the text \r
-of the announcement you wish to broadcast. If you do not wish to receive\r
-announces, use the <em>set/noannounce</em> command. Any announces made by\r
-a sysop will override set/noannounce.\r
-\r
-<sect1>announce full (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>announce full <text></bf> Send an announcement cluster wide\r
-</tt>\r
-\r
-<P>\r
-This command will send your announcement across the whole cluster\r
-network.\r
-\r
-\r
-<sect1>announce sysop (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>announce sysop <text></bf>\r
-</tt>\r
-\r
-<P>\r
-Send an announcement to Sysops only\r
-\r
-<sect1>apropos (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>apropos <string></bf> Search the help database\r
-</tt>\r
-\r
-<P>\r
-Search the help database for <string> (it isn't case sensitive), \r
-and print the names of all the commands that may be relevant.\r
-\r
-<sect1>bye (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>bye</bf> Exit from the cluster\r
-</tt>\r
-\r
-<P>\r
-This will disconnect you from the cluster\r
-\r
-<sect1>catchup (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>catchup <node_call> All|[<msgno> ...]</bf> \r
-Mark a message as sent\r
-</tt>\r
-\r
-<P>\r
-When you send messages the fact that you have forwarded it to another node \r
-is remembered so that it isn't sent again. When you have a new partner\r
-node and you add their callsign to your /spider/msg/forward.pl file, all\r
-outstanding non-private messages will be forwarded to them. This may well\r
-be ALL the non-private messages. You can prevent this by using these \r
-commmands:-\r
-\r
-<tscreen><verb>\r
- catchup GB7DJK all\r
- catchup GB7DJK 300 301 302 303 500-510\r
-</verb></tscreen>\r
- \r
-and to undo what you have just done:-\r
- \r
-<tscreen><verb>\r
- uncatchup GB7DJK all\r
- uncatchup GB7DJK 300 301 302 303 500-510\r
-</verb></tscreen>\r
-\r
-which will arrange for them to be forward candidates again.\r
-\r
-Order is not important.\r
-\r
-<sect1>clear/announce (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>clear/announce <callsign> [input] [0-9|all]</bf> Clear an announce filter line\r
-</tt>\r
-\r
-<P>\r
-A sysop can clear an input or normal output filter for a user or the\r
-node_default or user_default. \r
-\r
-<sect1>clear/route (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>clear/route <callsign> [input] [0-9|all]</bf> Clear a route filter line\r
-</tt>\r
-\r
-<P>\r
-This command allows you to clear (remove) a line in a route filter or to \r
-remove the whole filter.\r
-\r
-see CLEAR/SPOTS for a more detailed explanation.\r
-\r
-A sysop can clear an input or normal output filter for a user or the\r
-node_default or user_default. \r
-\r
-<sect1>clear/spots (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>clear/spots [1|all]</bf> Clear a spot filter line\r
-</tt>\r
-\r
-<P>\r
-This command allows you to clear (remove) a line in a spot filter or to \r
-remove the whole filter.\r
-\r
-If you have a filter:-\r
-\r
-<tscreen><verb>\r
- acc/spot 1 on hf/cw\r
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)\r
-</verb></tscreen>\r
-\r
-and you say:-\r
-\r
-<tscreen><verb>\r
- clear/spot 1\r
-</verb></tscreen>\r
-\r
-you will be left with:-\r
-\r
-<tscreen><verb>\r
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)\r
-</verb></tscreen>\r
-\r
-If you do:\r
-\r
-<tscreen><verb>\r
- clear/spot all\r
-</verb></tscreen>\r
-\r
-the filter will be completely removed.\r
-\r
-<sect1>clear/spots (extended for sysops) (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>clear/spots <callsign> [input] [0-9|all]</bf> Clear a spot filter line\r
-</tt>\r
-\r
-<P>\r
-A sysop can clear an input or normal output filter for a user or the\r
-node_default or user_default. \r
-\r
-<sect1>clear/wcy (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>clear/wcy [1|all]</bf> Clear a WCY filter line\r
-</tt>\r
-\r
-<P>\r
-This command allows you to clear (remove) a line in a WCY filter or to \r
-remove the whole filter.\r
-\r
-see CLEAR/SPOTS for a more detailed explanation.\r
-\r
-<sect1>clear/wcy (extended for sysops) (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>clear/wcy <callsign> [input] [0-9|all]</bf> Clear a WCY filter line\r
-</tt>\r
-\r
-<P>\r
-A sysop can clear an input or normal output filter for a user or the\r
-node_default or user_default. \r
-\r
-<sect1>clear/wwv (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>clear/wwv [1|all]</bf> Clear a WWV filter line\r
-</tt>\r
-\r
-<P>\r
-This command allows you to clear (remove) a line in a WWV filter or to\r
-remove the whole filter.\r
-\r
-see CLEAR/SPOTS for a more detailed explanation.\r
-\r
-<sect1>clear/wwv (extended for sysops) (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>clear/wwv <callsign> [input] [0-9|all]</bf> Clear a WWV filter line\r
-</tt>\r
-\r
-<P>\r
-A sysop can clear an input or normal output filter for a user or the\r
-node_default or user_default.\r
-\r
-<sect1>connect (5) \r
-\r
-<P>\r
-<tt>\r
-<bf>connect <callsign></bf> Start a connection to another DX Cluster\r
-</tt>\r
-\r
-<P>\r
-Start a connection process that will culminate in a new connection to the\r
-DX cluster <callsign>. This process creates a new 'client' process which will\r
-use the script in /spider/connect/<callsign> to effect the 'chat' exchange\r
-necessary to traverse the network(s) to logon to the cluster <callsign>.\r
-\r
-<sect1>dbavail (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>dbavail</bf> Show a list of all the databases in the system\r
-</tt>\r
-\r
-<P>\r
-The title says it all really, this command lists all the databases defined\r
-in the system. It is also aliased to SHOW/COMMAND.\r
-\r
-<sect1>dbcreate (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>dbcreate <name></bf> Create a database entry<newline>\r
-<bf>dbcreate <name> chain <name> [<name>..]</bf> Create a \r
-chained database entry<newline>\r
-<bf>dbcreate <name> remote <node></bf> Create a remote database\r
-entry<newline>\r
-</tt>\r
-\r
-<P>\r
-DBCREATE allows you to define a database in the system. It doesn't actually\r
-create anything, just defines it.\r
-\r
-The databases that are created are simple DB_File hash databases, they are \r
-therefore already 'indexed'.\r
-\r
-You can define a local database with the first form of the command eg:\r
-\r
- DBCREATE oblast\r
-\r
-You can also chain databases with the addition of the 'chain' keyword. \r
-This will search each database one after the other. A typical example \r
-is:\r
-\r
- DBCREATE sdx_qsl chain sql_ad\r
-\r
-No checking is done to see if the any of the chained databases exist, in\r
-fact it is usually better to do the above statement first then do each of\r
-the chained databases.\r
-\r
-Databases can exist offsite. To define a database that lives on another \r
-node do:\r
-\r
- DBCREATE buckmaster remote gb7dxc\r
-\r
-Remote databases cannot be chained; however, the last database in a \r
-a chain can be a remote database eg:\r
-\r
- DBCREATE qsl chain gb7dxc\r
-\r
-To see what databases have been defined do:\r
-\r
- DBAVAIL (or it will have been aliased to SHOW/COMMAND)\r
-\r
-It would be normal for you to add an entry into your local Aliases file\r
-to allow people to use the 'SHOW/<dbname>' style syntax. So you would\r
-need to add a line like:-\r
-\r
-<tscreen><verb>\r
- 's' => [\r
- ..\r
- ..\r
- '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',\r
- ..\r
- ..\r
- ],\r
-</verb></tscreen>\r
-\r
-to allow \r
-\r
- SH/BUCK g1tlh\r
-\r
-to work as they may be used to.\r
-\r
-See DBIMPORT for the importing of existing AK1A format data to databases.\r
-See DBSHOW for generic database enquiry\r
-\r
-<sect1>dbimport (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>dbimport <dbname></bf> Import AK1A data into a database\r
-</tt>\r
-\r
-<P>\r
-If you want to import or update data in bulk to a database you can use\r
-this command. It will either create or update entries into an existing\r
-database. For example:-\r
-\r
- DBIMPORT oblast /tmp/OBLAST.FUL\r
-\r
-will import the standard OBLAST database that comes with AK1A into the\r
-oblast database held locally.\r
-\r
-<sect1>dbremove (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>dbremove <dbname></bf> Delete a database\r
-</tt>\r
-\r
-<P>\r
-DBREMOVE will completely remove a database entry and also delete any data\r
-file that is associated with it. \r
-\r
-There is no warning, no comeback, no safety net. \r
-\r
-For example:\r
-\r
- DBREMOVE oblast \r
-\r
-will remove the oblast database from the system and it will also remove\r
-the associated datafile.\r
-\r
-I repeat:\r
-\r
-There is no warning, no comeback, no safety net.\r
-\r
-You have been warned.\r
-\r
-<sect1>dbshow (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>dbshow <dbname> <key></bf> Display an entry, if it exists, \r
-in a database\r
-</tt>\r
-\r
-<P>\r
-This is the generic user interface to the database to the database system.\r
-It is expected that the sysop will add an entry to the local Aliases file\r
-so that users can use the more familiar AK1A style of enquiry such as:\r
-\r
-<tscreen><verb>\r
- SH/BUCK G1TLH\r
-</verb></tscreen>\r
-\r
-but if he hasn't and the database really does exist (use DBAVAIL or\r
-SHOW/COMMAND to find out) you can do the same thing with:\r
-\r
-<tscreen><verb>\r
- DBSHOW buck G1TLH\r
-</verb></tscreen>\r
-\r
-\r
-<sect1>debug (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>debug</bf> Set the cluster program into debug mode\r
-</tt>\r
-\r
-<P>\r
-Executing this command will only have an effect if you are running the cluster\r
-in debug mode i.e.\r
-\r
-<tscreen><verb>\r
- perl -d cluster.pl\r
-</verb></tscreen>\r
-\r
-It will interrupt the cluster just after the debug command has finished.\r
-\r
-<sect1>delete/user (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>delete/user <callsign></bf> Delete a user from the User Database\r
-</tt>\r
-\r
-<P>\r
-This command will completely remove a one or more users from the database.\r
-\r
-There is NO SECOND CHANCE.\r
-\r
-It goes without saying that you should use this command CAREFULLY!\r
-\r
-<sect1>demonstrate (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>demonstrate <call> <command></bf> Demonstrate a command to another user\r
-</tt>\r
-\r
-<P>\r
-This command is provided so that sysops can demonstrate commands to \r
-other users. It runs a command as though that user had typed it in and\r
-then sends the output to that user, together with the command that \r
-caused it.\r
-\r
-<tscreen><verb>\r
- DEMO g7brn sh/dx iota oc209\r
- DEMO g1tlh set/here\r
-</verb></tscreen>\r
-\r
-Note that this command is similar to SPOOF and will have the same side\r
-effects. Commands are run at the privilege of the user which is being\r
-demonstrated to.\r
-\r
-<sect1>directory (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>directory</bf> List messages<newline> \r
-<bf>directory all</bf> List all messages<newline>\r
-<bf>directory own</bf> List your own messages<newline>\r
-<bf>directory new</bf> List all new messages<newline>\r
-<bf>directory to <call></bf> List all messages to <call><newline>\r
-<bf>directory from <call></bf> List all messages from <call><newline>\r
-<bf>directory subject <string></bf> List all messages with <string> \r
-in subject<newline>\r
-<bf>directory <nn></bf> List last <nn> messages<newline>\r
-<bf>directory <from>-<to></bf> List messages <from> message <to> message <newline>\r
-</tt>\r
-\r
-<P>\r
-List the messages in the messages directory.\r
-\r
-If there is a 'p' one space after the message number then it is a \r
-personal message. If there is a '-' between the message number and the\r
-'p' then this indicates that the message has been read.\r
-\r
-You can use shell escape characters such as '*' and '?' in the <call>\r
-fields.\r
-\r
-You can combine some of the various directory commands together eg:-\r
-\r
-<tscreen><verb>\r
- DIR TO G1TLH 5\r
-or \r
- DIR SUBJECT IOTA 200-250\r
-</verb></tscreen>\r
-\r
-You can abbreviate all the commands to one letter and use ak1a syntax:-\r
-\r
-<tscreen><verb>\r
- DIR/T G1* 10\r
- DIR/S QSL 10-100 5\r
-</verb></tscreen>\r
-\r
-\r
-<sect1>directory (extended for sysops) (5)\r
-\r
-<P>\r
-Works just like the user command except that sysops can see ALL messages.\r
-\r
-<sect1>disconnect (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>disconnect <call> [<call> ...]</bf> Disconnect a user or node\r
-</tt>\r
-\r
-<P>\r
-Disconnect any <call> connected locally\r
-\r
-<sect1>dx (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>dx [by <call>] <freq> <call> <remarks></bf> Send a DX spot\r
-</tt>\r
-\r
-<P>\r
-This is how you send a DX Spot to other users. You can, in fact, now\r
-enter the <freq> and the <call> either way round. \r
-\r
-<tscreen><verb>\r
- DX FR0G 144.600\r
- DX 144.600 FR0G\r
- DX 144600 FR0G \r
-</verb></tscreen>\r
-\r
-will all give the same result. You can add some remarks to the end\r
-of the command and they will be added to the spot.\r
-\r
-<tscreen><verb>\r
- DX FR0G 144600 this is a test\r
-</verb></tscreen>\r
-\r
-You can credit someone else by saying:-\r
-\r
-<tscreen><verb>\r
- DX by G1TLH FR0G 144.600 he isn't on the cluster\r
-</verb></tscreen>\r
-\r
-The <freq> is compared against the available bands set up in the \r
-cluster. See SHOW/BANDS for more information.\r
-\r
-<sect1>export (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>export <msgno> <filename></bf> Export a message to a file\r
-</tt>\r
-\r
-<P>\r
-Export a message to a file. This command can only be executed on a local\r
-console with a fully privileged user. The file produced will be in a form\r
-ready to be imported back into the cluster by placing it in the import \r
-directory (/spider/msg/import).\r
-\r
-This command cannot overwrite an existing file. This is to provide some \r
-measure of security. Any files written will owned by the same user as the \r
-main cluster, otherwise you can put the new files anywhere the cluster can\r
-access. For example:-\r
-\r
- EXPORT 2345 /tmp/a\r
-\r
-<sect1>export_users (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>export_users [<filename>]</bf> Export the users database to ascii\r
-</tt>\r
-\r
-<P>\r
-Export the users database to a file in ascii format. If no filename\r
-is given then it will export the file to /spider/data/user_asc.\r
-\r
-If the file already exists it will be renamed to <filename>.o. In fact\r
-up to 5 generations of the file can be kept each one with an extra 'o' on the\r
-suffix. \r
-\r
-BE WARNED: this will write to any file you have write access to. No check is\r
-made on the filename (if any) that you specify.\r
-\r
-<sect1>filtering (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>filtering</bf> Filtering things in DXSpider\r
-</tt>\r
-\r
-<P>\r
-There are a number of things you can filter in the DXSpider system. They\r
-all use the same general mechanism.\r
-\r
-In general terms you can create a 'reject' or an 'accept' filter which\r
-can have up to 10 lines in it. You do this using, for example:-\r
- \r
- accept/spots .....\r
- reject/spots .....\r
-\r
-where ..... are the specific commands for that type of filter. There\r
-are filters for spots, wwv, announce, wcy and (for sysops)\r
-connects. See each different accept or reject command reference for\r
-more details.\r
-\r
-There is also a command to clear out one or more lines in a filter and\r
-one to show you what you have set. They are:-\r
-\r
- clear/spots 1\r
- clear/spots all\r
-\r
-and \r
- \r
- show/filter\r
-\r
-There is clear/xxxx command for each type of filter.\r
-\r
-For now we are going to use spots for the examples, but you can apply\r
-the principles to all types of filter.\r
-\r
-There are two main types of filter 'accept' or 'reject'; which you use\r
-depends entirely on how you look at the world and what is least\r
-writing to achieve what you want. Each filter has 10 lines (of any\r
-length) which are tried in order. If a line matches then the action\r
-you have specified is taken (ie reject means ignore it and accept\r
-means gimme it).\r
-\r
-The important thing to remember is that if you specify a 'reject'\r
-filter (all the lines in it say 'reject/spots' (for instance) then if\r
-a spot comes in that doesn't match any of the lines then you will get\r
-it BUT if you specify an 'accept' filter then any spots that don't\r
-match are dumped. For example if I have a one line accept filter:-\r
-\r
- accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)\r
-\r
-then automatically you will ONLY get VHF spots from or to CQ zones 14\r
-15 and 16. If you set a reject filter like:\r
-\r
- reject/spots on hf/cw\r
-\r
-Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA\r
-and will work it even on CW then you could say:-\r
-\r
- reject/spots on hf/cw and not info iota\r
-\r
-But in that case you might only be interested in iota and say:-\r
-\r
- accept/spots not on hf/cw or info iota\r
-\r
-which is exactly the same. You should choose one or the other until\r
-you are confortable with the way it works. Yes, you can mix them\r
-(actually you can have an accept AND a reject on the same line) but\r
-don't try this at home until you can analyse the results that you get\r
-without ringing up the sysop for help.\r
-\r
-You can arrange your filter lines into logical units, either for your\r
-own understanding or simply convenience. I have one set frequently:-\r
-\r
- reject/spots 1 on hf/cw\r
- reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16) \r
-\r
-What this does is to ignore all HF CW spots (being a class B I can't\r
-read any CW and couldn't possibly be interested in HF :-) and also\r
-rejects any spots on VHF which don't either originate or spot someone\r
-in Europe.\r
-\r
-This is an exmaple where you would use the line number (1 and 2 in\r
-this case), if you leave the digit out, the system assumes '1'. Digits\r
-'0'-'9' are available.\r
-\r
-You can leave the word 'and' out if you want, it is implied. You can\r
-use any number of brackets to make the 'expression' as you want\r
-it. There are things called precedence rules working here which mean\r
-that you will NEED brackets in a situation like line 2 because,\r
-without it, will assume:-\r
-\r
- (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16 \r
-\r
-annoying, but that is the way it is. If you use OR - use\r
-brackets. Whilst we are here CASE is not important. 'And BY_Zone' is\r
-just 'and by_zone'.\r
-\r
-If you want to alter your filter you can just redefine one or more\r
-lines of it or clear out one line. For example:-\r
-\r
- reject/spots 1 on hf/ssb\r
-\r
-or \r
-\r
- clear/spots 1\r
-\r
-To remove the filter in its entirty:-\r
-\r
- clear/spots all\r
-\r
-There are similar CLEAR commands for the other filters:-\r
-\r
- clear/announce\r
- clear/wcy\r
- clear/wwv\r
-\r
-ADVANCED USERS:-\r
-\r
-Once you are happy with the results you get, you may like to experiment. \r
-\r
-my example that filters hf/cw spots and accepts vhf/uhf spots from EU\r
-can be written with a mixed filter, eg:\r
-\r
- rej/spot on hf/cw\r
- acc/spot on 0/30000\r
- acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)\r
-\r
-each filter slot actually has a 'reject' slot and an 'accept'\r
-slot. The reject slot is executed BEFORE the accept slot.\r
-\r
-It was mentioned earlier that after a reject test that doesn't match,\r
-the default for following tests is 'accept', the reverse is true for\r
-'accept'. In the example what happens is that the reject is executed\r
-first, any non hf/cw spot is passed to the accept line, which lets\r
-thru everything else on HF.\r
-\r
-The next filter line lets through just VHF/UHF spots from EU.\r
-\r
-<sect1>forward/latlong (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>forward/latlong <node_call></bf> Send latitude and longitude \r
-information to another cluster\r
-</tt>\r
-\r
-<P>\r
-This command sends all the latitude and longitude information that your\r
-cluster is holding against callsigns. One advantage of recieving this\r
-information is that more locator information is held by you. This\r
-means that more locators are given on the DX line assuming you have\r
-<em>set/dxgrid</em> enabled. This could be a LOT of information though, so\r
-it is not recommended on slow links.\r
-\r
-<sect1>forward/opername (1)\r
-\r
-<P>\r
-<tt>\r
-<bf>forward/opername <call></bf> Send out information on this <call> \r
-to all clusters\r
-</tt>\r
-\r
-<P>\r
-This command sends out any information held in the user file which can \r
-be broadcast in PC41 protocol packets. This information is Name, QTH, Location\r
-and Homenode. PC41s are only sent for the information that is available.\r
-\r
-<sect1>help (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>help <cmd></bf> Get help on a command\r
-</tt>\r
-\r
-<P>\r
-All commands can be abbreviated, so SHOW/DX can be abbreviated\r
-to SH/DX, ANNOUNCE can be shortened to AN and so on.\r
-\r
-Look at the APROPOS <string> command which will search the help database\r
-for the <string> you specify and give you a list of likely commands\r
-to look at with HELP.\r
-\r
-<sect1>init (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>init <node call></bf> Re-initialise a link to an AK1A compatible node\r
-</tt>\r
-\r
-<P>\r
-This command attempts to re-initialise a link to a (usually) AK1A node\r
-that has got confused, usually by a protocol loop of some kind. It may\r
-work - but you usually will be better off simply disconnecting it (or\r
-better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your\r
-node>).\r
-\r
-Best of luck - you will need it.\r
-\r
-<sect1>kill (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>kill <msgno> [<msgno> ..]</bf> Delete a message \r
-from the local system\r
-</tt>\r
-\r
-<P>\r
-Delete a message from the local system. You will only be able to\r
-delete messages that you have originated or been sent (unless you are\r
-the sysop).\r
-\r
-<sect1>kill (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>kill <msgno> [<msgno> ...]</bf> Remove or erase a message from \r
-the system<newline>\r
-<bf>kill from <call></bf> Remove all messages from a callsign<newline>\r
-<bf>kill to <call></bf> Remove all messages to a callsign<newline>\r
-</tt>\r
-\r
-<P>\r
-You can get rid of any message to or originating from your callsign using \r
-this command. You can remove more than one message at a time.\r
-\r
-As a sysop you can kill any message on the system.\r
-\r
-<sect1>kill full (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>kill full <msgno> [<msgno>]</bf> Delete a message from the \r
-whole cluster\r
-</tt>\r
-\r
-<P>\r
-Delete a message (usually a 'bulletin') from the whole cluster system. \r
-\r
-This uses the subject field, so any messages that have exactly the same subject\r
-will be deleted. Beware!\r
-\r
-<sect1>kill/expunge (6)\r
-\r
-<P>\r
-<tt>\r
-<bf>kill/expunge <msgno> [<msgno>..]</bf>Expunge a message\r
-</tt>\r
-\r
-<P>\r
-Deleting a message using the normal KILL commands only marks that message\r
-for deletion. The actual deletion only happens later (usually two days later).\r
-\r
-The KILL EXPUNGE command causes the message to be truly deleted more or less\r
-immediately.\r
-\r
-It otherwise is used in the same way as the KILL command.\r
-\r
-\r
-<sect1>links (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>links</bf> Show which nodes are physically connected\r
-</tt>\r
-\r
-<P>\r
-This is a quick listing that shows which links are connected and\r
-some information about them. See WHO for a list of all connections.\r
-\r
-\r
-<sect1>load/aliases (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>load/aliases</bf> Reload the command alias table\r
-</tt>\r
-\r
-<P>\r
-Reload the /spider/cmd/Aliases file after you have editted it. You will need to\r
-do this if you change this file whilst the cluster is running in order for the\r
-changes to take effect.\r
-\r
-<sect1>load/badmsg (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>load/badmsg</bf> Reload the bad message table\r
-</tt>\r
-\r
-<P>\r
-Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst\r
-the cluster is running. This table contains a number of perl regular \r
-expressions which are searched for in the fields targetted of each message. \r
-If any of them match then that message is immediately deleted on receipt. \r
-\r
-<sect1>load/badwords (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>load/badwords</bf> Reload the bad words table\r
-</tt>\r
-\r
-<P>\r
-Reload the /spider/data/badwords file if you have changed it manually whilst\r
-the cluster is running. This file contains a list of words which, if found\r
-on certain text portions of PC protocol, will cause those protocol frames\r
-to be rejected. It will all put out a message if any of these words are\r
-used on the announce, dx and talk commands. The words can be one or \r
-more on a line, lines starting with '#' are ignored.\r
-\r
-<sect1>load/bands (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>load/bands</bf> Reload the band limits table\r
-</tt>\r
-\r
-<P>\r
-Reload the /spider/data/bands.pl file if you have changed it manually whilst\r
-the cluster is running. \r
-\r
-<sect1>load/cmd_cache (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>load/cmd_cache</bf> Reload the automatic command cache\r
-</tt>\r
-\r
-<P>\r
-Normally, if you change a command file in the cmd or local_cmd tree it will\r
-automatially be picked up by the cluster program. Sometimes it can get confused\r
-if you are doing a lot of moving commands about or delete a command in the \r
-local_cmd tree and want to use the normal one again. Execute this command to\r
-reset everything back to the state it was just after a cluster restart.\r
-\r
-<sect1>load/forward (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>load/forward</bf> Reload the msg forwarding routing table\r
-</tt>\r
-\r
-Reload the /spider/msg/forward.pl file if you have changed it\r
-manually whilst the cluster is running.\r
-\r
-<sect1>load/messages (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>load/messages</bf> Reload the system messages file\r
-</tt>\r
-\r
-<P>\r
-If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne\r
-commands) you can have them take effect during a cluster session by executing this\r
-command. You need to do this if get something like :-\r
-\r
-unknown message 'xxxx' in lang 'en'\r
-\r
-<sect1>load/prefixes (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>load/prefixes</bf> Reload the prefix table\r
-</tt>\r
-\r
-<P>\r
-Reload the /spider/data/prefix_data.pl file if you have changed it manually \r
-whilst the cluster is running. \r
-\r
-<sect1>merge (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>merge <node> [<no spots>/<no wwv>]</bf> Ask for the \r
-latest spots and WWV\r
-</tt>\r
-\r
-<P>\r
-MERGE allows you to bring your spot and wwv database up to date. By default\r
-it will request the last 10 spots and 5 WWVs from the node you select. The \r
-node must be connected locally.\r
-\r
-You can request any number of spots or wwv and although they will be appended\r
-to your databases they will not duplicate any that have recently been added \r
-(the last 2 days for spots and last month for WWV data).\r
-\r
-<sect1>msg (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>msg <cmd> <msgno> [data ...]</bf> Alter various message \r
-parameters\r
-</tt>\r
-\r
-<P>\r
-Alter message parameters like To, From, Subject, whether private or bulletin\r
-or return receipt (RR) is required or whether to keep this message from timing\r
-out.\r
-\r
-<tscreen><verb>\r
- MSG TO <msgno> <call> - change TO callsign to <call>\r
- MSG FRom <msgno> <call> - change FROM callsign to <call>\r
- MSG PRrivate <msgno> - set private flag\r
- MSG NOPRrivate <msgno> - unset private flag\r
- MSG RR <msgno> - set RR flag\r
- MSG NORR <msgno> - unset RR flag\r
- MSG KEep <msgno> - set the keep flag (message won't be deleted ever)\r
- MSG NOKEep <msgno> - unset the keep flag\r
- MSG SUbject <msgno> <new> - change the subject to <new>\r
- MSG WAittime <msgno> - remove any waitting time for this message\r
- MSG NOREad <msgno> - mark message as unread\r
- MSG REad <msgno> - mark message as read\r
- MSG QUeue - queue any outstanding bulletins\r
- MSG QUeue 1 - queue any outstanding private messages\r
-</verb></tscreen>\r
-\r
-You can look at the status of a message by using:-\r
-\r
- STAT/MSG <msgno> \r
-\r
-This will display more information on the message than DIR does.\r
-\r
-<sect1>pc (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>pc <call> <text></bf> Send text (eg PC Protocol) to <call>\r
-</tt>\r
-\r
-<P>\r
-Send some arbitrary text to a locally connected callsign. No processing is done on\r
-the text. This command allows you to send PC Protocol to unstick things if problems\r
-arise (messages get stuck etc). eg:-\r
-\r
- pc gb7djk PC33^GB7TLH^GB7DJK^400^\r
-\r
-You can also use in the same way as a talk command to a connected user but\r
-without any processing, added of "from <blah> to <blah>" or whatever.\r
-\r
- pc G1TLH Try doing that properly!!!\r
-\r
-<sect1>ping (1)\r
-\r
-<P>\r
-<tt>\r
-<bf>ping <node></bf> Check the link quality between nodes\r
-</tt>\r
-\r
-<P>\r
-his command allows you to send a frame to another cluster node on\r
-the network and get a return frame. The time it takes to do this\r
-is a good indication of the quality of the link. The actual time\r
-it takes is output to the console in seconds.\r
-Any visible cluster node can be PINGed.\r
-\r
-\r
-<sect1>rcmd (1)\r
-\r
-<P>\r
-<tt>\r
-<bf>rcmd <node call> <cmd></bf> Send a command to another DX cluster\r
-</tt>\r
-\r
-<P>\r
-This command allows you to send nearly any command to another DX Cluster\r
-node that is connected to the system. \r
-\r
-Whether you get any output is dependant on a) whether the other system knows\r
-that the node callsign of this cluster is in fact a node b) whether the\r
-other system is allowing RCMDs from this node and c) whether you have\r
-permission to send this command at all.\r
-\r
-<sect1>read (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>read</bf> Read the next unread personal message addressed to you<newline>\r
-<bf>read <msgno></bf> Read the specified message<newline>\r
-</tt>\r
-\r
-<P>\r
-You can read any messages that are sent as 'non-personal' and also any\r
-message either sent by or sent to your callsign.\r
-\r
-\r
-<sect1>read (extended for sysops) (5) \r
-\r
-<P>\r
-<tt>\r
-<bf>read <msgno></bf> Read a message on the system\r
-</tt>\r
-\r
-<P>\r
-As a sysop you may read any message on the system\r
-\r
-<sect1>reject/announce\r
-\r
-<P>\r
-<tt>\r
-<bf>reject/announce [0-9] <pattern></bf> Set a reject filter\r
-for announce\r
-</tt>\r
-\r
-<P>\r
-Create an 'reject this announce' line for a filter. \r
-\r
-An reject filter line means that if the announce matches this filter it is\r
-passed onto the user. See HELP FILTERS for more info. Please read this\r
-to understand how filters work - it will save a lot of grief later on.\r
-\r
-You can use any of the following things in this line:-\r
-\r
-<tscreen><verb>\r
- info <string> eg: iota or qsl\r
- by <prefixes> eg: G,M,2 \r
- origin <prefixes>\r
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)\r
- origin_itu <numbers>\r
- origin_zone <numbers>\r
- by_dxcc <numbers>\r
- by_itu <numbers>\r
- by_zone <numbers>\r
- channel <prefixes>\r
- wx 1 filter WX announces\r
- dest <prefixes> eg: 6MUK,WDX (distros)\r
-</verb></tscreen>\r
-\r
-some examples:-\r
-\r
-<tscreen><verb>\r
- rej/ann by_zone 14,15,16 and not by G,M,2\r
-</verb></tscreen>\r
- \r
-You can use the tag 'all' to reject everything eg:\r
-\r
-<tscreen><verb>\r
- rej/ann all\r
-</verb></tscreen>\r
-\r
-but this probably for advanced users...\r
-\r
-<sect1>reject/announce (extended for sysops) (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>reject/announce <call> [input] [0-9] <pattern></bf> Announce filter sysop version\r
-</tt>\r
-\r
-<P>\r
-This version allows a sysop to set a filter for a callsign as well as the\r
-default for nodes and users eg:-\r
-\r
-<tscreen><verb>\r
- reject/ann by G,M,2\r
- reject/ann input node_default by G,M,2\r
- reject/ann user_default by G,M,2\r
-</verb></tscreen>\r
-\r
-<sect1>reject/route (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>reject/route <call> [0-9] <pattern></bf> Set an 'reject' filter line for routing\r
-</tt>\r
-\r
-<P>\r
-Create an 'reject this routing PC Protocol' line for a filter. \r
-\r
-<P>\r
-An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter \r
-it is NOT passed thru that interface. See HELP FILTERING for more info. Please \r
-read this to understand how filters work - it will save a lot of grief later on.\r
-You can use any of the following things in this line:-\r
-\r
-<tscreen><verb>\r
- call <prefixes> the callsign of the thingy\r
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)\r
- call_itu <numbers>\r
- call_zone <numbers>\r
- origin <prefixes> really the interface it came in on\r
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)\r
- origin_itu <numbers>\r
- origin_zone <numbers>\r
-</verb></tscreen>\r
-\r
-<P>\r
-some examples:-\r
-\r
-<tscreen><verb>\r
- rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)\r
-</verb></tscreen>\r
-\r
-<P>\r
-You can use the tag 'all' to reject everything eg:\r
-\r
-<tscreen><verb>\r
- rej/route all (equiv to [very] restricted mode)\r
-</verb></tscreen>\r
-\r
-<sect1>reject/spots (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>reject/spots [0-9] <pattern></bf> Set a reject filter \r
-line for spots\r
-</tt>\r
-\r
-<P>\r
-Create a 'reject this spot' line for a filter. \r
-\r
-A reject filter line means that if the spot matches this filter it is\r
-dumped (not passed on). See HELP FILTERS for more info. Please read this\r
-to understand how filters work - it will save a lot of grief later on.\r
-\r
-You can use any of the following things in this line:-\r
-\r
-<tscreen><verb>\r
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m\r
- on <range> same as 'freq'\r
- call <prefixes> eg: G,PA,HB9\r
- info <string> eg: iota or qsl\r
- by <prefixes> \r
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)\r
- call_itu <numbers>\r
- call_zone <numbers>\r
- by_dxcc <numbers>\r
- by_itu <numbers>\r
- by_zone <numbers>\r
- origin <prefixes>\r
- channel <prefixes>\r
-</verb></tscreen>\r
-\r
-For frequencies, you can use any of the band names defined in\r
-SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -\r
-thus: hf/ssb. You can also just have a simple range like: 0/30000 -\r
-this is more efficient than saying simply: on HF (but don't get\r
-too hung up about that)\r
-\r
-some examples:-\r
-\r
-<tscreen><verb>\r
- rej/spot 1 on hf\r
- rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)\r
-</verb></tscreen>\r
-\r
-You can use the tag 'all' to reject everything eg:\r
-\r
-<tscreen><verb>\r
- rej/spot 3 all\r
-</verb></tscreen>\r
-\r
-but this probably for advanced users...\r
-\r
-<sect1>reject/spots (extended for sysops) (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>reject/spots <call> [input] [0-9] <pattern></bf>\r
- Reject spot filter sysop version \r
-</tt>\r
-\r
-<P>\r
-This version allows a sysop to set a filter for a callsign as well as the\r
-default for nodes and users eg:-\r
-\r
-<tscreen><verb>\r
- reject/spot db0sue-7 1 by_zone 14,15,16\r
- reject/spot node_default all\r
- set/hops node_default 10\r
-\r
- reject/spot user_default by G,M,2\r
-</verb></tscreen>\r
-\r
-<sect1>reject/wcy (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>reject/wcy [0-9] <pattern></bf> Set a reject WCY filter\r
-</tt>\r
-\r
-<P>\r
-It is unlikely that you will want to do this, but if you do then you can\r
-filter on the following fields:-\r
-\r
-<tscreen><verb>\r
- by <prefixes> eg: G,M,2 \r
- origin <prefixes>\r
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)\r
- origin_itu <numbers>\r
- origin_zone <numbers>\r
- by_dxcc <numbers>\r
- by_itu <numbers>\r
- by_zone <numbers>\r
- channel <prefixes>\r
-</verb></tscreen>\r
-\r
-There are no examples because WCY Broadcasts only come from one place and\r
-you either want them or not (see UNSET/WCY if you don't want them).\r
-\r
-This command is really provided for future use.\r
-\r
-See HELP FILTER for information.\r
-\r
-<sect1>reject/wcy (extended for sysops) (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>reject/wcy <call> [input] [0-9] <pattern></bf>\r
- WCY reject filter sysop version\r
-</tt>\r
-\r
-<P>\r
-This version allows a sysop to set a filter for a callsign as well as the\r
-default for nodes and users eg:-\r
-\r
- reject/wcy gb7djk all\r
-\r
-<sect1>reject/wwv (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>reject/wwv [0-9] <pattern></bf> Set a reject WWV filter\r
-</tt>\r
-\r
-<P>\r
-It is unlikely that you will want to do this, but if you do then you can\r
-filter on the following fields:-\r
-\r
-<tscreen><verb>\r
- by <prefixes> eg: G,M,2 \r
- origin <prefixes>\r
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)\r
- origin_itu <numbers>\r
- origin_zone <numbers>\r
- by_dxcc <numbers>\r
- by_itu <numbers>\r
- by_zone <numbers>\r
- channel <prefixes>\r
-</verb></tscreen>\r
-\r
-for example \r
-\r
-<tscreen><verb>\r
- reject/wwv by_zone 14,15,16\r
-</verb></tscreen>\r
-\r
-is probably the only useful thing to do (which will only show WWV broadcasts\r
-by stations in the US).\r
-\r
-See HELP FILTER for information.\r
-\r
-<sect1>reject/wwv (extended for sysops) (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>reject/wwv <call> [input] [0-9] <pattern></bf>\r
- WWV reject filter sysop version\r
-</tt>\r
-\r
-<P>This version allows a sysop to set a filter for a callsign as well as the\r
-default for nodes and users eg:-\r
-\r
-<tscreen><verb>\r
- reject/wwv db0sue-7 1 by_zone 4\r
- reject/wwv node_default all\r
-\r
- reject/wwv user_default by W\r
-</verb></tscreen>\r
-\r
-<sect1>reply (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>reply</bf> Reply (privately) to the last message that you have read<newline>\r
-<bf>reply <msgno></bf> Reply (privately) to the specified message<newline>\r
-<bf>reply B <msgno></bf> Reply as a Bulletin to the specified message<newline>\r
-<bf>reply NOPrivate <msgno></bf> Reply as a Bulletin to the specified\r
-message<newline>\r
-<bf>reply RR <msgno></bf> Reply to the specified message with read \r
-receipt<newline>\r
-</tt>\r
-\r
-<P>\r
-You can reply to a message and the subject will automatically have\r
-"Re:" inserted in front of it, if it isn't already present.\r
-\r
-You can also use all the extra qualifiers such as RR, PRIVATE, \r
-NOPRIVATE, B that you can use with the SEND command (see SEND\r
-for further details)\r
-\r
-<sect1>send (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>send <call> [<call> ...]</bf> Send a message to \r
-one or more callsigns<newline>\r
-<bf>send RR <call></bf> Send a message and ask for a read receipt<newline>\r
-<bf>send COPY <msgno> <call></bf> Send a copy of a message \r
-to someone<newline>\r
-<bf>send PRIVATE <call></bf> Send a personal message<newline>\r
-<bf>send NOPRIVATE <call></bf> Send a message to all stations<newline>\r
-</tt>\r
-\r
-<P>\r
-All the SEND commands will create a message which will be sent either to\r
-an individual callsign or to one of the 'bulletin' addresses. \r
-\r
-SEND <call> on its own acts as though you had typed SEND PRIVATE, that is\r
-it will mark the message as personal and send it to the cluster node that\r
-that callsign is connected to.\r
-\r
-You can have more than one callsign in all of the SEND commands.\r
-\r
-You can have multiple qualifiers so that you can have for example:-\r
-\r
-<tscreen><verb>\r
- SEND RR COPY 123 PRIVATE G1TLH G0RDI\r
-</verb></tscreen>\r
-\r
-which should send a copy of message 123 to G1TLH and G0RDI and you will\r
-receive a read receipt when they have read the message.\r
-\r
-SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)\r
-SP is an alias for SEND PRIVATE\r
-\r
-<sect1>set/address (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/address <your_address></bf> Record your postal address\r
-</tt>\r
-\r
-<P>\r
-Literally, record your address details on the cluster.\r
-\r
-<sect1>set/announce (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/announce</bf> Allow announce messages\r
-</tt>\r
-\r
-<P>\r
-Allow announce messages to arrive at your terminal.\r
-\r
-<sect1>set/arcluster (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/arcluster <node_call> [<node_call> ...]</bf> Make\r
-the node_call an AR-Cluster type node\r
-</tt>\r
-\r
-<P>\r
-Set the node_call as an AR-Cluster type node\r
-\r
-<sect1>set/baddx (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/baddx <call></bf> Stop words we do not wish to see in the callsign field\r
-of a dx spot being propagated\r
-</tt>\r
-\r
-<P>\r
-Setting a word as 'baddx' will prevent spots with that word in the callsign \r
-field of a DX spot from going any further. They will not be displayed and they \r
-will not be sent onto other nodes.\r
-\r
-The word must be wriiten in full, no wild cards are allowed eg:-\r
-\r
-<tscreen><verb>\r
- set/baddx FORSALE VIDEO FR0G \r
-</verb></tscreen>\r
-\r
-To allow a word again, use the following command ...\r
-\r
-<tscreen><verb>\r
- unset/baddx VIDEO\r
-</verb></tscreen>\r
-\r
-<sect1>set/badnode (6)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/badnode <node_call></bf> Stop spots from this node_call\r
-being propagated\r
-</tt>\r
-\r
-<P>\r
-Setting a callsign as a 'badnode' will prevent spots from that node \r
-going any further. They will not be displayed and they will not be \r
-sent onto other nodes.\r
-\r
-The call can be a full or partial call (or a prefix), eg:-\r
-\r
-<tscreen><verb>\r
- set/badnode K1TTT \r
-</verb></tscreen>\r
-\r
-will stop anything from K1TTT (including any SSID's)\r
-\r
-<tscreen><verb>\r
- unset/badnode K1TTT\r
-</verb></tscreen>\r
-\r
-will allow spots from him again.\r
-\r
-Use with extreme care. This command may well be superceded by FILTERing.\r
-\r
-<sect1>set/badspotter (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/badspotter <call></bf> Stop spots from this callsign being propagated\r
-</tt>\r
-\r
-<P>\r
-Setting a callsign as a 'badspotter' will prevent spots from this callsign \r
-going any further. They will not be displayed and they will not be \r
-sent onto other nodes.\r
-\r
-The call must be written in full, no wild cards are allowed eg:-\r
-\r
-<tscreen><verb>\r
- set/badspotter VE2STN \r
-</verb></tscreen>\r
-\r
-will stop anything from VE2STN. If you want SSIDs as well then you must\r
-enter them specifically.\r
-\r
-<tscreen><verb>\r
- unset/badspotter VE2STN\r
-</verb></tscreen>\r
-\r
-will allow spots from him again.\r
-\r
-Use with extreme care. This command may well be superceded by FILTERing.\r
-\r
-<sect1>set/badword (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/badword <word></bf> Stop things with this word being propogated\r
-</tt>\r
-\r
-<P>\r
-Setting a word as a 'badword' will prevent things like spots,\r
-announces or talks with this word in the the text part from going any\r
-further. They will not be displayed and they will not be sent onto\r
-other nodes.\r
-\r
-The word must be written in full, no wild cards are allowed eg:-\r
-\r
- set/badword annihilate annihilated annihilation \r
-\r
-will stop anything with these words in the text.\r
-\r
- unset/badword annihilated\r
-\r
-will allow text with this word again.\r
-\r
-\r
-<sect1>set/beep (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/beep</bf> Add beeps to terminal messages\r
-</tt>\r
-\r
-<P>\r
-Add a beep to DX and other terminal messages.\r
-\r
-<sect1>set/bbs (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/bbs <call> [<call>..]</bf>Make <call> a BBS\r
-</tt>\r
-\r
-<sect1>set/clx (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/clx <node_call> [<node_call> ...]</bf> Make\r
-the node_call a CLX type node\r
-</tt>\r
-\r
-<P>\r
-Set the node_call as a CLX type node\r
-\r
-<sect1>set/debug (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/debug <name></bf> Add a debug level to the debug set\r
-</tt>\r
-\r
-<P>\r
-You can choose to log several different levels. The levels are\r
-\r
-chan\r
-state\r
-msg\r
-cron\r
-connect\r
-\r
-You can show what levels you are logging with the <em>show/debug</em>\r
-command.\r
-\r
-You can remove a debug level with unset/debug <name>\r
-\r
-<sect1>set/dx (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/dx</bf>Allow DX messages to arrive at your terminal\r
-</tt>\r
-\r
-<P>\r
-You can stop DX messages with the <em>unset/dx</em> command\r
-\r
-<sect1>set/dxgrid (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/dxgrid</bf>Allow grid squares on the end of DX messages\r
-</tt>\r
-\r
-<P>\r
-Some logging programs do not like the additional information at\r
-the end of a DX spot. If this is the case, use the <em>unset/dxgrid</em>\r
-command to remove the grid squares.\r
-\r
-<sect1>set/dxnet (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/dxnet <node_call> [<node_call> ...]</bf> Make\r
-the node_call a DXNet type node\r
-</tt>\r
-\r
-<P>\r
-Set the node_call as a DXNet type node\r
-\r
-<sect1>set/echo (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/echo</bf> Make the cluster echo your input\r
-</tt>\r
-\r
-<P>\r
-If you are connected via a telnet session, different implimentations\r
-of telnet handle echo differently depending on whether you are \r
-connected via port 23 or some other port. You can use this command\r
-to change the setting appropriately. \r
-\r
-You can remove the echo with the <em>unset/echo</em> command\r
-\r
-The setting is stored in your user profile.\r
-\r
-YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.\r
-\r
-<sect1>set/email (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/email <email_address></bf> Set email address(es) and forward your personals\r
-</tt>\r
-\r
-<P>\r
-If any personal messages come in for your callsign then you can use\r
-these commands to control whether they are forwarded onto your email\r
-address. To enable the forwarding do something like:-\r
-\r
- SET/EMAIL mike.tubby@somewhere.com\r
-\r
-You can have more than one email address (each one separated by a space).\r
-Emails are forwarded to all the email addresses you specify.\r
-\r
-You can disable forwarding by:-\r
-\r
- UNSET/EMAIL\r
-\r
-<sect1>set/here (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/here</bf> Set the here flag\r
-</tt>\r
-\r
-<P>\r
-Let others on the cluster know you are here by only displaying your\r
-callsign. If you are away from your terminal you can use the <em>unset/here</em>\r
-command to let people know you are away. This simply puts brackets\r
-around your callsign to indicate you are not available.\r
-\r
-<sect1>set/homenode (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/homenode <node_call></bf> Set your home cluster\r
-</tt>\r
-\r
-<P>\r
-Tell the cluster system where you normally connect to. Any Messages sent\r
-to you will normally find their way there should you not be connected.\r
-eg:-\r
-\r
-<tscreen><verb>\r
- SET/HOMENODE gb7djk\r
-</verb></tscreen>\r
-\r
-<sect1>set/hops (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/hops <node_call> ann|spots|wwv|wcy <n></bf>\r
-Set hop count\r
-</tt>\r
-\r
-<P>\r
-Set the hop count for a particular type of broadcast for a node.\r
-\r
-This command allows you to set up special hop counts for a node \r
-for currently: announce, spots, wwv and wcy broadcasts.\r
-\r
-<tscreen><verb>\r
-eg:\r
- set/hops gb7djk ann 10\r
- set/hops gb7mbc spots 20\r
-</verb></tscreen>\r
-\r
-Set SHOW/HOPS for information on what is already set. This command\r
-creates a filter and works in conjunction with the filter system. \r
-\r
-<sect1>set/isolate (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/isolate <node call></bf> Isolate a node from the rest of the network\r
-</tt>\r
-\r
-<P>\r
-Connect a node to your system in such a way that you are a full protocol\r
-member of its network and can see all spots on it, but nothing either leaks\r
-out from it nor goes back into from the rest of the nodes connected to you.\r
-\r
-You can potentially connect several nodes in this way.\r
-\r
-You can see which nodes are isolated with the show/isolate (1) command.\r
-\r
-You can remove the isolation with the command unset/isolate.\r
-\r
-<sect1>set/language (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/language <language></bf> Set the language you wish to use\r
-</tt>\r
-\r
-<P>\r
-You can select the language that you want the cluster to use. Currently\r
-the languages available are <em>en</em> (English) and <em>nl</em> (Dutch).\r
-\r
-<sect1>set/location (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/location <lat and long></bf> Set your latitude and longitude\r
-</tt>\r
-\r
-<P>\r
-You can set your latitude and longitude manually or alternatively use the\r
-<em>set/qra</em> command which will do the conversion for you.\r
-\r
-<tscreen><verb>\r
- set/location 54 04 N 2 02 E\r
-</verb></tscreen>\r
-\r
-\r
-<sect1>set/sys_location (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/sys_location <lat & long></bf> Set your cluster latitude and longitude\r
-</tt>\r
-\r
-<P>\r
-In order to get accurate headings and such like you must tell the system\r
-what your latitude and longitude is. If you have not yet done a SET/QRA\r
-then this command will set your QRA locator for you. For example:-\r
-\r
-<tscreen><verb>\r
- SET/LOCATION 52 22 N 0 57 E\r
-</verb></tscreen>\r
-\r
-<sect1>set/logininfo (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/logininfo</bf> Show logins and logouts of nodes and users\r
-</tt>\r
-\r
-<P>\r
-Show users and nodes when they log in and out of the local cluster. You\r
-can stop these messages by using the <em>unset/logininfo</em> command.\r
-\r
-\r
-<sect1>set/lockout (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/lockout <call></bf> Stop a callsign connecting to the cluster\r
-</tt>\r
-\r
-<P>\r
-You can show who is locked out with the <em>show/lockout</em> command.\r
-To allow the user to connect again, use the <em>unset/lockout</em> command.\r
-\r
-<sect1>set/name (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/name <your_name></bf> Set your name\r
-</tt>\r
-\r
-<P>\r
-Tell the cluster what your name is, eg:-\r
-\r
-<tscreen><verb>\r
- set/name Dirk\r
-</verb></tscreen>\r
-\r
-<sect1>set/node (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/node <call> [<call> ...]</bf> Make the callsign an AK1A cluster\r
-</tt>\r
-\r
-<P>\r
-Tell the system that the call(s) are to be treated as AK1A cluster and\r
-fed PC Protocol rather normal user commands.\r
-\r
-From version 1.41 you can also set the following types of cluster\r
-\r
-<tscreen><verb>\r
- set/spider\r
- set/dxnet\r
- set/clx\r
- set/arcluster\r
-</verb></tscreen>\r
-\r
-To see what your nodes are set to, use the <em>show/nodes</em> command.\r
-\r
-<sect1>set/obscount (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/obscount <count> <node call></bf> Set the 'pump-up' \r
-obsolescence counter\r
-</tt>\r
-\r
-<P>\r
-From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see\r
-SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'\r
-counter which is decremented on every outgoing ping and then reset to\r
-the 'obscount' value on every incoming ping. The default value of this\r
-parameter is 2. \r
-\r
-What this means is that a neighbouring node will be pinged twice at \r
-(default) 300 second intervals and if no reply has been heard just before\r
-what would be the third attempt, that node is disconnected.\r
-\r
-If a ping is heard then the obscount is reset to the full value. Using\r
-default values, if a node has not responded to a ping within 15 minutes,\r
-it is disconnected.\r
-\r
-<sect1>set/page (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/page <n></bf> Set the number of lines per page\r
-</tt>\r
-\r
-<P>\r
-Tell the system how many lines you wish on a page when the number of lines\r
-of output from a command is more than this. The default is 20. Setting it\r
-explicitly to 0 will disable paging. \r
-\r
-<tscreen><verb>\r
- SET/PAGE 30\r
- SET/PAGE 0\r
-</verb></tscreen>\r
-\r
-The setting is stored in your user profile.\r
-\r
-<sect1>set/password (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/password</bf> Set your own password\r
-</tt>\r
-\r
-<P>\r
-This command only works for a 'telnet' user (currently). It will\r
-only work if you have a password already set. This initial password\r
-can only be set by the sysop.\r
-\r
-When you execute this command it will ask you for your old password,\r
-then ask you to type in your new password twice (to make sure you\r
-get it right). You may or may not see the data echoed on the screen\r
-as you type, depending on the type of telnet client you have.\r
-\r
-<sect1>set/password (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/password <callsign> <string></bf> Set a users password\r
-</tt>\r
-\r
-<P>\r
-The password for a user can only be set by a full sysop. The string\r
-can contain any characters. \r
-\r
-The way this field is used depends on context. If it is being used in\r
-the SYSOP command context then you are offered 5 random numbers and you\r
-have to supply the corresponding letters. This is now mainly for ax25\r
-connections.\r
-\r
-If it is being used on incoming telnet connections then, if a password\r
-is set or the:\r
-\r
- set/var $main::passwdreq = 1\r
-\r
-command is executed in the startup script, then a password prompt is\r
-given after the normal 'login: ' prompt. \r
-\r
-The command "unset/password" is provided to allow a sysop to remove a\r
-users password completely in case a user forgets or loses their password.\r
-\r
-<sect1>set/pinginterval (9)\r
-\r
-<P>\r
-<tt><bf>set/pinginterval <time> <node call></bf> Set the ping time \r
-to neighbouring nodes\r
-</tt>\r
-\r
-<P>\r
-As from version 1.35 all neighbouring nodes are pinged at regular intervals\r
-in order to determine the rolling quality of the link and, in future, to\r
-affect routing decisions. The default interval is 300 secs or 5 minutes.\r
-\r
-You can use this command to set a different interval. Please don't. \r
-\r
-But if you do the value you enter is treated as minutes up 60 and seconds\r
-for numbers greater than that.\r
-\r
-This is used also to help determine when a link is down at the far end\r
-(as certain cluster software doesn't always notice), see SET/OBSCOUNT\r
-for more information.\r
-\r
-<sect1>set/privilege (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/privilege <n> <call> [<call> ...]</bf> Set the \r
-privilege level on a call\r
-</tt>\r
-\r
-<P>\r
-Set the privilege level on a callsign. The privilege levels that pertain\r
-to commands are as default:-\r
-\r
-<tscreen><verb>\r
- 0 - normal user\r
- 1 - allow remote nodes normal user RCMDs\r
- 5 - various privileged commands (including shutdown, but not disc-\r
- connect), the normal level for another node.\r
- 8 - more privileged commands (including disconnect)\r
- 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS\r
- LEVEL.\r
-</verb></tscreen>\r
-\r
-If you are a sysop and you come in as a normal user on a remote connection\r
-your privilege will automatically be set to 0.\r
-\r
-<sect1>set/spider (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/spider <node_call> [<node_call> ...]</bf> Make\r
-the node_call a DXSpider type node\r
-</tt>\r
-\r
-<P>\r
-Set the node_call as a DXSpider type node\r
-\r
-<sect1>set/sys_qra (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/sys_qra <locator></bf> Set your cluster QRA locator\r
-</tt>\r
-\r
-<sect1>set/qra (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/qra <locator></bf> Set your QRA locator\r
-</tt>\r
-\r
-<P>\r
-Tell the system what your QRA (or Maidenhead) locator is. If you have not\r
-done a SET/LOCATION then your latitude and longitude will be set roughly\r
-correctly (assuming your locator is correct ;-). For example:-\r
-\r
-<tscreen><verb>\r
- SET/QRA JO02LQ\r
-</verb></tscreen>\r
-\r
-<sect1>set/qth (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/qth <your QTH></bf> Set your QTH\r
-</tt>\r
-\r
-<P>\r
-Tell the system where your are. For example:-\r
-\r
-<tscreen><verb>\r
- set/qth East Dereham, Norfolk\r
-</verb></tscreen>\r
-\r
-<sect1>set/register (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/register <call></bf> Mark a user as registered\r
-</tt>\r
-\r
-<P>\r
-Registration is a concept that you can switch on by executing the\r
-\r
- set/var $main::regreq = 1 \r
-\r
-command (usually in your startup file)\r
-\r
-If a user is NOT registered then, firstly, instead of the normal\r
-motd file (/spider/data/motd) being sent to the user at startup, the\r
-user is sent the motd_nor file instead. Secondly, the non registered\r
-user only has READ-ONLY access to the node. The non-registered user\r
-cannot use DX, ANN etc. \r
-\r
-The only exception to this is that a non-registered user can TALK or\r
-SEND messages to the sysop.\r
- \r
-To unset a user use the 'unset/register' command\r
-\r
-<sect1>set/talk (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/talk</bf> Allow talk messages to be seen at your console\r
-</tt>\r
-\r
-<P>\r
-Allow talk messages to arrive at your console. You can switch off\r
-talks with the <em>unset/talk</em> command.\r
-\r
-<sect1>set/wcy (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/wcy</bf> Allow WCY messages to be seen at your console\r
-</tt>\r
-\r
-<P>\r
-Allow WCY information to be seen at your console. You can switch off\r
-WCY messages with the <em>unset/wcy</em> command.\r
-\r
-<sect1>set/wwv (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/wwv</bf> Allow WWV messages to be seen at your console\r
-</tt>\r
-\r
-<P>\r
-Allow WWV information to be seen at your console. You can switch off\r
-WWV messages with the <em>unset/wwv</em> command.\r
-\r
-<sect1>set/wx (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>set/wx</bf> Allow WX messages to be seen at your console\r
-</tt>\r
-\r
-<P>\r
-Allow WX information to be seen at your console. You can switch off\r
-WX messages with the <em>unset/wx</em> command.\r
-\r
-<sect1>show/baddx (1)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/baddx</bf>Show all the bad dx calls in the system\r
-</tt>\r
-\r
-<P>\r
-Display all the bad dx callsigns in the system, see SET/BADDX\r
-for more information.\r
-\r
-<sect1>show/badnode (6)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/badnode</bf> Show all the bad nodes in the system\r
-</tt>\r
-\r
-<P>\r
-Display all the bad node callsigns in the system, see SET/BADNODE\r
-for more information.\r
-\r
-<sect1>show/badspotter (1)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/badspotter</bf> Show all the bad spotters in the system\r
-</tt>\r
-\r
-<P>\r
-Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER\r
-for more information.\r
-\r
-<sect1>show/badword (1)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/badword</bf> Show all the bad words in the system\r
-</tt>\r
-\r
-<P>\r
-Display all the bad words in the system, see SET/BADWORD\r
-for more information.\r
-\r
-<sect1>show/configuration (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/configuration [<node>]</bf> Show all visible nodes and their users\r
-</tt>\r
-\r
-<P>\r
-This command allows you to see all the users that can be seen\r
-and the nodes to which they are connected. With the optional <em>node</em>,\r
-you can specify a particular node to look at.\r
-\r
-This command is normally abbreviated to: sh/c\r
-\r
-BE WARNED: the list that is returned can be VERY long\r
-\r
-<sect1>show/configuration/node (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/configuration/node</bf> Show all the nodes connected\r
-</tt>\r
-\r
-<P>\r
-Show all the nodes connected locally and the nodes they have connected.\r
-\r
-<sect1>show/connect (1)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/connect</bf> Show all the active connections\r
-</tt>\r
-\r
-<P>\r
-This command shows information on all the active connections known to\r
-the node. This command gives slightly more information than WHO.\r
-\r
-<sect1>show/date (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/date [<prefix>|<callsign>]</bf> Show\r
-the local time\r
-</tt>\r
-\r
-<P>\r
-This is very nearly the same as SHOW/TIME, the only difference the format\r
-of the date string if no arguments are given.\r
-\r
-If no prefixes or callsigns are given then this command returns the local\r
-time and UTC as the computer has it right now. If you give some prefixes\r
-then it will show UTC and UTC + the local offset (not including DST) at\r
-the prefixes or callsigns that you specify.\r
-\r
-<sect1>show/debug (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/debug</bf> Show what levels of debug you are logging\r
-</tt>\r
-\r
-<P>\r
-The levels can be set with <em>set/debug</em>\r
-\r
-<sect1>show/dx (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/dx [options]</bf> interrogate the spot database\r
-</tt>\r
-\r
-<P>\r
-If you just type SHOW/DX you will get the last so many spots\r
-(sysop configurable, but usually 10).\r
- \r
-In addition you can add any number of these options in very nearly\r
-any order to the basic SHOW/DX command, they are:-\r
-\r
-<tscreen><verb> \r
-on <band> - eg 160m 20m 2m 23cm 6mm\r
-on <region> - eg hf vhf uhf shf (see SHOW/BANDS)\r
- \r
-<number> - the number of spots you want\r
-<from>-<to> - <from> spot no <to> spot no in \r
- the selected list\r
- \r
-<prefix> - for a spotted callsign beginning with <prefix>\r
-*<suffix> - for a spotted callsign ending in <suffix>\r
-*<string>* - for a spotted callsign containing <string>\r
- \r
-day <number> - starting <number> days ago\r
-day <from>-<to> - <from> days <to> days ago\r
- \r
-info <text> - any spots containing <text> in the info or remarks\r
- \r
-by <call> - any spots spotted by <call> (spotter <call> \r
- is the same).\r
-\r
-qsl - this automatically looks for any qsl info on the call\r
- held in the spot database.\r
-\r
-iota [<iota>] - If the iota island number is missing it will \r
- look for the string iota and anything which looks like \r
- an iota island number. If you specify then it will look \r
- for that island.\r
-\r
-qra [<locator>] - this will look for the specific locator if \r
- you specify one or else anything that looks like a locator.\r
-</verb></tscreen>\r
- \r
-e.g. \r
-\r
-<tscreen><verb> \r
- SH/DX 9m0\r
- SH/DX on 20m info iota\r
- SH/DX 9a on vhf day 30\r
- SH/DX rf1p qsl\r
- SH/DX iota \r
- SH/DX iota eu-064\r
- SH/DX qra jn86\r
-</verb></tscreen>\r
-\r
-<sect1>show/dxcc (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/dxcc <prefix></bf> Interrogate the spot database by country\r
-</tt>\r
-\r
-<P>\r
-This command takes the <prefix> (which can be a full or partial \r
-callsign if desired), looks up which internal country number it is\r
-and then displays all the spots as per SH/DX for that country.\r
- \r
-The options for SHOW/DX also apply to this command. \r
-e.g. \r
-\r
-<tscreen><verb> \r
- SH/DXCC G\r
- SH/DXCC W on 20m info iota\r
-</verb></tscreen>\r
-\r
-<sect1>sh/dxstats (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>sh/dxstats</bf> Show the DX Statistics for last 31 days\r
-</tt>\r
-\r
-<P>\r
-Show the total DX spots for the last 31 days\r
-\r
-\r
-<sect1>show/files (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/files [<filearea> [<string>]]</bf> List\r
-the contents of a filearea\r
-</tt>\r
-\r
-<P>\r
-SHOW/FILES on its own will show you a list of the various fileareas\r
-available on the system. To see the contents of a particular file\r
-area type:-\r
-\r
-<tscreen><verb>\r
- SH/FILES <filearea>\r
-</verb></tscreen>\r
-\r
-where <filearea> is the name of the filearea you want to see the \r
-contents of.\r
-\r
-You can also use shell globbing characters like '*' and '?' in a\r
-string to see a selection of files in a filearea eg:-\r
-\r
-<tscreen><verb>\r
- SH/FILES bulletins arld*\r
-</verb></tscreen>\r
-\r
-See also TYPE - to see the contents of a file.\r
-\r
-<sect1>show/filter (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/filter</bf> Show the filters you have set\r
-</tt>\r
-\r
-<P>\r
-Show the contents of all the filters that are set by you. This command \r
-displays all the filters set - for all the various categories.\r
-\r
-<sect1>show/filter (extended for sysops) (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/filter <callsign></bf> Show the filters set by <callsign>\r
-</tt>\r
-\r
-<P>\r
-A sysop can look at any filters that have been set.\r
-\r
-<sect1>show/hfstats (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/hfstats</bf> Show the HF DX Statistics for last 31 days\r
-</tt>\r
-\r
-<P>\r
-Show the HF DX spots breakdown by band for the last 31 days\r
-\r
-<sect1>show/hftable (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/hftable</bf> Show the HF DX Spotter Table for your country\r
-</tt>\r
-\r
-<P>\r
-Show the HF DX Spotter table for your country for the last 31 days\r
-\r
-<sect1>show/hops (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/hops <node_call> [ann|spots|wcy|wwv|]</bf> Show the hop \r
-counts for a node\r
-</tt>\r
-\r
-<P>\r
-This command shows the hop counts set up for a node. You can specify\r
-which category you want to see. If you leave the category out then \r
-all the categories will be listed.\r
-\r
-<sect1>show/isolate (1)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/isolate</bf> Show a list of isolated nodes\r
-</tt>\r
-\r
-<P>\r
-Show which nodes are currently set to be isolated.\r
-\r
-<sect1>show/lockout (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/lockout</bf> Show a list of excluded callsigns\r
-</tt>\r
-\r
-<P>\r
-Show a list of callsigns that have been excluded (locked out) of the\r
-cluster locally with the <em>set/lockout</em> command\r
-\r
-<sect1>show/log (8)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/log [<callsign>]</bf> Show excerpts from the system log\r
-</tt>\r
-\r
-<P>\r
-This command outputs a short section of the system log. On its own\r
-it will output a general logfile. With the optional callsign it will\r
-show output from the log associated with that callsign.\r
-\r
-<sect1>show/moon (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/moon [<prefix>|<callsign>]</bf> Show moon\r
-rise and set times\r
-</tt>\r
-\r
-<P>\r
-Show the Moon rise and set times for a (list of) prefixes or callsigns, \r
-together with the azimuth and elevation of the sun currently at those\r
-locations.\r
-\r
-If you don't specify any prefixes or callsigns, it will show the times for\r
-your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),\r
-together with the current azimuth and elevation.\r
-\r
-In addition, it will show the gain or loss dB relative to the nominal \r
-distance of 385,000Km due to the ellipsoidal nature of the orbit.\r
-\r
-If all else fails it will show the Moonrise and set times for the node\r
-that you are connected to. \r
-\r
-For example:-\r
-\r
-<tscreen><verb>\r
- SH/MOON\r
- SH/MOON G1TLH W5UN\r
-</verb></tscreen>\r
-\r
-<sect1>show/muf (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/muf <prefix> [<hours>][long]</bf> Show\r
-the likely propagation to <prefix>\r
-</tt>\r
-\r
-<P>\r
-This command allow you to estimate the likelihood of you contacting\r
-a station with the prefix you have specified. The output assumes a modest\r
-power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)\r
-\r
-The result predicts the most likely operating frequencies and signal\r
-levels for high frequency (shortwave) radio propagation paths on\r
-specified days of the year and hours of the day. It is most useful for\r
-paths between 250 km and 6000 km, but can be used with reduced accuracy\r
-for paths shorter or longer than this.\r
-\r
-The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and\r
-used to predict the MUF given the predicted flux, day of the year,\r
-hour of the day and geographic coordinates of the transmitter and\r
-receiver. This routine is reasonably accurate for the purposes here,\r
-with a claimed RMS error of 3.8 MHz, but much smaller and less complex\r
-than the programs used by major shortwave broadcasting organizations,\r
-such as the Voice of America.\r
-\r
-The command will display some header information detailing its\r
-assumptions, together with the locations, latitude and longitudes and\r
-bearings. It will then show UTC (UT), local time at the other end\r
-(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path\r
-(Zen) and the likely signal strengths. Then for each frequency for which\r
-the system thinks there is a likelihood of a circuit it prints a value.\r
-\r
-The value is currently a likely S meter reading based on the conventional\r
-6dB / S point scale. If the value has a '+' appended it means that it is\r
-1/2 an S point stronger. If the value is preceeded by an 'm' it means that\r
-there is likely to be much fading and by an 's' that the signal is likely\r
-to be noisy. \r
-\r
-By default SHOW/MUF will show the next two hours worth of data. You\r
-can specify anything up to 24 hours worth of data by appending the no of\r
-hours required after the prefix. For example:-\r
-\r
-<tscreen><verb>\r
- SH/MUF W\r
-</verb></tscreen>\r
-\r
-produces:\r
-\r
-<tscreen><verb>\r
- RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21\r
- Power : 20 dBW Distance: 6283 km Delay: 22.4 ms\r
- Location Lat / Long Azim\r
- East Dereham, Norfolk 52 41 N 0 57 E 47\r
- United-States-W 43 0 N 87 54 W 299\r
- UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0\r
- 18 23 11.5 -35 mS0+ mS2 S3\r
- 19 0 11.2 -41 mS0+ mS2 S3\r
-</verb></tscreen>\r
-\r
-indicating that you will have weak, fading circuits on top band and \r
-80m but usable signals on 40m (about S3).\r
-\r
-inputting:-\r
-\r
-<tscreen><verb>\r
- SH/MUF W 24\r
-</verb></tscreen>\r
-\r
-will get you the above display, but with the next 24 hours worth of\r
-propagation data.\r
-\r
-<tscreen><verb>\r
- SH/MUF W L 24\r
- SH/MUF W 24 Long\r
-</verb></tscreen>\r
-\r
-Gives you an estimate of the long path propagation characterics. It\r
-should be noted that the figures will probably not be very useful, nor\r
-terrible accurate, but it is included for completeness.\r
-\r
-<sect1>show/newconfiguration (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/newconfiguration [<node>]</bf> Show all the nodes and users visible\r
-</tt>\r
-\r
-<P>\r
-This command allows you to see all the users that can be seen\r
-and the nodes to which they are connected. \r
-\r
-This command produces essentially the same information as \r
-SHOW/CONFIGURATION except that it shows all the duplication of\r
-any routes that might be present It also uses a different format\r
-which may not take up quite as much space if you don't have any\r
-loops.\r
-\r
-BE WARNED: the list that is returned can be VERY long\r
-\r
-<sect1>show/newconfiguration/node (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/newconfiguration/node</bf> Show all the nodes connected locally\r
-</tt>\r
-\r
-<P>\r
-Show all the nodes connected to this node in the new format.\r
-\r
-<sect1>show/node (1)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/node [<node_call> ...]</bf> Show the type and version\r
-number of nodes\r
-</tt>\r
-\r
-<P>\r
-Show the type and version (if connected) of the nodes specified on the\r
-command line. If no callsigns are specified then a sorted list of all\r
-the non-user callsigns known to the system will be displayed.\r
-\r
-<sect1>show/prefix (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/prefix <callsign></bf> Interrogate the prefix database\r
-</tt>\r
-\r
-<P>\r
-This command takes the <callsign> (which can be a full or partial \r
-callsign or a prefix), looks up which internal country number \r
-it is and then displays all the relevant prefixes for that country\r
-together with the internal country no, the CQ and ITU regions. \r
-\r
-See also SHOW/DXCC\r
-\r
-\r
-<sect1>show/program (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/program</bf> Show the locations of all the included program modules\r
-</tt>\r
-\r
-<P>\r
-Show the name and location where every program module was load from. This\r
-is useful for checking where you think you have loaded a .pm file from.\r
-\r
-<sect1>show/qra (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/qra <locator> [<locator>]</bf> Show the distance\r
-between locators<newline>\r
-<bf>show/qra <lat> <long></bf> Convert latitude and longitude to \r
-a locator\r
-</tt>\r
-\r
-<P>\r
-This is a multipurpose command that allows you either to calculate the\r
-distance and bearing between two locators or (if only one locator is\r
-given on the command line) the distance and beraing from your station\r
-to the locator. For example:-\r
-\r
-<tscreen><verb>\r
-SH/QRA IO92QL \r
-SH/QRA JN06 IN73\r
-</verb></tscreen>\r
-\r
-The first example will show the distance and bearing to the locator from\r
-yourself, the second example will calculate the distance and bearing from\r
-the first locator to the second. You can use 4 or 6 character locators.\r
-\r
-It is also possible to convert a latitude and longitude to a locator by \r
-using this command with a latitude and longitude as an argument, for\r
-example:-\r
-\r
-<tscreen><verb>\r
-SH/QRA 52 41 N 0 58 E\r
-</verb></tscreen>\r
-\r
-<sect1>show/qrz (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/qrz <callsign></bf> Show any callbook details on a callsign\r
-</tt>\r
-\r
-<P>\r
-This command queries the QRZ callbook server on the internet\r
-and returns any information available for that callsign. This service\r
-is provided for users of this software by http://www.qrz.com \r
-\r
-<sect1>show/registered (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/registered [<prefix>[</bf> Show the registered users\r
-</tt>\r
-\r
-<sect1>show/route (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/route <callsign></bf> Show the route to <callsign>\r
-</tt>\r
-\r
-<P>\r
-This command allows you to see to which node the callsigns specified are\r
-connected. It is a sort of inverse sh/config.\r
-\r
-<tscreen><verb>\r
- sh/route n2tly\r
-</verb></tscreen>\r
-\r
-<sect1>show/satellite (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/satellite <name> [<hours> <interval>]</bf>\r
-Show satellite tracking data\r
-</tt>\r
-\r
-<P>\r
-Show the tracking data from your location to the satellite of your choice\r
-from now on for the next few hours.\r
-\r
-If you use this command without a satellite name it will display a list\r
-of all the satellites known currently to the system. \r
-\r
-If you give a name then you can obtain tracking data of all the passes\r
-that start and finish 5 degrees below the horizon. As default it will\r
-give information for the next three hours for every five minute period.\r
-\r
-You can alter the number of hours and the step size, within certain \r
-limits. \r
-\r
-Each pass in a period is separated with a row of '-----' characters\r
-\r
-So for example:-\r
-\r
-<tscreen><verb>\r
-SH/SAT AO-10 \r
-SH/SAT FENGYUN1 12 2\r
-</verb></tscreen>\r
-\r
-<sect1>show/sun (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/sun [<prefix>|<callsign>]</bf> Show\r
-sun rise and set times\r
-</tt>\r
-\r
-<P>\r
-Show the sun rise and set times for a (list of) prefixes or callsigns, \r
-together with the azimuth and elevation of the sun currently at those\r
-locations.\r
-\r
-If you don't specify any prefixes or callsigns, it will show the times for\r
-your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),\r
-together with the current azimuth and elevation.\r
-\r
-If all else fails it will show the sunrise and set times for the node\r
-that you are connected to. \r
-\r
-For example:-\r
-\r
-<tscreen><verb>\r
- SH/SUN\r
- SH/SUN G1TLH K9CW ZS\r
-</verb></tscreen>\r
-\r
-<sect1>show/time (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/time [<prefix>|<callsign>]</bf> Show\r
-the local time\r
-</tt>\r
-\r
-<P>\r
-If no prefixes or callsigns are given then this command returns the local\r
-time and UTC as the computer has it right now. If you give some prefixes\r
-then it will show UTC and UTC + the local offset (not including DST) at\r
-the prefixes or callsigns that you specify.\r
-\r
-<sect1>show/vhfstats (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/vhfstats</bf> Show the VHF DX Statistics for last 31 days\r
-</tt>\r
-\r
-<P>\r
-Show the VHF DX spots breakdown by band for the last 31 days\r
-\r
-<sect1>show/vhftable (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/vhftable</bf> Show the VHF DX Spotter Table for your country\r
-</tt>\r
-\r
-<P>\r
-Show the VHF DX Spotter table for your country for the last 31 days\r
-\r
-<sect1>show/wcy (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/wcy</bf> Show the last 10 WCY broadcasts<newline>\r
-<bf>show/wcy <n></bf> Show the last <n> WCY broadcasts\r
-</tt>\r
-\r
-<P>\r
-Display the most recent WCY information that has been received by the system\r
-\r
-<sect1>show/wwv (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>show/wwv</bf> Show the last 10 WWV broadcasts<newline>\r
-<bf>show/wwv <n></bf> Show the last <n> WWV broadcasts\r
-</tt>\r
-\r
-<P>\r
-Display the most recent WWV information that has been received by the system\r
-\r
-\r
-<sect1>shutdown (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>shutdown</bf> Shutdown the cluster\r
-</tt>\r
-\r
-<P>\r
-Shutdown the cluster and disconnect all the users. If you have Spider\r
-set to respawn in /etc/inittab it will of course restart.\r
-\r
-<sect1>spoof (9)\r
-\r
-<P>\r
-<tt>\r
-<bf>spoof <callsign> <command></bf> Run commands as another user\r
-</tt>\r
-\r
-<P>\r
-This is a very simple yet powerful command for the sysop. It allows you to\r
-issue commands as if you were a different user. This is very useful for the\r
-kind of things that users seem to always get wrong.. like home_node for\r
-example.\r
-\r
-<sect1>stat/db (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>stat/db <dbname></bf> Show the status of a database\r
-</tt>\r
-\r
-<P>\r
-Show the internal status of a database descriptor.\r
-\r
-Depending on your privilege level you will see more or less information. \r
-This command is unlikely to be of much use to anyone other than a sysop.\r
-\r
-<sect1>stat/channel (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>stat/channel <callsign></bf> Show the status of a channel on the cluster\r
-</tt>\r
-\r
-<P>\r
-Show the internal status of the channel object either for the channel that \r
-you are on or else for the callsign that you asked for.\r
-\r
-Only the fields that are defined (in perl term) will be displayed.\r
-\r
-<sect1>stat/msg (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>stat/msg <msgno></bf> Show the status of a message\r
-</tt>\r
-\r
-<P>\r
-This command shows the internal status of a message and includes information\r
-such as to whom it has been forwarded, its size, origin etc etc.\r
-\r
-<P>\r
-If no message number is given then the status of the message system is \r
-displayed.\r
-\r
-<sect1>stat/route_node (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>stat/route_node <callsign></bf> Show the data in a Route::Node object\r
-</tt>\r
-\r
-<sect1>stat/route_user (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>stat/route_user <callsign></bf> Show the data in a Route::User object\r
-</tt>\r
-\r
-<sect1>stat/user (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>stat/user <callsign></bf> Show the full status of a user\r
-</tt>\r
-\r
-<P>\r
-Shows the full contents of a user record including all the secret flags\r
-and stuff.\r
-\r
-Only the fields that are defined (in perl term) will be displayed.\r
-\r
-<sect1>sysop (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>sysop</bf> Regain your privileges if you login remotely\r
-</tt>\r
-\r
-<P>\r
-The system automatically reduces your privilege level to that of a\r
-normal user if you login in remotely. This command allows you to\r
-regain your normal privilege level. It uses the normal system: five\r
-numbers are returned that are indexes into the character array that is\r
-your assigned password (see SET/PASSWORD). The indexes start from\r
-zero.\r
-\r
-You are expected to return a string which contains the characters\r
-required in the correct order. You may intersperse those characters\r
-with others to obscure your reply for any watchers. For example (and\r
-these values are for explanation :-):\r
-\r
-<tscreen><verb>\r
- password = 012345678901234567890123456789\r
- > sysop\r
- 22 10 15 17 3\r
-</verb></tscreen>\r
-\r
-you type:-\r
-\r
-<tscreen><verb>\r
- aa2bbbb0ccc5ddd7xxx3n\r
- or 2 0 5 7 3\r
- or 20573\r
-</verb></tscreen>\r
-\r
-They will all match. If there is no password you will still be offered\r
-numbers but nothing will happen when you input a string. Any match is\r
-case sensitive.\r
-\r
-<sect1>talk (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>talk <callsign></bf> Enter talk mode with <callsign><newline>\r
-<bf>talk <callsign> <text></bf> Send a text message to <callsign><newline>\r
-<bf>talk <callsign> > <node_call> [<text>]</bf>\r
-Send a text message to <callsign> via <node_call>\r
-</tt>\r
-\r
-<P>\r
-Send a short message to any other station that is visible on the cluster\r
-system. You can send it to anyone you can see with a SHOW/CONFIGURATION \r
-command, they don't have to be connected locally.\r
-\r
-The second form of TALK is used when other cluster nodes are connected\r
-with restricted information. This usually means that they don't send \r
-the user information usually associated with logging on and off the cluster.\r
-\r
-If you know that G3JNB is likely to be present on GB7TLH, but you can only\r
-see GB7TLH in the SH/C list but with no users, then you would use the\r
-second form of the talk message.\r
-\r
-If you want to have a ragchew with someone you can leave the text message\r
-out and the system will go into 'Talk' mode. What this means is that a\r
-short message is sent to the recipient telling them that you are in a 'Talking' \r
-frame of mind and then you just type - everything you send will go to the \r
-station that you asked for. \r
-\r
-All the usual announcements, spots and so on will still come out on your\r
-terminal.\r
-\r
-If you want to do something (such as send a spot) you precede the normal \r
-command with a '/' character, eg:-\r
-\r
-<tscreen><verb>\r
- /DX 14001 G1TLH What's a B class licensee doing on 20m CW?\r
- /HELP talk\r
-</verb></tscreen>\r
-\r
-To leave talk mode type:\r
- \r
-<tscreen><verb>\r
- /EX\r
-</verb></tscreen>\r
-\r
-<sect1>type (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>type <filearea>/<name></bf> Look at a file in one of the fileareas\r
-</tt>\r
-\r
-<P>\r
-Type out the contents of a file in a filearea. So, for example, in \r
-filearea 'bulletins' you want to look at file 'arld051' you would \r
-enter:-\r
-\r
-<tscreen><verb>\r
- TYPE bulletins/arld051\r
-</verb></tscreen>\r
-\r
-See also SHOW/FILES to see what fileareas are available and a \r
-list of content.\r
-\r
-<sect1>who (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>who</bf> Show who is physically connected locally\r
-</tt>\r
-\r
-<P>\r
-This is a quick listing that shows which callsigns are connected and\r
-what sort of connection they have\r
-\r
-<sect1>wx (0)\r
-\r
-<P>\r
-<tt>\r
-<bf>wx <text></bf> Send a weather message to local users<newline>\r
-<bf>wx full <text> </bf> Send a weather message to all cluster users\r
-</tt>\r
-\r
-<P>\r
-Weather messages can sometimes be useful if you are experiencing an extreme\r
-that may indicate enhanced conditions\r
-\r
-<sect1>wx (enhanced for sysops) (5)\r
-\r
-<P>\r
-<tt>\r
-<bf>wx sysop <text></bf> Send a weather message to other clusters only\r
-</tt>\r
-\r
-<P>\r
-Send a weather message only to other cluster nodes and not to general users.\r
-\r
-\r
\r
-</article>\r
projects / spider.git / blobdiff