info-cvs
[Top][All Lists]
Advanced

[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 15:41:25 -0700

Thanks.

I think(?) we've pinpointed the culprit (search for tags in Tortoise) and have asked the user not to execute and redo what she did to cause the problem. So since last week the problem has stopped. So I deduced that was the culprit.

In the mean time, I could modify my shell script to do a combo on 'find' : find ..../cvs/ -name *lock* && -ctime? I'll look for any locks older than a certain number of days. However, the problem is that our Builds are automated and at 2 a.m. I'm not here watching them to call or stop the person who caused the problem and if the builds are successful, the tagging must go on.

----Original Message Follows----
From: address@hidden (Larry Jones)
To: address@hidden (S I)
CC: address@hidden, address@hidden
Subject: Re: CVS Lock Files
Date: Wed, 22 Jun 2005 18:22:17 -0400 (EDT)
MIME-Version: 1.0
Received: from sdrc.com ([146.122.132.195]) by mc5-f16.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 22 Jun 2005 15:22:19 -0700 Received: from sunlist.sdrc.com (sunlist.sdrc.com [146.122.142.20])by sdrc.com (8.9.1/8.9.1) with ESMTP id SAA16078;Wed, 22 Jun 2005 18:22:18 -0400 (EDT) Received: from thor.net.plm.eds.com (thor.net.plm.eds.com [146.122.201.250])by sunlist.sdrc.com (8.11.6+Sun/8.11.6) with ESMTP id j5MMMId07711;Wed, 22 Jun 2005 18:22:18 -0400 (EDT) Received: (from address@hidden)by thor.net.plm.eds.com (8.11.6/8.10.1) id j5MMMHF28349;Wed, 22 Jun 2005 18:22:17 -0400 (EDT)
X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtfpLB7P/ybN8=
X-Mailer: ELM [version 2.5 PL3]
Return-Path: address@hidden
X-OriginalArrivalTime: 22 Jun 2005 22:22:19.0839 (UTC) FILETIME=[DAABA4F0:01C57778]

S I writes:
>
> 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?

Yes, it very well might.  You're not making any attempt to differentiate
between legitimate lock files (caused by someone currently running CVS)
and stale lock files (those left over from something horrible
happening).  Removing legitimate lock files is a recipe for disaster.
Figuring out which is which is somewhat tricky, particularly in a
script, so I strongly suggest you figure out what the horrible thing is
that's happening to leave you with stale lock files and fix it.

-Larry Jones

Just when I thought this junk was beginning to make sense. -- Calvin






reply via email to

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