X-Git-Url: http://scm.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;ds=inline;f=html%2Fadminmanual-7.html;h=619745f4eafd2f2f4d89f5ca8a5e15e6237da530;hb=7392e25c792e4d7754f955d1ae0e32f05b7e1359;hp=50f14cdbfcaf19b9004276fee5e19ad0476aa448;hpb=7e7c5eedb4cccbb363db142d29438261b1c804da;p=spider.git diff --git a/html/adminmanual-7.html b/html/adminmanual-7.html index 50f14cdb..619745f4 100644 --- a/html/adminmanual-7.html +++ b/html/adminmanual-7.html @@ -1,8 +1,8 @@
- -CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held -at -Sourceforge. This means -that it is possible to update your DXSpider installation to the latest -sources by using a few simple commands. -
-
Please be aware that if you update your system using CVS, it is possible that -you could be running code that is very beta and not fully tested. There is -a possibility that it could be unstable. -
-
I am of course assuming that you have a machine with both DXSpider and -Internet access running. -
-
BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR -ENTIRE SPIDER TREE!! -
-
Assuming you are connected to the Internet, you need to login to the -CVS repository and then update your Spider source. There are several -steps which are listed below ... -
-
First login as the user sysop. Next you need to connect to the CVS -repository. You do this with the command below ... -
-
-cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login --
You will get a password prompt. Simply hit return here and your machine should -return to a normal linux prompt. -
-
What happens next depends on whether you have an existing installation that -you want to update with the latest and greatest or whether you just want -to see what is there and/or run it on a new machine for testing. -
If you are installing Spider from CVS then change directory to /home/sysop -
If you are wanting to update Spider then cd to /tmp -
-
The next step will create a brand new 'spider' directory in your current -directory. -
-
-cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider --
This command is all on one line. -
-
Hopefully your screen should show you downloading files. The -z3 simply compresses -the download to improve speed. -When this has finished, you will have exactly the same as if you had untarred a full -tarball PLUS some extra directories and files that CVS needs to do the magic that -it does. -
-
Now if you are doing a new installation, that's it. Carry on as if you have -just downloaded and untarred the lastest tarball. -
-
If you want to upgrade your current installation then do this ... +
In the spider tree will be a directory spider-web. This is a +neat little java web applet that can be run from a website. The applet +must run on the same machine as the cluster. The included README file is +shown below.
+ +I should comment here that the applet is precompiled, that is, ready to go. +It was compiled using JDK1.3.1. If your version is earlier than this then it +may not work. Should that be the case you need to recompile or update your +JDK. To recompile do the following ...
-tar cvfz /tmp/s.tgz spider
-cd /
-tar xvfzp /tmp/s.tgz
+cd /spider/spider-web
+rm *.class
+/usr/bin/javac spiderclient.java
-This is assuming you downloaded to the /tmp directory of course. -
-
NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions -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) 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! -
-
Now the magic part! From now on when you want to update, simply connect to the -Internet and then, as the user sysop ... +
+ +I have used /usr/bin/javac as an example, your path to javac may be different.
-
-cd /spider
-cvs -z3 update -d
+Spider-WEB v0.6b
+
+Completely based on a clx web client written in Java by dl6dbh
+(ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
+
+The webserver has to run on the same machine as your DxSpider software!
+
+It is assumed that you have Java installed. You need JDK1.3.1 at least.
+
+Installation instructions (Performed as root):
+
+Put all the files in the spider-web directory into a newly created directory
+under the DocumentRoot of your websever for instance 'client'. In my case
+this is: /home/httpd/html/client/ although ymmv. For Suse the correct
+path should be /usr/local/httpd/htdocs/client/ for example.
+
+Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
+/home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
+/usr/local/httpd/cgi-bin/ for example.
+
+Change the permissions of the files to ensure they are correct, obviously you
+will need to use the correct path the the files according to your system:
+
+chmod 755 /home/httpd/html/cgi-bin/spider.cgi
+chmod -R 755 /home/httpd/html/client/
+
+By default the spider.cgi script should pick up your hostname (As long as this
+is set correctly). If it does not or your hostname differs from the name that
+you attach to the public address that you are using, then edit spider.cgi :
+
+# Uncomment and set the hostname manually here if the above fails.
+# $HOSTNAME = "gb7mbc.spoo.org" ;
+$PORT = "8000" ;
+
+'HOSTNAME' is the hostname of your cluster.
+
+'PORT' is the portnumber that you use to connect to your DxSpider via
+telnet (see Listeners.pm)
+
+NOTE: If you can start the console but cannot connect to the cluster from it,
+then it is possible that the machine you are on cannot resolve the hostname of
+your cluster machine. If this is the case, you need to set your hostname
+manually as above.
+
+You also need to set the $NODECALL variable. This prints the name of your
+choosing (probably your cluster callsign) on the html page.
+
+You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
-
-and your files will be updated. As above, remember to recompile the "C" client -if it has been updated (CVS will tell you) and restart if any of the perl scripts -have been altered or added, again, CVS will tell you. -
-
You will find any changes documented in the /spider/Changes file. -
+
+