X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=b9d59a9a623f3d610a0cc1af8de9e0495ce0ad0b;hb=f0323dc530e2aa3fe5b8cd50b1c8c35aac67c52e;hp=bf86e53552b422b52d3268e22ba324851bb25401;hpb=6ccc3a6e864a2fee18786a7070400c7c4f22cf7c;p=spider.git diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp index bf86e535..b9d59a9a 100644 --- a/cmd/Commands_en.hlp +++ b/cmd/Commands_en.hlp @@ -207,6 +207,26 @@ This will send your announcement cluster wide Search the help database for (it isn't case sensitive), and print the names of all the commands that may be relevant. +=== 0^BLANK [] []^Print nn (default 1) blank lines (or strings) +In its basic form this command prints one or more blank lines. However if +you pass it a string it will replicate the string for the width of the +screen (default 80) and then print that one or more times, so: + + blank 2 + +prints two blank lines + + blank - + +prints a row of - characters once. + + blank abc + +prints 'abcabcabcabcabcabc....' + +This is really only of any use in a script file and you can print a maximum +of 9 lines. + === 0^BYE^Exit from the cluster This will disconnect you from the cluster @@ -671,16 +691,42 @@ node>). Best of luck - you will need it. === 0^KILL [-^Delete a range of messages +=== 0^KILL from ^Delete messages FROM a callsign or pattern +=== 0^KILL to ^Delete messages TO a callsign or pattern +=== 5^KILL FULL [ [ [ + +on a file containing NASA 2 line keps as a message issued by AMSAT. + +If there is a message number, then it will take the message, run +convkeps.pl on it and then load the data, all in one step. + +These messages are sent to ALL by GB7DJK (and others) from time to time. + === 9^LOAD/MESSAGES^Reload the system messages file If you change the /spider/perl/Messages file (usually whilst fiddling/writing new commands) you can have them take effect during a @@ -1037,16 +1097,31 @@ SP is an alias for SEND PRIVATE === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal +=== 0^SET/ANNTALK^Allow talk like announce messages on your terminal +=== 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal +The announce system on legacy cluster nodes is used as a talk +substitute because the network is so poorly connected. If you: + + unset/anntalk + +you will suppress several of these announces, you may miss the odd +useful one as well, but you would probably miss them anyway in the +welter of useless ones. + + set/anntalk + +allows you to see them again. This is the default. + === 5^SET/ARCLUSTER [..]^Make the callsign an AR-Cluster node -=== 8^SET/BADDX ..^Stop words we do not wish to see in the callsign field -of a dx spot being propagated -=== 8^UNSET/BADDX ..^Allow a word to be seen again in a DX spot -Setting a word as 'baddx' will prevent spots with that word in the -callsign field of a DX spot from going any further. They will not be -displayed and they will not be sent onto other nodes. +=== 8^SET/BADDX ..^Stop callsigns in a dx spot being propagated +=== 8^UNSET/BADDX ..^Propagate a dx spot with this callsign again +Setting a word as 'baddx' will prevent spots with that word in the +'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any +further. They will not be displayed and they will not be sent onto +other nodes. -The word must be wriiten in full, no wild cards are allowed eg:- +The word must be written in full, no wild cards are allowed eg:- set/baddx FORSALE VIDEO FR0G @@ -1092,6 +1167,23 @@ will allow spots from him again. Use with extreme care. This command may well be superceded by FILTERing. +=== 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, +announces or talks with this word in the the text part from going any +further. They will not be displayed and they will not be sent onto +other nodes. + +The word must be written in full, no wild cards are allowed eg:- + + set/badword annihilate annihilated annihilation + +will stop anything with these words in the text. + + unset/badword annihilated + +will allow text with this word again. + === 0^SET/BEEP^Add a beep to DX and other messages on your terminal === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal @@ -1114,8 +1206,8 @@ You can show what levels you are logging with SHOW/DEBUG === 0^SET/DX^Allow DX messages to come out on your terminal === 0^UNSET/DX^Stop DX messages coming out on your terminal -=== 0^SET/DXGRID^Allow Grid Squares on the end of DX announcements -=== 0^UNSET/DXGRID^Stop Grid Squares on the end of DX announcements +=== 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements +=== 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements A standard feature which is enabled in version 1.43 and above is that if the spotter's grid square is known it is output on the end of a DX announcement (there is just enough room). Some user programs @@ -1135,6 +1227,21 @@ The setting is stored in your user profile. YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25. +=== 0^SET/EMAIL ...^Set email address(es) and forward your personals +=== 0^UNSET/EMAIL^Stop personal msgs being forwarded by email +If any personal messages come in for your callsign then you can use +these commands to control whether they are forwarded onto your email +address. To enable the forwarding do something like:- + + SET/EMAIL mike.tubby@somewhere.com + +You can have more than one email address (each one separated by a space). +Emails are forwarded to all the email addresses you specify. + +You can disable forwarding by:- + + UNSET/EMAIL + === 0^SET/HERE^Tell the system you are present at your terminal === 0^UNSET/HERE^Tell the system you are absent from your terminal @@ -1144,7 +1251,8 @@ to you will normally find their way there should you not be connected. eg:- SET/HOMENODE gb7djk -=== 8^SET/HOPS ann|spots|wwv|wcy ^Set hop count +=== 8^SET/HOPS ann|spots|route|wwv|wcy ^Set hop count +=== 8^UNSET/HOPS ann|spots|route|wwv|wcy^Unset hop count Set the hop count for a particular type of broadcast for a node. This command allows you to set up special hop counts for a node @@ -1157,6 +1265,12 @@ eg: Set SHOW/HOPS for information on what is already set. This command creates a filter and works in conjunction with the filter system. +You can unset the hops with command UNSET/HOPS. For example:- + + unset/hops gb7djk ann + unset/hops gb7mbc spots + + === 9^SET/ISOLATE^Isolate a node from the rest of the network Connect a node to your system in such a way that you are a full protocol member of its network and can see all spots on it, but nothing either leaks @@ -1169,7 +1283,8 @@ Remove isolation from a node - SET/ISOLATE === 0^SET/LANGUAGE ^Set the language you want to use You can select the language that you want the cluster to use. Currently -the languages available are en (english) and nl (dutch). +the languages available are en (English), de (German), es (Spanish) +and nl (Dutch). === 0^SET/LOCATION ^Set your latitude and longitude === 9^SET/SYS_LOCATION ^Set your cluster latitude and longitude @@ -1269,18 +1384,55 @@ use. If you want to get your normal privilege back you will need to either logout and login again (if you are on a console) or use the SYSOP command. +=== 0^SET/PASSWORD^Set your own password +This command only works for a 'telnet' user (currently). It will +only work if you have a password already set. This initial password +can only be set by the sysop. + +When you execute this command it will ask you for your old password, +then ask you to type in your new password twice (to make sure you +get it right). You may or may not see the data echoed on the screen +as you type, depending on the type of telnet client you have. + === 9^SET/PASSWORD ^Set a users password The password for a user can only be set by a full sysop. The string -can contain any characters but any spaces are removed (you can type in -spaces - but they won't appear in the password). You can see the -result with STAT/USER. +can contain any characters. + +The way this field is used depends on context. If it is being used in +the SYSOP command context then you are offered 5 random numbers and you +have to supply the corresponding letters. This is now mainly for ax25 +connections. + +If it is being used on incoming telnet connections then, if a password +is set or the: + + set/var $main::passwdreq = 1 + +command is executed in the startup script, then a password prompt is +given after the normal 'login: ' prompt. + +=== 9^UNSET/PASSWORD ...^Delete (remove) a user's password +This command allows the sysop to completely delete and remove a +password for a user. + +=== 0^SET/PROMPT ^Set your prompt to +=== 0^UNSET/PROMPT^Set your prompt back to default +This command will set your user prompt to exactly the string that you +say. The point of this command to enable a user to interface to programs +that are looking for a specific prompt (or else you just want a different +fixed prompt). + + SET/PROMPT clx > + +UNSET/PROMPT will undo the SET/PROMPT command and set you 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 locator -=== 0^SET/QRA ^Set your QRA locator +=== 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 done a SET/LOCATION then your latitude and longitude will be set roughly correctly (assuming your locator is correct ;-). For example:- @@ -1290,6 +1442,23 @@ correctly (assuming your locator is correct ;-). For example:- Tell the system where you are. For example:- SET/QTH East Dereham, Norfolk +=== 9^SET/REGISTER ...^Mark a user as registered +=== 9^UNSET/REGISTER ...^Mark a user as not registered +Registration is a concept that you can switch on by executing the + + set/var $main::regreq = 1 + +command (usually in your startup file) + +If a user is NOT registered then, firstly, instead of the normal +motd file (/spider/data/motd) being sent to the user at startup, the +user is sent the motd_nor file instead. Secondly, the non registered +user only has READ-ONLY access to the node. The non-registered user +cannot use DX, ANN etc. + +The only exception to this is that a non-registered user can TALK or +SEND messages to the sysop. + === 0^SET/TALK^Allow TALK messages to come out on your terminal === 0^UNSET/TALK^Stop TALK messages coming out on your terminal @@ -1314,6 +1483,10 @@ for more information. Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER for more information. +=== 1^SHOW/BADWORD^Show all the bad words in the system +Display all the bad words in the system, see SET/BADWORD +for more information. + === 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. @@ -1424,14 +1597,14 @@ Show the HF DX spots breakdown by band for the last 31 days === 0^SHOW/HFTABLE^Show the HF DX Spotter Table for your country Show the HF DX Spotter table for your country for the last 31 days -=== 8^SHOW/HOPS [ann|spots|wcy|wwv]^Show the hop counts for a node +=== 8^SHOW/HOPS [ann|spots|route|wcy|wwv]^Show the hop counts for a node This command shows the hop counts set up for a node. You can specify which category you want to see. If you leave the category out then all the categories will be listed. === 1^SHOW/ISOLATE^Show list of ISOLATED nodes -=== 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns +=== 9^SHOW/LOCKOUT |ALL^Show the list of locked out or excluded callsigns === 8^SHOW/LOG []^Show excerpts from the system log This command outputs a short section of the system log. On its own @@ -1458,6 +1631,15 @@ For example:- SH/MOON SH/MOON 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/MOON -1 + +or in three days time:- + + SH/MOON +3 W9 + === 0^SHOW/MUF [][long]^Show the likely propagation to a prefix This command allow you to estimate the likelihood of you contacting a station with the prefix you have specified. The output assumes a modest @@ -1524,6 +1706,21 @@ Gives you an estimate of the long path propagation characterics. It should be noted that the figures will probably not be very useful, nor terrible accurate, but it is included for completeness. +=== 0^SHOW/NEWCONFIGURATION []^Show all the nodes and users visible +This command allows you to see all the users that can be seen +and the nodes to which they are connected. + +This command produces essentially the same information as +SHOW/CONFIGURATION except that it shows all the duplication of +any routes that might be present It also uses a different format +which may not take up quite as much space if you don't have any +loops. + +BE WARNED: the list that is returned can be VERY long + +=== 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally +Show all the nodes connected to this node in the new format. + === 1^SHOW/NODE [ ...]^Show the type and version number of nodes Show the type and version (if connected) of the nodes specified on the command line. If no callsigns are specified then a sorted list of all @@ -1541,8 +1738,8 @@ See also SHOW/DXCC Show the name and location where every program module was load from. This is useful for checking where you think you have loaded a .pm file from. -=== 0^SHOW/QRA []^Show distance between locators -=== 0^SHOW/QRA ^Convert latitude and longitude to a locator +=== 0^SHOW/QRA []^Show distance between QRA Grid locators +=== 0^SHOW/QRA ^Convert lat/long to a QRA Grid locator This is a multipurpose command that allows you either to calculate the distance and bearing between two locators or (if only one locator is given on the command line) the distance and beraing from your station @@ -1566,6 +1763,8 @@ This command queries the QRZ callbook server on the internet and returns any information available for that callsign. This service is provided for users of this software by http://www.qrz.com +=== 9^SHOW/REGISTERED []^Show the registered users + === 0^SHOW/ROUTE ...^Show the route to the callsign This command allows you to see to which node the callsigns specified are connected. It is a sort of inverse sh/config. @@ -1602,7 +1801,7 @@ that callsign is connected to the cluster. If no callsign is given then show the information for yourself. -=== 0^SHOW/SUN [|]^Show sun rise and set times +=== 0^SHOW/SUN [+/- days][|]^Show sun rise and set times Show the sun rise and set times for a (list of) prefixes or callsigns, together with the azimuth and elevation of the sun currently at those locations. @@ -1619,6 +1818,15 @@ For example:- SH/SUN SH/SUN G1TLH K9CW ZS +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/SUN -1 + +or in three days time:- + + SH/SUN +3 W9 + === 0^SHOW/TIME [|]^Show the local time If no prefixes or callsigns are given then this command returns the local time and UTC as the computer has it right now. If you give some prefixes