mapping SYNCHRONIZE permission in NTFS ACL for ZFS
Jeremy Allison
jra at samba.org
Tue Jan 11 18:15:19 MST 2011
On Tue, Jan 11, 2011 at 05:03:05PM -0800, Paul B. Henson wrote:
> On Tue, 11 Jan 2011, Jeremy Allison wrote:
>
> > Hmmm. Yes. I was going to recommend leaving it alone on set, but if it's
> > really being defined as a server-side NO-OP then there's really no need.
>
> A more general implementation would be to leave it set if it is set, but
> not set it otherwise, but that would be more complicated. As far as I can
> tell the function which is called to set the acl is passed the windows acl
> and the file name with no knowledge of the existing acl. To maintain the
> sync bit if set it would need to read in the existing acl and do a
> comparision between the old and new. Possible, but doesn't really seem
> worth the effort.
Yes, exactly what I decided also :-).
> > Can you do me a favour, and log a bug against 3.5.6 on bugzilla.samba.org
> > so I can add in the patch for 3.6.0 and a future 3.5.x release ?
>
> Will do, thanks...
Thanks - I'll add in the fix to active branches (and in the
generic NFSv4 ACL module) once you've logged the bug.
Cheers,
Jeremy.
More information about the samba-technical
mailing list