[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Locking mechanisms
From: |
Mark D. Baushke |
Subject: |
Re: Locking mechanisms |
Date: |
Wed, 16 Jun 2004 01:01:07 -0700 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sandhya <address@hidden> writes:
> Needed to know if there was any possiblity of locking a particular
> file in the client so that the user can have a previlage of exclusive
> checkout.
No. Advisory locks exist in cvs, but exclusive locks do not unless you
dive in under the covers and play more directly with RCS locks than is
generally desirable.
> This should not allow other users to edit the file. Is there
> any particular way by which this can be acheived ?
I would recommend moving to another source control system if you need
exclusive checkouts.
> One way of thinking was writing a shell script which tracks the
> command for locking from a user, and registers his name in a lock-file
> in the same directory. When the user unlocks the file , this lock-is
> deleted. When others try to access this during locked period, it
> should give an error.
>
> Whether this would work out or not and if this method has any problems
> -- please let me know.
This topic has been discussed in the address@hidden archives a few
times.
Don't abuse the 'Concurrent Version System' to try to use non-concurrent
development methodologies. You will not be happy with the results.
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFAz/5D3x41pRYZE/gRArmmAKCw3Q8eRg5uxfhWjRFS2YGOFbKyWACg1Es2
BY5h/dYvifXvrB/ue/+FQdo=
=PoXC
-----END PGP SIGNATURE-----