[Top][All Lists]

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

RE: the server gets tougher!!!

From: kent emia
Subject: RE: the server gets tougher!!!
Date: Fri, 24 Oct 2003 16:29:34 +0800

On Fri, 2003-10-24 at 16:02, Gisbert Amm wrote:
> > 
> > after of several 'cvs -d /repo init' i've encountered problem 
> > which i've
> > never encountered before..
> > 
> > i've tried to set cvs to check systemusers loggin - in is fine but as
> > the second user tried to edit/checkout the work of the first user who
> > checked in the 2nd user encountered
> > 
> > 'cvs server: failed to create lock directory for `/repo/cdrdocs'
> > (/repo/cdrdocs/#cvs.lock): Permission denied'
> > 
> > do i have to create the '#cvs.lock
> > 
> Probably this helps:
> """
> LockDir is also a rarely used feature. In special circumstances, you may
> want to tell CVS to create its lockfiles somewhere other than directly in
> the project subdirectories, in order to avoid permission problems. These
> lockfiles keep CVS from tripping over itself when multiple operations are
> performed on the same repository directory simultaneously. Generally, you
> never need to worry about them, but sometimes users may have trouble
> updating or checking out from a repository directory because they're unable
> to create a lockfile (even on read-only operations, CVS needs to create a
> lockfile to avoid situations where it could end up reading while another
> invocation of CVS is writing). The usual fix for this is to change
> repository permissions, but when that's not feasible, the LockDir parameter
> can come in handy.
> """

ok that explains some of my questions in mind to send to these group :)

> or:
> """
> When protecting $CVSROOT/CVSROOT against modification, by removing 
> write access to the directory to users, you may encounter an error 
> as CVS's default behaviour is to create lock files under this directory.

so i can restrict 'users' of 'cvs group' of not accessing the
$CVSROOT/CVSROOT folder ??? so that only root can change settings? is
these pracktical...???

> One way to avoid this limitation is to configure the LockDir option 
> in the CVSROOT/config file, so that lock are created somewhere else 

yes i re-config the LockDir to $CVSROOT/lock .... <- is this O.K. ???
and one more thing how can i say $CVSROOT/CVSROOT can only be accessed
by root..

chgrp -R root $CVSROOT/CVSROOT
chmod 700 or 750 ????
or can i say
chmod ug+rwx . $CVSROOT/CVSROOT

> """


> Regards,
> Gisbert Amm
kent emia <address@hidden>

reply via email to

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