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 sales@march-hare.com.
Can anyone confirm that chacl isn't applicable to files? Then why does it modify fileattr.xml when I use it to set permissions on a file, and why does the command line help indicate it can be applied to files and directories? Thanks, Vlad "Vlad" <nospam at noserver.net> wrote in message news:ct60lv$lgf$1 at paris.nodomain.org... > Hi, > > This probably isnt' a bug, but rather a problem in my own understanding of > the chacl command. I'm using cvsnt 2.0.58d with the pserver protocol for > the clients, the server is running on WindowsXP. When an admin uses chacl > to allow "write" on a directory by a certain user, for example with the > following command: > > cvs chacl -u username1 -a read,write,nocontrol,tag,create . > > And then executes the following command for a file WITHIN the same > directory > > cvs chacl -u username1 -a noread,nowrite,nocontrol,notag,nocreate file.c > > Should username1 be allowed to make commits to file.c? I would think no, > because in this case the file permissions should have precedence over the > directory permissions. However, when I try this out, username1 is able do > anything to file.c except change ACLs. Note that username1 is a regular > user who is not an admin (neither in the admins file nor under NTFS). > > Could someone help out? > > Thanks, > > Vlad >