[cvsnt] Re: Repository TAG behavior

[Randy McCharles]

I have seen this before and the cause appeared to be some very large binary files that were put under source control. cvsnt appears to spend an inordinate amount of time tagging these large files, which I suspect the only requirement is to add a couple of lines of RCS text to the top of the file.
Regardless, one I noticed the large binaries, I immediately took them out of source control and the tag timeout problem went away. (As did other "wait" problems such as very long checkout times.)

Randy McCharles

SMART Technologies Inc.

Senior Software Developer

Tel. 403.802.3347  Fax 403.229.2531
randymccharles at smarttech.com
http://www.smarttech.com

Bringing people and ideas together.(tm)



-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Michael Wojcik
Sent: Monday, February 06, 2006 8:40 AM
To: cvsnt at cvsnt.org
Subject: RE: [cvsnt] Re: Repository TAG behavior


> From: cvsnt-bounces at cvsnt.org 
> [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Tony Hoyle
> Sent: Sunday, 05 February, 2006 17:44
> 
> Alberto Di Fede wrote:
> > 
> > To be more precise this behavior fails when two concurrent TAG are
done 
> > on the same repository. At one point in the middle of the TAG the
two 
> > operations try to tag the same file at the same time: as you wrote,
the 
> > lock server try for 20 seconds then it returns a fail to one of the
two 
> > operations while letting the other one finish.
> > 
> tag itself won't lock an individual file for 20 seconds though... it's

> not a situation that will normally arise, even if you try multiple
tags 
> of the entire repository (which is itself fairly unusual).