[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: freezing cvs repository to rsync to a remote location

From: Mark D. Baushke
Subject: Re: freezing cvs repository to rsync to a remote location
Date: Thu, 04 Nov 2004 16:54:41 -0800

Hash: SHA1

<address@hidden> writes:

> Does anyone know of a good (and safe) way to lock users out of the cvs
> repository so we can rsync the repository to a remote site and not
> risk any data corruption?

If you use

  --exclude "#cvs*" --exclude ",*,"

then all of the files that you rsync to the remote site should be free
of any data corruption. When cvs moves from ,file, to file,v it is an
atomic rename operation, so as long as rsync is ignoring the ,file,v RCS
'lock files' and the '#cvs*' lock files, you will not have a 'corrupt'
copy of the repository... of course, this does not mean it will be a
'sane' copy of the repository as you may have copied only some files
that were in the process of being changed during a commit.

If you are worred about having a consistent repository, then you may
find it desirable to look at cvslock

and have it lock the repository directories of interest before starting
your rsync and then unlock them. You will still want to have the
- --exclude "#cvs*" to avoid dragging cvs locks to the remote site.

Finally, have you considered doing a 'pull' from the secondary to the
primary using cvsup on the client and cvsupd on the server?

You may find that the cvsup/cvsupd is really the 'better' solution:

you will also need to fetch a copy of a Modula-3 compiler ezm3

note that some pre-built Modula-3 compilers exist such as

depending on the CPU type you have.

        -- Mark
Version: GnuPG v1.2.3 (FreeBSD)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]