Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
John Cole wrote: > Hello, > I have been running CVSNT for a while now, and have NTFS permissions > running great. Recently, we branched our main application for a release, > and we want to lock the release so that we have better control over who > makes changes to a product in the field. > > I've been reading about the chacl command, but the information is, well, > sparse. :-) Has anyone used this command to restrict access to a branch? Let us know, or better yet flesh out the wiki docs with more information as you are learning about them. :) I use it all the time. In a nutshell (as if sparse docs weren't sparse enough), a branch assumes everyone can have all permissions on a branch (RWC). Only when you use chacl on a particular branch does it take affect. "default" means the default user (anyone who isn't otherwise explicitly listed). > > We use sspi to authenticate, so I'm a little confused as to how groups and > such will work. Any information and insight would be greatly apreciated. Are you referring to NT groups? If you have file permissions set on your repository, they will obey the NT file system permissions as you would normally expect, assuming you have left the default "use impersonation" enabled. Some notes though: SYSTEM needs access to your CVSROOT directory and the users need RW to a couple files in CVSROOT. See http://www.cvsnt.org/wiki/SetAcl for more information. -- Glen Starrett