Kyle McDonald wrote: > Don Cragun wrote: >> >> I believe that the default should be POSIX compliant. Let >> administrators specify options if they want non-standard behavior. >> >> > ...<snip> >> ACLs are not in POSIX. (POSIX does, however, specify two classes of >> extended access control mechanisms [known as "additional file access >> control mechanisms" and "alternate file access control mechanisms"] and >> specifies interactions between chmod() and these classes of file access >> control mechanisms. ACLs can be added as additional and/or alternate >> file access control mechanism as long as the interactions follow the >> standards.) >> >> > I'm confused. How is that the current default behavior is required in > order to be POSIX compliant if POSIX doesn't actually standardize ACLs? > > -Kyle >
Because the applications requested file creation mode must be honored. The default behavior today will disable inherited ACEs that affect the mode in order to set the mode of the file as requested by the application. The default behavior isn't being changed. The change is to allow "passthrough" to ignore the applications requested mode and instead use the mode as determined by inherited ACEs that affect the mode. -Mark
