[cvsnt] Locking??

[Keith D. Zimmerman]

ok, a read lock i can live with.  But does it have to do a read lock on
the entire repository?  Or is it doing it on the top level module, or
what?  And the write lock, is that also the entire repository?

keith d. zimmerman, mcsd 
eagle solutions

-----Original Message-----
From: Tony Hoyle [mailto:tmh at nodomain.org] 
Sent: Friday, January 31, 2003 5:15 AM
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Locking??


On Fri, 31 Jan 2003 02:29:23 -0500, "Keith D. Zimmerman"
<kzimmerman at eshcom.com> wrote:

>While doing the following:
>
>	cvs -d :ssh:user at servername:/cvsroot co module
>
>And doing this on another computer:
>
>	cvs -d :ssh:user at servername:/cvsroot rtag -F -R -b tagName
module
>
>The computer that is doing the rtag gets this error:
>	waiting for SYSTEM's lock in
module/subdir/subsubdir/subsubsubdir
>
>Note that module is very large - many files/folders are being checked 
>out, but does checkout do a lock?  Why?  I can see that rtag would need

>to do a lock, but why checkout?
>
Checkout does a read lock.  You can have multiple read locks on a
repository.  However rtag needs a write lock, which is an exclusive
lock, and can't happen until all reads of the repository have finished
(you don't want the checkouts to get inconsistent copies of the
repository).

Tony

_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt