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
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
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; info-cvs@gnu.org
Subject: RE: CVS Lock Files
Thank you. But do you see anything wrong with me manually
Follows
From: Rod Macpherson [EMAIL PROTECTED]
To: S I [EMAIL PROTECTED],info-cvs@gnu.org
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
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
are successful, the tagging
must go on.
Original Message Follows
From: [EMAIL PROTECTED] (Larry Jones)
To: [EMAIL PROTECTED] (S I)
CC: [EMAIL PROTECTED], info-cvs@gnu.org
Subject: Re: CVS Lock Files
Date: Wed, 22 Jun 2005 18:22:17 -0400 (EDT)
MIME-Version: 1.0
Received: from sdrc.com
Message Follows
From: Todd Denniston [EMAIL PROTECTED]
To: S I [EMAIL PROTECTED]
CC: info-cvs@gnu.org
Subject: Re: CVS Lock Errors
Date: Thu, 16 Jun 2005 19:13:39 -0500
MIME-Version: 1.0
Received: from mail.ssa.crane.navy.mil ([164.227.42.3]) by
mc3-f29.hotmail.com with Microsoft SMTPSVC
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 [EMAIL PROTECTED]
To: S I [EMAIL PROTECTED],info-cvs@gnu.org
Subject: RE: CVS Lock Errors
Date: Fri, 17 Jun 2005 10
S I wrote:
Hi
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
Steven,
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
, 2004 12:09 PM
To: Gurpreet Singh (SCM)
Cc: [EMAIL PROTECTED]
Subject: Re: cvs lock ..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is a script I have used in the past to locate and
possibly to clean stale cvs locks that might exist.
It should be noted that most of those stale locks only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Christopher,
[EMAIL PROTECTED] writes:
Running your script on my RH Fedora gives the following errors. Any
clues?
What perl version are you using?
I have tried
cvs -d /tmp/mytest-repos init
/some/path/to/perl ./find-cvs-locks -d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is a script I have used in the past to locate and possibly to clean
stale cvs locks that might exist.
It should be noted that most of those stale locks only happen when cvs
exits abnormally or the system itself crashes.
I hope you find it
: RE: cvs lock ..
Hi,
That's fine for now, that for the lock directory where these are being
created.
But I am looking for a work-around which can identify (how?) between a live
cvs-client process and a *dead*/stale cvs-client process or else atleast an
assumption that the pids lasting since say
So what workaround can there be to check this !!
Regards
Gurpreet S
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im
Auftrag von Gurpreet Singh (SCM)
Gesendet: donderdag 7 oktober 2004 11:06
Betreff: cvs lock ..
It gives a message waiting for
of time is a
*dead*/stale process id and killing the same.
any thoughts on this !!
Regards,
Gurpreet S
-Original Message-
From: Malhotra, Neti [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 07, 2004 9:55 PM
To: Gurpreet Singh (SCM); Guus Leeuw jr.; [EMAIL PROTECTED]
Subject: RE: cvs lock
--- Forwarded mail from [EMAIL PROTECTED]
Hello. I have noticed several different kind of lockfiles that CVS
seems to create (and sometimes leave laying around) and was hoping
someone could help me out on what they are used for, when are they
created, where they are created, and when are they
bdcutler2001 writes:
Hello. I have noticed several different kind of lockfiles that CVS
seems to create (and sometimes leave laying around) and was hoping
someone could help me out on what they are used for, when are they
created, where they are created, and when are they removed.
If you encounter a ,DevelopersGuide.doc, file in the repository,
this is the working file that RCS primatives uses while
it is changing the file.
Typically, it works something like this:
cp DevelopersGuide.doc,v ,DevelopersGuide.doc,
make changes to ,DevelopersGuide.doc,
mv ,DevelopersGuide.doc,
Paddy T writes:
I haven't got any response for this question.If anyone
ever got such an error,pls give the remedy.I am still
unable to delete these lock files from the
reposiitory.
You haven't gotten any response because this isn't a CVS question and
you haven't provided enough details for
20 matches
Mail list logo
