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.
> From: cvsnt-bounces at cvsnt.org > [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Randy McCharles > Sent: Tuesday, 07 February, 2006 12:11 > > I suspect putting the binaries in a separate repository will > just move the problem. You won't experience time-outs on the > original repository, but will on the new one. It would be an > interesting experiment. If time-outs continue on the original > repository. i.e. if the original is being tagged while > another client is committing or tagging the binary > repository, then this would imply that the lock-server is > being tied up and not the actual files. This is my suspicion too, based on the behavior we're seeing. We've seen tagging conflicts when tagging modules (with rtag), tagging all the files in a directory (with tag and a directory argument), and tagging specific files in a directory (with tag and filename arguments). And some of those conflicts were for unrelated files. It appears to be a lockserver bug (or a rather subtle feature of some sort), but as I said, I didn't see anything obvious when I traced the lockserver traffic in some local testing, or when I looked at the lockserver source. "cvs tag" locks individual files while it tags them, and the lockserver appears to be comparing the entire lock-target string when checking for conflicts. I may have to reproduce this artificially in a debug environment to find out what's going on. That will probably take a while, as I haven't tried to build CVSNT from source yet, and then I'll have to try to find a case where I can consistently reproduce it on my own server. -- Michael Wojcik Software Systems Developer, Comms phone 517 676-0892 Micro Focus mobile 517 862-9464 Mason, Michigan