RE: $CVSROOT/CVSROOT file perms. - 2nd asking

[Jim.Hyslop]

address@hidden wrote:
> I have the the unix file and corresponding RCS 
> file permissions set for the folllowing file...
> 
>    rwxrwx---  file1
>    rwxrwx---  file1,v
> 
> When I do a cvs init, permissions get set to
> 
>    r-xr-xr-x  file1
>    rwxrwx---  file1,v
> 
> How can I make the unix file "follow" the RCS file
> permissions?
You generally don't want write permissions on the ,v file - CVS will manage
that for you. See
https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_2.html#SEC13 for more
details.

What permissions do you get when you actually check the files out? That's
what's important, and I've found that CVS will maintain the write and
execute flags (I haven't tried removing 'world' permissions, though).
Generally, you don't want to be modifying the files within the CVSROOT
directory itself - you should check out CVSROOT, modify the file(s) and
check back in (there are exceptions, such as val-tags).

Does this happen to all files within CVSROOT, or to specific files? If it's
specific files, which one(s) are affected?

How frequently are you running 'cvs init'? It should only be necessary to
run it once per repository. If you're running it more frequently, then as a
workaround you might want to create a script that issues 'cvs init' then
resets the permissions.

HTH!

-- 
Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. ( http://www.leitch.com )
Columnist, C/C++ Users Journal ( http://www.cuj.com/experts )