Re: locked file unlocked by any user

[Larry Jones]

MURVAI-BUZOGANY Laszlo writes:
> 
> So, the problem is, that any file, locked by any ordinary user, may be
> unlocked by any - same or other - user, and then locked again with his own
> lock. There is an error message when an other user wants to lock an already
> locked file, or unlocks a file that is not locked. But, when wanting to
> unlock a file locked by anyone, it gets unlocked immediately, without any
> warning or error.

Note that that only happens if you specify a particular revision to
unlock; if you just use -u with no revision, you get a message telling
you that you don't have the file locked.  In this situation, RCS would
tell you that the file is locked by someone else and ask you if you want
to break the lock or not.  Unfortunately, that is not compatible with
CVS's client/server operation since only the server knows about locks
and only the client is able to communicate with the user.  So, I've
checked in a change that at least tells you that you've broken someone
else's lock.  (Note that the original locker does gets notified of
broken locks if they have asked for commit notification on the file via
"cvs watch add".)

-Larry Jones

If I was being raised in a better environment, I wouldn't
do things like that. -- Calvin