"Howard, Les" wrote: > > I've hacked my way through setting up a few CVS repositories in the past, > but I've always struggled with getting the user/group ownership and file > permissions correct. I always seem to end up with a setup where the users > can't access the files that other users have submitted without going into > the repository as root and chmod/chowning some of the files.
Sounds like you did not set the SGID bit on the directory structure. https://www.cvshome.org/docs/manual/cvs-1.11.19/cvs_2.html#SEC13 "(On some systems, you also need to set the set-group-ID-on-execution bit on the repository directories (see chmod(1)) so that newly-created files and directories get the group-ID of the parent directory rather than that of the current process.)" <SNIP> > What is the right way to set up the repository, users/groups on the > repository or users/groups on the remote workstations as far as file > ownership and permissions go so that all users will be able to easily work > on the files that each-other has submitted? <SNIP> > but nothing about how to setup file > permissions/ownership properly. > Les 1) all the users who need write access to the repository should be in the same UNIX group. 2) after doing `cvs init` you need to chmod g+sw the repository project directory, i.e., `chown :projectUNIXgroup $CVSROOT/project/; \ chmod g+sw $CVSROOT/project/` -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
