Changes to spider-web from OZ1LQH

[spider.git] / spider-web / README

diff --git a/spider-web/README b/spider-web/README
index 6406d43c2f287ef37355a719f54e96a62e11503b..e253db7255daebe31b9f2bff6e8d79ecdcb290fb 100644 (file)
--- a/spider-web/README
+++ b/spider-web/README
@@ -5,14 +5,18 @@ Completely based on a clx web client written in Java by dl6dbh
 
 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:  /var/www/html/client/
+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
-/var/www/cgi-bin/ 
+/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 :
 
@@ -32,5 +36,12 @@ $PORT = "8000" ;
 '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