I think there may be atomicity problems when mounting a CVS repository via NFS.
I'm assuming you're asking about POSIX file system ACLs. It's perfectly fine to use ACLs within the CVS repo, in fact I promote them since it makes things much simpler. However, be sure you understand exactly how permissions are used within the repo. One thing you'll need to do is create a loginfo script that'll setfacl new directories and the archive file each time it's checked in since there's no decent mechanism for new files to inherit ACLs. Hope this helps, Noel --- Axelle <[EMAIL PROTECTED]> wrote: > Hi, > I have set up a locally mounted CVS repository, to > share sources between 2 > of us on a same project. > I can checkout files without any problem, but the > other user can't and gets > a > "cvs [checkout aborted]: connect to machine:2401 > failed: Connection refused" > > What is most surprising is that the user does have > access to the repository > directory he wants to checkout. He can 'cd' to it > without any problem, and > even read a document. (I have set the corresponding > ACLs for him). > Why can't he checkout ? > > (I'm using a locally mounted repository. Not a > pserver or another kind of > remote CVS server). > The user is specified in a 'writers' file in > $CVSROOT/CVSROOT > > > bash-2.03$ cvs checkout > docs/internal/papers/toto/toto.txt > cvs [checkout aborted]: connect to machine:2401 > failed: Connection refused > > Axelle Apvrille. > > PS. Is it a problem to use ACLs with CVS ? > _______________________________________________ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
