+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.
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;
)
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>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.
export 5467 /spider/perl/keps.in
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>would export message number 5467 as a file called keps.in in the
/spider/perl directory.
+<P>
<P>Now login to a VT as sysop and cd /spider/perl. There is a command in
the perl directory called <EM>convkeps.pl</EM>. All we need to do now is
convert the file like so ...
./convkeps.pl keps.in
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>Now go back to the cluster and issue the command ...
<P>
<BLOCKQUOTE><CODE>
load/keps
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>That is it! the kepler data has been updated.
<P>
<H2><A NAME="ss6.8">6.8 The QRZ callbook</A>
<P>
<P>In addition to the standard Red Hat distribution you will require the
following modules from
-<A HREF="http://www.cpan.org/CPAN.html">http://www.cpan.org/CPAN.html</A> ...
+<A HREF="http://www.cpan.org/CPAN.html">http://www.cpan.org/CPAN.html</A> , 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.
<P>
<P>
<UL>
<A HREF="http://www.cpan.org/modules/by-module/Time/Time-HiRes-01.20.tar.gz">Time-HiRes-01.20.tar.gz</A></LI>
</UL>
<P>
-<P>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.
+<P>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.
<P>
<P>Log in as 'root', and make sure you're at '/root' before you continue. Here are exactly the commands you must issue next: -
<P>
# cd ..
</PRE>
<P>
-<P>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.
+<P>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 <EM>IO</EM>, above.
<P>
<P>
<H2><A NAME="ss1.2">1.2 Preparation</A>
# groupadd -g 251 spider (or another number)
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>If you do not have the command <EM>groupadd</EM> available to you simply
add a line in /etc/group by hand.
<P>
# vi /etc/group (or your favorite editor)
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>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
</CODE></BLOCKQUOTE>
<P>
<P>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.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+$mycall = "GB7DJK";
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>This is the call sign of your cluster. If you use an SSID then include it here
+also.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+$myalias = "G1TLH";
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>This is the sysop user callsign, normally your own.
+<P>
+<P><B>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</B>
+<P>
+<P>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 ....
<P><CODE>$myemail = "ianmaude\@btinternet.com";</CODE>
<P>
<P>There appears to be an extra slash in there. However this has to be there
for the file to work so leave it in.
<P>
-<P><B>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</B>
-<P>
<P>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
G0VGS de GB7MBC 19-Nov-1999 2150Z >
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>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 ....
<LI>./create_sysop.pl (sysop)</LI>
<LI>./cluster.pl (sysop)</LI>
</UL>
+<P>
<P>Spider should now be running and you should be able to login using the
client program.
<P>
<LI>Enter the correct line in /etc/inetd.conf (root)</LI>
<LI>killall -HUP inetd (root)</LI>
</UL>
+<P>
<P>Spider should now be able to accept logins via telnet, netrom and ax25.
<P>
<UL>
default * * * * * * - sysop /spider/src/client client %u ax25
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>or, if you wish your users to be able to use SSID's on their callsigns ..
<P>
<BLOCKQUOTE><CODE>
default * * * * * * - sysop /spider/src/client client %s ax25
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>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
spdlogin 8000/tcp # spider anonymous login port
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>Then add a line in /etc/inetd.conf like this ....
<P>
<BLOCKQUOTE><CODE>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>
<P>Now login as <EM>sysop</EM> and cd spider/src. You can test that spider
is accepting telnet logins by issuing the following command ....
<P>
./client login telnet
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>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.
G0VGS de GB7MBC 13-Dec-1998 2043Z >
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>This will start a connection using the script called <EM>gb7djk-1</EM>. You can
follow the connection by watching the term or console from where you started
<EM>cluster.pl</EM>. From version 1.47 onwards, you will need to <CODE>set/debug connect</CODE> first.
'connect' ''
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>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
<H1>The DXSpider Installation Manual v1.49</H1>
<H2>Iain Philipps, G0RDI (g0rdi@77hz.com) and
-Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>November 2001 revision 1.0
+Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>December 2001 revision 1.1
<P><HR>
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
<HR>
cluster. It may take a little time to become fully functional but
should solve your problem.
<P>
+<H2><A NAME="ss2.8">2.8 I have deleted a message but it is still there, why?</A>
+</H2>
+
+<P>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 <EM>delete/expunge</EM>
+to delete it immediately.
+<P>
<HR>
Next
<A HREF="spiderFAQ-1.html">Previous</A>
<HR>
<H1>The DXSpider FAQ</H1>
-<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>$Date$ $Revision$
+<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>December 2001 Revision: 1.8
<P><HR>
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
<HR>
<LI><A HREF="spiderFAQ-2.html#ss2.5">2.5 How can I automatically limit the amount of debug logfiles that are stored?</A>
<LI><A HREF="spiderFAQ-2.html#ss2.6">2.6 I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?</A>
<LI><A HREF="spiderFAQ-2.html#ss2.7">2.7 Since I last updated I seem to be getting duplicate spots appearing.</A>
+<LI><A HREF="spiderFAQ-2.html#ss2.8">2.8 I have deleted a message but it is still there, why?</A>
</UL>
<HR>
<A HREF="spiderFAQ-1.html">Next</A>
)
</verb></tscreen>
+<P>
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.
export 5467 /spider/perl/keps.in
</verb></tscreen>
+<P>
would export message number 5467 as a file called keps.in in the
/spider/perl directory.
+<P>
Now login to a VT as sysop and cd /spider/perl. There is a command in
the perl directory called <em>convkeps.pl</em>. All we need to do now is
convert the file like so ...
./convkeps.pl keps.in
</verb></tscreen>
+<P>
Now go back to the cluster and issue the command ...
<tscreen><verb>
load/keps
</verb></tscreen>
+<P>
That is it! the kepler data has been updated.
<sect1>The QRZ callbook
<title>The DXSpider Installation Manual v1.49</title>
<author>Iain Philipps, G0RDI (g0rdi@77hz.com) and
Ian Maude, G0VGS, (ianmaude@btinternet.com)</author>
-<date>November 2001 revision 1.0</date>
+<date>December 2001 revision 1.1</date>
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
that you use at least version 5.005_03 as this is the version being used
in the development of Spider.
-<P>In addition to the standard Red Hat distribution you will require the
-following modules from <htmlurl url="http://www.cpan.org/CPAN.html" name="http://www.cpan.org/CPAN.html"> ...
+<P>
+In addition to the standard Red Hat distribution you will require the
+following modules from <htmlurl url="http://www.cpan.org/CPAN.html" name="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.
<P>
<itemize>
</itemize>
<P>
-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.
<P>
Log in as 'root', and make sure you're at '/root' before you continue. Here are exactly the commands you must issue next: -
</verb>
<P>
-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 <em>IO</em>, above.
<sect1>Preparation
# groupadd -g 251 spider (or another number)
</verb></tscreen>
+<P>
If you do not have the command <em>groupadd</em> available to you simply
add a line in /etc/group by hand.
# vi /etc/group (or your favorite editor)
</verb></tscreen>
+<P>
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
<P>
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.
+
+<tscreen><verb>
+$mycall = "GB7DJK";
+</verb></tscreen>
+
+<P>
+This is the call sign of your cluster. If you use an SSID then include it here
+also.
+
+<tscreen><verb>
+$myalias = "G1TLH";
+</verb></tscreen>
+
+<P>
+This is the sysop user callsign, normally your own.
+
+<P>
+<bf>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</bf>
+
+<P>
+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 ....
<tt>
$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.
-<P><bf>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</bf>
-
<P>
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
G0VGS de GB7MBC 19-Nov-1999 2150Z >
</verb></tscreen>
+<P>
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 ....
<item>./cluster.pl (sysop)
</itemize>
+<P>
Spider should now be running and you should be able to login using the
client program.
<item>killall -HUP inetd (root)
</itemize>
+<P>
Spider should now be able to accept logins via telnet, netrom and ax25.
<itemize>
default * * * * * * - sysop /spider/src/client client %u ax25
</verb></tscreen>
+<P>
or, if you wish your users to be able to use SSID's on their callsigns ..
<tscreen><verb>
default * * * * * * - sysop /spider/src/client client %s ax25
</verb></tscreen>
+<P>
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
spdlogin 8000/tcp # spider anonymous login port
</verb></tscreen>
+<P>
Then add a line in /etc/inetd.conf like this ....
<tscreen><verb>
killall -HUP inetd
</verb></tscreen>
-
-<P>Now login as <em>sysop</em> and cd spider/src. You can test that spider
+<P>
+Now login as <em>sysop</em> and cd spider/src. You can test that spider
is accepting telnet logins by issuing the following command ....
<tscreen><verb>
./client login telnet
</verb></tscreen>
+<P>
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.
connects to GB7DJK-1 [instead of a script called gb7djk-1]).
</descrip>
-
+<P>
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.
G0VGS de GB7MBC 13-Dec-1998 2043Z >
</verb></tscreen>
+<P>
This will start a connection using the script called <em>gb7djk-1</em>. You can
follow the connection by watching the term or console from where you started
<em>cluster.pl</em>. From version 1.47 onwards, you will need to <tt>set/debug connect</tt> first.
'connect' ''
</verb></tscreen>
+<P>
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
DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
</verb></tscreen>
-
+<P>
The line required for Slackware distributions is slightly different. My thanks to
Aurelio, PA3EZL for this information.
<title>The DXSpider FAQ</title>
<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)</author>
-<date>$Date$ $Revision$</date>
+<date>December 2001 Revision: 1.8</date>
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
</abstract>
cluster. It may take a little time to become fully functional but
should solve your problem.
+<sect1>I have deleted a message but it is still there, why?
+
+<P>
+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 <em>delete/expunge</em>
+to delete it immediately.
+
</article>
+
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.
+
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 ...
+
Now go back to the cluster and issue the command ...
- That is it! the kepler data has been updated.
-
+ That is it! the kepler data has been updated.
6.8. The QRZ callbook
registered users, use the command show/register.
+
7.2. Passwords
At the moment, passwords only affect users who login to a DXSpider
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
dest <prefixes> eg: 6MUK,WDX (distros)
+ some examples:-
- some examples:-
acc/ann dest 6MUK
acc/ann 2 by_zone 14,15,16
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 <prefixes> the callsign of the thingy
call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
call_itu <numbers>
- 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>
+
+
-
-
-
-
-
-
-
-
- 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>
- 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>
for example
+
accept/wwv by_zone 4
This command will send your announcement across the whole cluster
network.
-
-
-
9.12. announce sysop (5)
announce sysop <text>
apropos <string> Search the help database
-
Search the help database for <string> (it isn't case sensitive), and
print the names of all the commands that may be relevant.
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
node_default or user_default.
-
-
-
9.20. clear/wcy (0)
clear/wcy [1|all] Clear a WCY filter line
to allow
+
SH/BUCK g1tlh
to work as they may be used to.
databases. See DBSHOW for generic database enquiry
-
-
9.27. dbimport (9)
dbimport <dbname> Import AK1A data into a database
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
-
- 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
- DX by G1TLH FR0G 144.600 he isn't on the cluster
+
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
export <msgno> <filename> 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
clear/spots 1
-
To remove the filter in its entirty:-
clear/spots all
same subject will be deleted. Beware!
+
+
9.46. kill/expunge (6)
kill/expunge <msgno> [<msgno>..]Expunge a message
It otherwise is used in the same way as the KILL command.
+
9.47. links (0)
links Show which nodes are physically connected
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.
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
msg <cmd> <msgno> [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 <msgno> <call> - change TO callsign to <call>
- MSG FRom <msgno> <call> - change FROM callsign to <call>
- MSG PRrivate <msgno> - set private flag
- MSG NOPRrivate <msgno> - unset private flag
- MSG RR <msgno> - set RR flag
- MSG NORR <msgno> - unset RR flag
- MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
- MSG NOKEep <msgno> - unset the keep flag
- MSG SUbject <msgno> <new> - change the subject to <new>
- MSG WAittime <msgno> - remove any waitting time for this message
- MSG NOREad <msgno> - mark message as unread
- MSG REad <msgno> - mark message as read
- MSG QUeue - queue any outstanding bulletins
- MSG QUeue 1 - queue any outstanding private messages
+ MSG TO <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - remove any waitting time for this message
+ MSG NOREad <msgno> - mark message as unread
+ MSG REad <msgno> - mark message as read
+ MSG QUeue - queue any outstanding bulletins
+ MSG QUeue 1 - queue any outstanding private messages
+
+
+
9.60. rcmd (1)
rcmd <node call> <cmd> Send a command to another DX cluster
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)
+
some examples:-
origin_itu <numbers>
origin_zone <numbers>
-
-
-
-
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)
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:
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.
______________________________________________________________________
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.
-
-
-
-
+
If you do not have the command groupadd available to you simply add a
line in /etc/group by hand.
+
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
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 {} \;
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
- $ ./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 ...
$ ./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
+
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 ....
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)
o ./cluster.pl (sysop)
+
Spider should now be running and you should be able to login using the
client program.
o killall -HUP inetd (root)
+
Spider should now be able to accept logins via telnet, netrom and
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
spdlogin 8000/tcp # spider anonymous login port
-
-
-
Then add a line in /etc/inetd.conf like this ....
-
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
killall -HUP inetd
-
-
-
to make the change happen...
-
-
-
-
- @listen = (
- ["gb7baa.dxcluster.net", 8000],
- ["44.131.16.2", 6300],
- );
+ @listen = (
+ ["gb7baa.dxcluster.net", 8000],
+ ["44.131.16.2", 6300],
+ );
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.
- set/node (AK1A type)
- set/spider
- set/dxnet
- set/clx
+ set/node (AK1A type)
+ set/spider
+ set/dxnet
+ set/clx
-
You should get an initialisation string from DXSpider like this ...
unset/node gb7baa
+
+
+
3.6. Connection scripts
Because DXSpider operates under Linux, connections can be made using
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!
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.
+
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
-
- <- 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
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 ...
+
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
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
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
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
+
I'm not going to bother you with exhaustive details of the rest of
them, but suffice it to say you need to:
because it suits me.
-
-
-
4.6. Getting Spider
Get the current version of the DX Spider distribution. This needs to
- cd \spider\local
+ cd \spider\local
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!
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
-
- perl cluster.pl
+ perl cluster.pl
- cd \spider\perl
- perl winclient.pl
+
+ cd \spider\perl
+ perl winclient.pl
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
+
+
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
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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.
______________________________________________________________________
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?
______________________________________________________________________
first need to apply patch-1.39 and then patch-1.40.
+
+
+
1\b1.\b.3\b3.\b. I\bIf\bf I\bI u\bus\bse\be a\ba t\bta\bar\brb\bba\bal\bll\bl t\bto\bo o\bov\bve\ber\brw\bwr\bri\bit\bte\be m\bmy\by i\bin\bns\bst\bta\bal\bll\bla\bat\bti\bio\bon\bn,\b, w\bwh\bha\bat\bt h\bha\bap\bpp\bpe\ben\bns\bs t\bto\bo
m\bmy\by c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn?\b?
-
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.
reset the home_node using the _\bs_\bp_\bo_\bo_\bf command like this ..
-
spoof gb7adx set/home gb7adx
+
+
+
Assuming that the node_call you are changing is gb7adx.
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\b2.\b.8\b8.\b. I\bI h\bha\bav\bve\be d\bde\bel\ble\bet\bte\bed\bd a\ba m\bme\bes\bss\bsa\bag\bge\be b\bbu\but\bt i\bit\bt i\bis\bs s\bst\bti\bil\bll\bl t\bth\bhe\ber\bre\be,\b, w\bwh\bhy\by?\b?
+
+ 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
+ _\bd_\be_\bl_\be_\bt_\be_\b/_\be_\bx_\bp_\bu_\bn_\bg_\be to delete it immediately.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
projects / spider.git / commitdiff