[Top][All Lists]

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

RE: cvs lock ..

From: Gurpreet Singh (SCM)
Subject: RE: cvs lock ..
Date: Fri, 8 Oct 2004 10:01:42 +0530

That's fine for now, that for the lock directory where these are being
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 a given amount of time is a
*dead*/stale process id and killing the same.

any thoughts on this !!

Gurpreet S

-----Original Message-----
From: Malhotra, Neti [mailto:address@hidden
Sent: Thursday, October 07, 2004 9:55 PM
To: Gurpreet Singh (SCM); Guus Leeuw jr.; address@hidden
Subject: RE: cvs lock ..


You can try looking directly in the repository for a cvslock file (#cvslock,
.#cvslock or something like that).  It should be in the directory of the
file that caused the problem.  If you can remove it manually, it may solve
your problem.


-----Original Message-----
From: address@hidden
[mailto:address@hidden Behalf Of
Gurpreet Singh (SCM)
Sent: Thursday, October 07, 2004 11:53 AM
To: Guus Leeuw jr.; address@hidden
Subject: RE: cvs lock ..

So what workaround can there be to check this !! 

Gurpreet S

> -----Urspr√ľngliche Nachricht-----
> Von: address@hidden 
> [mailto:address@hidden Im 
> Auftrag von Gurpreet Singh (SCM)
> Gesendet: donderdag 7 oktober 2004 11:06
> Betreff: cvs lock ..
> It gives a message "waiting for <sys_user>'s lock at <CVS_File_Path>"

I've seen this only happening when somebody did a cvs ci and forgot about
it, or when a CVS process dies somehow before nicely cleaning up.


Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (
Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004

Info-cvs mailing list

reply via email to

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