Re: Setting up write proxying

[Mark D. Baushke]

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

Jon Foster <address@hidden> writes:

> I'm trying to set up two servers as primary and secondary CVS servers,
> using write proxying.  Please can someone point me at a simple guide to
> do this?  (If no simple guide exists, please give me a few pointers &
> I'll write the guide).
> 
> The CVS manual[1] rather unhelpfully gives an example that appears to be
> wrong[2] and incomplete[3].
> 
> Thanks!
> 
> Kind regards,
> 
> Jon Foster
> 
> [1]
> http://ximbiot.com/cvs/wiki/index.php?title=CVS--Concurrent_Versions_Sys
> tem_v1.12.12.1:_The_Repository#Distributing_load_across_several_CVS_serv
> ers
> [2] http://lists.gnu.org/archive/html/info-cvs/2005-04/msg00047.html

The message gives an exaple of how to fix things.

> [3] The manual itself says "You would probably actually want to lock
> directories for write on the secondary and for read on the primary
> before running the `rsync' in the above example, but describing such a
> setup is beyond the scope of this document".  Help!!

There are a number of methods that you could use to syncronize the
primary and secondary servers. The simplest from a functional point of
view is probably CVSup, but it requires some work to get CVSupd and
CVSup installed and operational. Alternatives such as doing an rsync of
a particular list of files can be problematic as has been mentioned, so
you would need to either use something like 'cvslock' which is able to
create CVS locks in your repository for you.

Other alternatives include ad hoc knowledge in commitinfo triggers about
the state of any synchronization operation that may be in progress.

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

iD8DBQFEYhLKCg7APGsDnFERAipqAKDNzzcIc+82vVMqwV59EssWk1U8zACfUT99
0PD6sKAfNZN9bZR4s1IDsic=
=uP98
-----END PGP SIGNATURE-----