[Top][All Lists]

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

Re: CVS replication question from a noob

From: Mark D. Baushke
Subject: Re: CVS replication question from a noob
Date: Fri, 19 May 2006 10:29:44 -0700

Hash: SHA1

Arnar Þórarinsson <address@hidden> writes:

> On Thu, 2006-05-18 at 13:33 -0500, Todd Denniston wrote:
> > Arnar Þórarinsson wrote:
> > > Hi,
> > > 
> > > Heres my situation.  I have a CVS server that is located behind a
> > > firewall and I have to replicate that CVS server ,or at least 2-3
> > > modules in it, to a CVS "server" outside the firewall.  What are my
> > > options ? The firewall allows all connections out but blocks connections
> > > that originate from the outside.
> > > As I  understand CVSup it does a pull from the master cvs server so that
> > > method would be out for me.  Are there any replication methods that use
> > > a "push" from the CVS master ?
> > > 
> > 
> > We need a bit more information before the question can really be
> > answered... Q) Do you need to be able to commit to the replicated
> > copy or is it read only?

>      Read only

You are possibly interested in using 'rsync'
you will find it here:

A possible command to run on a periodic basis is here:

  rsync \
    --blocking-io \
    --delete \
    --group \
    --links \
    --owner \
    --perms \
    --recursive \
    --stats \
    --times \
    --verbose \
    --exclude '#cvs*' \
    --exclude ',*,' \
    --exlucde 'CVS'
    /path/to/your/master/repository \

The --exclude '#cvs*' is not needed if you use LockDir=/some/path in
your CVSROOT/config where /some/path is outside of the tree you are
using for your repository.

The --exclude ',*,' stops you from sending over files that are in the
process of being committed.

The --exclude 'CVS' stops you from sending over the CVS/fileattr files
where users have done various 'cvs watch' and 'cvs edit' commands.

As to WHEN you want to trigger the rsync, that can be more

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


reply via email to

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