1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
4 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
5 <TITLE>The DXSpider Installation and Administration Manual : CVS</TITLE>
6 <LINK HREF="adminmanual-11.html" REL=next>
7 <LINK HREF="adminmanual-9.html" REL=previous>
8 <LINK HREF="adminmanual.html#toc10" REL=contents>
11 <A HREF="adminmanual-11.html">Next</A>
12 <A HREF="adminmanual-9.html">Previous</A>
13 <A HREF="adminmanual.html#toc10">Contents</A>
15 <H2><A NAME="s10">10. CVS</A></H2>
17 <P>CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held
19 <A HREF="http://www.sourceforge.net">Sourceforge</A>. This means
20 that it is possible to update your DXSpider installation to the latest
21 sources by using a few simple commands.
23 <P>THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST
24 INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!!
25 THIS MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!!
26 YOU HAVE BEEN WARNED!!!
28 <P>DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE
31 <P>I am of course assuming that you have a machine with both DXSpider and
32 Internet access running.
34 <P>BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
37 <P>Assuming you are connected to the Internet, you need to login to the
38 CVS repository and then update your Spider source. There are several
39 steps which are listed below ...
41 <P>First login as the user <EM>sysop</EM>. Next you need to connect to the CVS
42 repository. You do this with the command below ...
45 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
47 <P>You will get a password prompt. Simply hit return here and your machine should
48 return to a normal linux prompt.
50 <P>What happens next depends on whether you have an existing installation that
51 you want to update with the latest and greatest or whether you just want
52 to see what is there and/or run it on a new machine for testing.
53 Either way you will want to change directory to a new place, if you want to
54 update an existing installation then I suggest /tmp, otherwise choose a
55 suitable place according to the normal installation instructions.
57 <P>The next step will create a brand new 'spider' directory in your current
61 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
63 <P>This command is all on one line.
65 <P>Hopefully your screen should show you downloading files. The -z3 simply compresses
66 the download to improve speed.
67 When this has finished, you will have exactly the same as if you had untarred a full
68 tarball PLUS some extra directories and files that CVS needs to do the magic that
71 <P>Now if you are doing a new installation, that's it. Carry on as if you have
72 just downloaded and untarred the lastest tarball.
74 <P>If you want to upgrade your current installation then do this ...
78 tar cvfz /tmp/s.tgz spider
83 <P>This is assuming you downloaded to the /tmp directory of course.
85 <P>NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions
86 correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????
87 <P>Remember to recompile the C client (cd /spider/src; make)
89 <P>At this point the files have been upgraded. You can (usually) restrt the cluster
90 in your own time. However, if you attempt to use any new commands or features
91 expect it to be fatal! At least your cluster will have been restarted then so it
92 will be too late to worry about it!
94 <P>Now the magic part! From now on when you want to update, simply connect to the
95 Internet and then, as the user <EM>sysop</EM> ...
103 <P>and your files will be updated. As above, remember to recompile the "C" client
104 if it has been updated (CVS will tell you) and restart if any of the perl scripts
105 have been altered or added, again, CVS will tell you.
107 <P>You will find any changes documented in the /spider/Changes file.
110 <A HREF="adminmanual-11.html">Next</A>
111 <A HREF="adminmanual-9.html">Previous</A>
112 <A HREF="adminmanual.html#toc10">Contents</A>