From: g0vgs Date: Sun, 8 Apr 2001 10:47:06 +0000 (+0000) Subject: as last log X-Git-Tag: R_1_47~46 X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=commitdiff_plain;h=e39b738850b9a122b60b179e9723e546ddacfd62;p=spider.git as last log --- diff --git a/Changes b/Changes index ca4487b6..fefdbcb4 100644 --- a/Changes +++ b/Changes @@ -1,3 +1,6 @@ +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(); diff --git a/html/adminmanual-1.html b/html/adminmanual-1.html index f30b0a40..0d902dd2 100644 --- a/html/adminmanual-1.html +++ b/html/adminmanual-1.html @@ -211,11 +211,11 @@ orft we jolly well go ...

If all is well then login on another term or console as sysop and -cd to /spider/perl. Now issue the following command ... +cd to /spider/src. Now issue the following command ... 

-$ ./client.pl
+$ ./client

@@ -241,6 +241,18 @@ shutdown

and both the cluster and the client should return to Linux prompts.

+

1.6 The Client program +

+ +

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 +incoming connects at the moment. Before you can use it though it +has to be "made". CD to /spider/src and type make. You +should see the output on your screen and hopefully now have a small C program +called client. Leave it in this directory. +

+

Next Previous diff --git a/html/adminmanual-11.html b/html/adminmanual-11.html index 75840549..1887acbf 100644 --- a/html/adminmanual-11.html +++ b/html/adminmanual-11.html @@ -64,14 +64,14 @@ an alias for this in the Alias file to allow them just to type news 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 -bulletins. Now copy any OPDX or similar bulletins into it. These +bulletin. Now copy any OPDX or similar bulletins into it. These can be listed by the user in the same way as above using the show/files -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 .... 

-show/files bulletins
+show/files bulletin

@@ -80,11 +80,11 @@ show/files bulletins 

 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 news and a directory called bulletins. You can +file called news and a directory called bulletin. You can also see that dates they were created. In the case of the file news, 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 @@ -95,11 +95,11 @@ file has been updated since you last read it. To read the file called type news -

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  
@@ -120,7 +120,7 @@ Press Enter to continue, A to abort (16 lines) >
 

 

 
-type bulletins/opdx391
+type bulletin/opdx391
 Ohio/Penn DX Bulletin No. 391
 The Ohio/Penn Dx PacketCluster
 DX Bulletin No. 391
@@ -290,7 +290,7 @@ results once you have set an alias.
 
 
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.
 

 
To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the 
 file with your favourite editor.
diff --git a/html/adminmanual-2.html b/html/adminmanual-2.html
index ecaf1910..a74ae76f 100644
--- a/html/adminmanual-2.html
+++ b/html/adminmanual-2.html
@@ -2,7 +2,7 @@
 
 
  
- The DXSpider Installation and Administration Manual : The Client program
+ The DXSpider Installation and Administration Manual : Quick installation guide
  
  
  
@@ -13,15 +13,56 @@
 Previous
 Contents
 

-
2. The Client program

+
2. Quick installation guide

 
-
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
-incoming connects at the moment.  Before you can use it though it 
-has to be "made".  CD to /spider/src and type make.  You 
-should see the output on your screen and hopefully now have a small C program 
-called client.  Leave it in this directory.
+
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.
+

+
    
+
  • Login as root
    • 
+
  • Get the additional CPAN modules and install them (root)
    • 
+
  • Create the "sysop" user and set a password (root)
    • 
+
  • Put the Spider tarball in  sysop and untar it (root)
    • 
+
  • ln -s  sysop/spider /spider (root)
    • 
+
  • groupadd -g 251 spider (root)
    • 
+
  • Add any more users you need to the group entry in /etc/group (root)
    • 
+
  • Set the permissions on the spider tree (root)
    • 
+
  • Fix permissions on ax25_call and netrom_call (root)
    • 
+
  • Login as the sysop user
    • 
+
  • cd to /spider (sysop)
    • 
+
  • mkdir local (sysop
    • 
+
  • mkdir local_cmd (sysop)
    • 
+
  • cp perl/DXVars.pm.issue local/DXVars.pm (sysop)
    • 
+
  • cd to /spider/local and edit DXVars to set your details (sysop)
    • 
+
  • cd ../perl (sysop)
    • 
+
  • ./create_sysop.pl (sysop)
    • 
+
  • ./cluster.pl (sysop)
    • 
+

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

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

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

+
    
+
  • Login as sysop
    • 
+
  • Start the cluster (sysop)
    • 
+
  • set/node and type for links (sysop)
    • 
+
  • Write any connect scripts (sysop)
    • 
+
  • Edit /spider/crontab as required (sysop)
    • 
+
  • Edit any other files as necessary (sysop)
    • 
+
  • Set filters, hops and forwarding files (sysop)
    • 
+
  • Login as root
    • 
+
  • Enter the correct line in /etc/inittab (root)
    • 
+

 

 

 Next
diff --git a/html/adminmanual-3.html b/html/adminmanual-3.html
index e11f175d..83fe1c0c 100644
--- a/html/adminmanual-3.html
+++ b/html/adminmanual-3.html
@@ -65,12 +65,12 @@ killall -HUP inetd
 

 

 

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

 

 
-./client.pl login telnet
+./client login telnet
 

 

 
You should get a login prompt and on issuing a callsign, you will be given 
@@ -113,7 +113,7 @@ set/clx
 
For now, we will assume that the cluster we are going to connect to is an
 AK1A type node.
 

-
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 ...
 

@@ -127,11 +127,11 @@ set/node gb7baa
 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 ...
+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)
 

 

 

@@ -139,7 +139,7 @@ console as sysop, cd to spider/perl and issue the command ...
 

 

 
-./client.pl gb7baa
+./client gb7baa
 PC38^GB7MBC^~
 

 

diff --git a/html/adminmanual.html b/html/adminmanual.html
index 7fb96ef8..c41f0630 100644
--- a/html/adminmanual.html
+++ b/html/adminmanual.html
@@ -15,7 +15,7 @@ Contents
 

 
The DXSpider Installation and Administration Manual 

 
-
Ian Maude, G0VGS, (ianmaude@btinternet.com)
Version 1.33 (Revision 1.22) March 2001
+
Ian Maude, G0VGS, (ianmaude@btinternet.com)
Version 1.34 (Revision 1.0) April 2001
 

 A reference for SysOps of the DXSpider DXCluster program.
 

@@ -28,9 +28,10 @@ Contents
 
  • 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
    
diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml
index effa0d27..b956474f 100644
--- a/sgml/adminmanual.sgml
+++ b/sgml/adminmanual.sgml
@@ -6,7 +6,7 @@
 
 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>
@@ -216,10 +216,10 @@ orft we jolly well go ...
 
 <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>
@@ -243,7 +243,7 @@ shutdown
 <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 
@@ -254,6 +254,61 @@ 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.
 
+
+<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
@@ -299,11 +354,11 @@ killall -HUP inetd
 </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 
@@ -347,7 +402,7 @@ For now, we will assume that the cluster we are going to connect to is an
 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 ...
 
@@ -361,17 +416,17 @@ The case does not matter as long as you have a version of DXSpider later than
 
 <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>
 
@@ -1686,13 +1741,13 @@ You can also store other information in this directory, either 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
-<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>
@@ -1700,11 +1755,11 @@ An example would look like this ....
 
 <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 
@@ -1714,10 +1769,10 @@ 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  
@@ -1737,7 +1792,7 @@ Press Enter to continue, A to abort (16 lines) >
 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
@@ -1906,7 +1961,7 @@ results once you have set an alias.
 <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 
diff --git a/txt/adminmanual.txt b/txt/adminmanual.txt
index f9b6da85..725b6856 100644
--- a/txt/adminmanual.txt
+++ b/txt/adminmanual.txt
@@ -1,6 +1,6 @@
   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.
   ______________________________________________________________________
@@ -71,8 +71,9 @@
      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
 
@@ -326,6 +327,7 @@
 
   +o  Net-Telnet-3.02.tar.gz
 
+
   +o  Curses-1.05.tar.gz
 
   +o  Time-HiRes-01.20.tar.gz
@@ -392,7 +394,10 @@
 
 
 
-       # 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
@@ -459,7 +464,6 @@
   alter the text of any section.  Some of the lines look a little odd.
   Take this line for example ....
 
-
   $myemail = "ianmaude\@btinternet.com";
 
 
@@ -520,11 +524,13 @@
 
 
   If all is well then login on another term or console as _s_y_s_o_p 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
@@ -554,7 +560,7 @@
   and both the cluster and the client should return to Linux prompts.
 
 
-  22..  TThhee CClliieenntt pprrooggrraamm
+  11..66..  TThhee CClliieenntt pprrooggrraamm
 
   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
@@ -565,8 +571,93 @@
   small C program called _c_l_i_e_n_t.  Leave it in this directory.
 
 
+
+  22..  QQuuiicckk iinnssttaallllaattiioonn gguuiiddee
+
+  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.
+
+
+  +o  Login as root
+
+  +o  Get the additional CPAN modules and install them (root)
+
+  +o  Create the "sysop" user and set a password (root)
+
+  +o  Put the Spider tarball in  sysop and untar it (root)
+
+  +o  ln -s  sysop/spider /spider (root)
+
+  +o  groupadd -g 251 spider (root)
+
+  +o  Add any more users you need to the group entry in /etc/group (root)
+
+  +o  Set the permissions on the spider tree (root)
+
+  +o  Fix permissions on ax25_call and netrom_call (root)
+
+  +o  Login as the sysop user
+
+  +o  cd to /spider (sysop)
+
+  +o  mkdir local (sysop
+
+  +o  mkdir local_cmd (sysop)
+
+  +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  ./create_sysop.pl (sysop)
+
+  +o  ./cluster.pl (sysop)
+
+  Spider should now be running and you should be able to login using the
+  client program.
+
+
+  +o  Login as root
+
+  +o  Enter the correct line in ax25d.conf (root)
+
+  +o  Enter the correct line in /etc/services (root)
+
+  +o  Enter the correct line in /etc/inetd.conf (root)
+
+  +o  killall -HUP inetd (root)
+
+  Spider should now be able to accept logins via telnet, netrom and
+  ax25.
+
+
+  +o  Login as sysop
+
+  +o  Start the cluster (sysop)
+
+  +o  set/node and type for links (sysop)
+
+  +o  Write any connect scripts (sysop)
+
+  +o  Edit /spider/crontab as required (sysop)
+
+  +o  Edit any other files as necessary (sysop)
+
+  +o  Set filters, hops and forwarding files (sysop)
+
+  +o  Login as root
+
+  +o  Enter the correct line in /etc/inittab (root)
+
+
   33..  CCoonnffiigguurraattiioonn
 
+
+
+
   33..11..  AAlllloowwiinngg aaxx2255 ccoonnnneeccttss ffrroomm uusseerrss
 
   As stated previously, the aim of this document is not to tell you how
@@ -592,6 +683,7 @@
 
 
 
+
   33..22..  AAlllloowwiinngg tteellnneett ccoonnnneeccttss ffrroomm uusseerrss
 
   Allowing telnet connections is quite simple.  Firstly you need to add
@@ -627,12 +719,12 @@
 
 
 
-  Now login as _s_y_s_o_p and cd spider/perl. You can test that spider is
+  Now login as _s_y_s_o_p 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
 
 
 
@@ -656,8 +748,6 @@
   You should now get the login prompt and be able to login as before.
 
 
-
-
   33..33..  SSeettttiinngg uupp nnooddee ccoonnnneeccttss
 
   In order to allow cluster node connections, spider needs to know that
@@ -689,7 +779,7 @@
 
 
   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 ...
 
@@ -700,18 +790,17 @@
 
 
 
-
   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)
 
 
 
@@ -721,9 +810,12 @@
 
 
 
-       ./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.
@@ -743,6 +835,27 @@
 
 
 
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
   #               All lines starting with a # are ignored, as are completely
                   blank lines.
 
@@ -788,14 +901,12 @@
 
 
 
-
-
-  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
 
 
 
@@ -811,9 +922,6 @@
        client gb7djk telnet
 
 
-
-
-
   Both these examples assume that everything is set up properly at the
   other end.  You will find other examples in the /spider/examples
   directory.
@@ -839,49 +947,32 @@
 
 
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-  <- D G1TLH connect gb7djk-1
-  -> D G1TLH connection to GB7DJK-1 started
-  -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
-  timeout set to 15
-  CONNECT sort: telnet command: dirkl.tobit.co.uk
-  CHAT "login" -> "gb7djk"
-  received "
-  Red Hat Linux release 5.1 (Manhattan)
-  Kernel 2.0.35 on an i586
-  "
-  received "login: "
-  sent "gb7djk"
-  CHAT "word" -> "gb7djk"
-  received "gb7djk"
-  received "Password: "
-  sent "gb7djk"
-  Connected to GB7DJK-1, starting normal protocol
-  <- O GB7DJK-1 telnet
-  -> B GB7DJK-1 0
-  GB7DJK-1 channel func  state 0 -> init
-  <- D GB7DJK-1
-  <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1
-  <- D GB7DJK-1 PC38^GB7DJK-1^~
-  <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users  Max users 0  Uptime
-  0 00:00^5447^~
-      etc
+       <- D G1TLH connect gb7djk-1
+       -> D G1TLH connection to GB7DJK-1 started
+       -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
+       timeout set to 15
+       CONNECT sort: telnet command: dirkl.tobit.co.uk
+       CHAT "login" -> "gb7djk"
+       received "
+       Red Hat Linux release 5.1 (Manhattan)
+       Kernel 2.0.35 on an i586
+       "
+       received "login: "
+       sent "gb7djk"
+       CHAT "word" -> "gb7djk"
+       received "gb7djk"
+       received "Password: "
+       sent "gb7djk"
+       Connected to GB7DJK-1, starting normal protocol
+       <- O GB7DJK-1 telnet
+       -> B GB7DJK-1 0
+       GB7DJK-1 channel func  state 0 -> init
+       <- D GB7DJK-1
+       <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1
+       <- D GB7DJK-1 PC38^GB7DJK-1^~
+       <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users  Max users 0  Uptime
+       0 00:00^5447^~
+           etc
 
 
 
@@ -897,12 +988,6 @@
   avoid this use the following line ...
 
 
-
-
-
-
-
-
   In a script, this might look like ...
 
 
@@ -988,6 +1073,7 @@
 
 
 
+
   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 ...
@@ -1031,10 +1117,13 @@
 
 
 
-       # 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')
 
 
 
@@ -1051,9 +1140,6 @@
   website at the cron page where it is explained more fully.
 
 
-
-
-
   55..  HHoopp ccoonnttrrooll
 
   Starting with version 1.13 there is simple hop control available on a
@@ -1091,26 +1177,6 @@
 
 
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
 
 
 
@@ -2330,14 +2396,14 @@
   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 _b_u_l_l_e_t_i_n_s.  Now copy any OPDX or similar
+  /spider/packclus called _b_u_l_l_e_t_i_n.  Now copy any OPDX or similar
   bulletins into it.  These can be listed by the user in the same way as
-  above using the _s_h_o_w_/_f_i_l_e_s command with an extension for the bulletins
+  above using the _s_h_o_w_/_f_i_l_e_s command with an extension for the bulletin
   directory you have just created, like this ....
 
 
 
-       show/files bulletins
+       show/files bulletin
 
 
 
@@ -2348,13 +2414,13 @@
 
 
        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 _n_e_w_s and a directory called _b_u_l_l_e_t_i_n_s.  You can
+  there is a file called _n_e_w_s and a directory called _b_u_l_l_e_t_i_n.  You can
   also see that dates they were created.  In the case of the file _n_e_w_s,
   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
@@ -2367,14 +2433,14 @@
 
 
 
-  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
@@ -2398,7 +2464,7 @@
 
 
 
-       type bulletins/opdx391
+       type bulletin/opdx391
        Ohio/Penn DX Bulletin No. 391
        The Ohio/Penn Dx PacketCluster
        DX Bulletin No. 391
@@ -2587,7 +2653,7 @@
   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