Re: users and right on CVSROOT

[Noel Yap]

Any user that needs read access to the repository will
need to be able to create a lock file.  This means
that read-only users need write permissions on the
directory where that lock file is created.  However,
if write permissions were granted to the repository,
users would also gain checkin priveleges.  Therefore,
place the lock file into another directory if you need
to grant some users read-only priveleges to the repo.

Noel
--- address@hidden wrote:
> Thank you for your attention. Actually i meant
> "chown" and not "chmod" !
> For the second question about a lock directory, i
> wonder what is the 
> benefit to create an externel directory for the lock
> files ?
> And i don't know how to use the #cvs_lock files. Is
> it an important aspect 
> of cvs ? 
> 
> 
> Sylvain
> 
> 
> 
> 
> 
> 
> 
> address@hidden (Larry Jones)
> 04/02/2002 22:14
> 
>  
>         To:     address@hidden
>         cc: 
>         Subject:        Re: users and right on
> CVSROOT
> 
> 
> address@hidden writes:
> > 
> > By defaut only the root user got the read access
> on  the  CVSROOT's 
> files 
> > because i've launch the cvs init command with this
> account
> > So i've change the owner on this repository by a
> chmod command ( chmod 
> -r 
> > root.cvs cvs ) to give the cvs users an access to
> these files
> > (because my root user can't commit files, and
> anyway i've set the 
> > systemauth variable to "no")
> > Is it the correct method ?
> 
> I presume you mean "chown", not "chmod".  Yes, that
> looks reasonable.
> 
> > Does a lock directory would do the same ?
> 
> I don't understand the question.
> 
> And please send all CVS qustions to address@hidden
> rather than sending
> them directly to me.
> 
> -Larry Jones
> 
> Wheeee. -- Calvin
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Send FREE Valentine eCards with Yahoo! Greetings!
http://greetings.yahoo.com