Well, an interruption during a CVS operation is precisely the kind of thing that will leave a "#cvs.lock", "#cvs.rfl" and/or "#cvs.wfl" file in the directory that is locked.
In a busy repository, I would normally will run a 'find /cvs/root -name "#cvs.*" -mtime 1' periodically on the entire repository in order to check to see if there are any dangling locks left out there for a day or more, then delete them. I'm running on Linux too, and I have never needed SmartCVS to clear locks. Scan your repository and see if there are any "#cvs.*" files there. I have a hunch you're not looking in the right place. http://ximbiot.com/cvs/manual/cvs-1.11.22/cvs_2.html#SEC17 pc On 7/26/07, Rupa N <[EMAIL PROTECTED]> wrote: > Actually I can't find any file #cvs.* in the directory. I'm told that the > lock happened as there was an interruption during some cvs operation. > > I got a suggestion to use Smart CVS and unlock them but I use Unix server > amd not SmartCVS. Any idea about this please? > > > On 7/26/07, Peter Connolly <[EMAIL PROTECTED]> wrote: > > > CVS locks are implemented by CVS creating lock files in the directory > > being committed: > > > > > http://ximbiot.com/cvs/manual/cvs-1.11.22/cvs_2.html#SEC17 > > > > Go in and delete the #cvs.* files and you will clear the lock. > > > > pc > > > > On 7/26/07, Rupa N <[EMAIL PROTECTED] > wrote: > > > Hi, > > > > > > > > > Can anybody help me with how to remove a lock on a file in CVS? > > > > > > CVS is not allowing any changes to be checked in.. > > > > > > Thanks in advance! > > > >
