"Fouts Christopher (6452)" wrote: > > I have a "sample" project with r-s permissions for g and o. > I have dir1/file1 directory/file in the project, which user > cvsadmin in the cvs group, created. so now file1 has > r--r--r-- permissions. > > I have a separate lock direcotry, called /cvsroot/lockDir > with rwxrwsrwx permissions. > > Now user1 in group user checks out sample and modifies > file1. When user1 checks in file1, it gets > "Could not open file /cvsroot/sample/dir1/file1, permission denied." > > I fixed it by chmod -R o+w /cvsroot/sample. I thought the idea > behind the LockDir was for me (cvs admin) NOT to have to do this? > > ------------------------------------------------------------- > Chris T Fouts checkin requires the user to write to the repository, for this user1 needs write privileges to the REPOSITORY. i.e. ls -ld /cvsroot/sample/dir1/ #should yield something like: drwxrwsr-x # cmuser projgrp 512 Jan 26 10:51 /cvsroot/sample/dir1/ #and ypcat group >/tmp/look; cat /etc/group /tmp/look| grep user1 #should yield something like projgrp::530:user1,me,restofgroup
LockDir lets you allow more people to read than to write, i.e. you can set it up so marketing and the PHB can read the repository but never commit. -- 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://mail.gnu.org/mailman/listinfo/info-cvs
