[Top][All Lists]

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

RE: CVS Lock Files

From: S I
Subject: RE: CVS Lock Files
Date: Wed, 22 Jun 2005 14:26:47 -0700

Thank you. But do you see anything wrong with me manually removing such files? They won't corrupt CVS or anything like that, would they?

p.s. the user is using tortoise with eclipse and I think that's what caused it or rather doing a search for tags within tortoise.

----Original Message Follows----
From: "Rod Macpherson" <address@hidden>
To: "S I" <address@hidden>,<address@hidden>
Subject: RE: CVS Lock Files
Date: Wed, 22 Jun 2005 14:12:46 -0700
MIME-Version: 1.0
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.211); Wed, 22 Jun 2005 14:13:13 -0700
X-Message-Info: JGTYoYF78jG7Wo4tVlYkO3SAsLmFQsbTobegfEpTil8=
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Thread-Topic: CVS Lock Files
Thread-Index: AcV3bmIGFH4V5F6wRG2knwRi1xbkTAAAExQg
Return-Path: address@hidden
X-OriginalArrivalTime: 22 Jun 2005 21:13:13.0132 (UTC) FILETIME=[330A5EC0:01C5776F]

Thing is, if this is that frequent there ottabee many reports of stray
locks. I can say we are not seeing that at all but will admit it used to
show up with a product called SmartCVS - not pointing the finger at that
product, just conveying our experience.

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf
Of S I
Sent: Wednesday, June 22, 2005 2:01 PM
To: address@hidden
Subject: CVS Lock Files


I've setup a cronjob on our unix server to run nightly to clean up CVS
files before my build and before tagging CVS.   A user using Tortoise
accidentally caused certain folders in the repository to lock up during
build (about 3x's in 1 week) and tagging took about 600 minutes
(pending) to
complete until I manually removed the offensive "#cvs.*.*" files on the
server side and we cleaned up her Windows PC of any cvs.lock.tmp or
cvs.lock.folder pattern files and folders.  We seem to be OK now since I

deleted the files.

During my research I've found out that there're PERHAPS 3 ways files
be locked up UNINTENTIONALLY (NOT executing cvs admin -l):

1. Multiple users concurrently doing checkout, commit, or update.

2. Tagging?

3. And by means of an IDE such as IntelliJ or Eclipse?

Do you see anything wrong or dangerous with my unix script below?


# Delete lock debris on cvs

find /usr/local/cvs -name "#cvs.lock*" -print | xargs rm -fdr
find /usr/local/cvs -name "#cvs.lock.*" -print | xargs rm -f
find /usr/local/cvs -name "#cvs.rfl.*" -print | xargs rm -f
find /usr/local/cvs -name "#cvs.wfl.*" -print | xargs rm -f
find /usr/local/cvs -name "#cvs.pfl.*" -print | xargs rm -f
find /usr/local/cvs -name "#cvs.tfl.*" -print | xargs rm -f
find /usr/local/cvs -name "cvsloc" -print | xargs rm -fdr

Thank you


Info-cvs mailing list

reply via email to

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