Re: moving cvs repository from one machine to another

[Eric Siegerman]

This may be too late to be of use, but here goes...

On Thu, Sep 27, 2001 at 07:09:56PM +0100, PRUDHVIDHAR lingala wrote:
> Once you setup the CVS server on new system
> 
> 1) Just copy the entire CVS repository from old 
> server and put it on new system
> 2) do following on the new cvs server
> cvs -d <new directory name > init
> 3) check whether you are able to access the new
> server's repository
> 4) Cut off the access to the cvs repository on old
> system

Do (4) first!  If you do the steps in the order shown here,
there's a race condition: a user could commit new revisions to
the old repo, too late for them to be copied to the new repo.
(For a large repo, step (1) could take a long time, so this isn't
a purely theoretical concern.)

It'd be much safer to take the repo offline during this process
-- scheduled downtime is almost certainly cheaper than lost
revisions!

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
The world has been attacked.  The world must respond ... [but] we must
be guided by a commitment to do what works in the long run, not by what
makes us feel better in the short run.
        - Jean Chrétien, Prime Minister of Canada