Mark D. Baushke wrote:
[...]
Or, you can just specify the remote repository with the -d argument to
cvs.
Yes, one can do that also.
In addition, if you use the CVS_LOCAL_BRANCH_NUM patch that has been
committed to the cvshome main trunk (already available for various of
the *BSD versions of cvs),
Mahantesh M Vantmuri <[EMAIL PROTECTED]> writes:
> Mark wrote:
>
> >Haven't looking into this much, but if CVSup can send based on date,
> >maybe it can be used to assist failover. Any thoughts from those that
> >have used/are using CVSup?
> >[...]
> >
> We are using cvsup as a repository syncing
Mark wrote:
Haven't looking into this much, but if CVSup can send based on date, maybe it
can be used to assist failover. Any thoughts from those that have used/are
using CVSup?
[...]
We are using cvsup as a repository syncing tool. The cvsup client,
running on machine having local repositiry, ge
Haven't looking into this much, but if CVSup can send based on date, maybe it
can be used to assist failover. Any thoughts from those that have used/are
using CVSup?
For example (active means cvs server working for users):
=
Normal operations:
On Fri, Mar 14, 2003, Eric Siegerman wrote:
> On Wed, Mar 05, 2003 at 10:39:21AM -0500, [EMAIL PROTECTED] wrote:
> > I'm looking for gotchas and best practices in implementing a failover
> > repository for CVS. The idea would be to use rsync or something similar to
> > copy the contents of a repos
On Wed, Mar 05, 2003 at 10:39:21AM -0500, [EMAIL PROTECTED] wrote:
> I'm looking for gotchas and best practices in implementing a failover
> repository for CVS. The idea would be to use rsync or something similar to
> copy the contents of a repository to a failover server with the cvspserver
> entr
I'm looking for gotchas and best practices in implementing a failover
repository for CVS. The idea would be to use rsync or something similar to
copy the contents of a repository to a failover server with the cvspserver
entry disabled in /etc/xinetd.d (RedHat 7.3 servers). In the case of
failure of
