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 Administration Manual v1.49: CVS</TITLE>
6 <LINK HREF="adminmanual-9.html" REL=next>
7 <LINK HREF="adminmanual-7.html" REL=previous>
8 <LINK HREF="adminmanual.html#toc8" REL=contents>
9 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="adminmanual-9.html">Next</A>
13 <A HREF="adminmanual-7.html">Previous</A>
14 <A HREF="adminmanual.html#toc8">Contents</A>
16 <H2><A NAME="s8">8. CVS</A></H2>
18 <P>CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held
20 <A HREF="http://www.sourceforge.net">Sourceforge</A>. This means
21 that it is possible to update your DXSpider installation to the latest
22 sources by using a few simple commands.
24 <P>Please be aware that if you update your system using CVS, it is possible that
25 you could be running code that is very beta and not fully tested. There is
26 a possibility that it could be unstable.
28 <P>I am of course assuming that you have a machine with both DXSpider and
29 Internet access running.
31 <P>BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
34 <P>Assuming you are connected to the Internet, you need to login to the
35 CVS repository and then update your Spider source. There are several
36 steps which are listed below ...
38 <P>First login as the user <EM>sysop</EM>. Next you need to connect to the CVS
39 repository. You do this with the command below ...
42 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
44 <P>You will get a password prompt. Simply hit return here and your machine should
45 return to a normal linux prompt.
47 <P>What happens next depends on whether you have an existing installation that
48 you want to update with the latest and greatest or whether you just want
49 to see what is there and/or run it on a new machine for testing.
50 <P>If you are installing Spider from CVS then change directory to /home/sysop
51 <P>If you are wanting to update Spider then cd to /tmp
53 <P>The next step will create a brand new 'spider' directory in your current
57 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
59 <P>This command is all on one line.
61 <P>Hopefully your screen should show you downloading files. The -z3 simply compresses
62 the download to improve speed.
63 When this has finished, you will have exactly the same as if you had untarred a full
64 tarball PLUS some extra directories and files that CVS needs to do the magic that
67 <P>Now if you are doing a new installation, that's it. Carry on as if you have
68 just downloaded and untarred the lastest tarball.
70 <P>If you want to upgrade your current installation then do this ...
74 tar cvfz /tmp/s.tgz spider
79 <P>This is assuming you downloaded to the /tmp directory of course.
81 <P>NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions
82 correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????
83 <P>Remember to recompile the C client (cd /spider/src; make)
85 <P>At this point the files have been upgraded. You can (usually) restart the cluster
86 in your own time. However, if you attempt to use any new commands or features
87 expect it to be fatal! At least your cluster will have been restarted then so it
88 will be too late to worry about it!
90 <P>Now the magic part! From now on when you want to update, simply connect to the
91 Internet and then, as the user <EM>sysop</EM> ...
99 <P>and your files will be updated. As above, remember to recompile the "C" client
100 if it has been updated (CVS will tell you) and restart if any of the perl scripts
101 have been altered or added, again, CVS will tell you.
103 <P>You will find any changes documented in the /spider/Changes file.
106 <A HREF="adminmanual-9.html">Next</A>
107 <A HREF="adminmanual-7.html">Previous</A>
108 <A HREF="adminmanual.html#toc8">Contents</A>