Hi, Szabolcs Szakacsits wrote: > Hello Jean-Pierre, > > On Thu, 27 Sep 2007, Jean-Pierre ANDRE wrote: > > >> Note : inheritance and cacheing are not possible on files >> and directories created by standard ntfs-3g. >> > > Do you mean that this is not possible because the $SECURITY_DESCRIPTOR > attribute was used? >
Yes. Inheritance is done by copying the security id. Simple and fast. The security id is also the base for cacheing. This way I do not have to keep track of individual files and the cache efficiency is over 99% > Not just ntfs-3g and NT4 create this attribute but I keep seeing it on > volumes too which never were touched by Linux or NT4. Windows respects it, > however I didn't check what it considers if both the security id and the > $SECURITY_DESCRIPTOR exist. > I do exactly the same for existing security attributes. When both the security id and the security descriptor exist, Windows XP uses the security id, but chkdsk complains and replaces both by a standard one. > Is $SECURITY_DESCRIPTOR always ignored or only in the above cases? > In my implementation, the security attribute is ignored only when there is a duplication. This duplication is bad (chkdsk complains) and should never happen. > Thanks, > Szaka > Regards Jean-Pierre ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ ntfs-3g-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
