+08Apr01=======================================================================
+1. added a quick installation guide to the admin manual and removed references
+to client.pl (g0vgs)
01Apr01=======================================================================
1. changed agwrestart semantics. You need to use main::agwrestart() in your
crontabs rather than AGWMsg::init();
</CODE></BLOCKQUOTE>
<P>
<P>If all is well then login on another term or console as <EM>sysop</EM> and
-cd to /spider/perl. Now issue the following command ...
+cd to /spider/src. Now issue the following command ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-$ ./client.pl
+$ ./client
</PRE>
</CODE></BLOCKQUOTE>
<P>
<P>
<P>and both the cluster and the client should return to Linux prompts.
<P>
+<H2><A NAME="ss1.6">1.6 The Client program</A>
+</H2>
+
+<P>In earlier versions of Spider, all the processes were Perl scripts. This
+was fine but with a lot of users your computer memory would soon be used up.
+To combat this a new client was written in "C". This client only works for
+<EM>incoming</EM> connects at the moment. Before you can use it though it
+has to be "made". CD to /spider/src and type <EM>make</EM>. You
+should see the output on your screen and hopefully now have a small C program
+called <EM>client</EM>. Leave it in this directory.
+<P>
+<P>
<HR>
<A HREF="adminmanual-2.html">Next</A>
Previous
nested under directories. One use for this would be to store DX bulletins
such as the OPDX bulletins. These can be listed and read by the user.
To keep things tidy, make a directory under /spider/packclus called
-<EM>bulletins</EM>. Now copy any OPDX or similar bulletins into it. These
+<EM>bulletin</EM>. Now copy any OPDX or similar bulletins into it. These
can be listed by the user in the same way as above using the <EM>show/files</EM>
-command with an extension for the bulletins directory you have just created,
+command with an extension for the bulletin directory you have just created,
like this ....
<P>
<BLOCKQUOTE><CODE>
<PRE>
-show/files bulletins
+show/files bulletin
</PRE>
</CODE></BLOCKQUOTE>
<P>
<BLOCKQUOTE><CODE>
<PRE>
sh/files
-bulletins DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
+bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
</PRE>
</CODE></BLOCKQUOTE>
<P>You can see that in the files area (basically the packclus directory) there is a
-file called <EM>news</EM> and a directory called <EM>bulletins</EM>. You can
+file called <EM>news</EM> and a directory called <EM>bulletin</EM>. You can
also see that dates they were created. In the case of the file <EM>news</EM>,
you can also see the time it was last modified, a good clue as to whether the
file has been updated since you last read it. To read the file called
type news
</PRE>
</CODE></BLOCKQUOTE>
-<P>To look what is in the bulletins directory you issue the command ....
+<P>To look what is in the bulletin directory you issue the command ....
<P>
<BLOCKQUOTE><CODE>
<PRE>
-show/files bulletins
+show/files bulletin
opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
<P>
<BLOCKQUOTE><CODE>
<PRE>
-type bulletins/opdx391
+type bulletin/opdx391
Ohio/Penn DX Bulletin No. 391
The Ohio/Penn Dx PacketCluster
DX Bulletin No. 391
<P>In later versions of Spider a simple console program is provided for the sysop.
This has a type ahead buffer with line editing facilities and colour for spots,
-announces etc. To use this program, simply use console.pl instead of client.pl.
+announces etc. To use this program, simply use console.pl instead of client.
<P>
<P>To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
file with your favourite editor.
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : The Client program</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual : Quick installation guide</TITLE>
<LINK HREF="adminmanual-3.html" REL=next>
<LINK HREF="adminmanual-1.html" REL=previous>
<LINK HREF="adminmanual.html#toc2" REL=contents>
<A HREF="adminmanual-1.html">Previous</A>
<A HREF="adminmanual.html#toc2">Contents</A>
<HR>
-<H2><A NAME="s2">2. The Client program</A></H2>
+<H2><A NAME="s2">2. Quick installation guide</A></H2>
-<P>In earlier versions of Spider, all the processes were Perl scripts. This
-was fine but with a lot of users your computer memory would soon be used up.
-To combat this a new client was written in "C". This client only works for
-<EM>incoming</EM> connects at the moment. Before you can use it though it
-has to be "made". CD to /spider/src and type <EM>make</EM>. You
-should see the output on your screen and hopefully now have a small C program
-called <EM>client</EM>. Leave it in this directory.
+<P>This section is designed for experienced Spider sysops who want to install
+Spider from scratch. It is simply a check list of things that need to be
+done without any explanations. The name in brackets at the end of each line
+is the user that should be doing that process.
+<P>
+<UL>
+<LI>Login as root</LI>
+<LI>Get the additional CPAN modules and install them (root)</LI>
+<LI>Create the "sysop" user and set a password (root)</LI>
+<LI>Put the Spider tarball in sysop and untar it (root)</LI>
+<LI>ln -s sysop/spider /spider (root)</LI>
+<LI>groupadd -g 251 spider (root)</LI>
+<LI>Add any more users you need to the group entry in /etc/group (root)</LI>
+<LI>Set the permissions on the spider tree (root)</LI>
+<LI>Fix permissions on ax25_call and netrom_call (root)</LI>
+<LI>Login as the sysop user</LI>
+<LI>cd to /spider (sysop)</LI>
+<LI>mkdir local (sysop</LI>
+<LI>mkdir local_cmd (sysop)</LI>
+<LI>cp perl/DXVars.pm.issue local/DXVars.pm (sysop)</LI>
+<LI>cd to /spider/local and edit DXVars to set your details (sysop)</LI>
+<LI>cd ../perl (sysop)</LI>
+<LI>./create_sysop.pl (sysop)</LI>
+<LI>./cluster.pl (sysop)</LI>
+</UL>
+<P>Spider should now be running and you should be able to login using the
+client program.
+<P>
+<UL>
+<LI>Login as root</LI>
+<LI>Enter the correct line in ax25d.conf (root)</LI>
+<LI>Enter the correct line in /etc/services (root)</LI>
+<LI>Enter the correct line in /etc/inetd.conf (root)</LI>
+<LI>killall -HUP inetd (root)</LI>
+</UL>
+<P>Spider should now be able to accept logins via telnet, netrom and ax25.
+<P>
+<UL>
+<LI>Login as sysop</LI>
+<LI>Start the cluster (sysop)</LI>
+<LI>set/node and type for links (sysop)</LI>
+<LI>Write any connect scripts (sysop)</LI>
+<LI>Edit /spider/crontab as required (sysop)</LI>
+<LI>Edit any other files as necessary (sysop)</LI>
+<LI>Set filters, hops and forwarding files (sysop)</LI>
+<LI>Login as root</LI>
+<LI>Enter the correct line in /etc/inittab (root)</LI>
+</UL>
<P>
<HR>
<A HREF="adminmanual-3.html">Next</A>
</CODE></BLOCKQUOTE>
<P>
<P>
-<P>Now login as <EM>sysop</EM> and cd spider/perl. 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 ....
<P>
<BLOCKQUOTE><CODE>
<PRE>
-./client.pl login telnet
+./client login telnet
</PRE>
</CODE></BLOCKQUOTE>
<P>You should get a login prompt and on issuing a callsign, you will be given
<P>For now, we will assume that the cluster we are going to connect to is an
AK1A type node.
<P>
-<P>Start up the cluster as you did before and login as the sysop with client.pl.
+<P>Start up the cluster as you did before and login as the sysop with client.
The cluster node I am wanting to make a connection to is GB7BAA but you would
obviously use whatever callsign you required. At the prompt type ...
<P>
1.33. Earlier versions required the callsign to be in upper case.
<P>
<P>That is now set, it is as simple as that. To prove it, login on yet another
-console as sysop, cd to spider/perl and issue the command ...
+console as sysop, cd to spider/src and issue the command ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-./client.pl gb7baa (using the callsign you set as a node)
+./client gb7baa (using the callsign you set as a node)
</PRE>
</CODE></BLOCKQUOTE>
<P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
-./client.pl gb7baa
+./client gb7baa
PC38^GB7MBC^~
</PRE>
</CODE></BLOCKQUOTE>
<HR>
<H1>The DXSpider Installation and Administration Manual </H1>
-<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.33 (Revision 1.22) March 2001
+<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.34 (Revision 1.0) April 2001
<P><HR>
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
<HR>
<LI><A HREF="adminmanual-1.html#ss1.3">1.3 Installing the software</A>
<LI><A HREF="adminmanual-1.html#ss1.4">1.4 Setting callsigns etc</A>
<LI><A HREF="adminmanual-1.html#ss1.5">1.5 Starting up for the first time</A>
+<LI><A HREF="adminmanual-1.html#ss1.6">1.6 The Client program</A>
</UL>
<P>
-<H2><A NAME="toc2">2.</A> <A HREF="adminmanual-2.html">The Client program</A></H2>
+<H2><A NAME="toc2">2.</A> <A HREF="adminmanual-2.html">Quick installation guide</A></H2>
<P>
<H2><A NAME="toc3">3.</A> <A HREF="adminmanual-3.html">Configuration</A></H2>
<title>The DXSpider Installation and Administration Manual
<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
-<date>Version 1.33 (Revision 1.22) March 2001
+<date>Version 1.34 (Revision 1.0) April 2001
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
</abstract>
<P>
If all is well then login on another term or console as <em>sysop</em> and
-cd to /spider/perl. Now issue the following command ...
+cd to /spider/src. Now issue the following command ...
<tscreen><verb>
-$ ./client.pl
+$ ./client
</verb></tscreen>
<P>
<P>
and both the cluster and the client should return to Linux prompts.
-<sect>The Client program
+<sect1>The Client program
<P>
In earlier versions of Spider, all the processes were Perl scripts. This
should see the output on your screen and hopefully now have a small C program
called <em>client</em>. Leave it in this directory.
+
+<sect>Quick installation guide
+
+<P>
+This section is designed for experienced Spider sysops who want to install
+Spider from scratch. It is simply a check list of things that need to be
+done without any explanations. The name in brackets at the end of each line
+is the user that should be doing that process.
+
+<itemize>
+<item>Login as root
+<item>Get the additional CPAN modules and install them (root)
+<item>Create the "sysop" user and set a password (root)
+<item>Put the Spider tarball in ~sysop and untar it (root)
+<item>ln -s ~sysop/spider /spider (root)
+<item>groupadd -g 251 spider (root)
+<item>Add any more users you need to the group entry in /etc/group (root)
+<item>Set the permissions on the spider tree (root)
+<item>Fix permissions on ax25_call and netrom_call (root)
+<item>Login as the sysop user
+<item>cd to /spider (sysop)
+<item>mkdir local (sysop
+<item>mkdir local_cmd (sysop)
+<item>cp perl/DXVars.pm.issue local/DXVars.pm (sysop)
+<item>cd to /spider/local and edit DXVars to set your details (sysop)
+<item>cd ../perl (sysop)
+<item>./create_sysop.pl (sysop)
+<item>./cluster.pl (sysop)
+</itemize>
+
+Spider should now be running and you should be able to login using the
+client program.
+
+<itemize>
+<item>Login as root
+<item>Enter the correct line in ax25d.conf (root)
+<item>Enter the correct line in /etc/services (root)
+<item>Enter the correct line in /etc/inetd.conf (root)
+<item>killall -HUP inetd (root)
+</itemize>
+
+Spider should now be able to accept logins via telnet, netrom and ax25.
+
+<itemize>
+<item>Login as sysop
+<item>Start the cluster (sysop)
+<item>set/node and type for links (sysop)
+<item>Write any connect scripts (sysop)
+<item>Edit /spider/crontab as required (sysop)
+<item>Edit any other files as necessary (sysop)
+<item>Set filters, hops and forwarding files (sysop)
+<item>Login as root
+<item>Enter the correct line in /etc/inittab (root)
+</itemize>
+
<sect>Configuration
<sect1>Allowing ax25 connects from users
</verb></tscreen>
-<P>Now login as <em>sysop</em> and cd spider/perl. 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.pl login telnet
+./client login telnet
</verb></tscreen>
You should get a login prompt and on issuing a callsign, you will be given
AK1A type node.
<P>
-Start up the cluster as you did before and login as the sysop with client.pl.
+Start up the cluster as you did before and login as the sysop with client.
The cluster node I am wanting to make a connection to is GB7BAA but you would
obviously use whatever callsign you required. At the prompt type ...
<P>
That is now set, it is as simple as that. To prove it, login on yet another
-console as sysop, cd to spider/perl and issue the command ...
+console as sysop, cd to spider/src and issue the command ...
<tscreen><verb>
-./client.pl gb7baa (using the callsign you set as a node)
+./client gb7baa (using the callsign you set as a node)
</verb></tscreen>
<P>
You should get an initialisation string from DXSpider like this ...
<tscreen><verb>
-./client.pl gb7baa
+./client gb7baa
PC38^GB7MBC^~
</verb></tscreen>
nested under directories. One use for this would be to store DX bulletins
such as the OPDX bulletins. These can be listed and read by the user.
To keep things tidy, make a directory under /spider/packclus called
-<em>bulletins</em>. Now copy any OPDX or similar bulletins into it. These
+<em>bulletin</em>. Now copy any OPDX or similar bulletins into it. These
can be listed by the user in the same way as above using the <em>show/files</em>
-command with an extension for the bulletins directory you have just created,
+command with an extension for the bulletin directory you have just created,
like this ....
<tscreen><verb>
-show/files bulletins
+show/files bulletin
</verb></tscreen>
<P>
<tscreen><verb>
sh/files
-bulletins DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
+bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
</verb></tscreen>
You can see that in the files area (basically the packclus directory) there is a
-file called <em>news</em> and a directory called <em>bulletins</em>. You can
+file called <em>news</em> and a directory called <em>bulletin</em>. You can
also see that dates they were created. In the case of the file <em>news</em>,
you can also see the time it was last modified, a good clue as to whether the
file has been updated since you last read it. To read the file called
type news
</verb></tscreen>
-To look what is in the bulletins directory you issue the command ....
+To look what is in the bulletin directory you issue the command ....
<tscreen><verb>
-show/files bulletins
+show/files bulletin
opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
You can now read any file in this directory using the type command, like this ....
<tscreen><verb>
-type bulletins/opdx391
+type bulletin/opdx391
Ohio/Penn DX Bulletin No. 391
The Ohio/Penn Dx PacketCluster
DX Bulletin No. 391
<P>
In later versions of Spider a simple console program is provided for the sysop.
This has a type ahead buffer with line editing facilities and colour for spots,
-announces etc. To use this program, simply use console.pl instead of client.pl.
+announces etc. To use this program, simply use console.pl instead of client.
<P>
To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
The DXSpider Installation and Administration Manual
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.33 (Revision 1.22) March 2001
+ Version 1.34 (Revision 1.0) April 2001
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
1.3 Installing the software
1.4 Setting callsigns etc
1.5 Starting up for the first time
+ 1.6 The Client program
- 2. The Client program
+ 2. Quick installation guide
3. Configuration
+\bo Net-Telnet-3.02.tar.gz
+
+\bo Curses-1.05.tar.gz
+\bo Time-HiRes-01.20.tar.gz
- # vi /etc/group (or your favorite editor)
+ # 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
alter the text of any section. Some of the lines look a little odd.
Take this line for example ....
-
$myemail = "ianmaude\@btinternet.com";
If all is well then login on another term or console as _\bs_\by_\bs_\bo_\bp and cd
- to /spider/perl. Now issue the following command ...
+ to /spider/src. Now issue the following command ...
+
+ $ ./client
+
- $ ./client.pl
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
and both the cluster and the client should return to Linux prompts.
- 2\b2.\b. T\bTh\bhe\be C\bCl\bli\bie\ben\bnt\bt p\bpr\bro\bog\bgr\bra\bam\bm
+ 1\b1.\b.6\b6.\b. T\bTh\bhe\be C\bCl\bli\bie\ben\bnt\bt p\bpr\bro\bog\bgr\bra\bam\bm
In earlier versions of Spider, all the processes were Perl scripts.
This was fine but with a lot of users your computer memory would soon
small C program called _\bc_\bl_\bi_\be_\bn_\bt. Leave it in this directory.
+
+ 2\b2.\b. Q\bQu\bui\bic\bck\bk i\bin\bns\bst\bta\bal\bll\bla\bat\bti\bio\bon\bn g\bgu\bui\bid\bde\be
+
+ This section is designed for experienced Spider sysops who want to
+ install Spider from scratch. It is simply a check list of things that
+ need to be done without any explanations. The name in brackets at the
+ end of each line is the user that should be doing that process.
+
+
+ +\bo Login as root
+
+ +\bo Get the additional CPAN modules and install them (root)
+
+ +\bo Create the "sysop" user and set a password (root)
+
+ +\bo Put the Spider tarball in sysop and untar it (root)
+
+ +\bo ln -s sysop/spider /spider (root)
+
+ +\bo groupadd -g 251 spider (root)
+
+ +\bo Add any more users you need to the group entry in /etc/group (root)
+
+ +\bo Set the permissions on the spider tree (root)
+
+ +\bo Fix permissions on ax25_call and netrom_call (root)
+
+ +\bo Login as the sysop user
+
+ +\bo cd to /spider (sysop)
+
+ +\bo mkdir local (sysop
+
+ +\bo mkdir local_cmd (sysop)
+
+ +\bo cp perl/DXVars.pm.issue local/DXVars.pm (sysop)
+
+ +\bo cd to /spider/local and edit DXVars to set your details (sysop)
+
+ +\bo cd ../perl (sysop)
+
+ +\bo ./create_sysop.pl (sysop)
+
+ +\bo ./cluster.pl (sysop)
+
+ Spider should now be running and you should be able to login using the
+ client program.
+
+
+ +\bo Login as root
+
+ +\bo Enter the correct line in ax25d.conf (root)
+
+ +\bo Enter the correct line in /etc/services (root)
+
+ +\bo Enter the correct line in /etc/inetd.conf (root)
+
+ +\bo killall -HUP inetd (root)
+
+ Spider should now be able to accept logins via telnet, netrom and
+ ax25.
+
+
+ +\bo Login as sysop
+
+ +\bo Start the cluster (sysop)
+
+ +\bo set/node and type for links (sysop)
+
+ +\bo Write any connect scripts (sysop)
+
+ +\bo Edit /spider/crontab as required (sysop)
+
+ +\bo Edit any other files as necessary (sysop)
+
+ +\bo Set filters, hops and forwarding files (sysop)
+
+ +\bo Login as root
+
+ +\bo Enter the correct line in /etc/inittab (root)
+
+
3\b3.\b. C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+
+
+
3\b3.\b.1\b1.\b. A\bAl\bll\blo\bow\bwi\bin\bng\bg a\bax\bx2\b25\b5 c\bco\bon\bnn\bne\bec\bct\bts\bs f\bfr\bro\bom\bm u\bus\bse\ber\brs\bs
As stated previously, the aim of this document is not to tell you how
+
3\b3.\b.2\b2.\b. A\bAl\bll\blo\bow\bwi\bin\bng\bg t\bte\bel\bln\bne\bet\bt c\bco\bon\bnn\bne\bec\bct\bts\bs f\bfr\bro\bom\bm u\bus\bse\ber\brs\bs
Allowing telnet connections is quite simple. Firstly you need to add
- Now login as _\bs_\by_\bs_\bo_\bp and cd spider/perl. You can test that spider is
+ Now login as _\bs_\by_\bs_\bo_\bp and cd spider/src. You can test that spider is
accepting telnet logins by issuing the following command ....
- ./client.pl login telnet
+ ./client login telnet
You should now get the login prompt and be able to login as before.
-
-
3\b3.\b.3\b3.\b. S\bSe\bet\btt\bti\bin\bng\bg u\bup\bp n\bno\bod\bde\be c\bco\bon\bnn\bne\bec\bct\bts\bs
In order to allow cluster node connections, spider needs to know that
Start up the cluster as you did before and login as the sysop with
- client.pl. The cluster node I am wanting to make a connection to is
+ client. The cluster node I am wanting to make a connection to is
GB7BAA but you would obviously use whatever callsign you required. At
the prompt type ...
-
The case does not matter as long as you have a version of DXSpider
later than 1.33. Earlier versions required the callsign to be in
upper case.
That is now set, it is as simple as that. To prove it, login on yet
- another console as sysop, cd to spider/perl and issue the command ...
+ another console as sysop, cd to spider/src and issue the command ...
- ./client.pl gb7baa (using the callsign you set as a node)
+ ./client gb7baa (using the callsign you set as a node)
- ./client.pl gb7baa
+ ./client gb7baa
PC38^GB7MBC^~
+
+
+
If the callsign you just set up as a cluster node is for an incoming
connect, this is all that needs to be done. If the connection is to
be outgoing then a connection script needs to be written.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
# All lines starting with a # are ignored, as are completely
blank lines.
-
-
- timeout 60
- abort (Busy|Sorry|Fail)
- # don't forget to chmod 4775 netrom_call!
- connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
- # you can leave this out if you call the script 'gb7dxm'
- client gb7dxm ax25
+ timeout 60
+ abort (Busy|Sorry|Fail)
+ # don't forget to chmod 4775 netrom_call!
+ connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
+ # you can leave this out if you call the script 'gb7dxm'
+ client gb7dxm ax25
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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <- 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
avoid this use the following line ...
-
-
-
-
-
-
In a script, this might look like ...
+
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 ...
- # 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') if !connected('gb7xxx')
+
+
+ # 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') if !connected('gb7xxx')
website at the cron page where it is explained more fully.
-
-
-
5\b5.\b. H\bHo\bop\bp c\bco\bon\bnt\btr\bro\bol\bl
Starting with version 1.13 there is simple hop control available on a
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
directly or nested under directories. One use for this would be to
store DX bulletins such as the OPDX bulletins. These can be listed
and read by the user. To keep things tidy, make a directory under
- /spider/packclus called _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn_\bs. Now copy any OPDX or similar
+ /spider/packclus called _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn. Now copy any OPDX or similar
bulletins into it. These can be listed by the user in the same way as
- above using the _\bs_\bh_\bo_\bw_\b/_\bf_\bi_\bl_\be_\bs command with an extension for the bulletins
+ above using the _\bs_\bh_\bo_\bw_\b/_\bf_\bi_\bl_\be_\bs command with an extension for the bulletin
directory you have just created, like this ....
- show/files bulletins
+ show/files bulletin
sh/files
- bulletins DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
+ bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
You can see that in the files area (basically the packclus directory)
- there is a file called _\bn_\be_\bw_\bs and a directory called _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn_\bs. You can
+ there is a file called _\bn_\be_\bw_\bs and a directory called _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn. You can
also see that dates they were created. In the case of the file _\bn_\be_\bw_\bs,
you can also see the time it was last modified, a good clue as to
whether the file has been updated since you last read it. To read the
- To look what is in the bulletins directory you issue the command ....
+ To look what is in the bulletin directory you issue the command ....
- show/files bulletins
+ show/files bulletin
opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
- type bulletins/opdx391
+ type bulletin/opdx391
Ohio/Penn DX Bulletin No. 391
The Ohio/Penn Dx PacketCluster
DX Bulletin No. 391
In later versions of Spider a simple console program is provided for
the sysop. This has a type ahead buffer with line editing facilities
and colour for spots, announces etc. To use this program, simply use
- console.pl instead of client.pl.
+ console.pl instead of client.
To edit the colours, copy /spider/perl/Console.pl to /spider/local and
projects / spider.git / commitdiff