[Top][All Lists]

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

Re: (cvs) how to restrict users

From: Ralf S. Engelschall
Subject: Re: (cvs) how to restrict users
Date: Thu, 6 Feb 2003 14:52:06 +0100
User-agent: Mutt/1.4i

On Thu, Feb 06, 2003, Shishir Singhai wrote:

>  can any body tell me how to restrict users editing the same file at a time

That's against the philosophy behind CVS. CVS was designed to explicitly
_allow_ people from editing a file at the same time. In case of no
conflict their changes are merged together. If a conflict situation
exists, the first person wins and the others have to resolve the
conflict individually. But keep in mind that in practice resolving a
conflict occurs a lot less often than the situation that you would be
not able to edit something because someone else is still working on
it. That's why CVS's approach is really the better one. If you insist
on restricting people from editing at the same time, IMHO you should
consider using CVS at all.

> I tried OSSP Shiela package but unable to run it. It gives me Error
> cvs Shiela Error: /usr/bin/cvs no such file or directory

OSSP shiela requires you to configure the path to your "cvs" binary
unless it is really in a default system path. Use the following in your
shiela.cfg for this:

 Environment {
     Program cvs /path/to/your/cvs;

> Is there any other tool to do the same

Be careful, OSSP shiela and similar tools do _NOT_ restrict your users
from _EDITING_ the same file at a time. As explained above, this is
against the design of CVS. OSSP shiela and similar tools "just" restrict
the _COMMIT_ access to files.
                                       Ralf S. Engelschall

reply via email to

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