X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=30c6aea54b06d84bedcc233c2f32bb7e94ed879e;hb=refs%2Fheads%2Fnewpc92timings;hp=eaa862ef50483d01cdd7fd7de4dc55b2b995b5e4;hpb=aad4e36d3753bf8dde671d14d73b1d9785b9ff41;p=spider.git diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp index eaa862ef..30c6aea5 100644 --- a/cmd/Commands_en.hlp +++ b/cmd/Commands_en.hlp @@ -9,6 +9,8 @@ # if the command ends in a - then that line isn't printed, but any # subsequent lines are # +# +# # Comment lines are indented before printing # === 0^ACCEPT^Set a filter to accept something @@ -326,6 +328,21 @@ 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. +=== 6^CLEAR/DUPEFILE^Clear out the dupefile completely +The system maintains a list of duplicate announces and spots (amongst many +other things). Sometimes this file gets corrupted during operation +(although not very often). This command will remove the file and start +again from scratch. + +Try this if you get several duplicate DX Spots, one after another. + +Please ONLY use this command if you have a problem. And then only once. +If it does not cure your problem, then repeating the command won't help. +Get onto the dxspider-support list and let us try to help. + +If you use this command frequently then you will cause other people, as +well as yourself, a lot of problems with duplicates. + === 0^CLEAR/ROUTE [1|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. @@ -913,7 +930,8 @@ 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. +was just after a cluster restart. To see what is in the command cache +see SHOW/CMD_CACHE. === 9^LOAD/FORWARD^Reload the msg forwarding routing table Reload the /spider/msg/forward.pl file if you have changed it @@ -1427,6 +1445,9 @@ will allow spots from him again. Use with extreme care. This command may well be superceded by FILTERing. +This command will also stop TALK and ANNOUNCE/FULL from any user marked +as a BADSPOTTER. + === 8^SET/BADWORD ..^Stop things with this word being propagated === 8^UNSET/BADWORD ..^Propagate things with this word again Setting a word as a 'badword' will prevent things like spots, @@ -1449,6 +1470,12 @@ will allow text with this word again. === 5^SET/BBS [..]^Make the callsign a BBS +=== 0^SET/BUDDY [..]^Add this call to my buddy list +=== 0^UNSET/BUDDY [..]^Remove this call from my buddy list +A notification message +is sent to you automatically if anybody on your buddy list logs in or +out of any node in this cluster. + === 5^SET/CLX [..]^Make the callsign an CLX node === 9^SET/DEBUG ^Add a debug level to the debug set @@ -1572,6 +1599,21 @@ You can select the language that you want the cluster to use. Currently the languages available are en (English), de (German), es (Spanish), Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch). +=== 5^SET/LOCAL_NODE^Add node to the local_node group +=== 5^UNSET/LOCAL_NODE^Remove node from the local_node group +The 'local_node' group is a group of nodes that you want a user +to perceive as effectively one big node. At the moment, this extends +only to announcing whenever a user is logging in or out of one of +the nodes in the group (if those users have SET/LOGININFO). + +The local node group is as setup on this node. If you want the other +nodes to also include this node and all the other nodes specified, then +you must get those nodes to also run this command (or rcmd them to do +so). + +In principle, therefore, each node determines its own local node group +and these can overlap with other nodes' views. + === 0^SET/LOCATION ^Set your latitude and longitude === 9^SET/SYS_LOCATION ^Set your cluster latitude and longitude In order to get accurate headings and such like you must tell the system @@ -1579,8 +1621,8 @@ 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 -=== 0^SET/LOGININFO^Inform when a station logs in locally -=== 0^UNSET/LOGININFO^Inform when a station logs out locally +=== 0^SET/LOGININFO^Inform when a station logs in/out locally +=== 0^UNSET/LOGININFO^No longer inform when a station logs in/out locally === 9^SET/LOCKOUT ^Stop a callsign connecting to the cluster === 9^UNSET/LOCKOUT ^Allow a callsign to connect to the cluster @@ -1724,10 +1766,6 @@ The standard prompt is defined as: UNSET/PROMPT will undo the SET/PROMPT command and set your prompt back to normal. -=== 5^SET/SPIDER [..]^Make the callsign an DXSpider node -Tell the system that the call(s) are to be treated as DXSpider node and -fed new style DX Protocol rather normal user commands. - === 9^SET/SYS_QRA ^Set your cluster QRA Grid locator === 0^SET/QRA ^Set your QRA Grid locator Tell the system what your QRA (or Maidenhead) locator is. If you have not @@ -1755,7 +1793,29 @@ cannot use DX, ANN etc. The only exception to this is that a non-registered user can TALK or SEND messages to the sysop. - + +=== 6^SET/STARTUP ^Create a user startup script +=== 0^SET/STARTUP^Create your own startup script +Create a startup script of DXSpider commands which will be executed +everytime that you login into this node. You can only input the whole +script afresh, it is not possible to 'edit' it. Inputting a new script is +just like typing in a message using SEND. To finish inputting type: /EX +on a newline, to abandon the script type: /ABORT. + +You may find the (curiously named) command BLANK useful to break +up the output. If you simply want a blank line, it is easier to +input one or more spaces and press the key. + +See UNSET/STARTUP to remove a script. + +=== 6^UNSET/STARTUP ^Remove a user startup script +=== 0^UNSET/STARTUP^Remove your own startup script +You can remove your startup script with UNSET/STARTUP. + +=== 5^SET/SPIDER [..]^Make the callsign an DXSpider node +Tell the system that the call(s) are to be treated as DXSpider node and +fed new style DX Protocol rather normal user commands. + === 0^SET/TALK^Allow TALK messages to come out on your terminal === 0^UNSET/TALK^Stop TALK messages coming out on your terminal @@ -1810,12 +1870,43 @@ for more information. Display all the bad words in the system, see SET/BADWORD for more information. +=== 0^SHOW/BANDS [band|region names]^Show the list of bands and regions +Display the bands and regions (collections of bands) known to +the system. If you supply band or region names to SHOW/BANDS, +the command will display just those bands or regions, e.g.: + + sh/band + sh/band 2m hf + +=== 0^SHOW/BUDDY^Show your list of buddies +See SET/BUDDY for more information about buddies. + === 0^SHOW/CHAT [] []^Show any chat or conferencing This command allows you to see any chat or conferencing that has occurred whilst you were away. SHOW/CHAT on its own will show data for all groups. If you use a group name then it will show only chat for that group. +=== 9^SHOW/CMD_CACHE [pattern]^Show the real source path of commands +It is possible in DXSpider to define local versions of commands. +Sometimes one forgets that one has these. This command will show you +the source path where the node is getting each one of its commands. + +If you find a local command that you don't want then then simply +delete it, run LOAD/CMD_CACHE to clear out the command cache and +try again. You will now be using the standard version. + +If you are looking for information on a specific command then +just add a string, eg: + + sh/cmd dx + +might give you: + + Command Path + set/dxgrid /spider/cmd/set/dxgrid.pl + sh/dx /spider/cmd/show/dx.pl + === 0^SHOW/CONFIGURATION []^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. @@ -2012,6 +2103,37 @@ See also TYPE - to see the contents of a file. Show the contents of all the filters that are set. This command displays all the filters set - for all the various categories. +=== 0^SHOW/GRAYLINE [ndays] [|]^Show Civil dawn/dusk times +This command is very similar to SHOW/SUN except that it shows the +start and end of "Official" or "Civil" Dawn and Dusk. This is defined +as when the Sun is 6 degrees below the horizon. + +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 civil dawn and dusk times for +the node that you are connected to. + +For example:- + + SH/GRAYLINE + SH/GRAYLINE G1TLH W5UN + +You can also use this command to see into the past or the future, so +if you want to see yesterday's times then do:- + + SH/GRAYLINE -1 + +or in three days time:- + + SH/GRAYLINE +3 W9 + +Upto 366 days can be checked both in the past and in the future. + +Please note that the times are given as the UT times of the requested +UT day. + === 0^SHOW/HFSTATS [days] [date]^Show the HF DX Statistics Show the HF DX spots breakdown by band for the last no of days (default is 31), starting from a (default: today). @@ -2285,6 +2407,10 @@ So for example:- SH/SAT AO-10 SH/SAT FENGYUN1 12 2 +=== 6^SHOW/STARTUP ^View a user startup script +=== 0^SHOW/STARTUP^View your own startup script +View the contents of a startup script created with SET/STARTUP. + === 6^SHOW/STATION ALL []^Show list of users in the system === 0^SHOW/STATION [ ..]^Show information about a callsign Show the information known about a callsign and whether (and where)