X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-12.html;fp=html%2Fadminmanual-12.html;h=0000000000000000000000000000000000000000;hb=161019eb8c45394eb742fe22826ee997f8d81c73;hp=99d45a2b0924dbfbe19a1700910e315015ec138c;hpb=c9768e5afacacc3dd4004a35aeef2a2e54865177;p=spider.git diff --git a/html/adminmanual-12.html b/html/adminmanual-12.html deleted file mode 100644 index 99d45a2b..00000000 --- a/html/adminmanual-12.html +++ /dev/null @@ -1,114 +0,0 @@ - - - - - The DXSpider Installation and Administration Manual: CVS - - - - - - -Next -Previous -Contents -
-

12. CVS

- -

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

-

THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST -INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!! -THIS MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!! -YOU HAVE BEEN WARNED!!! -

-

DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE -CONSEQUENCES!!! -

-

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

-

-
-tar cvfz /tmp/s.tgz spider
-cd /
-tar xvfzp /tmp/s.tgz
-
-
-

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

-

-
-cd /spider
-cvs -z3 update -d
-
-
-

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

-


-Next -Previous -Contents - -