acl_get_file() -- failure mode when ACLs not available on file system?

[Casey Schaufler]

Robert Watson wrote:
> 
> Just to throw some more fuel on the fire: returning EOPNOTSUPP would be
> nice for situations where a file system doesn't offer protection (ISO 9660
> cd file system, for example) and you'd like to report that fact to the
> application without attempting to non-sensically emulate ownership and
> permissions for the object.  The ability to return EOPNOTSUPP legally
> would mean that file systems (such as AFS, SMBfs, NFSv4, ...) would not
> have to emulate permission/POSIX.1e ACL semantics with very poor side
> effects.  In any of these cases, either the burden of handling failure is
> placed on the application, or the file system masks the failure.  I'd
> rather see explicit failure than poorly masked failure..

I believe that acl_set_file() ought not to pretend to work
if it does not. On Irix we return ENOSYS, as that was the
required return in one of the DRAFTS.

-- 

Casey Schaufler				Manager, Trust Technology, SGI
casey at sgi.com				voice: 650.933.1634
casey_p at pager.sgi.com			Pager: 888.220.0607
To Unsubscribe: send mail to majordomo at cyrus.watson.org
with "unsubscribe posix1e" in the body of the message