Thanks for the reply, but we were able to figure out the problem. The locks were being stored in a separate lock directory, rather than in cvsroot.
- Jeff On Wed, Apr 15, 2009 at 10:32 PM, Arthur Barrett < [email protected]> wrote: > Jeff, > > Please send the exact error message and the exact command including the > CVSROOT along with the version of CVS you are using (you can get the version > of CVS client and server from the command 'cvs ver'). > > Regards, > > > Arthur Barrett > > > -----Original Message----- > *From:* [email protected] [mailto: > info-cvs-bounces+arthur.barrett <info-cvs-bounces%2Barthur.barrett>= > [email protected]] *On Behalf Of *Jeff Simpson > *Sent:* Wednesday, 15 April 2009 3:20 PM > *To:* [email protected] > *Subject:* waiting for lock, but no lock exists > > I'm using CVS on an AFS mount, and running into this problem where it > claims to be waiting for a lock by my own user. I look through the repo > directly and see nothing that resembles a lock file. Any idea what could > cause this or how to forcibly reset locks? Thanks > > - Jeff > >
