From 8e862ce4b386889bc91c34ec788df0bd1a062c6c Mon Sep 17 00:00:00 2001 From: g0vgs Date: Mon, 31 Dec 2001 09:18:21 +0000 Subject: [PATCH] make some documentation changes and fix unset/register --- Changes | 4 + cmd/unset/register.pl | 2 +- html/adminmanual-6.html | 5 + html/installation-1.html | 47 ++++++-- html/installation-2.html | 2 + html/installation-3.html | 7 +- html/installation.html | 2 +- html/spiderFAQ-2.html | 9 ++ html/spiderFAQ.html | 3 +- sgml/adminmanual.sgml | 5 + sgml/installation.sgml | 68 ++++++++--- sgml/spiderFAQ.sgml | 11 +- txt/adminmanual.txt | 196 +++++++++++++++---------------- txt/installation.txt | 244 +++++++++++++++++++-------------------- txt/spiderFAQ.txt | 72 +++++++++++- 15 files changed, 423 insertions(+), 254 deletions(-) diff --git a/Changes b/Changes index c1df82e8..6368ff21 100644 --- a/Changes +++ b/Changes @@ -1,3 +1,7 @@ +31Dec01======================================================================= +1. Make a couple of changes to the Installation Manual and add a FAQ on msg +deletion. (g0vgs) +2. Fix unset/register so it works (g0vgs) 30Dec01======================================================================= 1. make PC21 coming from the channel's node call then treat it as a PC39 and disconnect it. diff --git a/cmd/unset/register.pl b/cmd/unset/register.pl index 7f5b6734..8685a13b 100644 --- a/cmd/unset/register.pl +++ b/cmd/unset/register.pl @@ -17,7 +17,7 @@ if ($self->priv < 9) { Log('DXCommand', $self->call . " attempted to unregister @args"); return (1, $self->msg('e5')); } -return (1, $self->msg('reginac')) unless $main::reqreq; +return (1, $self->msg('reginac')) unless $main::reqreg; foreach $call (@args) { $call = uc $call; diff --git a/html/adminmanual-6.html b/html/adminmanual-6.html index 1857f2a4..850938a3 100644 --- a/html/adminmanual-6.html +++ b/html/adminmanual-6.html @@ -288,6 +288,7 @@ package CmdAlias; ) +

You can create aliases for commands at will. Beware though, these may not always turn out as you think. Care is needed and you need to test the results once you have set an alias. @@ -317,8 +318,10 @@ 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 ... @@ -328,6 +331,7 @@ convert the file like so ... ./convkeps.pl keps.in +

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

@@ -335,6 +339,7 @@ convert the file like so ... load/keps
+

That is it! the kepler data has been updated.

6.8 The QRZ callbook diff --git a/html/installation-1.html b/html/installation-1.html index a781b1e2..28cb629e 100644 --- a/html/installation-1.html +++ b/html/installation-1.html @@ -36,7 +36,10 @@ in the development of Spider.

In addition to the standard Red Hat distribution you will require the following modules from -http://www.cpan.org/CPAN.html ... +http://www.cpan.org/CPAN.html , please note however that with later versions of perl, some of these +modules may be included with the distribution. Get the modules anyway and try +to install as below. If they complain, they are probably already a part of your +perl distribution.

-

Copy the CPAN modules listed above to a convenient place on your computer. One good place would be /usr/local/packages, and the instructions which follow will assume that that's where you have put them. +

Copy the CPAN modules listed above to a convenient place on your computer. One good +place would be /usr/local/packages, and the instructions which follow will assume that +that's where you have put them.

Log in as 'root', and make sure you're at '/root' before you continue. Here are exactly the commands you must issue next: -

@@ -102,7 +107,8 @@ following modules from # cd ..

-

Do not fall into the trap of thinking they're all the same, just because they nearly are! Pay particular attention to the instructions of IO, above. +

Do not fall into the trap of thinking they're all the same, just because they +nearly are! Pay particular attention to the instructions of IO, above.

1.2 Preparation @@ -157,6 +163,7 @@ permissions. Copy the tarball to /home/sysop and do the following. # groupadd -g 251 spider (or another number) +

If you do not have the command groupadd available to you simply add a line in /etc/group by hand.

@@ -165,6 +172,7 @@ add a line in /etc/group by hand. # vi /etc/group (or your favorite editor) +

You also need to add some others to the group, including your own callsign (this will be used as an alias) and root. The finished line in /etc/group should look something like this @@ -213,18 +221,36 @@ $ vi DXVars.pm (or your favourite editor)

Using the distributed DXVars.pm as a a template, set your cluster callsign, -sysop callsign and other user info to suit your own environment. Note that -this a perl file which will be parsed and executed as part of the cluster. If -you get it wrong then perl will complain when you start the cluster process. -It is important only to alter the text of any section. Some of the lines look -a little odd. Take this line for example .... +sysop callsign and other user info to suit your own environment. +

+

+
+$mycall = "GB7DJK";     
+
+
+

+

This is the call sign of your cluster. If you use an SSID then include it here +also. +

+

+
+$myalias = "G1TLH";
+
+
+

+

This is the sysop user callsign, normally your own. +

+

PLEASE USE CAPITAL LETTERS FOR CALLSIGNS +

+

Note that this a perl file which will be parsed and executed as part of the +cluster. If you get it wrong then perl will complain when you start the cluster +process. It is important only to alter the text of any section. Some of the +lines look a little odd. Take this line for example ....

$myemail = "ianmaude\@btinternet.com";

There appears to be an extra slash in there. However this has to be there for the file to work so leave it in.

-

PLEASE USE CAPITAL LETTERS FOR CALLSIGNS -

DON'T alter any file in /spider/perl, they are overwritten with every release. Any files or commands you place in /spider/local or /spider/local_cmd will automagically be used in preference to the ones in /spider/perl EVEN @@ -299,6 +325,7 @@ was set as GB7MBC. You should therefore see this when you login .... G0VGS de GB7MBC 19-Nov-1999 2150Z > +

If you do, congratulations! If not, look over the instructions again, you have probably missed something out. You can shut spider down again with the command .... diff --git a/html/installation-2.html b/html/installation-2.html index 5ccaefef..8008f5b8 100644 --- a/html/installation-2.html +++ b/html/installation-2.html @@ -40,6 +40,7 @@ is the user that should be doing that process.

  • ./create_sysop.pl (sysop)
  • ./cluster.pl (sysop)
    • +

    Spider should now be running and you should be able to login using the client program.

    @@ -50,6 +51,7 @@ client program.

  • Enter the correct line in /etc/inetd.conf (root)
  • killall -HUP inetd (root)
    • +

    Spider should now be able to accept logins via telnet, netrom and ax25.

    December 2001 revision 1.1

    A reference for SysOps of the DXSpider DXCluster program.
    diff --git a/html/spiderFAQ-2.html b/html/spiderFAQ-2.html index 60681fd8..300b2774 100644 --- a/html/spiderFAQ-2.html +++ b/html/spiderFAQ-2.html @@ -103,6 +103,15 @@ some way. Simply delete the /spider/data/dupefile and restart the cluster. It may take a little time to become fully functional but should solve your problem.

    +

    2.8 I have deleted a message but it is still there, why? +

    + +

    This is now the way messages are handled for deletion in Spider. If you +look closely you will see a 'D' following the message number. This +message is marked for deletion and will be deleted in 2 days if nothing +further is done. Optionally you can use the command delete/expunge +to delete it immediately. +

    Next Previous diff --git a/html/spiderFAQ.html b/html/spiderFAQ.html index 5a838e0b..0f9cdd2a 100644 --- a/html/spiderFAQ.html +++ b/html/spiderFAQ.html @@ -15,7 +15,7 @@ Contents

    The DXSpider FAQ

    -

    Ian Maude, G0VGS, (ianmaude@btinternet.com)

    $Date$ $Revision$ +

    Ian Maude, G0VGS, (ianmaude@btinternet.com)

    December 2001 Revision: 1.8

    A reference for SysOps of the DXSpider DXCluster program.
    @@ -42,6 +42,7 @@ Contents
  • 2.5 How can I automatically limit the amount of debug logfiles that are stored?
  • 2.6 I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?
  • 2.7 Since I last updated I seem to be getting duplicate spots appearing. +
  • 2.8 I have deleted a message but it is still there, why?
    Next diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 4a25de0c..18ec8449 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -1340,6 +1340,7 @@ package CmdAlias; ) +

    You can create aliases for commands at will. Beware though, these may not always turn out as you think. Care is needed and you need to test the results once you have set an alias. @@ -1369,9 +1370,11 @@ 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 ... @@ -1380,12 +1383,14 @@ 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. The QRZ callbook diff --git a/sgml/installation.sgml b/sgml/installation.sgml index 50e9e5c2..4fbf7fbd 100644 --- a/sgml/installation.sgml +++ b/sgml/installation.sgml @@ -7,7 +7,7 @@ The DXSpider Installation Manual v1.49 Iain Philipps, G0RDI (g0rdi@77hz.com) and Ian Maude, G0VGS, (ianmaude@btinternet.com) -November 2001 revision 1.0 +December 2001 revision 1.1 A reference for SysOps of the DXSpider DXCluster program. @@ -41,8 +41,12 @@ Spider required perl 5.004, however it is now STRONGLY recommended that you use at least version 5.005_03 as this is the version being used in the development of Spider. -

    In addition to the standard Red Hat distribution you will require the -following modules from ... +

    +In addition to the standard Red Hat distribution you will require the +following modules from , please note however that with later versions of perl, some of these +modules may be included with the distribution. Get the modules anyway and try +to install as below. If they complain, they are probably already a part of your +perl distribution.

    @@ -55,7 +59,9 @@ following modules from + +

    +This is the call sign of your cluster. If you use an SSID then include it here +also. + + +$myalias = "G1TLH"; + + +

    +This is the sysop user callsign, normally your own. + +

    +PLEASE USE CAPITAL LETTERS FOR CALLSIGNS + +

    +Note that this a perl file which will be parsed and executed as part of the +cluster. If you get it wrong then perl will complain when you start the cluster +process. It is important only to alter the text of any section. Some of the +lines look a little odd. Take this line for example .... $myemail = "ianmaude\@btinternet.com"; @@ -226,8 +255,6 @@ $myemail = "ianmaude\@btinternet.com"; There appears to be an extra slash in there. However this has to be there for the file to work so leave it in. -

    PLEASE USE CAPITAL LETTERS FOR CALLSIGNS -

    DON'T alter any file in /spider/perl, they are overwritten with every release. Any files or commands you place in /spider/local or /spider/local_cmd @@ -298,6 +325,7 @@ was set as GB7MBC. You should therefore see this when you login .... G0VGS de GB7MBC 19-Nov-1999 2150Z > +

    If you do, congratulations! If not, look over the instructions again, you have probably missed something out. You can shut spider down again with the command .... @@ -339,6 +367,7 @@ is the user that should be doing that process. ./cluster.pl (sysop) +

    Spider should now be running and you should be able to login using the client program. @@ -350,6 +379,7 @@ client program. killall -HUP inetd (root) +

    Spider should now be able to accept logins via telnet, netrom and ax25. @@ -378,12 +408,14 @@ each interface that you wish to allow connections on, use the following format . default * * * * * * - sysop /spider/src/client client %u ax25 +

    or, if you wish your users to be able to use SSID's on their callsigns .. default * * * * * * - sysop /spider/src/client client %s ax25 +

    For most purposes this is not desirable. The only time you probably will need this is when you need to allow other cluster nodes that are using SSID's in. In this case it would probably be better to use the first example and @@ -409,6 +441,7 @@ in /etc/services to allow connections to a port number, like this .... spdlogin 8000/tcp # spider anonymous login port +

    Then add a line in /etc/inetd.conf like this .... @@ -422,14 +455,15 @@ Once this is done, you need to restart inetd like this .... killall -HUP inetd - -

    Now login as sysop and cd spider/src. You can test that spider +

    +Now login as sysop and cd spider/src. You can test that spider is accepting telnet logins by issuing the following command .... ./client login telnet +

    You should get a login prompt and on issuing a callsign, you will be given access to the cluster. Note, you will not get a password login. There seems no good reason for a password prompt to be given so it is not asked for. @@ -643,7 +677,7 @@ or symbols:- connects to GB7DJK-1 [instead of a script called gb7djk-1]). - +

    There are many possible ways to configure the script but here are three examples, one for a NETRom/AX25 connect, one for AGW engines and one for tcp/ip. @@ -702,6 +736,7 @@ connection to GB7DJK-1 started G0VGS de GB7MBC 13-Dec-1998 2043Z > +

    This will start a connection using the script called gb7djk-1. You can follow the connection by watching the term or console from where you started cluster.pl. From version 1.47 onwards, you will need to set/debug connect first. @@ -794,6 +829,7 @@ connect telnet mary.lancs.ac.uk 'connect' '' +

    So, the first connection is made by Spider. This is fine as Spider uses the Net_Telnet script from within perl. This actually uses TCP rather than TELNET so no negotiation will be done on the first connection. Once connected to @@ -833,7 +869,7 @@ This line works fine for RedHat distributions. It is also fine for SuSE up to DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 - +

    The line required for Slackware distributions is slightly different. My thanks to Aurelio, PA3EZL for this information. diff --git a/sgml/spiderFAQ.sgml b/sgml/spiderFAQ.sgml index a34a1efa..cdeb3738 100644 --- a/sgml/spiderFAQ.sgml +++ b/sgml/spiderFAQ.sgml @@ -6,7 +6,7 @@ The DXSpider FAQ Ian Maude, G0VGS, (ianmaude@btinternet.com) -$Date$ $Revision$ +December 2001 Revision: 1.8 A reference for SysOps of the DXSpider DXCluster program. @@ -147,4 +147,13 @@ some way. Simply delete the /spider/data/dupefile and restart the cluster. It may take a little time to become fully functional but should solve your problem. +I have deleted a message but it is still there, why? + +

    +This is now the way messages are handled for deletion in Spider. If you +look closely you will see a 'D' following the message number. This +message is marked for deletion and will be deleted in 2 days if nothing +further is done. Optionally you can use the command delete/expunge +to delete it immediately. + diff --git a/txt/adminmanual.txt b/txt/adminmanual.txt index 5887f5fc..d8078515 100644 --- a/txt/adminmanual.txt +++ b/txt/adminmanual.txt @@ -1917,6 +1917,7 @@ + You can create aliases for commands at will. Beware though, these may not always turn out as you think. Care is needed and you need to test the results once you have set an alias. @@ -1950,9 +1951,11 @@ + 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 ... @@ -1964,6 +1967,7 @@ + Now go back to the cluster and issue the command ... @@ -1973,9 +1977,8 @@ - That is it! the kepler data has been updated. - + That is it! the kepler data has been updated. 6.8. The QRZ callbook @@ -2040,6 +2043,7 @@ registered users, use the command show/register. + 7.2. Passwords At the moment, passwords only affect users who login to a DXSpider @@ -2106,10 +2110,10 @@ CVS repository and then update your Spider source. There are several steps which are listed below ... - First login as the user sysop. Next you need to connect to the CVS repository. You do this with the command below ... + cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login @@ -2238,9 +2242,9 @@ dest eg: 6MUK,WDX (distros) + some examples:- - some examples:- acc/ann dest 6MUK acc/ann 2 by_zone 14,15,16 @@ -2304,10 +2308,10 @@ more info. Please 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:- + call the callsign of the thingy call_dxcc eg: 61,62 (from eg: sh/pre G) call_itu @@ -2358,19 +2362,33 @@ - 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 + + @@ -2432,23 +2450,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 @@ -2490,15 +2500,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 @@ -2506,6 +2522,7 @@ for example + accept/wwv by_zone 4 @@ -2555,9 +2572,6 @@ This command will send your announcement across the whole cluster network. - - - 9.12. announce sysop (5) announce sysop @@ -2571,7 +2585,6 @@ apropos Search the help database - Search the help database for (it isn't case sensitive), and print the names of all the commands that may be relevant. @@ -2637,7 +2650,6 @@ This command allows you to clear (remove) a line in a route filter or to remove the whole filter. - see CLEAR/SPOTS for a more detailed explanation. A sysop can clear an input or normal output filter for a user or the @@ -2701,9 +2713,6 @@ node_default or user_default. - - - 9.20. clear/wcy (0) clear/wcy [1|all] Clear a WCY filter line @@ -2826,6 +2835,7 @@ to allow + SH/BUCK g1tlh to work as they may be used to. @@ -2834,8 +2844,6 @@ databases. See DBSHOW for generic database enquiry - - 9.27. dbimport (9) dbimport Import AK1A data into a database @@ -2894,11 +2902,10 @@ but if he hasn't and the database really does exist (use DBAVAIL or SHOW/COMMAND to find out) you can do the same thing with: + DBSHOW buck G1TLH - DBSHOW buck G1TLH - @@ -2959,15 +2966,20 @@ - DIR TO G1TLH 5 - or - DIR SUBJECT IOTA 200-250 + + + DIR TO G1TLH 5 + or + DIR SUBJECT IOTA 200-250 You can abbreviate all the commands to one letter and use ak1a syntax:- + + + DIR/T G1* 10 DIR/S QSL 10-100 5 @@ -3021,7 +3033,8 @@ - DX by G1TLH FR0G 144.600 he isn't on the cluster + + DX by G1TLH FR0G 144.600 he isn't on the cluster @@ -3034,6 +3047,7 @@ 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 ready to be imported back into the cluster by placing it in @@ -3165,7 +3179,6 @@ clear/spots 1 - To remove the filter in its entirty:- clear/spots all @@ -3283,6 +3296,8 @@ same subject will be deleted. Beware! + + 9.46. kill/expunge (6) kill/expunge [..]Expunge a message @@ -3298,6 +3313,7 @@ It otherwise is used in the same way as the KILL command. + 9.47. links (0) links Show which nodes are physically connected @@ -3348,7 +3364,6 @@ load/bands Reload the band limits table - Reload the /spider/data/bands.pl file if you have changed it manually whilst the cluster is running. @@ -3364,6 +3379,8 @@ delete a command in the local_cmd tree and want to use the normal one again. Execute this command to reset everything back to the state it was just after a cluster restart. + + 9.53. load/forward (9) load/forward Reload the msg forwarding routing table @@ -3413,37 +3430,26 @@ msg [data ...] Alter various message parameters - 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 - MSG NOPRrivate - unset private flag - MSG RR - set RR flag - MSG NORR - unset RR flag - MSG KEep - set the keep flag (message won't be deleted ever) - MSG NOKEep - unset the keep flag - MSG SUbject - change the subject to - MSG WAittime - remove any waitting time for this message - MSG NOREad - mark message as unread - MSG REad - mark message as read - MSG QUeue - queue any outstanding bulletins - MSG QUeue 1 - queue any outstanding private messages + MSG TO - change TO callsign to + MSG FRom - change FROM callsign to + MSG PRrivate - set private flag + MSG NOPRrivate - unset private flag + MSG RR - set RR flag + MSG NORR - unset RR flag + MSG KEep - set the keep flag (message won't be deleted ever) + MSG NOKEep - unset the keep flag + MSG SUbject - change the subject to + MSG WAittime - remove any waitting time for this message + MSG NOREad - mark message as unread + MSG REad - mark message as read + MSG QUeue - queue any outstanding bulletins + MSG QUeue 1 - queue any outstanding private messages @@ -3487,6 +3493,9 @@ + + + 9.60. rcmd (1) rcmd Send a command to another DX cluster @@ -3495,7 +3504,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) @@ -3553,6 +3561,7 @@ + some examples:- @@ -3619,16 +3628,11 @@ origin_itu origin_zone - - - - some examples:- - - rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes) + rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes) @@ -3690,10 +3694,6 @@ rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16) - - - - You can use the tag 'all' to reject everything eg: diff --git a/txt/installation.txt b/txt/installation.txt index df4e0cdf..a555718b 100644 --- a/txt/installation.txt +++ b/txt/installation.txt @@ -1,7 +1,7 @@ The DXSpider Installation Manual v1.49 Iain Philipps, G0RDI (g0rdi@77hz.com) and Ian Maude, G0VGS, (ianmaude@btinternet.com) - November 2001 revision 1.0 + December 2001 revision 1.1 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -79,7 +79,11 @@ In addition to the standard Red Hat distribution you will require the - following modules from http://www.cpan.org/CPAN.html ... + following modules from http://www.cpan.org/CPAN.html , please note + however that with later versions of perl, some of these modules may be + included with the distribution. Get the modules anyway and try to + install as below. If they complain, they are probably already a part + of your perl distribution. @@ -121,10 +125,6 @@ - - - - @@ -240,6 +240,7 @@ + If you do not have the command groupadd available to you simply add a line in /etc/group by hand. @@ -250,6 +251,7 @@ + You also need to add some others to the group, including your own callsign (this will be used as an alias) and root. The finished line in /etc/group should look something like this @@ -260,11 +262,9 @@ The next step is to set the permissions on the Spider directory tree and files .... - - - # chown -R sysop.spider spider - # find . -type d -exec chmod 2775 {} \; - # find . -type f -exec chmod 775 {} \; + # chown -R sysop.spider spider + # find . -type d -exec chmod 2775 {} \; + # find . -type f -exec chmod 775 {} \; @@ -309,22 +309,44 @@ Using the distributed DXVars.pm as a a template, set your cluster callsign, sysop callsign and other user info to suit your own - environment. Note that this a perl file which will be parsed and - executed as part of the cluster. If you get it wrong then perl will - complain when you start the cluster process. It is important only to - alter the text of any section. Some of the lines look a little odd. - Take this line for example .... + environment. - $myemail = "ianmaude\@btinternet.com"; - There appears to be an extra slash in there. However this has to be - there for the file to work so leave it in. + $mycall = "GB7DJK"; + + + + + + This is the call sign of your cluster. If you use an SSID then + include it here also. + + + + $myalias = "G1TLH"; + + + + This is the sysop user callsign, normally your own. PLEASE USE CAPITAL LETTERS FOR CALLSIGNS + Note that this a perl file which will be parsed and executed as part + of the cluster. If you get it wrong then perl will complain when you + start the cluster process. It is important only to alter the text of + any section. Some of the lines look a little odd. Take this line for + example .... + + $myemail = "ianmaude\@btinternet.com"; + + + There appears to be an extra slash in there. However this has to be + there for the file to work so leave it in. + + DON'T alter any file in /spider/perl, they are overwritten with every release. Any files or commands you place in /spider/local or /spider/local_cmd will automagically be used in preference to the ones @@ -371,16 +393,17 @@ - $ ./cluster.pl - DXSpider DX Cluster Version 1.47 - Copyright (c) 1998 Dirk Koopman G1TLH - loading prefixes ... - loading band data ... - loading user file system ... - starting listener ... - reading existing message headers - reading cron jobs - orft we jolly well go ... + + $ ./cluster.pl + DXSpider DX Cluster Version 1.47 + Copyright (c) 1998 Dirk Koopman G1TLH + loading prefixes ... + loading band data ... + loading user file system ... + starting listener ... + reading existing message headers + reading cron jobs + orft we jolly well go ... @@ -394,6 +417,9 @@ $ ./client + + + This should log you into the cluster as the sysop under the alias callsign we set earlier. In this case the callsign is G0VGS. The cluster callsign is set in the DXVars.pm file in /spider/local. In @@ -407,6 +433,7 @@ + If you do, congratulations! If not, look over the instructions again, you have probably missed something out. You can shut spider down again with the command .... @@ -459,7 +486,6 @@ o cp perl/DXVars.pm.issue local/DXVars.pm (sysop) - o cd to /spider/local and edit DXVars to set your details (sysop) o cd ../perl (sysop) @@ -468,6 +494,7 @@ o ./cluster.pl (sysop) + Spider should now be running and you should be able to login using the client program. @@ -482,6 +509,7 @@ o killall -HUP inetd (root) + Spider should now be able to accept logins via telnet, netrom and ax25. @@ -522,15 +550,18 @@ + or, if you wish your users to be able to use SSID's on their callsigns .. + default * * * * * * - sysop /spider/src/client client %s ax25 + For most purposes this is not desirable. The only time you probably will need this is when you need to allow other cluster nodes that are using SSID's in. In this case it would probably be better to use the @@ -561,9 +592,6 @@ spdlogin 8000/tcp # spider anonymous login port - - - Then add a line in /etc/inetd.conf like this .... @@ -584,7 +612,6 @@ - Now login as sysop and cd spider/src. You can test that spider is accepting telnet logins by issuing the following command .... @@ -592,6 +619,10 @@ ./client login telnet + + + + You should get a login prompt and on issuing a callsign, you will be given access to the cluster. Note, you will not get a password login. There seems no good reason for a password prompt to be given so it is @@ -627,9 +658,6 @@ killall -HUP inetd - - - to make the change happen... @@ -654,14 +682,10 @@ - - - - - @listen = ( - ["gb7baa.dxcluster.net", 8000], - ["44.131.16.2", 6300], - ); + @listen = ( + ["gb7baa.dxcluster.net", 8000], + ["44.131.16.2", 6300], + ); @@ -699,6 +723,7 @@ installation. If you haven't set any there, then you should not touch these values. + o You can connect to a remote AGW engine (ie on some other machine) by changing $addr and $port appropriately. @@ -724,10 +749,10 @@ - set/node (AK1A type) - set/spider - set/dxnet - set/clx + set/node (AK1A type) + set/spider + set/dxnet + set/clx @@ -765,7 +790,6 @@ - You should get an initialisation string from DXSpider like this ... @@ -790,6 +814,9 @@ unset/node gb7baa + + + 3.6. Connection scripts Because DXSpider operates under Linux, connections can be made using @@ -856,6 +883,9 @@ There are many possible ways to configure the script but here are three examples, one for a NETRom/AX25 connect, one for AGW engines and one for tcp/ip. + + + timeout 60 abort (Busy|Sorry|Fail) # don't forget to chmod 4775 netrom_call! @@ -892,9 +922,6 @@ client gb7djk telnet - - - Both these examples assume that everything is set up properly at the other end. You will find other examples in the /spider/examples directory. @@ -914,6 +941,7 @@ + This will start a connection using the script called gb7djk-1. You can follow the connection by watching the term or console from where you started cluster.pl. From version 1.47 onwards, you will need to @@ -921,33 +949,32 @@ - - <- D G1TLH connect gb7djk-1 - -> D G1TLH connection to GB7DJK-1 started - -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z > - timeout set to 15 - CONNECT sort: telnet command: dirkl.tobit.co.uk - CHAT "login" -> "gb7djk" - received " - Red Hat Linux release 5.1 (Manhattan) - Kernel 2.0.35 on an i586 - " - received "login: " - sent "gb7djk" - CHAT "word" -> "gb7djk" - received "gb7djk" - received "Password: " - sent "gb7djk" - Connected to GB7DJK-1, starting normal protocol - <- O GB7DJK-1 telnet - -> B GB7DJK-1 0 - GB7DJK-1 channel func state 0 -> init - <- D GB7DJK-1 - <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1 - <- D GB7DJK-1 PC38^GB7DJK-1^~ - <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime - 0 00:00^5447^~ - etc + <- D G1TLH connect gb7djk-1 + -> D G1TLH connection to GB7DJK-1 started + -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z > + timeout set to 15 + CONNECT sort: telnet command: dirkl.tobit.co.uk + CHAT "login" -> "gb7djk" + received " + Red Hat Linux release 5.1 (Manhattan) + Kernel 2.0.35 on an i586 + " + received "login: " + sent "gb7djk" + CHAT "word" -> "gb7djk" + received "gb7djk" + received "Password: " + sent "gb7djk" + Connected to GB7DJK-1, starting normal protocol + <- O GB7DJK-1 telnet + -> B GB7DJK-1 0 + GB7DJK-1 channel func state 0 -> init + <- D GB7DJK-1 + <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1 + <- D GB7DJK-1 PC38^GB7DJK-1^~ + <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime + 0 00:00^5447^~ + etc @@ -961,14 +988,6 @@ This means if a node is unreachable, it will continue sending logins and logouts to users even though it is not actually connecting. To avoid this use the following line ... - - - - - - - - In a script, this might look like ... @@ -1013,6 +1032,7 @@ + So, the first connection is made by Spider. This is fine as Spider uses the Net_Telnet script from within perl. This actually uses TCP rather than TELNET so no negotiation will be done on the first @@ -1033,6 +1053,7 @@ automatically. + This is not only a way to start the cluster automatically, it also works as a watchdog, checking the sanity of DXSpider and respawning it should it crash for any reason. Before doing the following, shutdown @@ -1054,6 +1075,9 @@ This line works fine for RedHat distributions. It is also fine for SuSE up to 7.0. From Suse 7.1 you need to add runlevels 2 and 5 like this ... + + + DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 @@ -1119,7 +1143,6 @@ download the necessary software bits and bobs directly to it. There are other ways, but this is preferable. - o Another cup of good, strong tea o If all goes according to plan, about an hour to spare @@ -1228,6 +1251,7 @@ + I'm not going to bother you with exhaustive details of the rest of them, but suffice it to say you need to: @@ -1249,9 +1273,6 @@ because it suits me. - - - 4.6. Getting Spider Get the current version of the DX Spider distribution. This needs to @@ -1297,7 +1318,7 @@ - cd \spider\local + cd \spider\local @@ -1317,7 +1338,6 @@ o $mycall - Should hold the callsign of your DX Cluster - o $myname - The SysOp's first name o $myalias - the SysOp's callsign. Cannot be the same as $mycall! @@ -1362,6 +1382,8 @@ o $passwd - password that matches $login + + 5.2. Setting up the initial user files Next you need to create the initial user files, etc. A tool is @@ -1383,8 +1405,7 @@ - - perl cluster.pl + perl cluster.pl @@ -1428,8 +1449,9 @@ - cd \spider\perl - perl winclient.pl + + cd \spider\perl + perl winclient.pl @@ -1494,7 +1516,6 @@ connected to anything particularly useful at any given moment. Contact me by Email if you want me to set up a connection for you. - 6. General Information The following relates to all versions of DXSpider and is not platform @@ -1516,6 +1537,8 @@ + + The callsign involved will be the callsign of the cluster node you are going to connect to. This will now check every 10 minutes to see if gb7xxx is connected, if it is then nothing will be done. If it is @@ -1545,29 +1568,6 @@ - - - - - - - - - - - - - - - - - - - - - - - diff --git a/txt/spiderFAQ.txt b/txt/spiderFAQ.txt index 3be1c9aa..885abf99 100644 --- a/txt/spiderFAQ.txt +++ b/txt/spiderFAQ.txt @@ -1,6 +1,6 @@ The DXSpider FAQ Ian Maude, G0VGS, (ianmaude@btinternet.com) - $Date$ $Revision$ + December 2001 Revision: 1.8 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -24,6 +24,7 @@ 2.5 How can I automatically limit the amount of debug logfiles that are stored? 2.6 I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem? 2.7 Since I last updated I seem to be getting duplicate spots appearing. + 2.8 I have deleted a message but it is still there, why? ______________________________________________________________________ @@ -60,10 +61,12 @@ first need to apply patch-1.39 and then patch-1.40. + + + 11..33.. IIff II uussee aa ttaarrbbaallll ttoo oovveerrwwrriittee mmyy iinnssttaallllaattiioonn,, wwhhaatt hhaappppeennss ttoo mmyy ccoonnffiigguurraattiioonn?? - The tarballs are designed to not overwrite your existing configuration and can be used at any time to update your Spider software. All the key files have the suffix .issue (eg. DXVars.pm.issue) at default. @@ -127,9 +130,11 @@ reset the home_node using the _s_p_o_o_f command like this .. - spoof gb7adx set/home gb7adx + + + Assuming that the node_call you are changing is gb7adx. @@ -185,6 +190,67 @@ some way. Simply delete the /spider/data/dupefile and restart the cluster. It may take a little time to become fully functional but should solve your problem. + + + 22..88.. II hhaavvee ddeelleetteedd aa mmeessssaaggee bbuutt iitt iiss ssttiillll tthheerree,, wwhhyy?? + + This is now the way messages are handled for deletion in Spider. If + you look closely you will see a 'D' following the message number. + This message is marked for deletion and will be deleted in 2 days if + nothing further is done. Optionally you can use the command + _d_e_l_e_t_e_/_e_x_p_u_n_g_e to delete it immediately. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + -- 2.34.1