[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: locking a file exclusively

From: Mark D. Baushke
Subject: Re: locking a file exclusively
Date: Tue, 30 Mar 2004 23:27:35 -0800

Hash: SHA1

Sandhya <address@hidden> writes:

> I was just wondering if we could lock a file exclusively so that
> others cannot edit that file.

All users will have full control over all files in their checked out
tree. Even if cvs initially provides read-only permissions to a given
file, the users may still change those permissions and modify the file.

If you mean that you do not want to allow other than a particular user
to commit change to it, then that is a different question.

You might also be asking about 'cvs edit' and 'cvs watch' functionality
that provide advisory locks. Those locks are not strict and may be
ignored by users.

Depending on the nature of the particular file or files that are to be
locked, you might write your commitinfo script reject any user attempt
to commit changes to that file by anyone other than a particular user or
set of users you have specified.

Failing that, there are various patches that try to implement strict
locking on top of cvs floating around out there, a search for "cvs edit
- -c" might turn up Noel Yap's patches... I have not looked at them in a
long time... once upon a time there was an rcvs project,
but I can't seem to find it this evening.

If that is not good enough, I would recommend you look around and
consider using another system for your source control. One that provides
reserved strict locking.

        Good luck,
        -- Mark
Version: GnuPG v1.2.3 (FreeBSD)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]