Removal of file locks

( CVSSCC , VS .NET, 2.0.x, WIN 2000/XP, CVS NT 2.x >= 2.0.58 )

Type: Public Status:Closed Created: 30 May 06 05:00 Updated: 30 May 06 05:00

--> Igor Pushkov (admin) at 30 May 06 05:00 writes

The locking functionality maintained by server. It creates special entry on
server side foe every locked (edited) file.
I not know which way is better to solve this, but we just pull entire tree
of sources using user name of locking user, then lock all files again (or
you may lock only those that already locked) and the either unedit (unlock)
them or make a commit (which also does nothing but remove lock). The
solution is based on the fact that one user cannot lock one file twice.
It is probably also possible to modify repository administartion files
which however not a good idea, as I think.

--> peter sandstrom (user) at 30 May 06 05:00 writes

Hi,

Our developers use PushOk CVSSCC in Reserved checkout mode against a CVSNT
server. One user did a checkout of some sources and then deleted the
directory from his local PC without first checking the sources back in.
This now (ofcourse) results in a "File being edited" -message from CVSSCC
whenever trying to do a new reserved checkout of them.

I've been trying to find out how to reset this without any luck. I may be
wrong here but, the way I understood it the exclusive-locking mechanism is
maintained by the client software (using special files), not visible
directly as source files. If that's the case, is there any safe (enough)
way to reset the locks by removing these files or altering the content of
them?

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

Removal of file locks