[Top][All Lists]

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

Re: user privileges for files / dirs / modules

From: Todd Denniston
Subject: Re: user privileges for files / dirs / modules
Date: Wed, 02 Feb 2005 13:24:37 -0500

address@hidden wrote:
> >-----Original Message-----
> >From: Larry Jones [mailto:address@hidden
> >address@hidden writes:
> >>
> >> Yes I started the discussion back then too, and did not get (or I
> >> couldn't filter out) a straight answer. So once checked-in with the
> >> "wrong" perms, how does one correct it?
> >
> >By changing the permissions on the RCS file in the repository.
> > The permissions on the working file are the same as the
> >permissions on the RCS file except that the read permissions
> >are copied to the write permissions and the user's umask is applied.
> >
> Thanks, but I believe I've done this, that is, changing the RCS
> file perms to no avail. Now I remember asking where "in" the RCS
> file, and getting "not in the RCS file, but of the RCS file."

The RCS portion of CVS will carry the execute bit if set when the file is
add+commited, to change that use 'chmod oug-x $CVSROOT/$relitivepath/file,v'
(with the chmod on a linux system anyway).

if you are using one of the 'cvs watch` commands and you do a checkout the
file in your sandbox may be read only.

for your taglogs file I think what you want is 
chmod oug+x $CVSROOT/CVSROOT/taglogs,v
then commit something to the $CVSROOT/CVSROOT directory to make sure it is
set correctly.

 This is different than what matthias was asking when the thread was started
(if I understood correctly).  matthias's question is usually answered by
indicating, "set the permissions of your DIRECTORIES to limit write access
and in some cases read access to the repository directories".  If you can
not read a repository directory, you can not read the file in it IIRC.
If you can not write to a repository directory, you can not change a file in
with CVS, If you can not write to a repository directory AND LockDir is not
set to somewhere that you can write to, you can not do a checkout IIRC.
If you want to give someone read access, but not write access, remove their
ability to write to the $CVSROOT directories and use LockDir in
CVSROOT/config .

Does this help the understanding?
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter

reply via email to

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