X-Git-Url: http://scm.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=sgml%2Fadminmanual.sgml;h=01d488fbd95d416e9b64c7205295e2bd8083e0fa;hb=63b5e2134b2ffba051682618f88b09d5ee5457c7;hp=d61944f320dc1dc136080c413aba5d298fedfd7b;hpb=b2478484ac66d4c499a2348b8163a7e0966f4250;p=spider.git diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index d61944f3..01d488fb 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -6,7 +6,7 @@
-This section describes the installation of DX Spider v1.35 on a
-
I am assuming a general knowledge of Linux and its commands. You should
@@ -34,24 +34,19 @@ know how to use tar and how to edit files using your favourite editor.
The crucial ingredient for all of this is
- In addition to the standard Red Hat distribution you will require the
-following
I will assume that you have already downloaded the latest tarball of
the DXSpider software and are ready to install it. I am assuming version
-1.35 for this section but of course you would use the latest version.
+1.46 for this section but of course you would use the latest version.
Login as root and create a user to run the cluster under.
-DON'T alter the DXVars.pm (or any other file) in /spider/perl, they are
-overwritten with every release. Any files or commands you place in /spider/local
-or /spider/local_cmd will automagically be used in preference to the ones in
-/spider/perl EVEN while the cluster is running!
+DON'T alter any file in /spider/perl, they are overwritten with every
+release. Any files or commands you place in /spider/local or /spider/local_cmd
+will automagically be used in preference to the ones in /spider/perl EVEN
+while the cluster is running!
Save the new file and change directory to ../perl ....
@@ -197,7 +192,7 @@ Now type the following command which creates the basic user file with you as
the sysop.
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 ...
@@ -248,7 +243,7 @@ shutdown
and both the cluster and the client should return to Linux prompts.
-
In earlier versions of Spider, all the processes were Perl scripts. This
@@ -259,6 +254,61 @@ 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.
+
+
@@ -298,11 +354,11 @@ 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 ....
-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 ...
@@ -360,17 +416,17 @@ The case does not matter as long as you have a version of DXSpider later than
That is now set, it is as simple as that. To prove it, login on yet another
-console as sysop and issue the command ...
+console as sysop, cd to spider/src and issue the command ...
You should get an initialisation string from DXSpider like this ...
+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 ...
+
+
This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart
it should it crash for any reason.
@@ -1669,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
-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 ....
@@ -1683,11 +1755,11 @@ An example would look like this ....
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
@@ -1928,6 +2000,16 @@ load/keps
That is it! the kepler data has been updated.
+
+The command sh/qrz will only work once you have followed a few
+simple steps. First you need to get a user ID and password from qrz.com.
+Simply go to the site and create one. Secondly you need to copy the file
+/spider/perl/Internet.pm to /spider/local and alter it to match your user
+ID and password. You also at this point need to set $allow=1 to complete
+the setup. Many thanks to Fred Lloyd, the proprieter of
+
The next step will create a brand new 'spider' directory in your current
@@ -2018,7 +2101,7 @@ correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????
Remember to recompile the C client (cd /spider/src; make)
-At this point the files have been upgraded. You can (usually) restrt the cluster
+At this point the files have been upgraded. You can (usually) restart the cluster
in your own time. However, if you attempt to use any new commands or features
expect it to be fatal! At least your cluster will have been restarted then so it
will be too late to worry about it!
@@ -3514,7 +3597,18 @@ Set the node_call as a CLX type node
-You can remove this level with unset/debug <name>
+You can choose to log several different levels. The levels are
+
+chan
+state
+msg
+cron
+connect
+
+You can show what levels you are logging with the show/debug
+command.
+
+You can remove a debug level with unset/debug <name>
-
@@ -3986,6 +4080,16 @@ time and UTC as the computer has it right now. If you give some prefixes
then it will show UTC and UTC + the local offset (not including DST) at
the prefixes or callsigns that you specify.
+
+
+
+The levels can be set with set/debug
+