X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=244688d99efea04bbac4ee37b8ad654d5f96c872;hb=refs%2Fheads%2Fmaster;hp=86e22d4c672c84f3a60919a045f017efa96bd9bd;hpb=963ead7224e53e257c7c661683174a75c2935cda;p=spider.git diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp index 86e22d4c..244688d9 100644 --- a/cmd/Commands_en.hlp +++ b/cmd/Commands_en.hlp @@ -500,8 +500,23 @@ You also use one of these databases in a chain. This may be useful locally. See DBIMPORT for the importing of existing AK1A format data to databases. +See DXEXPORT for how to export an AK1A data in a form able to be imported. See DBSHOW for generic database enquiry - + + +=== 9^DBEXPORT ^Export an AK1A data to a file +Sometimes one needs to export the data from an existing database file, +maybe for a backup or to send to another node. + + DBEXPORT oblast /tmp/OBLAST.FUL + +will export the OBLAST database to /tmp/OBLAST.FUL + +There is no protection, it is up to you not to overwrite a file that +is important to you. + +See DBIMPORT for the importing of existing AK1A format data to databases. + === 9^DBIMPORT ^Import AK1A data into a database If you want to import or update data in bulk to a database you can use this command. It will either create or update entries into an existing @@ -512,6 +527,8 @@ database. For example:- will import the standard OBLAST database that comes with AK1A into the oblast database held locally. +See DBEXPORT for how to export an AK1A database + === 9^DBREMOVE ^Delete a database DBREMOVE will completely remove a database entry and also delete any data file that is associated with it. @@ -618,6 +635,41 @@ 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. +=== 9^DXQSL_EXPORT ^Export SH/DXSQL information to a file +The SHOW/DXQSL command shows any QSL managers that have been extracted +from comments on a DX spot. + +Use this command to export the current state of the information to +a CSV style text file. For example: + + DXQSL_EXPORT /tmp/qsl.csv + +NOTE: this command will overwrite any file that you have write +permission for. + +See also DXQSL_IMPORT to import one of these files. + +=== 9^DXQSL_IMPORT ^Import SH/DXSQL information from a file +The SHOW/DXQSL command shows any QSL managers that have been extracted +from comments on a DX spot. + +Use this command to restore a file created by the DXSQL_EXPORT command. +For example: + + DXQSL_IMPORT /tmp/qsl.csv + +The data in this file will UPDATE any information that may already be +present. This may not be what you want. To make the data the same as +the import file then you must: + +* stop the node +* remove /spider/data/qsl.v1 +* restart the node +* login as sysop +* do the import + +Preferably before too many DX spots with qsl manager info come in. + === 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 @@ -825,6 +877,21 @@ This command sends out any information held in the user file which can be broadcast in PC41 protocol packets. This information is Name, QTH, Location and Homenode. PC41s are only sent for the information that is available. +=== 8^GET/KEPS^Obtain the latest AMSAT Keplarian Elements from the web +There are various ways that one can obtain the AMSAT keps. Traditionally the +regular method was to get on the mailing list and then arrange for the email +to be piped into convkeps.pl and arrange from the crontab to run LOAD/KEPS. +For various reasons, it was quite easy for one to be silently dropped +from this mailing list. + +With the advent of asynchronous (web) connections in DXSpider it is now +possible to use this command to get the latest keps direct from the +AMSAT web site. One can do this from the command line or one can add a line +in the local DXSpider crontab file to do periodically (say once a week). + +This command will clear out the existing keps and then run LOAD/KEPS +for you (but only) after a successful download from the AMSAT website. + === 0^HELP^The HELP Command HELP is available for a number of commands. The syntax is:- @@ -1986,13 +2053,20 @@ Show all the nodes connected to this node. This command shows information on all the active connections known to the node. This command gives slightly more information than WHO. -=== 0^SHOW/CONTEST ^Show all the contests for a month +=== 0^SHOW/CONTEST [] []^Show all the contests for a month Show all known contests which are maintained at http://www.sk3bg.se/contest/ for a particular month or year. The format is reasonably flexible. For example:- - SH/CONTEST sep2003 - SH/CONTEST 03 march + SH/CONTEST + SH/CONTEST mar + SH/CONTEST mar 13 + SH/CONTEST 13 march + +If there is no month/year then the current month's contests are shown. + +Note that it expects ENGLISH (jan/feb/mar/apr/may/jun/jul/aug/sep/oct/nov/dec) +month names. === 0^SHOW/DATE [|]^Show the local time This is very nearly the same as SHOW/TIME, the only difference the format @@ -2086,6 +2160,12 @@ any order to the basic SHOW/DX command, they are:- by_state - look for spots spotted by people in the US state specified. + + origin - the node from which this spot originated (must be an + exact callsign with SSID e.g. gb7tlh-4) + + ip - the IP address of the spotter (either in IPV4 or IPV6) + format. These addresses can be partial. e.g. @@ -2103,6 +2183,8 @@ any order to the basic SHOW/DX command, they are:- SH/DX state in,oh SH/DX by_state in,oh SH/DX hb2008g exact + SH/DX origin gb7tlh-4 + SH/DX ip 82.65.128.4 (or SH/DX ip 2a00:1450:4009:800::200e) === 0^SHOW/DXCC ^Interrogate the spot database by country This command takes the (which can be a full or partial @@ -2278,6 +2360,16 @@ Upto 366 days can be checked both in the past and in the future. Please note that the rise and set times are given as the UT times of rise and set on the requested UT day. +=== 0^SHOW/MOTD^Show your MOTD (the Message of the Day) +The Message of the Day is normally printed whenever one logs on. However +many people now login using logging programs or something other than plain +telnet or ax25 connections. This command allows the user (or the program) +to see what is in the MOTD. + +The actual MOTD that you are shown depends on what carrier you are logged +on via, whether you are registered and some other factors that your sysop +may have thrown in. + === 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