From db143ea6ee006dd7ffc360fcf022459d68412976 Mon Sep 17 00:00:00 2001 From: g0vgs Date: Fri, 26 Jan 2001 20:13:20 +0000 Subject: [PATCH] Add information on updating kepler data to manual --- html/adminmanual-1.html | 2 +- html/adminmanual-9.html | 36 +++++ html/adminmanual.html | 1 + sgml/adminmanual.sgml | 36 ++++- txt/adminmanual.txt | 338 ++++++++++++++++++++++++---------------- 5 files changed, 275 insertions(+), 138 deletions(-) diff --git a/html/adminmanual-1.html b/html/adminmanual-1.html index a6d6da64..bb9dff66 100644 --- a/html/adminmanual-1.html +++ b/html/adminmanual-1.html @@ -15,7 +15,7 @@ Previous

1. Installation (Original version by Iain Phillips, G0RDI)

-

Last modified: 24 January 2001 by Ian Maude, G0VGS +

Last modified: 26 January 2001 by Ian Maude, G0VGS

1.1 Introduction

diff --git a/html/adminmanual-9.html b/html/adminmanual-9.html index 6f0d0ef6..a002c013 100644 --- a/html/adminmanual-9.html +++ b/html/adminmanual-9.html @@ -394,6 +394,42 @@ the interface is one-way. Make sure you only send mail to the clusters that want it by using the Forward.pl file very carefully.

+

9.9 Updating kepler data +

+ +

Spider has a powerful and flexible show/satellite command. In order for +this to be accurate, the kepler data has to be updated regularly. In +general, this data is available as an email or via cluster mail. +Updating it is simple. First you need to export the mail message as a +file. You do this with the export command from the cluster prompt +as the sysop. For example ... +

+

+
+export 5467 /spider/perl/keps.in
+
+
+

would export message number 5467 as a file called keps.in in the +/spider/perl directory. +

Now login to a VT as sysop and cd /spider/perl. There is a command in +the perl directory called convkeps.pl. All we need to do now is +convert the file like so ... +

+

+
+./convkeps.pl keps.in
+
+
+

Now go back to the cluster and issue the command ... +

+

+
+load/keps
+
+
+

That is it! the kepler data has been updated. +

+

Next Previous diff --git a/html/adminmanual.html b/html/adminmanual.html index 66ff522c..b7446d2f 100644 --- a/html/adminmanual.html +++ b/html/adminmanual.html @@ -95,6 +95,7 @@ Contents
  • 9.6 Distribution lists
  • 9.7 Console.pl
  • 9.8 BBS interface +
  • 9.9 Updating kepler data

    10. CVS

    diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index d66afd9a..07c72386 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -19,7 +19,7 @@ A reference for SysOps of the DXSpider DXCluster program. Installation (Original version by Iain Phillips, G0RDI)

    -Last modified: 24 January 2001 by Ian Maude, G0VGS +Last modified: 26 January 2001 by Ian Maude, G0VGS Introduction @@ -1687,6 +1687,40 @@ Please be careful not to flood the cluster network with unnecessary mail. Make sure you only send mail to the clusters that want it by using the Forward.pl file very carefully. +Updating kepler data + +

    +Spider has a powerful and flexible show/satellite command. In order for +this to be accurate, the kepler data has to be updated regularly. In +general, this data is available as an email or via cluster mail. +Updating it is simple. First you need to export the mail message as a +file. You do this with the export command from the cluster prompt +as the sysop. For example ... + + +export 5467 /spider/perl/keps.in + + +would export message number 5467 as a file called keps.in in the +/spider/perl directory. + +Now login to a VT as sysop and cd /spider/perl. There is a command in +the perl directory called convkeps.pl. All we need to do now is +convert the file like so ... + + +./convkeps.pl keps.in + + +Now go back to the cluster and issue the command ... + + +load/keps + + +That is it! the kepler data has been updated. + + CVS

    diff --git a/txt/adminmanual.txt b/txt/adminmanual.txt index 2fe1ffcc..98aa9af5 100644 --- a/txt/adminmanual.txt +++ b/txt/adminmanual.txt @@ -123,6 +123,7 @@ 9.6 Distribution lists 9.7 Console.pl 9.8 BBS interface + 9.9 Updating kepler data 10. CVS @@ -270,7 +271,7 @@ 11.. IInnssttaallllaattiioonn ((OOrriiggiinnaall vveerrssiioonn bbyy IIaaiinn PPhhiilllliippss,, GG00RRDDII)) - Last modified: 24 January 2001 by Ian Maude, G0VGS + Last modified: 26 January 2001 by Ian Maude, G0VGS 11..11.. IInnttrroodduuccttiioonn @@ -327,7 +328,6 @@ the DXSpider software and are ready to install it. I am assuming version 1.35 for this section but of course you would use the latest version. - Login as root and create a user to run the cluster under. _U_N_D_E_R _N_O _C_I_R_C_U_M_S_T_A_N_C_E_S _U_S_E _R_O_O_T _A_S _T_H_I_S _U_S_E_R_!. I am going to use the name _s_y_s_o_p. You can call it anything you wish. Depending on your security @@ -2294,6 +2294,47 @@ using the Forward.pl file very carefully. + 99..99.. UUppddaattiinngg kkeepplleerr ddaattaa + + Spider has a powerful and flexible show/satellite command. In order + for this to be accurate, the kepler data has to be updated regularly. + In general, this data is available as an email or via cluster mail. + Updating it is simple. First you need to export the mail message as a + file. You do this with the _e_x_p_o_r_t command from the cluster prompt as + the sysop. For example ... + + + + export 5467 /spider/perl/keps.in + + + would export message number 5467 as a file called keps.in in the + /spider/perl directory. + + Now login to a VT as sysop and cd /spider/perl. There is a command in + the perl directory called _c_o_n_v_k_e_p_s_._p_l. All we need to do now is + convert the file like so ... + + + + ./convkeps.pl keps.in + + + + + Now go back to the cluster and issue the command ... + + + + load/keps + + + + + That is it! the kepler data has been updated. + + + 1100.. CCVVSS CVS stands for "Concurrent Versions System" and the CVS for DXSpider @@ -2372,11 +2413,9 @@ - - - tar cvfz /tmp/s.tgz spider - cd / - tar xvfzp /tmp/s.tgz + tar cvfz /tmp/s.tgz spider + cd / + tar xvfzp /tmp/s.tgz @@ -2401,8 +2440,6 @@ Now the magic part! From now on when you want to update, simply connect to the Internet and then, as the user _s_y_s_o_p ... - - cd /spider cvs -z3 update -d @@ -2439,7 +2476,6 @@ read this to understand how filters work - it will save a lot of grief later on. - You can use any of the following things in this line:- @@ -2470,7 +2506,6 @@ - or @@ -2504,11 +2539,9 @@ - - - accept/ann by G,M,2 - accept/ann input node_default by G,M,2 - accept/ann user_default by G,M,2 + accept/ann by G,M,2 + accept/ann input node_default by G,M,2 + accept/ann user_default by G,M,2 @@ -2530,19 +2563,28 @@ - freq eg: 0/30000 or hf or hf/cw or 6m,4m,2m - on same as 'freq' - call eg: G,PA,HB9 - info eg: iota or qsl - by - call_dxcc eg: 61,62 (from eg: sh/pre G) - call_itu - call_zone - by_dxcc - by_itu - by_zone - origin - channel + + + + + + + + + + freq eg: 0/30000 or hf or hf/cw or 6m,4m,2m + on same as 'freq' + call eg: G,PA,HB9 + info eg: iota or qsl + by + call_dxcc eg: 61,62 (from eg: sh/pre G) + call_itu + call_zone + by_dxcc + by_itu + by_zone + origin + channel @@ -2572,6 +2614,7 @@ + but this probably for advanced users... @@ -2638,8 +2681,8 @@ - accept/wcy node_default all - set/hops node_default 10 + accept/wcy node_default all + set/hops node_default 10 @@ -2655,15 +2698,21 @@ - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel + + + + + + + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu + origin_zone + by_dxcc + by_itu + by_zone + channel @@ -2703,7 +2752,6 @@ - 1111..99.. aannnnoouunnccee ((00)) aannnnoouunnccee <> Send an announcement to local users @@ -2722,7 +2770,6 @@ network. - 1111..1111.. aannnnoouunnccee ssyyssoopp ((55)) aannnnoouunnccee ssyyssoopp <> @@ -2770,6 +2817,8 @@ and to undo what you have just done:- + + uncatchup GB7DJK all uncatchup GB7DJK 300 301 302 303 500-510 @@ -2786,6 +2835,7 @@ cclleeaarr//ssppoottss [[11||aallll]] Clear a spot filter line + This command allows you to clear (remove) a line in a spot filter or to remove the whole filter. @@ -2835,7 +2885,6 @@ ccoonnnneecctt <> Start a connection to another DX Cluster - Start a connection process that will culminate in a new connection to the DX cluster . This process creates a new 'client' process which will use the script in /spider/connect/ to effect the @@ -2852,6 +2901,7 @@ defined in the system. It is also aliased to SHOW/COMMAND. + 1111..1188.. ddbbccrreeaattee ((99)) ddbbccrreeaattee <> Create a database entry @@ -2900,15 +2950,13 @@ - - - 's' => [ - .. - .. - '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', - .. - .. - ], + 's' => [ + .. + .. + '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', + .. + .. + ], @@ -2919,6 +2967,7 @@ to work as they may be used to. + See DBIMPORT for the importing of existing AK1A format data to databases. See DBSHOW for generic database enquiry @@ -2967,7 +3016,6 @@ ddbbsshhooww <> <> Display an entry, if it exists, in a database - This is the generic user interface to the database to the database system. It is expected that the sysop will add an entry to the local Aliases file so that users can use the more familiar AK1A style of @@ -2985,7 +3033,8 @@ - DBSHOW buck G1TLH + + DBSHOW buck G1TLH @@ -3034,6 +3083,7 @@ You can combine some of the various directory commands together eg:- + DIR TO G1TLH 5 or DIR SUBJECT IOTA 200-250 @@ -3050,10 +3100,6 @@ DIR/S QSL 10-100 5 - - - - 1111..2244.. ddiirreeccttoorryy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) Works just like the user command except that sysops can see ALL @@ -3099,8 +3145,7 @@ - - DX by G1TLH FR0G 144.600 he isn't on the cluster + DX by G1TLH FR0G 144.600 he isn't on the cluster @@ -3230,8 +3275,6 @@ same subject will be deleted. Beware! - - 1111..3366.. lliinnkkss ((00)) lliinnkkss Show which nodes are physically connected @@ -3253,6 +3296,8 @@ + + 1111..3388.. llooaadd//bbaaddddxx ((99)) llooaadd//bbaaddddxx Reload the bad DX table @@ -3364,6 +3409,9 @@ Alter message parameters like To, From, Subject, whether private or bulletin or return receipt (RR) is required or whether to keep this message from timing out. + + + MSG TO - change TO callsign to MSG FRom - change FROM callsign to MSG PRrivate - set private flag @@ -3429,7 +3477,6 @@ This command allows you to send nearly any command to another DX Cluster node that is connected to the system. - Whether you get any output is dependant on a) whether the other system knows that the node callsign of this cluster is in fact a node b) whether the other system is allowing RCMDs from this node and c) @@ -3447,6 +3494,8 @@ + + 1111..5522.. rreeaadd ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) rreeaadd <> Read a message on the system @@ -3513,7 +3562,6 @@ rreejjeecctt//aannnnoouunnccee <> [[iinnppuutt]] [[00--99]] <> Announce filter sysop version - This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:- @@ -3580,7 +3628,7 @@ - rej/spot 3 all + rej/spot 3 all @@ -3619,24 +3667,15 @@ - - - - - - - - - - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu + origin_zone + by_dxcc + by_itu + by_zone + channel @@ -3655,7 +3694,6 @@ rreejjeecctt//wwccyy <> [[iinnppuutt]] [[00--99]] <> WCY reject filter sysop version - This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:- @@ -3720,6 +3758,8 @@ + + 1111..6611.. rreeppllyy ((00)) rreeppllyy Reply (privately) to the last message that you have read @@ -3759,8 +3799,7 @@ - - SEND RR COPY 123 PRIVATE G1TLH G0RDI + SEND RR COPY 123 PRIVATE G1TLH G0RDI @@ -3787,7 +3826,6 @@ Allow announce messages to arrive at your terminal. - 1111..6655.. sseett//aarrcclluusstteerr ((55)) sseett//aarrcclluusstteerr <> [[<> ......]] Make the node_call an AR- @@ -3892,6 +3930,8 @@ Use with extreme care. This command may well be superceded by FILTERing. + + 1111..6699.. sseett//bbeeeepp ((00)) sseett//bbeeeepp Add beeps to terminal messages @@ -3917,6 +3957,7 @@ You can remove this level with unset/debug + 1111..7722.. sseett//ddxx ((00)) sseett//ddxxAllow DX messages to arrive at your terminal @@ -3983,7 +4024,7 @@ - SET/HOMENODE gb7djk + SET/HOMENODE gb7djk @@ -4049,7 +4090,7 @@ - set/location 54 04 N 2 02 E + set/location 54 04 N 2 02 E @@ -4089,7 +4130,6 @@ sseett//lloocckkoouutt <> Stop a callsign connecting to the cluster - You can show who is locked out with the _s_h_o_w_/_l_o_c_k_o_u_t command. To allow the user to connect again, use the _u_n_s_e_t_/_l_o_c_k_o_u_t command. @@ -4116,7 +4156,6 @@ Tell the system that the call(s) are to be treated as AK1A cluster and fed PC Protocol rather normal user commands. - From version 1.41 you can also set the following types of cluster @@ -4153,9 +4192,6 @@ minutes, it is disconnected. - - - 1111..8888.. sseett//ppaaggee ((00)) sseett//ppaaggee <> Set the number of lines per page @@ -4221,14 +4257,13 @@ - - 0 - normal user - 1 - allow remote nodes normal user RCMDs - 5 - various privileged commands (including shutdown, but not disc- - connect), the normal level for another node. - 8 - more privileged commands (including disconnect) - 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS - LEVEL. + 0 - normal user + 1 - allow remote nodes normal user RCMDs + 5 - various privileged commands (including shutdown, but not disc- + connect), the normal level for another node. + 8 - more privileged commands (including disconnect) + 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS + LEVEL. @@ -4251,6 +4286,8 @@ sseett//ssyyss__qqrraa <> Set your cluster QRA locator + + 1111..9944.. sseett//qqrraa ((00)) sseett//qqrraa <> Set your QRA locator @@ -4317,8 +4354,6 @@ Allow WX information to be seen at your console. You can switch off WX messages with the _u_n_s_e_t_/_w_x command. - - 1111..110000.. sshhooww//bbaaddddxx ((11)) sshhooww//bbaaddddxxShow all the bad dx calls in the system @@ -4374,35 +4409,46 @@ - on - eg 160m 20m 2m 23cm 6mm - on - eg hf vhf uhf shf (see SHOW/BANDS) - - 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 - ** - for a spotted callsign containing - 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 same). - qsl - this automatically looks for any qsl info on the call - held in the spot database. - iota [] - If the iota island number is missing it will - look for the string iota and anything which looks like - an iota island number. If you specify then it will look - for that island. - qra [] - this will look for the specific locator if - you specify one or else anything that looks like a locator. + + + + on - eg 160m 20m 2m 23cm 6mm + on - eg hf vhf uhf shf (see SHOW/BANDS) + + - 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 + ** - for a spotted callsign containing + + 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 same). + + qsl - this automatically looks for any qsl info on the call + held in the spot database. + + iota [] - If the iota island number is missing it will + look for the string iota and anything which looks like + an iota island number. If you specify then it will look + for that island. + + qra [] - this will look for the specific locator if + you specify one or else anything that looks like a locator. @@ -4420,6 +4466,10 @@ SH/DX iota eu-064 SH/DX qra jn86 + + + + 1111..110055.. sshhooww//ddxxcccc ((00)) sshhooww//ddxxcccc <> Interrogate the spot database by country @@ -4434,8 +4484,10 @@ - SH/DXCC G - SH/DXCC W on 20m info iota + + + SH/DXCC G + SH/DXCC W on 20m info iota @@ -4486,6 +4538,7 @@ sshhooww//ffiilltteerr <> Show the filters set by + A sysop can look at any filters that have been set. @@ -4499,7 +4552,6 @@ which category you want to see. If you leave the category out then all the categories will be listed. - 1111..111100.. sshhooww//iissoollaattee ((11)) sshhooww//iissoollaattee Show a list of isolated nodes @@ -4552,6 +4604,7 @@ sshhooww//mmuuff <> [[<>]][[lloonngg]] Show the likely propagation to + This command allow you to estimate the likelihood of you contacting a station with the prefix you have specified. The output assumes a modest power of 20dBW and receiver sensitivity of -123dBm (about @@ -4618,6 +4671,7 @@ inputing:- + SH/MUF W 24 @@ -4628,8 +4682,10 @@ - SH/MUF W L 24 - SH/MUF W 24 Long + + + SH/MUF W L 24 + SH/MUF W 24 Long @@ -4684,6 +4740,8 @@ given on the command line) the distance and beraing from your station to the locator. For example:- + + SH/QRA IO92QL SH/QRA JN06 IN73 @@ -4758,7 +4816,6 @@ So for example:- - SH/SAT AO-10 SH/SAT FENGYUN1 12 2 @@ -4814,8 +4871,6 @@ system - - 1111..112244.. sshhooww//wwwwvv ((00)) sshhooww//wwwwvv Show the last 10 WWV broadcasts @@ -4880,8 +4935,6 @@ etc etc. - - 1111..113300.. ssttaatt//uusseerr ((55)) ssttaatt//uusseerr <> Show the full status of a user @@ -4893,6 +4946,8 @@ Only the fields that are defined (in perl term) will be displayed. + + 1111..113311.. ssyyssoopp ((00)) ssyyssoopp Regain your privileges if you login remotely @@ -4947,7 +5002,6 @@ cluster system. You can send it to anyone you can see with a SHOW/CONFIGURATION command, they don't have to be connected locally. - The second form of TALK is used when other cluster nodes are connected with restricted information. This usually means that they don't send the user information usually associated with logging on and off the @@ -5014,6 +5068,8 @@ This is a quick listing that shows which callsigns are connected and what sort of connection they have + + 1111..113355.. wwxx ((00)) wwxx <> Send a weather message to local users @@ -5070,6 +5126,16 @@ + + + + + + + + + + -- 2.34.1