X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=41d6313b625d5ee1f3d9d4f91040cf4d5869155c;hb=61148e50735498a356ffd95b5a79faf1dc6b9d82;hp=095b7764cfa6977964bfc82873a00542fa91d1c7;hpb=d0e9787ea8e709d8cbd91e87e363812e669c0ca6;p=spider.git diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp index 095b7764..41d6313b 100644 --- a/cmd/Commands_en.hlp +++ b/cmd/Commands_en.hlp @@ -497,6 +497,39 @@ You can credit someone else by saying:- The is compared against the available bands set up in the cluster. See SHOW/BANDS for more information. +=== 0^ECHO ^Echo the line to the output +This command is useful in scripts and so forth for printing the +line that you give to the command to the output. You can use this +in user_default scripts and the SAVE command for titling and so forth + +The script will interpret certain standard "escape" sequences as follows:- + + \t - becomes a TAB character (0x09 in ascii) + \a - becomes a BEEP character (0x07 in ascii) + \n - prints a new line + +So the following example:- + + echo GB7DJK is a dxcluster + +produces:- + + GB7DJK is a dxcluster + +on the output. You don't need a \n on the end of the line you want to send. + +A more complex example:- + + echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard + +produces:- + + GB7DJK + g1tlh Dirk + g3xvf Richard + +on the output. + === 9^EXPORT ^Export a message to a file Export a message to a file. This command can only be executed on a local console with a fully privileged user. The file produced will be in a form @@ -691,16 +724,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 @@ -1028,6 +1101,48 @@ You can also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B that you can use with the SEND command (see SEND for further details) +=== 9^SAVE [-d -t -a] "" [...]^Save command output to a file +This sysop only cammand allows you to save the output of one or more +commands to a file. For example:- + + save /spider/packclus/dxstats show/dxstat + +will save the output of the normal command "show/dxstat" to the file +"dxstats" in the files area. + +You can have some extra flags to the save which will either +date stamp or time stamp or both the filename so:- + + save -d /tmp/a creates /tmp/a_6-Jan-2002 + save -t /tmp/a creates /tmp/a_2301Z + save -d -t /tmp/a creates /tmp/a_6-Jan-2002_2301Z + +The -a flag means append to the file instead of overwriting it. + +You can have more than one command on the line, to do this you MUST +enclose each command in double quotes (") eg:- + + save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats" + +or + + save /tmp/a "sh/hfstats","blank +","sh/vhfstats" + +You can only write into places that the cluster has permission for (which +is that of the "sysop" user [which had BETTER NOT BE "root"]), you will +need to create any directories you want to put stuff in beforehand as well. + +It is likely that you will want to run these commands in a crontab type +situation. You would do that something like:- + + 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"') + +Note that you still enclose each command with (") characters but you must +enclose the entire save command in (') characters. + +Now in fact, this can be varied if you know what you are doing. See the +admin manual for more details. + === 0^SEND [ ...]^Send a message to one or more callsigns === 0^SEND RR ^Send a message and ask for a read receipt === 0^SEND COPY ^Send a copy of a message to someone @@ -1038,7 +1153,9 @@ an individual callsign or to one of the 'bulletin' addresses. SEND on its own acts as though you had typed SEND PRIVATE, that is it will mark the message as personal and send it to the cluster node that -that callsign is connected to. +that callsign is connected to. If the you have specified is in fact +a known bulletin category on your node (eg: ALL) then the message should +automatically become a bulletin. You can have more than one callsign in all of the SEND commands. @@ -1052,6 +1169,51 @@ receive a read receipt when they have read the message. SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP is an alias for SEND PRIVATE +The system will ask you for a subject. Conventionally this should be +no longer than 29 characters for compatibility. Most modern cluster +software should accept more. + +You will now be prompted to start entering your text. + +You finish the message by entering '/EX' on a new line. For instance: + + ... + bye then Jim + 73 Dirk + /ex + +If you have started a message and you don't want to keep it then you +can abandon the message with '/ABORT' on a new line, like:- + + line 1 + line 2 + oh I just can't be bothered with this + /abort + +If you abort the message it will NOT be sent. + +When you are entering the text of your message, most normal output (such +as DX announcements and so on are suppressed and stored for latter display +(upto 20 such lines are stored, as new ones come along, so the oldest +lines are dropped). + +Also, you can enter normal commands commands (and get the output +immediately) whilst in the middle of a message. You do this by typing +the command preceeded by a '/' character on a new line, so:- + + /dx g1tlh 144010 strong signal + +Will issue a dx annoucement to the rest of the cluster. + +Also, you can add the output of a command to your message by preceeding +the command with '//', thus :- + + //sh/vhftable + +This will show YOU the output from SH/VHFTABLE and also store it in the +message. + +You can carry on with the message until you are ready to send it. === 0^SET/ADDRESS ^Record your postal address === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal @@ -1140,7 +1302,7 @@ The word must be written in full, no wild cards are allowed eg:- will stop anything with these words in the text. - unset/badspotter annihilated + unset/badword annihilated will allow text with this word again. @@ -1166,8 +1328,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 @@ -1187,6 +1349,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 @@ -1197,6 +1374,7 @@ eg:- SET/HOMENODE gb7djk === 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 @@ -1209,6 +1387,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 @@ -1221,7 +1405,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 @@ -1323,16 +1508,53 @@ SYSOP command. === 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. + +=== 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^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:- @@ -1342,6 +1564,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 @@ -1405,9 +1644,12 @@ any order to the basic SHOW/DX command, they are:- on - eg 160m 20m 2m 23cm 6mm on - eg hf vhf uhf shf (see SHOW/BANDS) +on / - eg 1000/4000 14000-30000 (in Khz) + - - the number of spots you want - - spot no spot no in the selected list +/ - for a spotted callsign beginning with * - for a spotted callsign ending in @@ -1415,7 +1657,8 @@ on - eg hf vhf uhf shf (see SHOW/BANDS) day - starting days ago day - - days days ago - + / + info - any spots containing in the info or remarks by - any spots spotted by (spotter is the @@ -1431,6 +1674,13 @@ iota [] - If the iota island number is missing it will look for qra [] - this will look for the specific locator if you specify one or else anything that looks like a locator. + +dxcc - treat the prefix as a 'country' and look for spots + from that country regardless of actual prefix. + eg dxcc oq2 + + You can also use this with the 'by' keyword so + eg by W dxcc e.g. @@ -1441,17 +1691,26 @@ e.g. SH/DX iota SH/DX iota eu-064 SH/DX qra jn86 + SH/DX dxcc oq2 + SH/DX dxcc oq2 by w dxcc === 0^SHOW/DXCC ^Interrogate the spot database by country This command takes the (which can be a full or partial callsign if desired), looks up which internal country number it is and then displays all the spots as per SH/DX for that country. + +This is now an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this command. e.g. SH/DXCC G - SH/DXCC W on 20m info iota + SH/DXCC W on 20m iota + +This can be done with the SHOW/DX command like this:- + + SH/DX dxcc g + SH/DX dxcc w on 20m iota === 0^SHOW/DXSTATS^Show the DX Statistics for last 31 days Show the total DX spots for the last 31 days @@ -1487,7 +1746,7 @@ 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 @@ -1514,6 +1773,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 @@ -1612,8 +1880,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 @@ -1637,6 +1905,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. @@ -1673,7 +1943,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. @@ -1690,6 +1960,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 @@ -1813,6 +2092,15 @@ To leave talk mode type: /EX +If you are in 'Talk' mode, there is an extention to the '/' command which +allows you to send the output to all the people you are talking to. You do +with the '//' command. For example:- + + //sh/hftable + +will send the hftable as you have it to all the people you are currently +talking to. + === 0^TYPE /^Look at the contents of a file in one of the fileareas Type out the contents of a file in a filearea. So, for example, in filearea 'bulletins' you want to look at file 'arld051' you would