[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: RE: Getting rid of locks (release command doesn't do anything
From: |
Schwenk, Jeanie |
Subject: |
RE: RE: Getting rid of locks (release command doesn't do anything |
Date: |
Wed, 18 Jul 2001 11:15:48 -0700 |
ignore the trailing ' it was a type-o
> -----Original Message-----
> From: Schwenk, Jeanie
> Sent: Wednesday, July 18, 2001 11:11 AM
> To: Cvs (E-mail); 'address@hidden'
> Subject: RE: Getting rid of locks (release command doesn't do
> anything
>
> Here's the brute force method to deal with locks in unix. It's VERY
> dangerous. You could first "exec ll" rather than "exec rm -rf" to see
> what will be deleted. I've used this here and it works but it gets ALL
> the locks from the point you run it down. So, if you run it from the top
> of the repo, ALL locks in the repo will go away. This might not be what
> you want.
>
> find . -name "\#cvs.[rw]fl*" -print -exec rm -rf {}\'
>
> This will remove locks that look like:
> #cvs.wfl.dioptase.15497 (dioptase is a node name and the 15497 is
> the pid)
> #cvs.rfl
> #cvs.wfl
>
> You may also have lock directories that look like this: #cvs.lock/
>
>
> Just modify the above find to do the job.
>
> Jeanie