Re: waiting for lock, but no lock exists

Thanks, but we already solved the problem. The configuration of the CVS tree
had the lock files in a separate directory I didn't know about. I'm not yet
sure why the lock files weren't being cleaned up properly, but now that I
know where they are being stored, it is easy to manually clean them up.

 - Jeff

On Sat, Apr 18, 2009 at 7:44 PM, Rob Jago <[email protected]>wrote:

>  I am not sure if this helps or not but I have seen this.
>
>
>
> Is there a virus scan program running?
>
> I have seen the virus scan program have a hold on the file while scanning
> at the same time that CVS is executing the check-in and/or tag operation.
>  At this time, CVS cannot work properly and reports the mysterious lock file
> (which doesn’t exist when you look for it after the fact)
>
>
>
> I am not sure if this helps or is off the mark.
>
>
>
> Cheers,
>
>
>
> Rob
>
>
>
>
>  ------------------------------
>
> *From:* [email protected][mailto:
> info-cvs-bounces+jago.mailing.list <info-cvs-bounces%2Bjago.mailing.list>=
> [email protected]] *On Behalf Of *Arthur Barrett
> *Sent:* Wednesday, April 15, 2009 10:32 PM
> *To:* Jeff Simpson; [email protected]
> *Subject:* RE: waiting for lock, but no lock exists
>
>
>
> 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
>
>