[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: CVS Lock Errors

From: S I
Subject: RE: CVS Lock Errors
Date: Thu, 16 Jun 2005 22:53:45 -0700

Thank you all for your help.

I found out(by googling) this was the case and cvs had left out debris of #cvs.rfl.blah.blah files in certain directories on the server as well as cvs.lock files on the user's pc. Once we made sure she had checked in all his work, we manually deleted the .lock files and everything SEEMS to be ok now. Thank you for the useful information. It's always good to know more :)

Thanks again

----Original Message Follows----
From: "Arthur Barrett" <address@hidden>
To: "S I" <address@hidden>,<address@hidden>
Subject: RE: CVS Lock Errors
Date: Fri, 17 Jun 2005 10:32:42 +1000
MIME-Version: 1.0
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.211); Thu, 16 Jun 2005 17:46:19 -0700
X-Message-Info: JGTYoYF78jH8W+5Xll35zI9kPqLdLWobjEchZ/b194k=
content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Thread-Topic: CVS Lock Errors
Thread-Index: AcVyqNiqBr4ZKrETSUePSnLXucct9QAKkT6N
Return-Path: address@hidden
X-OriginalArrivalTime: 17 Jun 2005 00:46:19.0718 (UTC) FILETIME=[F9F60E60:01C572D5]


This is quite a common problem (at least for some people).

CVS locks at the directory level on the server, by creating a "lock file". If the server process terminates unexpectedly (eg: kill -9) then the "lock file" is left in place. To "unlock" your repository remove the lock files.

CVSNT (open source, GPL, Linux, Unix, Mac, Windows, just like CVS) resolves this by having a separate lock server process. If the client process dies so do the locks. It also means that checkout and update are atomic. CVSNT also includes "chacl", "lsacl" etc for setting access control lists on branhes etc which I notice was another question of yours in another thread).

If you are using Tortoise on the client - by default Tortoise uses the CVSNT client (it comes with Tortoise) - you will get better integration if you use CVSNT server and Tortoise with CVSNT...

If you are interested in CVSNT please refer questions to the CVSNT newsgroup:


Arthur Barrett

-----Original Message-----
From: address@hidden on behalf of S I
Sent:   Fri 6/17/2005 5:35 AM
To:     address@hidden
Subject:        CVS Lock Errors


I have a 2nd question:

A user using Tortoise window's client using :pserver to the linux box,
executed the commad searching for tags.  Not a specific tag but all tags in
the repository.  The command's been running for about 15 hours now, locking
cvs, and not allowing anyone else to tag.  We can update, commit, etc but
not tag. And I do need to tag my build today.

When I try to tag, I get the error msg that so & so user has it locked. When
I do -cvs admin -U, the server says waiting for the user's lock, etc.

On the linux server side, I thought it was a ps process I could kill...but

How can I kill this annoying process?  I told him to delete all his working
folders, reboot, and check out fresh and anew again.

Any suggestions?

Thank you


Info-cvs mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]