RE: cvs lock ..

[Gurpreet Singh (SCM)]

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 a given amount 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:address@hidden
Sent: Thursday, October 07, 2004 9:55 PM
To: Gurpreet Singh (SCM); Guus Leeuw jr.; address@hidden
Subject: RE: cvs lock ..


Gurpreet,

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.

Neti

-----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 !! 

Regards
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.

Guus

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



_______________________________________________
Info-cvs mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/info-cvs