+<sect1>I have updated from CVS and I get all sorts of errors when I restart
+
+<P>
+Whenever you update from CVS, a log is displayed. Next to each
+file that is downloaded there is a letter, e.g.:
+
+<tscreen><verb>
+? fred.pl
+? jim
+..
+.
+..
+cvs server: Updating perl
+P cluster.pl
+C Messages
+M Internet.pm
+U DXProt.pm
+..
+.
+..
+</verb></tscreen>
+
+<P>
+For normal CVS use you should only ever see the letters 'P', 'U' or '?'. The
+letter 'P' means that the file has
+changed in CVS and is more recent than the one that is currently on your system. You will also
+see the letter '?', which means that
+there is a file that you (or the system) has created that CVS doesn't know about and isn't
+under its control. These are all normal and good.
+
+<P>
+Sometimes you will see the letter 'U' next to a file. This means that it is a new file that you don't currently
+have. This is also OK.
+
+<P>
+However, if you see the letter 'C' or 'M', that means that CVS thinks that the file has
+changed locally. For the letter 'C', it has changed sufficiently near to one or more
+modifications which CVS wants to download to your system. For the 'M', CVS thinks that it
+is OK to make the change (you may also see some messages about "merging revision 1.xx with 1.yy").
+Neither of these things are good. Files that are under the control of CVS
+must not be changed by sysops. It is the files that have the 'C' next to them that will show
+the errors that you are complaining about and they will be things like:-
+
+<tscreen><verb>
+Syntax error near '<<<<' at line 23
+Syntax error near '===' at line 40
+Syntax error near '>>>' at line 51
+</verb></tscreen>
+
+<P>
+You will not necessarily see all of the errors shown but you will get one or more sets of some
+of them. The cure is simple:
+
+<itemize>
+<item> identify the file that is causing the problem.
+<item> remove the file.
+<item> run the cvs update again.
+</itemize>
+
+<P>
+You will see that file come back (with a letter 'U' next to it). That will be the correct
+file as CVS thinks it should be. If you <em>still</em> have a problem, then get onto the
+dxspider-support mailing list.
+
+<P>
+If all else fails (or you have several conflicts) you can safely remove the entire <tt>/spider/perl</tt> and
+<tt>/spider/cmd</tt> directories and then run the cvs update. They will all be recreated in their pristine
+condition.
+
+<sect1>I have done a CVS update, restarted and it says that "fileX" is missing
+
+<P>
+The correct way to run cvs is:-
+
+<tscreen><verb>
+cd /spider
+cvs -z3 update -d
+</verb></tscreen>
+
+<P>
+The '-d' is crucial. It makes sure that any new directories, that may contain new code,
+are created and that new code downloaded. I have absolutely no idea why this is not the
+default, seeing as CVS (in other circumstances) happily recurses its merry way down a
+directory tree, but there you are.
+
+<P>
+WinCVS and other graphical CVS frontends have a checkbox for the update screen called something
+like "create sub-directories" (it may be hidden in some sub-screen - go look for it if it isn't
+obvious). Make sure that this box is checked. If you can make this the
+default setting in the program's setup screen then please do that. It will save you a lot
+of pulled hair.
+