I set something similiar up once. I used the cvslock program (forgot the link,
sorry) wrapped in rsync or rdist to wrap the backup of each major module (once
each for x in $CVSROOT/*) with a read lock/unlock cycle for that section of the
tree. You can change the granularity depending on what kind of integrity is
important to you, but this level worked for my purposes.
Derek
"Greg A. Woods" wrote:
> [ On Thursday, May 25, 2000 at 13:54:07 (-0400), Noel L Yap wrote: ]
> > Subject: Re: CVS Source Repository
> >
> > Preventing login to the machine is a bit overkill for this purpose, don't you
> > think?
>
> Actually I was thinking that if all the backups are done at that time
> then they'll all have better integrity. :-)
--
Derek Price CVS Solutions Architect
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
I will not prescribe medication.
I will not prescribe medication.
I will not prescribe medication...
- Bart Simpson on chalkboard, _The Simpsons_
