Martin Marques wrote:
I'm trying to commit some changes I made to one of my repositopries, and I get
constantly this message:
cvs commit: [19:37:22] waiting for martin's lock in /var/lib/cvs/siprebi/sql
When I look at the /var/lib/cvs/siprebi/sql directory I find lots of locks:
bugs:/var/lib/cvs/siprebi/sql# ls \#cvs*
#cvs.pfl.bugs.19610 #cvs.rfl.bugs.19217 #cvs.rfl.bugs.19578
#cvs.rfl.bugs.20224 #cvs.rfl.bugs.3410
#cvs.rfl.bugs.18898 #cvs.rfl.bugs.19263 #cvs.rfl.bugs.19610
#cvs.rfl.bugs.20243 #cvs.rfl.bugs.3419
#cvs.rfl.bugs.19016 #cvs.rfl.bugs.19301 #cvs.rfl.bugs.19891
#cvs.rfl.bugs.22395 #cvs.rfl.bugs.3443
#cvs.rfl.bugs.19058 #cvs.rfl.bugs.19448 #cvs.rfl.bugs.19899
#cvs.rfl.bugs.22633
#cvs.rfl.bugs.19201 #cvs.rfl.bugs.19467 #cvs.rfl.bugs.20217
#cvs.rfl.bugs.3392
Can they be deleted?
are you sure martin is not doing anything in the repo?
how old are the files, e.g.,
cd /var/lib/cvs/siprebi/sql; ls -ltrh \#cvs*
how long has the machine been up?
are there any cvs processes up with the PIDs listed on the ends of the files,
i.e.,
ps aux |grep cvs
That is...If you _know_ the locks are bogus, yes.
And why aren't they been removed automatically?
If you are working in client server mode, something is killing the cvs server
with extreme prejudice, like a 'kill -9' or the power being pulled.
If you are working directly with the directory (CVSROOT=/var/lib/cvs/), the
same things as happened to the server could be happening to your cvs program.
What version(s) of CVS are you using??
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
_______________________________________________
info-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/info-cvs
