X-Git-Url: http://scm.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-1.html;h=6a109bf85a9ab7d9ecdec32de76cd297a924425f;hb=81a5b9bf8d3101bbc1a8190a9de72de0117d302a;hp=e85ba645a1aaeb762260e04b212c945c2c9dd20d;hpb=bff9ecf00b14e7d71d9504088a2fd7b9e5115fe1;p=spider.git diff --git a/html/adminmanual-1.html b/html/adminmanual-1.html index e85ba645..6a109bf8 100644 --- a/html/adminmanual-1.html +++ b/html/adminmanual-1.html @@ -2,7 +2,7 @@
-Last modified: November 1999 by Ian Maude, G0VGS +
Last modified: 25 July 2000 by Ian Maude, G0VGS
@@ -51,7 +52,7 @@ Previous
I will assume that you have already downloaded the latest tarball of the DXSpider software and are ready to install it. +
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.
Login as root and create a user to run the cluster under. UNDER NO CIRCUMSTANCES USE ROOT AS THIS USER!. I am going to use the name sysop. You can call it anything you wish. Depending on your security requirements you may wish to use an existing user, however this is your own choice.
@@ -76,7 +77,7 @@ passwd: all authentication tokens updated successfully
Now to unpack the DX Spider distribution, set symbolic links and group permissions. This example assumes you are using version 1.35 but of course you would substitute the correct version number. Copy the tarball to /home/sysop and do the following. +
Now to unpack the DX Spider distribution, set symbolic links and group permissions. Copy the tarball to /home/sysop and do the following.
@@ -127,7 +128,7 @@ passwd: all authentication tokens updated successfully
$ cd /spider
$ mkdir local
$ mkdir local_cmd
-$ cp perl/DXVars.pm local
+$ cp perl/DXVars.pm.issue local/DXVars.pm
$ cd local
$ vi DXVars.pm (or your favourite editor)
@@ -136,11 +137,11 @@ $ vi DXVars.pm (or your favourite editor)
Using the distributed DXVars.pm as a a template, set your cluster callsign, sysop callsign and other user info to suit your own environment. Note that this a perl file which will be parsed and executed as part of the cluster. If you get it wrong then perl will complain when you start the cluster process. It is important only to alter the text of any section. Some of the lines look a little odd. Take this line for example ....
$myemail = "ianmaude\@btinternet.com";
-
There appears to be an extraeneous slash in there. However this has to be there for the file to work so leave it in.
+
There appears to be an extra slash in there. However this has to be there for the file to work so leave it in.
PLEASE USE CAPITAL LETTERS FOR CALLSIGNS
-
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 whilst the cluster is running!
+
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!
Save the new file and change directory to ../perl ....
@@ -178,7 +179,7 @@ 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 ... +
If all is well then login on another term or console as sysop and cd to /spider/perl. Now issue the following command ...