[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: #cvs.locks directories multiplying
From: |
Larry Jones |
Subject: |
Re: #cvs.locks directories multiplying |
Date: |
Fri, 11 Feb 2005 17:24:00 -0500 (EST) |
John Davin writes:
>
> I checked the repository and it does have nested #cvs.locks directories
> (which doesn't even make sense because there's no point in putting
> #cvs.locks within other #cvs.locks's), but I definitely did not put them
> there, nor did anyone else.
Sorry, the CVS lock file is named #cvs.lock, not #cvs.locks. From your
description of what's happening, I'm betting that that's not a typo and
that your stray directories really are named #cvs.locks. In that case,
somebody (not CVS) created them -- perhaps a defect in some kind of a
backup script that's attempting to lock the entire repository. You
should delete them: as far as CVS is concerned, they're legitimate
repository directories, which is why it's checking them out.
-Larry Jones
...That would be pretty cool, if they weren't out to kill me. -- Calvin