info-cvs
[Top][All Lists]
Advanced

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

Re: backing up of cvs repositories


From: Mark D. Baushke
Subject: Re: backing up of cvs repositories
Date: Wed, 31 May 2006 01:05:06 -0700

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

ankush grover <address@hidden> writes:

> > You could just do a normal rsync and exclude ,.*,
> > files as well as the various CVS lock files
> > themselves. Doing it multiple times until there
> > are no new files updated would probably work fine.
> >
> hey Mr. Mark
> 
> Can you give me an example what files to exclude  for example cvs lock
> files and some other files?

I typically keep my lock files in a separate directory hierarchy and use
the LockDir= directive in the CVSROOT/config file.

I expect that this is generally what you want to use:

  --exclude '#cvs*' --exclude ',*,'

If you feel you want something more specific, then perhaps:

  --exclude '#cvs.lock' \
  --exclude '#cvs.history.lock' \
  --exlcude '#cvs.val-tags.lock' \
  --exlcude '#cvs.rfl*' \
  --exlcude '#cvs.pfl*' \
  --exlcude '#cvs.wfl*' \
  --exlcude ',*,' \
  --exclude 'CVS'

This last entry above may depend on what your intent for the mirror
might be. Including the above would exclude the CVS/fileattr file where
advisory locks are kept.

  #cvs.rfl.<hostname>.<pid>           - read locks
  #cvs.wfl.<hostname>.<pid>           - write locks
  #cvs.pfl.<hostname>.<pid>           - promotable locks
  #cvs.rfl.<pid>                      - read locks
  #cvs.wfl.<pid>                      - write locks
  #cvs.pfl.<pid>                      - promotable locks
  #cvs.history.lock.<hostname>.<pid>  - lock for the CVSROOT/history file
  #cvs.history.lock.<pid>             - lock for the CVSROOT/history file
  #cvs.val-tags.lock.<hostname>.<pid> - lock for the CVSROOT/val-tags file
  #cvs.val-tags.lock.<pid>            - lock for the CVSROOT/val-tags file
  ,*,                                 - RCS lock file.
  CVS/fileattr                        - watches and editors info

Whete <hostname> is likely to the string that gethostname() returns and
<pid> will be the process-id number of the process that is holding the
lock.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)

iD8DBQFEfU4yCg7APGsDnFERAoFhAKCmJeLRdmE2yYE2FBSsrC31trazEQCaAqH1
KXypI+Cu9MVxWtUxlqyWwXQ=
=yXNG
-----END PGP SIGNATURE-----




reply via email to

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