The DXSpider Installation and Administration Manual
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.29 January 2001
+ Version 1.30 January 2001
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
9.5 Forward.pl
9.6 Distribution lists
9.7 Console.pl
+ 9.8 BBS interface
+ 9.9 Updating kepler data
10. CVS
1\b1.\b. I\bIn\bns\bst\bta\bal\bll\bla\bat\bti\bio\bon\bn (\b(O\bOr\bri\big\bgi\bin\bna\bal\bl v\bve\ber\brs\bsi\bio\bon\bn b\bby\by I\bIa\bai\bin\bn P\bPh\bhi\bil\bll\bli\bip\bps\bs,\b, G\bG0\b0R\bRD\bDI\bI)\b)
- Last modified: 13 January 2001 by Ian Maude, G0VGS
+ Last modified: 26 January 2001 by Ian Maude, G0VGS
1\b1.\b.1\b1.\b. I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
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. _\bU_\bN_\bD_\bE_\bR _\bN_\bO
_\bC_\bI_\bR_\bC_\bU_\bM_\bS_\bT_\bA_\bN_\bC_\bE_\bS _\bU_\bS_\bE _\bR_\bO_\bO_\bT _\bA_\bS _\bT_\bH_\bI_\bS _\bU_\bS_\bE_\bR_\b!. I am going to use the name
_\bs_\by_\bs_\bo_\bp. You can call it anything you wish. Depending on your security
edit the file with your favourite editor.
+ 9\b9.\b.8\b8.\b. B\bBB\bBS\bS i\bin\bnt\bte\ber\brf\bfa\bac\bce\be
+
+ Spider provides a simple BBS interface. No input is required from the
+ sysop of the cluster at all. The BBS simply sets the cluster as a BBS
+ and pushes any required mail to the cluster. No mail can flow from
+ Spider to the BBS, the interface is one-way.
+
+
+ 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.
+
+
+ 9\b9.\b.9\b9.\b. U\bUp\bpd\bda\bat\bti\bin\bng\bg k\bke\bep\bpl\ble\ber\br d\bda\bat\bta\ba
+
+ 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 _\be_\bx_\bp_\bo_\br_\bt 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 _\bc_\bo_\bn_\bv_\bk_\be_\bp_\bs_\b._\bp_\bl. 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.
+
+
+
1\b10\b0.\b. C\bCV\bVS\bS
CVS stands for "Concurrent Versions System" and the CVS for DXSpider
ENTIRE SPIDER TREE!!
-
Assuming you are connected to the Internet, you need to login to the
CVS repository and then update your Spider source. There are several
steps which are listed below ...
Now the magic part! From now on when you want to update, simply
connect to the Internet and then, as the user _\bs_\by_\bs_\bo_\bp ...
-
-
cd /spider
cvs -z3 update -d
-
-
-
-
-
-
-
-
-
-
-
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
-
or
+
+
1\b11\b1.\b.3\b3.\b. a\bac\bcc\bce\bep\bpt\bt/\b/s\bsp\bpo\bot\bts\bs (\b(0\b0)\b)
a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set an accept filter line for spots
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
- on <range> same as 'freq'
- call <prefixes> eg: G,PA,HB9
- info <string> eg: iota or qsl
- by <prefixes>
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- origin <prefixes>
- channel <prefixes>
+
+
+
+
+
+
+
+
+
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[i
\bin
\bnp
\bpu
\but
\bt]
\b] [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Spot 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:-
-
1\b11\b1.\b.7\b7.\b. a\bac\bcc\bce\bep\bpt\bt/\b/w\bww\bwv\bv (\b(0\b0)\b)
a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bww
\bwv
\bv [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set an accept WWV filter
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
+
+
+
+
+
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
Send an announcement to LOCAL users only, where <text> is the text of
the announcement you wish to broadcast
+
1\b11\b1.\b.1\b10\b0.\b. a\ban\bnn\bno\bou\bun\bnc\bce\be f\bfu\bul\bll\bl (\b(0\b0)\b)
a\ban\bnn\bno\bou\bun\bnc\bce\be f\bfu\bul\bll\bl <\b<t\bte\bex\bxt\bt>\b> Send an announcement cluster wide
network.
-
1\b11\b1.\b.1\b11\b1.\b. a\ban\bnn\bno\bou\bun\bnc\bce\be s\bsy\bys\bso\bop\bp (\b(5\b5)\b)
a\ban\bnn\bno\bou\bun\bnc\bce\be s\bsy\bys\bso\bop\bp <\b<t\bte\bex\bxt\bt>\b>
-
which will arrange for them to be forward candidates again.
Order is not important.
c\bcl\ble\bea\bar\br/\b/s\bsp\bpo\bot\bts\bs [\b[1\b1|\b|a\bal\bll\bl]\b] Clear a spot filter line
+
This command allows you to clear (remove) a line in a spot filter or
to remove the whole filter.
defined in the system. It is also aliased to SHOW/COMMAND.
+
1\b11\b1.\b.1\b18\b8.\b. d\bdb\bbc\bcr\bre\bea\bat\bte\be (\b(9\b9)\b)
d\bdb\bbc\bcr\bre\bea\bat\bte\be <\b<n\bna\bam\bme\be>\b> Create a database entry
],
+
+
to allow
SH/BUCK g1tlh
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
- DBSHOW buck G1TLH
+
+ DBSHOW buck G1TLH
syntax:-
+
DIR/T G1* 10
DIR/S QSL 10-100 5
-
-
-
-
1\b11\b1.\b.2\b24\b4.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(5\b5)\b)
Works just like the user command except that sysops can see ALL
e\bex\bxp\bpo\bor\brt\bt <\b<m\bms\bsg\bgn\bno\bo>\b> <\b<f\bfi\bil\ble\ben\bna\bam\bme\be>\b> 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 ready to be imported back into the cluster by placing it in
Look at the APROPOS <string> command which will search the help
database for the <string> you specify and give you a list of likely
commands to look at with HELP.
+
+
1\b11\b1.\b.3\b32\b2.\b. i\bin\bni\bit\bt (\b(5\b5)\b)
i\bin\bni\bit\bt <\b<n\bno\bod\bde\be c\bca\bal\bll\bl>\b> Re-initialise a link to an AK1A compatible node
As a sysop you can kill any message on the system.
- 1\b11\b1.\b.3\b35\b5.\b. k\bki\bil\bll\bl f\bfu\bul\bll\bl <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[<\b<m\bms\bsg\bgn\bno\bo>\b>]\b] D\bDe\bel\ble\bet\bte\be a\ba m\bme\bes\bss\bsa\bag\bge\be f\bfr\bro\bom\bm t\bth\bhe\be w\bwh\bho\bol\ble\be
- c\bcl\blu\bus\bst\bte\ber\br k\bki\bil\bll\bl f\bfu\bul\bll\bl (\b(5\b5)\b)
+ 1\b11\b1.\b.3\b35\b5.\b. k\bki\bil\bll\bl f\bfu\bul\bll\bl (\b(5\b5)\b)
+
+ k\bki\bil\bll\bl f\bfu\bul\bll\bl <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[<\b<m\bms\bsg\bgn\bno\bo>\b>]\b] Delete a message from the whole cluster
+
Delete a message (usually a 'bulletin') from the whole cluster system.
running in order for the changes to take effect.
- 1\b11\b1.\b.3\b38\b8.\b. l\blo\boa\bad\bd/\b/b\bba\bad\bdd\bdx\bx R\bRe\bel\blo\boa\bad\bd t\bth\bhe\be b\bba\bad\bd D\bDX\bX t\bta\bab\bbl\ble\be l\blo\boa\bad\bd/\b/b\bba\bad\bdd\bdx\bx (\b(9\b9)\b)
+
+
+
+ 1\b11\b1.\b.3\b38\b8.\b. l\blo\boa\bad\bd/\b/b\bba\bad\bdd\bdx\bx (\b(9\b9)\b)
+
+ l\blo\boa\bad\bd/\b/b\bba\bad\bdd\bdx\bx Reload the bad DX table
+
Reload the /spider/data/baddx.pl file if you have changed it manually
whilst the cluster is running. This table contains the DX Calls that,
whilst the cluster is running.
-
-
-
1\b11\b1.\b.4\b44\b4.\b. l\blo\boa\bad\bd/\b/m\bme\bes\bss\bsa\bag\bge\bes\bs (\b(9\b9)\b)
l\blo\boa\bad\bd/\b/m\bme\bes\bss\bsa\bag\bge\bes\bs Reload the system messages file
projects / spider.git / blobdiff