hamradio/spider
1
0
Fork 0
mirror of git://scm.dxcluster.org/scm/spider synced 2024-09-20 23:37:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix some typos

Browse Source 
rearrange and update a few things in the installation manual
This commit is contained in:
minima 2005-02-09 11:10:54 +00:00
parent 4a988d6dfc
commit 4bcd914bdf
10 changed files with 386 additions and 307 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
html/installation_en-1.html
View File

@ -43,20 +43,36 @@ perl distribution.</P>
<LI>
<A HREF="http://www.cpan.org/modules/by-module/Data/Data-Dumper-2.101.tar.gz">Data-Dumper-2.101.tar.gz</A> <EM> this is included in perl 5.6.1 and above </EM></LI>
<LI>
<A HREF="http://www.cpan.org/modules/by-module/Date/TimeDate-1.10.tar.gz">TimeDate-1.10.tar.gz</A></LI>
<A HREF="http://www.cpan.org/modules/by-module/Date/TimeDate-2.27.tar.gz">TimeDate-2.27.tar.gz</A></LI>
<LI>
<A HREF="http://www.cpan.org/modules/by-module/IO/IO-1.20.tar.gz">IO-1.20.tar.gz</A> (<EM>for perl 5.00403 and lower</EM>)</LI>
<LI>
<A HREF="http://www.cpan.org/modules/by-module/Net/Net-Telnet-3.03.tar.gz">Net-Telnet-3.03.tar.gz</A></LI>
<LI>
<A HREF="http://www.cpan.org/modules/by-module/Curses/Curses-1.06.tar.gz">Curses-1.06.tar.gz</A></LI>
<A HREF="http://www.cpan.org/modules/by-module/Curses/Curses-1.08a.tar.gz">Curses-1.08a.tar.gz</A></LI>
<LI>
<A HREF="http://www.cpan.org/modules/by-module/Time/Time-HiRes-01.20.tar.gz">Time-HiRes-01.20.tar.gz</A></LI>
<A HREF="http://www.cpan.org/modules/by-module/Time/Time-HiRes-01.20.tar.gz">Time-HiRes-01.20.tar.gz</A> (<EM>for perl versions lower than 5.8 </EM>)</LI>
<LI>
<A HREF="http://www.cpan.org/modules/by-module/Digest/Digest-SHA1-2.01.tar.gz">Digest-SHA1-2.01.tar.gz</A></LI>
</UL>
</P>
<P>
On most modern distributions most (if not all) the modules you will need are either included or
can be loaded automatically. Please consult your distro's instructions for loading new programs
and look for modules that usually start with the string "perl-". For instance:-</P>
<P>
<UL>
<LI>Mandrake: urpmi perl-TimeDate perl-Digest-SHA1 perl-Curses perl-Net-Telnet</LI>
<LI>Redhat/Fedora: up2date perl-TimeDate perl-Digest-SHA1 perl-Curses perl-Net-Telnet</LI>
<LI>SuSE: use yast</LI>
<LI>Debian: use apt-get</LI>
</UL>
</P>
<P>Some distros are now packaging perl-DB_File separately as well, so you may have to add that to the list
above.</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>
@ -64,8 +80,8 @@ 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>
<P>
<PRE>
# tar xvfz /usr/local/packages/TimeDate-1.10.tar.gz
# cd TimeDate-1.10
# tar xvfz /usr/local/packages/TimeDate-2.27.tar.gz
# cd TimeDate-2.27
# perl Makefile.PL
# make test
# make install
@ -78,8 +94,8 @@ that's where you have put them.</P>
# make install
# cd ..
#
# tar xvfz /usr/local/packages/Curses-1.06.tar.gz
# cd Curses-1.06
# tar xvfz /usr/local/packages/Curses-1.08a.tar.gz
# cd Curses-1.08a
# perl Makefile.PL
# make test
# make install
@ -101,7 +117,7 @@ that's where you have put them.</P>
</PRE>
</P>
<P>Only if you need to do these (because your perl is old):-</P>
<P>Only if you need to do these because your perl is old:-</P>
<P>
<PRE>
#

125
html/installation_en-4.html
View File

@ -20,12 +20,75 @@
<P>This is dealt with in the previous section</P>
<H2><A NAME="ss4.2">4.2</A> <A HREF="installation_en.html#toc4.2">Allowing telnet connects from users </A>
<H2><A NAME="ss4.2">4.2</A> <A HREF="installation_en.html#toc4.2">Setting up telnet connects (from 1.47 onwards)</A>
</H2>
<P>>From version 1.47 you can choose to allow the perl cluster.pl program to
allow connections directly (i.e. not via the <CODE>/spider/src/client</CODE>
interface program). If you are using Windows then this is the only method
available of allowing incoming telnet connections.</P>
<P>to make the change happen...</P>
<P>Having done that, you need to copy the file
<EM>/spider/perl/Listeners.pm</EM> to <EM>/spider/local</EM> and
then edit it. You will need to uncomment the line containing &quot;0.0.0.0&quot;
and select the correct port to listen on.</P>
<P>It comes out of the box looking something like:-</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
@listen = (
# ["0.0.0.0", 7300],
);
</PRE>
</CODE></BLOCKQUOTE>
</P>
<P>Change it so that it looks like this:-</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
@listen = (
["0.0.0.0", 7300],
);
</PRE>
</CODE></BLOCKQUOTE>
</P>
<P>Later versions have more comments in the Listeners.pm file that
are designed to help you remove the correct '#' character.</P>
<P>As standard, the listener will listen on all interfaces simultaneously.
If you require more control than this, you can specify each interface
individually:-</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
@listen = (
["gb7baa.dxcluster.net", 7300],
["44.131.16.2", 6300],
);
</PRE>
</CODE></BLOCKQUOTE>
</P>
<P>This will only be successful if the IP addresses on each interface are static.
If you are using some kind of dynamic IP addressing then the 'default' method
is the only one that will work.</P>
<P>Restart the cluster.pl program to enable the listener.</P>
<P>One important difference with the internal listener is that no echoing
is done by the cluster program. Users will need to set 'local-echo' on in
their telnet clients if it isn't set automatically (as per the standards).
Needless to say this will probably only apply to Windows users. </P>
<H2><A NAME="ss4.3">4.3</A> <A HREF="installation_en.html#toc4.3">Allowing telnet connects from users (before version 1.47 or for special purposes)</A>
</H2>
<P>
>From version 1.47 there is a new (more efficient) way of doing this
(see next section) but, if you prefer, the method of doing it described
(see previous section) but, if you prefer, the method of doing it described
here will continue to work just fine.</P>
<P>Allowing telnet connections is quite simple. Firstly you need to add a line
@ -81,64 +144,6 @@ telnet localhost 8000
<P>You should now get the login prompt and be able to login as before.</P>
<H2><A NAME="ss4.3">4.3</A> <A HREF="installation_en.html#toc4.3">Setting up telnet connects (from 1.47 onwards)</A>
</H2>
<P>>From version 1.47 you can choose to allow the perl cluster.pl program to
allow connections directly (i.e. not via the <CODE>/spider/src/client</CODE>
interface program). If you are using Windows then this is the only method
available of allowing incoming telnet connections.</P>
<P>To do this you need first to remove any line that you may previously have set
up in /etc/inetd.conf. Remember to:-</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
killall -HUP inetd
</PRE>
</CODE></BLOCKQUOTE>
</P>
<P>to make the change happen...</P>
<P>Having done that, you need to copy the file
<EM>/spider/perl/Listeners.pm</EM> to <EM>/spider/local</EM> and
then edit it. You will need to uncomment the line containing &quot;0.0.0.0&quot;
and select the correct port to listen on. So that it looks like this:-</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
@listen = (
["0.0.0.0", 8000],
);
</PRE>
</CODE></BLOCKQUOTE>
</P>
<P>As standard, the listener will listen on all interfaces simultaneously.
If you require more control than this, you can specify each interface
individually:-</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
@listen = (
["gb7baa.dxcluster.net", 8000],
["44.131.16.2", 6300],
);
</PRE>
</CODE></BLOCKQUOTE>
</P>
<P>This will only be successful if the IP addresses on each interface are static.
If you are using some kind of dynamic IP addressing then the 'default' method
is the only one that will work.</P>
<P>Restart the cluster.pl program to enable the listener.</P>
<P>One important difference with the internal listener is that no echoing
is done by the cluster program. Users will need to set 'local-echo' on in
their telnet clients if it isn't set automatically (as per the standards).
Needless to say this will probably only apply to Windows users. </P>
<H2><A NAME="ss4.4">4.4</A> <A HREF="installation_en.html#toc4.4">Setting up for AGW Engine (1.47 onwards)</A>
</H2>

4
html/installation_en.html
View File

@ -55,8 +55,8 @@ Carroll, K1XX, (k1xx@ptcnh.net)</H2>March 2003 revision 0.7
<UL>
<LI><A NAME="toc4.1">4.1</A> <A HREF="installation_en-4.html#ss4.1">Allowing ax25 connects from users</A>
<LI><A NAME="toc4.2">4.2</A> <A HREF="installation_en-4.html#ss4.2">Allowing telnet connects from users </A>
<LI><A NAME="toc4.3">4.3</A> <A HREF="installation_en-4.html#ss4.3">Setting up telnet connects (from 1.47 onwards)</A>
<LI><A NAME="toc4.2">4.2</A> <A HREF="installation_en-4.html#ss4.2">Setting up telnet connects (from 1.47 onwards)</A>
<LI><A NAME="toc4.3">4.3</A> <A HREF="installation_en-4.html#ss4.3">Allowing telnet connects from users (before version 1.47 or for special purposes)</A>
<LI><A NAME="toc4.4">4.4</A> <A HREF="installation_en-4.html#ss4.4">Setting up for AGW Engine (1.47 onwards)</A>
<LI><A NAME="toc4.5">4.5</A> <A HREF="installation_en-4.html#ss4.5">Setting up node connects</A>
<LI><A NAME="toc4.6">4.6</A> <A HREF="installation_en-4.html#ss4.6">Connection scripts</A>

2
html/spiderFAQ_en-1.html
View File

@ -45,7 +45,7 @@ to apply patch-1.39 and then patch-1.40.</P>
<P>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.</P>
files have the suffix .issue (eg. DXVars.pm.issue) at default. </P>
<H2><A NAME="ss1.4">1.4</A> <A HREF="spiderFAQ_en.html#toc1.4">I am running RedHat 5.2 and I am getting strange errors, what is wrong?</A>
</H2>

27
html/spiderFAQ_en-2.html
View File

@ -55,8 +55,9 @@ watchdbg G0VGS
<P>Please check the time on your PC. </P>
<P>All spots are checked that they are no more
than 15 minutes in the future and 60 minutes in the past. If your clock is not set
to GMT (UTC) and is more than one hour out (say on your local (summer) time) then
than 15 minutes in the future and 60 minutes in the past. If your clock on your client
prompt (or console.pl display) is not set to the correct time
in GMT (UTC) and is more than one hour out (say on your local (summer) time) then
the test will fail and no spots will come out. Neither will they be stored.</P>
<P>If you are connected to the internet, most linux distributions have an implementation of
@ -102,7 +103,8 @@ take effect.</P>
</CODE></BLOCKQUOTE>
</P>
<P>Remember to make it executable!</P>
<P>This will limit your debug data down to the last 10 days</P>
<P>This will limit your debug data down to the last 10 days. </P>
<P>However, modern versions of DXSpider will do this for you, so this is now probably unnecessary.</P>
<H2><A NAME="ss2.7">2.7</A> <A HREF="spiderFAQ_en.html#toc2.7">I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?</A>
</H2>
@ -113,7 +115,7 @@ few steps to correct the problem.</P>
<UL>
<LI>stop the cluster (disable any autostart in inittab)</LI>
<LI>cd /spider/data</LI>
<LI>issue the command perl user_asc</LI>
<LI>issue the command: perl user_asc</LI>
<LI>restart the cluster</LI>
</UL>
</P>
@ -136,10 +138,10 @@ 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>
<H2><A NAME="ss2.10">2.10</A> <A HREF="spiderFAQ_en.html#toc2.10">I am updating from CVS and I get all sorts of errors when I restart</A>
<H2><A NAME="ss2.10">2.10</A> <A HREF="spiderFAQ_en.html#toc2.10">I have updated from CVS and I get all sorts of errors when I restart</A>
</H2>
<P>Firstly, whenever you update from CVS, a log is displayed. Next to each
<P>Whenever you update from CVS, a log is displayed. Next to each
file that is downloaded there is a letter, e.g.:</P>
<P>
<BLOCKQUOTE><CODE>
@ -161,9 +163,10 @@ U DXProt.pm
</CODE></BLOCKQUOTE>
</P>
<P>For normal CVS use you should only ever see the letter 'P'. This means that the file has
changed in CVS and is more recent than the one that is currenly on your system. You may also
possibly see the letter '?', which means that
<P>For normal CVS use you should only ever see the letters 'P', 'U' or '?'. The
letter 'P' means that the file has
changed in CVS and is more recent than the one that is currently on your system. You will also
see the letter '?', which means that
there is a file that you (or the system) has created that CVS doesn't know about and isn't
under its control. These are all normal and good.</P>
@ -176,7 +179,7 @@ modifications which CVS wants to download to your system. For the 'M', CVS think
is OK to make the change (you may also see some messages about "merging revision 1.xx with 1.yy").
Neither of these things are good. Files that are under the control of CVS
must not be changed by sysops. It is the files that have the 'C' next to them that will show
the errors and they will be things like:-</P>
the errors that you are complaining about and they will be things like:-</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
@ -187,7 +190,7 @@ Syntax error near '>>>' at line 51
</CODE></BLOCKQUOTE>
</P>
<P>You will now necessarily see all of the errors shown but you will get one or more sets of some
<P>You will not necessarily see all of the errors shown but you will get one or more sets of some
of them. The cure is simple: </P>
<P>
<UL>
@ -218,7 +221,7 @@ cvs -z3 update -d
</CODE></BLOCKQUOTE>
</P>
<P>The '-d' is crucial. It makes sure that any new directories that may contain new code
<P>The '-d' is crucial. It makes sure that any new directories, that may contain new code,
are created and that new code downloaded. I have absolutely no idea why this is not the
default, seeing as CVS (in other circumstances) happily recurses its merry way down a
directory tree, but there you are.</P>

2
html/spiderFAQ_en.html
View File

@ -44,7 +44,7 @@ Contents
<LI><A NAME="toc2.7">2.7</A> <A HREF="spiderFAQ_en-2.html#ss2.7">I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?</A>
<LI><A NAME="toc2.8">2.8</A> <A HREF="spiderFAQ_en-2.html#ss2.8">Since I last updated I seem to be getting duplicate spots appearing.</A>
<LI><A NAME="toc2.9">2.9</A> <A HREF="spiderFAQ_en-2.html#ss2.9">I have deleted a message but it is still there, why?</A>
<LI><A NAME="toc2.10">2.10</A> <A HREF="spiderFAQ_en-2.html#ss2.10">I am updating from CVS and I get all sorts of errors when I restart</A>
<LI><A NAME="toc2.10">2.10</A> <A HREF="spiderFAQ_en-2.html#ss2.10">I have updated from CVS and I get all sorts of errors when I restart</A>
<LI><A NAME="toc2.11">2.11</A> <A HREF="spiderFAQ_en-2.html#ss2.11">I have done a CVS update, restarted and it says that "fileX" is missing</A>
</UL>
<HR>

155
sgml/installation_en.sgml
View File

@ -49,14 +49,30 @@ perl distribution.
<P>
<itemize>
<item> <htmlurl url="http://www.cpan.org/modules/by-module/Data/Data-Dumper-2.101.tar.gz" name="Data-Dumper-2.101.tar.gz"> <em> this is included in perl 5.6.1 and above </em>
<item> <htmlurl url="http://www.cpan.org/modules/by-module/Date/TimeDate-1.10.tar.gz" name="TimeDate-1.10.tar.gz">
<item> <htmlurl url="http://www.cpan.org/modules/by-module/Date/TimeDate-2.27.tar.gz" name="TimeDate-2.27.tar.gz">
<item> <htmlurl url="http://www.cpan.org/modules/by-module/IO/IO-1.20.tar.gz" name="IO-1.20.tar.gz"> (<em>for perl 5.00403 and lower</em>)
<item> <htmlurl url="http://www.cpan.org/modules/by-module/Net/Net-Telnet-3.03.tar.gz" name="Net-Telnet-3.03.tar.gz">
<item> <htmlurl url="http://www.cpan.org/modules/by-module/Curses/Curses-1.06.tar.gz" name="Curses-1.06.tar.gz">
<item> <htmlurl url="http://www.cpan.org/modules/by-module/Time/Time-HiRes-01.20.tar.gz" name="Time-HiRes-01.20.tar.gz">
<item> <htmlurl url="http://www.cpan.org/modules/by-module/Curses/Curses-1.08a.tar.gz" name="Curses-1.08a.tar.gz">
<item> <htmlurl url="http://www.cpan.org/modules/by-module/Time/Time-HiRes-01.20.tar.gz" name="Time-HiRes-01.20.tar.gz"> (<em>for perl versions lower than 5.8 </em>)
<item> <htmlurl url="http://www.cpan.org/modules/by-module/Digest/Digest-SHA1-2.01.tar.gz" name="Digest-SHA1-2.01.tar.gz">
</itemize>
<P>
On most modern distributions most (if not all) the modules you will need are either included or
can be loaded automatically. Please consult your distro's instructions for loading new programs
and look for modules that usually start with the string "perl-". For instance:-
<itemize>
<item>Mandrake: urpmi perl-TimeDate perl-Digest-SHA1 perl-Curses perl-Net-Telnet
<item>Redhat/Fedora: up2date perl-TimeDate perl-Digest-SHA1 perl-Curses perl-Net-Telnet
<item>SuSE: use yast
<item>Debian: use apt-get
</itemize>
<p>
Some distros are now packaging perl-DB_File separately as well, so you may have to add that to the list
above.
<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
@ -66,8 +82,8 @@ 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: -
<verb>
# tar xvfz /usr/local/packages/TimeDate-1.10.tar.gz
# cd TimeDate-1.10
# tar xvfz /usr/local/packages/TimeDate-2.27.tar.gz
# cd TimeDate-2.27
# perl Makefile.PL
# make test
# make install
@ -80,8 +96,8 @@ Log in as 'root', and make sure you're at '/root' before you continue. Here are
# make install
# cd ..
#
# tar xvfz /usr/local/packages/Curses-1.06.tar.gz
# cd Curses-1.06
# tar xvfz /usr/local/packages/Curses-1.08a.tar.gz
# cd Curses-1.08a
# perl Makefile.PL
# make test
# make install
@ -103,7 +119,7 @@ Log in as 'root', and make sure you're at '/root' before you continue. Here are
</verb>
<p>
Only if you need to do these (because your perl is old):-
Only if you need to do these because your perl is old:-
<verb>
#
@ -893,11 +909,74 @@ netrom connections.
<P>
This is dealt with in the previous section
<sect1>Allowing telnet connects from users
<sect1>Setting up telnet connects (from 1.47 onwards)
<P>
>From version 1.47 you can choose to allow the perl cluster.pl program to
allow connections directly (i.e. not via the <tt>/spider/src/client</tt>
interface program). If you are using Windows then this is the only method
available of allowing incoming telnet connections.
<P>
to make the change happen...
<P>
Having done that, you need to copy the file
<em>/spider/perl/Listeners.pm</em> to <em>/spider/local</em> and
then edit it. You will need to uncomment the line containing &dquot;0.0.0.0&dquot;
and select the correct port to listen on.
It comes out of the box looking something like:-
<tscreen><verb>
@listen = (
# ["0.0.0.0", 7300],
);
</verb></tscreen>
Change it so that it looks like this:-
<tscreen><verb>
@listen = (
["0.0.0.0", 7300],
);
</verb></tscreen>
<p>
Later versions have more comments in the Listeners.pm file that
are designed to help you remove the correct '#' character.
<P>
As standard, the listener will listen on all interfaces simultaneously.
If you require more control than this, you can specify each interface
individually:-
<tscreen><verb>
@listen = (
["gb7baa.dxcluster.net", 7300],
["44.131.16.2", 6300],
);
</verb></tscreen>
<P>
This will only be successful if the IP addresses on each interface are static.
If you are using some kind of dynamic IP addressing then the 'default' method
is the only one that will work.
<P>
Restart the cluster.pl program to enable the listener.
<P>
One important difference with the internal listener is that no echoing
is done by the cluster program. Users will need to set 'local-echo' on in
their telnet clients if it isn't set automatically (as per the standards).
Needless to say this will probably only apply to Windows users.
<sect1>Allowing telnet connects from users (before version 1.47 or for special purposes)
<P>
>From version 1.47 there is a new (more efficient) way of doing this
(see next section) but, if you prefer, the method of doing it described
(see previous section) but, if you prefer, the method of doing it described
here will continue to work just fine.
<P>
@ -945,62 +1024,6 @@ telnet localhost 8000
<P>
You should now get the login prompt and be able to login as before.
<sect1>Setting up telnet connects (from 1.47 onwards)
<P>
>From version 1.47 you can choose to allow the perl cluster.pl program to
allow connections directly (i.e. not via the <tt>/spider/src/client</tt>
interface program). If you are using Windows then this is the only method
available of allowing incoming telnet connections.
<P>
To do this you need first to remove any line that you may previously have set
up in /etc/inetd.conf. Remember to:-
<tscreen><verb>
killall -HUP inetd
</verb></tscreen>
<P>
to make the change happen...
<P>
Having done that, you need to copy the file
<em>/spider/perl/Listeners.pm</em> to <em>/spider/local</em> and
then edit it. You will need to uncomment the line containing &dquot;0.0.0.0&dquot;
and select the correct port to listen on. So that it looks like this:-
<tscreen><verb>
@listen = (
["0.0.0.0", 8000],
);
</verb></tscreen>
<P>
As standard, the listener will listen on all interfaces simultaneously.
If you require more control than this, you can specify each interface
individually:-
<tscreen><verb>
@listen = (
["gb7baa.dxcluster.net", 8000],
["44.131.16.2", 6300],
);
</verb></tscreen>
<P>
This will only be successful if the IP addresses on each interface are static.
If you are using some kind of dynamic IP addressing then the 'default' method
is the only one that will work.
<P>
Restart the cluster.pl program to enable the listener.
<P>
One important difference with the internal listener is that no echoing
is done by the cluster program. Users will need to set 'local-echo' on in
their telnet clients if it isn't set automatically (as per the standards).
Needless to say this will probably only apply to Windows users.
<sect1>Setting up for AGW Engine (1.47 onwards)

30
sgml/spiderFAQ_en.sgml
View File

@ -48,7 +48,7 @@ to apply patch-1.39 and then patch-1.40.
<P>
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.
files have the suffix .issue (eg. DXVars.pm.issue) at default.
<sect1>I am running RedHat 5.2 and I am getting strange errors, what is wrong?
@ -96,8 +96,9 @@ Please check the time on your PC.
<P>
All spots are checked that they are no more
than 15 minutes in the future and 60 minutes in the past. If your clock is not set
to GMT (UTC) and is more than one hour out (say on your local (summer) time) then
than 15 minutes in the future and 60 minutes in the past. If your clock on your client
prompt (or console.pl display) is not set to the correct time
in GMT (UTC) and is more than one hour out (say on your local (summer) time) then
the test will fail and no spots will come out. Neither will they be stored.
<P>
@ -141,7 +142,9 @@ Use the tmpwatch command. Create a file in /etc/cron.daily/ containing the line
Remember to make it executable!
This will limit your debug data down to the last 10 days
This will limit your debug data down to the last 10 days.
However, modern versions of DXSpider will do this for you, so this is now probably unnecessary.
<sect1>I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?
@ -152,7 +155,7 @@ few steps to correct the problem.
<itemize>
<item>stop the cluster (disable any autostart in inittab)
<item>cd /spider/data
<item>issue the command perl user_asc
<item>issue the command: perl user_asc
<item>restart the cluster
</itemize>
@ -175,10 +178,10 @@ 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.
<sect1>I am updating from CVS and I get all sorts of errors when I restart
<sect1>I have updated from CVS and I get all sorts of errors when I restart
<P>
Firstly, whenever you update from CVS, a log is displayed. Next to each
Whenever you update from CVS, a log is displayed. Next to each
file that is downloaded there is a letter, e.g.:
<tscreen><verb>
@ -198,9 +201,10 @@ U DXProt.pm
</verb></tscreen>
<P>
For normal CVS use you should only ever see the letter 'P'. This means that the file has
changed in CVS and is more recent than the one that is currenly on your system. You may also
possibly see the letter '?', which means that
For normal CVS use you should only ever see the letters 'P', 'U' or '?'. The
letter 'P' means that the file has
changed in CVS and is more recent than the one that is currently on your system. You will also
see the letter '?', which means that
there is a file that you (or the system) has created that CVS doesn't know about and isn't
under its control. These are all normal and good.
@ -215,7 +219,7 @@ modifications which CVS wants to download to your system. For the 'M', CVS think
is OK to make the change (you may also see some messages about "merging revision 1.xx with 1.yy").
Neither of these things are good. Files that are under the control of CVS
must not be changed by sysops. It is the files that have the 'C' next to them that will show
the errors and they will be things like:-
the errors that you are complaining about and they will be things like:-
<tscreen><verb>
Syntax error near '<<<<' at line 23
@ -224,7 +228,7 @@ Syntax error near '>>>' at line 51
</verb></tscreen>
<P>
You will now necessarily see all of the errors shown but you will get one or more sets of some
You will not necessarily see all of the errors shown but you will get one or more sets of some
of them. The cure is simple:
<itemize>
@ -254,7 +258,7 @@ cvs -z3 update -d
</verb></tscreen>
<P>
The '-d' is crucial. It makes sure that any new directories that may contain new code
The '-d' is crucial. It makes sure that any new directories, that may contain new code,
are created and that new code downloaded. I have absolutely no idea why this is not the
default, seeing as CVS (in other circumstances) happily recurses its merry way down a
directory tree, but there you are.

266
txt/installation_en.txt
View File

@ -33,8 +33,8 @@
4. Configuration
4.1 Allowing ax25 connects from users
4.2 Allowing telnet connects from users
4.3 Setting up telnet connects (from 1.47 onwards)
4.2 Setting up telnet connects (from 1.47 onwards)
4.3 Allowing telnet connects from users (before version 1.47 or for special purposes)
4.4 Setting up for AGW Engine (1.47 onwards)
4.5 Setting up node connects
4.6 Connection scripts
@ -95,19 +95,41 @@
o Data-Dumper-2.101.tar.gz this is included in perl 5.6.1 and above
o TimeDate-1.10.tar.gz
o TimeDate-2.27.tar.gz
o IO-1.20.tar.gz (for perl 5.00403 and lower)
o Net-Telnet-3.03.tar.gz
o Curses-1.06.tar.gz
o Curses-1.08a.tar.gz
o Time-HiRes-01.20.tar.gz
o Time-HiRes-01.20.tar.gz (for perl versions lower than 5.8 )
o Digest-SHA1-2.01.tar.gz
On most modern distributions most (if not all) the modules you will
need are either included or can be loaded automatically. Please
consult your distro's instructions for loading new programs and look
for modules that usually start with the string "perl-". For instance:-
o Mandrake: urpmi perl-TimeDate perl-Digest-SHA1 perl-Curses perl-
Net-Telnet
o Redhat/Fedora: up2date perl-TimeDate perl-Digest-SHA1 perl-Curses
perl-Net-Telnet
o SuSE: use yast
o Debian: use apt-get
Some distros are now packaging perl-DB_File separately as well, so you
may have to add that to the list above.
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
@ -118,9 +140,8 @@
Here are exactly the commands you must issue next: -
# tar xvfz /usr/local/packages/TimeDate-1.10.tar.gz
# cd TimeDate-1.10
# tar xvfz /usr/local/packages/TimeDate-2.27.tar.gz
# cd TimeDate-2.27
# perl Makefile.PL
# make test
# make install
@ -133,8 +154,8 @@
# make install
# cd ..
#
# tar xvfz /usr/local/packages/Curses-1.06.tar.gz
# cd Curses-1.06
# tar xvfz /usr/local/packages/Curses-1.08a.tar.gz
# cd Curses-1.08a
# perl Makefile.PL
# make test
# make install
@ -156,7 +177,8 @@
Only if you need to do these (because your perl is old):-
Only if you need to do these because your perl is old:-
#
@ -220,8 +242,6 @@
# Retype new UNIX password:
passwd: all authentication tokens updated successfully
1.3. Installing the software
Now to unpack the DX Spider distribution, set symbolic links and group
@ -241,7 +261,7 @@
# vi /etc/group (or your favorite editor)
# vi /etc/group (or your favorite editor)
@ -299,6 +319,9 @@
Using the distributed DXVars.pm as a a template, set your cluster
callsign, sysop callsign and other user info to suit your own
environment.
$mycall = "GB7DJK";
@ -396,7 +419,6 @@
$ ./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
@ -415,7 +437,7 @@
shutdown
shutdown
@ -478,7 +500,6 @@
o Enter the correct line in /etc/services (root)
o Enter the correct line in /etc/inetd.conf (root)
o killall -HUP inetd (root)
@ -526,7 +547,6 @@
more comprehensive and an interesting configuration program is also
available called ax25-config which may help you to configure things.
The following files are extracts from the working files at GB7MBC and
are in daily use. However, there are many ways that you can configure
the ax25 utils, this is just the one I use, it does not mean it is
@ -545,6 +565,8 @@
There are 2 main node packages in use of which I shall keep to the
original by Tomi Manninen, OH2BNS as this is included in the ax25 rpms
as standard. The other is AWZNode by IZ5AWZ.
NB: The AX25 stuff in 2.4 kernels appears to have been broken until
2.4.18. I strongly suggest you get at least this kernel.
@ -591,7 +613,6 @@
rpm -ivh ax25-apps-0.0.4-9.i386.rpm
3.4. Configuration
You will find the configuration files in /etc/ax25. These consist of
@ -655,9 +676,9 @@
#portname callsign alias paclen description
netrom gb7mbc-8 BARE 236 Node Netrom Port
netrom2 gb7mbc-9 MBCDX 236 Cluster Netrom Port
#portname callsign alias paclen description
netrom gb7mbc-8 BARE 236 Node Netrom Port
netrom2 gb7mbc-9 MBCDX 236 Cluster Netrom Port
@ -667,7 +688,6 @@
The file headings are as follows ...
portname - The name you will refer to the port by
callsign - This is the callsign that NET/ROM traffic from this
port will use
@ -1018,11 +1038,79 @@
This is dealt with in the previous section
4.2. Allowing telnet connects from users
4.2. Setting up telnet connects (from 1.47 onwards)
>From version 1.47 you can choose to allow the perl cluster.pl program
to allow connections directly (i.e. not via the /spider/src/client
interface program). If you are using Windows then this is the only
method available of allowing incoming telnet connections.
to make the change happen...
Having done that, you need to copy the file /spider/perl/Listeners.pm
to /spider/local and then edit it. You will need to uncomment the line
containing "0.0.0.0" and select the correct port to listen on.
It comes out of the box looking something like:-
@listen = (
# ["0.0.0.0", 7300],
);
Change it so that it looks like this:-
@listen = (
["0.0.0.0", 7300],
);
Later versions have more comments in the Listeners.pm file that are
designed to help you remove the correct '#' character.
As standard, the listener will listen on all interfaces
simultaneously. If you require more control than this, you can
specify each interface individually:-
@listen = (
["gb7baa.dxcluster.net", 7300],
["44.131.16.2", 6300],
);
This will only be successful if the IP addresses on each interface are
static. If you are using some kind of dynamic IP addressing then the
'default' method is the only one that will work.
Restart the cluster.pl program to enable the listener.
One important difference with the internal listener is that no echoing
is done by the cluster program. Users will need to set 'local-echo' on
in their telnet clients if it isn't set automatically (as per the
standards). Needless to say this will probably only apply to Windows
users.
4.3. Allowing telnet connects from users (before version 1.47 or for
special purposes)
>From version 1.47 there is a new (more efficient) way of doing this
(see next section) but, if you prefer, the method of doing it
(see previous section) but, if you prefer, the method of doing it
described here will continue to work just fine.
@ -1030,14 +1118,14 @@
a line 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 ....
spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
@ -1076,66 +1164,6 @@
You should now get the login prompt and be able to login as before.
4.3. Setting up telnet connects (from 1.47 onwards)
>From version 1.47 you can choose to allow the perl cluster.pl program
to allow connections directly (i.e. not via the /spider/src/client
interface program). If you are using Windows then this is the only
method available of allowing incoming telnet connections.
To do this you need first to remove any line that you may previously
have set up in /etc/inetd.conf. Remember to:-
killall -HUP inetd
to make the change happen...
Having done that, you need to copy the file /spider/perl/Listeners.pm
to /spider/local and then edit it. You will need to uncomment the line
containing "0.0.0.0" and select the correct port to listen on. So that
it looks like this:-
@listen = (
["0.0.0.0", 8000],
);
As standard, the listener will listen on all interfaces
simultaneously. If you require more control than this, you can
specify each interface individually:-
@listen = (
["gb7baa.dxcluster.net", 8000],
["44.131.16.2", 6300],
);
This will only be successful if the IP addresses on each interface are
static. If you are using some kind of dynamic IP addressing then the
'default' method is the only one that will work.
Restart the cluster.pl program to enable the listener.
One important difference with the internal listener is that no echoing
is done by the cluster program. Users will need to set 'local-echo' on
in their telnet clients if it isn't set automatically (as per the
standards). Needless to say this will probably only apply to Windows
users.
4.4. Setting up for AGW Engine (1.47 onwards)
@ -1146,15 +1174,12 @@
In order to enable access to an AGW Engine you need to copy
/spider/perl/AGWConnect.pm to /spider/local and edit it. Specifically
you must:-
o set $enable to 1.
o set $login and $passwd to the values set up in your AGW
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.
@ -1210,7 +1235,6 @@
another console as sysop, cd to spider/src and issue the command ...
./client gb7baa (using the callsign you set as a node)
@ -1328,11 +1352,13 @@
timeout 15
connect telnet dirkl.tobit.co.uk
# tell GB7DJK-1 that it is connected to GB7DJK
# you can leave this out if you call this script 'gb7djk'
client gb7djk telnet
timeout 15
connect telnet dirkl.tobit.co.uk
# tell GB7DJK-1 that it is connected to GB7DJK
# you can leave this out if you call this script 'gb7djk'
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
@ -1396,6 +1422,9 @@
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 ...
@ -1457,7 +1486,6 @@
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
@ -1502,6 +1530,7 @@
tty you run it on.
As root type the command telinit q. DXSpider should start up
immediately. You will see the output on tty7 and if you login as
sysop you should find everything running nicely.
@ -1568,7 +1597,6 @@
any platform that has reasonably complete support for Perl. Is there
someone out there with both an enquiring mind and (say) a Macintosh,
for instance?
Please bear in mind, though, that my instructions relate solely to how
to get this going under a Microsoft Windows environment, and I have
zero intention of trying to make them say otherwise.
@ -1583,7 +1611,6 @@
noticable difficulty.) You can get this from:
http://www.activestate.com/Products/ActivePerl/Download.html
The link takes you to an initial page of System Requirements and
Software Prerequisites. If you do not have it already installed, you
can download and install the Windows Installer 2.0 for a Win98
@ -1648,16 +1675,16 @@
D:\ppm>ppm install Data-Dumper.ppd
Installing package 'Data-Dumper.ppd'
Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs
Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll
Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp
Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib
Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html
Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm
Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist
D:\ppm>
D:\ppm>ppm install Data-Dumper.ppd
Installing package 'Data-Dumper.ppd'
Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs
Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll
Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp
Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib
Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html
Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm
Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist
D:\ppm>
@ -1700,7 +1727,6 @@
unstable. Generally, there will be a note on the website if this is
the case.
The only difference between "CVSlatest.tgz" and the latest "official"
release version is that it is more up to date. Do not confuse the
"CVSlatest.tgz" file with "Downloading from Sourceforge with CVS" -
@ -1763,6 +1789,7 @@
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!
@ -1774,7 +1801,6 @@
o $mylongitude - The station longitude in degrees and decimal
fractions
o $mylocator - The Maidenhead (or QRA) locator of the station
You really also ought to update the $myqth and $myemail variables. And
@ -1828,7 +1854,6 @@
somesuch), then you need to have the machine listening at least to
"127.0.0.1" ("0.0.0.0" means all IP addresses).
6.2. The AGW packet engine
On the assumption that you'll be using the SV2AGW Packet Engine to
@ -1893,8 +1918,6 @@
cd \spider\perl
perl create_sysop.pl
If all goes according to plan, you will see no output from this
program, and after a brief wait, your DOS prompt will be returned.
@ -1902,6 +1925,7 @@
following:-
perl cluster.pl
@ -1957,13 +1981,15 @@
Menu->Start->Run
telnet localhost 7300
Menu->Start->Run
telnet localhost 7300
On getting the login: prompt, enter your sysop callsign (the one you
put in DXVars.pm as $myalias).
I would recommend strongly that you obtain a better telnet client than
that which comes with windows (I use PuTTY).
@ -2016,10 +2042,10 @@
# check every 10 minutes to see if gb7xxx is connected and if not
# start a connect job going
# check every 10 minutes to see if gb7xxx is connected and if not
# start a connect job going
0,10,20,30,40,50 * * * * start_connect('gb7xxx') unless connected('gb7xxx')
0,10,20,30,40,50 * * * * start_connect('gb7xxx') unless connected('gb7xxx')
@ -2027,6 +2053,8 @@
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
not, then a connect attempt will be started.
There are probably lots of other things you could use this crontab
file for. If you want to know more about it, look at the DXSpider
website at the cron page where it is explained more fully.

50
txt/spiderFAQ_en.txt
View File

@ -24,7 +24,7 @@
2.7 I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?
2.8 Since I last updated I seem to be getting duplicate spots appearing.
2.9 I have deleted a message but it is still there, why?
2.10 I am updating from CVS and I get all sorts of errors when I restart
2.10 I have updated from CVS and I get all sorts of errors when I restart
2.11 I have done a CVS update, restarted and it says that "fileX" is missing
@ -121,10 +121,11 @@
All spots are checked that they are no more than 15 minutes in the
future and 60 minutes in the past. If your clock is not set to GMT
(UTC) and is more than one hour out (say on your local (summer) time)
then the test will fail and no spots will come out. Neither will they
be stored.
future and 60 minutes in the past. If your clock on your client prompt
(or console.pl display) is not set to the correct time in GMT (UTC)
and is more than one hour out (say on your local (summer) time) then
the test will fail and no spots will come out. Neither will they be
stored.
If you are connected to the internet, most linux distributions have an
@ -174,7 +175,10 @@
Remember to make it executable!
This will limit your debug data down to the last 10 days
This will limit your debug data down to the last 10 days.
However, modern versions of DXSpider will do this for you, so this is
now probably unnecessary.
2.7. I updated my Linux distribution and now Spider cannot read the
@ -183,13 +187,11 @@
Almost certainly this is a change in the db format of perl. Follow
these few steps to correct the problem.
o stop the cluster (disable any autostart in inittab)
o cd /spider/data
o issue the command perl user_asc
o issue the command: perl user_asc
o restart the cluster
@ -214,11 +216,11 @@
delete/expunge to delete it immediately.
2.10. I am updating from CVS and I get all sorts of errors when I
2.10. I have updated from CVS and I get all sorts of errors when I
restart
Firstly, whenever you update from CVS, a log is displayed. Next to
each file that is downloaded there is a letter, e.g.:
Whenever you update from CVS, a log is displayed. Next to each file
that is downloaded there is a letter, e.g.:
@ -238,19 +240,17 @@
For normal CVS use you should only ever see the letter 'P'. This means
that the file has changed in CVS and is more recent than the one that
is currenly on your system. You may also possibly see the letter '?',
which means that there is a file that you (or the system) has created
that CVS doesn't know about and isn't under its control. These are all
normal and good.
For normal CVS use you should only ever see the letters 'P', 'U' or
'?'. The letter 'P' means that the file has changed in CVS and is more
recent than the one that is currently on your system. You will also
see the letter '?', which means that there is a file that you (or the
system) has created that CVS doesn't know about and isn't under its
control. These are all normal and good.
Sometimes you will see the letter 'U' next to a file. This means that
it is a new file that you don't currently have. This is also OK.
However, if you see the letter 'C' or 'M', that means that CVS thinks
that the file has changed locally. For the letter 'C', it has changed
sufficiently near to one or more modifications which CVS wants to
@ -258,8 +258,8 @@
the change (you may also see some messages about "merging revision
1.xx with 1.yy"). Neither of these things are good. Files that are
under the control of CVS must not be changed by sysops. It is the
files that have the 'C' next to them that will show the errors and
they will be things like:-
files that have the 'C' next to them that will show the errors that
you are complaining about and they will be things like:-
@ -269,7 +269,7 @@
You will now necessarily see all of the errors shown but you will get
You will not necessarily see all of the errors shown but you will get
one or more sets of some of them. The cure is simple:
@ -303,8 +303,8 @@
The '-d' is crucial. It makes sure that any new directories that may
contain new code are created and that new code downloaded. I have
The '-d' is crucial. It makes sure that any new directories, that may
contain new code, are created and that new code downloaded. I have
absolutely no idea why this is not the default, seeing as CVS (in
other circumstances) happily recurses its merry way down a directory
tree, but there you are.