Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Mon, 3 Oct 2005 16:43:16 -0600, "Lehman, Curtis" <CLehman at carrieraccess.com> wrote: >Bo, > >Do you have any suggestion on how to mitigate or fix this issue? I am >worried my system will run into this eventually since we are revision >controlling binary files (-kb) that change a lot. I was wondering if I could >change the way CVS saved the file, maybe by switching to the -KB for delta >binary's? Can I make this change on existing binary files and still retain >the ability to pull early versions that were under the -kb option? > >Any other suggestions on what we could do to prevent this from happening? > >Thanks, >Curt As far as I know there are just these few things you can do: 1) As you suggested change to binary deltas. I have never tried this myself so I don't know all ramifications, but one is a complete break with standard RCS file format so you cannot go back to a non-CVSNT server on these repositories. I also do not think that this will affect the existing data, only new additions to the file. If the file changes a lot inside for your actions then binary deltas might not even help... 2) Get a *lot* more RAM for your server 3) Use the cvs admin command to get rid of the non-relevant revisions in the file. This is a *very* slow and painstaking process on big RCS files and the server must be able to work with the file in the first place. How big was the RCS file in your repository when you checked? And how much physical RAM is the server equippped with? /Bo (Bo Berglund, developer in Sweden)