(UPDATE) (UPDATE) getting rid of locks (release command doesn't d o anything)

[Roger Thornblad]

Sorry for all the posts.  We've resolved the problem (we think) and are
testing everything to make sure.

Next time we'll read a little more B4 posting questions.

R.

>  -----Original Message-----
> From:         Roger Thornblad  
> Sent: Wednesday, July 18, 2001 9:39 AM
> To:   'address@hidden'
> Subject:      (UPDATE) getting rid of locks (release command doesn't do
> anything) 
> 
> OK, we found the #cvs.lock and #cvs.wfl..... files and directories.  Is it
> safe to just remove them if we know the repository is not being used by
> anyone?
> 
> Thanks,
> 
> Roger.
> 
> 
> 
>  -----Original Message-----
> From:         Roger Thornblad  
> Sent: Wednesday, July 18, 2001 9:30 AM
> To:   'address@hidden'
> Subject:      Getting rid of locks (release command doesn't do anything)
> 
> To All,
> 
> 1.  General Problem
> 
> A commit procedure failed and now we get an error message regarding a lock
> on a directory in the repository.
> 
> 2. Details
> 
> We were in the middle of a commit and the developer didn't include the -m
> option.  He also piped the output to a file.  He received an error about
> the output not being a terminal and then the process hung.  Now whenever
> we try and perform an operation we get an error stating it's waiting for
> the developers lock on a directory in the repository that's several
> directories down from the root dir of the project.
> 
> We have tried the release command with no change.  
> 
> What do we have to do to clear the lock(s) (there may be others we haven't
> yet seen) so we can start using the CVS system again?
> 
> Regards,
> 
> Roger.