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.
Aleksander, The "noread" acl applied to a file is generally not logical (because you can still "read" it's existance - there is no separate ACL for "nolist") - put all "noread" files in the same directory and put the "noread" ACL there. All the other ACL's (nowrite etc can be applied to single files as you wrote. I'll have a quick look at this but from memory there was a very long thread about this last year. The correct way to report bugs is described in the FAQ, including a trace and config files. Why can't you move this file into another directory? Regards, Arthur -----Original Message----- From: cvsnt-bounces at cvsnt.org on behalf of Aleksander Pahor Sent: Fri 3/30/2007 12:15 AM To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Cc: Subject: Re: [cvsnt] Read-Write Hi. Persmissions on only one file don't work as they should. Example: if I want to deny users the possibility to read a file - I expect if the do a checkout this file will be missing in their directory. Checking-out a "noread" acl-ed file is possible. On the other hand update works almost fine as it doesn't copy the file into the sandbox but aborts the update (doesn't continue). Do you have any defect tracking system where bugs to cvsnt can be submitted? BR, Aleksander _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs