Should be fine. When we had that issue coming up we whacked the locks one at a time but automating should be safe. I would be a little troubled that it's happening constantly. If asked to guess I'd pick Tortoise over Eclipse as the culprit. We have dozens of Eclipse users accessing our repository at all hours of the day and night and never get that lock thingy.
-----Original Message----- From: S I [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 22, 2005 2:27 PM To: Rod Macpherson; [email protected] Subject: RE: CVS Lock Files 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" <[EMAIL PROTECTED]> To: "S I" <[EMAIL PROTECTED]>,<[email protected]> Subject: RE: CVS Lock Files Date: Wed, 22 Jun 2005 14:12:46 -0700 MIME-Version: 1.0 Received: from exchange1.meddatahcs.com ([66.193.203.133]) by MC8-F38.hotmail.com 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 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: CVS Lock Files Thread-Index: AcV3bmIGFH4V5F6wRG2knwRi1xbkTAAAExQg Return-Path: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of S I Sent: Wednesday, June 22, 2005 2:01 PM To: [email protected] Subject: CVS Lock Files Hi I've setup a cronjob on our unix server to run nightly to clean up CVS lock files before my build and before tagging CVS. A user using Tortoise accidentally caused certain folders in the repository to lock up during my 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 COULD 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? #!/bin/sh # 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 Steve _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
