[oclug] CVS Lock File
Brenda J. Butler
bjb at achilles.net
Sun Jan 21 09:07:03 EST 2001
On Fri, Jan 19, 2001 at 08:48:34AM -0500, Collin McCrank wrote:
> Somebody here has tried to checkout /checkin a file from or local CVS
> and the file is locked. In essence nobody can update this file. Does
> anybody know of a way to get rid of this LOCK?
The FILES section of man cvs (version 1.10.7) shows:
#cvs.lock
A lock directory created by cvs when doing sensitive
changes to the source repository.
#cvs.tfl.pid
Temporary lock file for repository
#cvs.rfl.pid
A read lock.
#cvs.wfl.pid
A write lock.
Not sure where these will be, I presume in the repository at the
level where you issued the command? Or in the repository at the
directory where the action is taking place.
It's been a while since I did serious cvs administration, I can't
remember anything about lock files except they were there, and
may not have been documented in the man pages in earlier versions
of cvs. And I think they clean themselves up after a while
(but you may not want to wait for it).
Aha, some poking around shows that at the time I used cvs, rcs
was in charge of locking. (Rcs has since been made obsolete,
and cvs does all the work rcs used to do.)
Some more poking around shows that the lock files might
be going in a directory set by the new LockDir option in
CVSROOT/config. The default continues to be to put the lock
files in the repository itself.
That last bit came from the NEWS file distributed with cvs
(debian potato distribution).
HTH
--
bjb at achilles.net
I am the "ILOVEGNU" signature virus. Just copy me to your signature.
This email was infected under the terms of the GNU General Public License.
More information about the OCLUG
mailing list