So, I've got the standard 'cvsuser' group to which I have added user accounts who are supposed to have read/write access to the repository.
Now, based on what I've read, I need to then use the 'other' permissions to control what other people can do with the CVS repository. However, it would appear that I need to make directories of the modules writable by 'other's so a lockfile can be created. Also, it would appear that either all(?) or some(?) of the files in $CVSROOT/CVSROOT/ need to be writable by 'other's as well.
Allowing these things to be writable by the world, makes me nervous and I am wondering if there is another, secure, method that I can use or if I a simply missing something here.
Comments? Thoughts?
(This might make a good FAQ question/answer...there doesn't seem to be one on this topic yet...)
_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
