1.\"- 2.\" Copyright (c) 2000 Robert N. M. Watson 3.\" All rights reserved. 4.\" 5.\" Redistribution and use in source and binary forms, with or without 6.\" modification, are permitted provided that the following conditions 7.\" are met: 8.\" 1. Redistributions of source code must retain the above copyright 9.\" notice, this list of conditions and the following disclaimer. 10.\" 2. Redistributions in binary form must reproduce the above copyright 11.\" notice, this list of conditions and the following disclaimer in the 12.\" documentation and/or other materials provided with the distribution. 13.\" 14.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND 15.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 16.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 17.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE 18.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 19.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 20.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 21.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 22.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 23.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 24.\" SUCH DAMAGE. 25.\" 26.\" $FreeBSD: src/lib/libposix1e/acl_delete.3,v 1.2.2.5 2001/12/20 16:27:06 ru Exp $ 27.\" $DragonFly: src/lib/libposix1e/acl_delete.3,v 1.3 2004/03/11 12:28:52 hmp Exp $ 28.\" 29.Dd January 28, 2000 30.Dt ACL_DELETE 3 31.Os 32.Sh NAME 33.Nm acl_delete_def_file , 34.Nm acl_delete_fd_np , 35.Nm acl_delete_file_np 36.Nd delete an ACL from a file 37.Sh LIBRARY 38.Lb libposix1e 39.Sh SYNOPSIS 40.In sys/types.h 41.In sys/acl.h 42.Ft int 43.Fn acl_delete_def_file "const char *path_p" 44.Ft int 45.Fn acl_delete_file_np "const char *path_p" "acl_type_t type" 46.Ft int 47.Fn acl_delete_fd_np "int filedes" "acl_type_t type" 48.Sh DESCRIPTION 49The 50.Fn acl_delete_def_file , 51.Fn acl_delete_file_np , 52and 53.Fn acl_delete_fd_np 54each allow the deletion of an ACL from a file. 55.Fn acl_delete_def_file 56is a POSIX.1e call that deletes the default ACL from a file (normally a 57directory) by name; the other two calls are non-portable extensions that 58allow deleting of arbitrary ACL types from a file/directory by either path 59name, or by file descriptor. 60.Sh IMPLEMENTATION NOTES 61.Dx Ns 's 62support for POSIX.1e interfaces and features is still under 63development at this time. 64.Sh RETURN VALUES 65.Rv -std 66.Sh ERRORS 67If any of the following conditions occur, these functions shall return -1 68and set 69.Va errno 70to the corresponding value: 71.Bl -tag -width Er 72.It Bq Er EACCES 73Search permission is denied for a component of the path prefix, or the 74object exists and the process does not have appropriate access rights. 75.It Bq Er EBADF 76The 77.Va fd 78argument is not a valid file descriptor. 79.It Bq Er EINVAL 80The ACL type passed is invalid for this file object. 81.It Bq Er ENAMETOOLONG 82A component of a pathname exceeded 255 characters, or an 83entire path name exceeded 1023 characters. 84.It Bq Er ENOENT 85The named object does not exist, or the 86.Va path_p 87argument points to an empty string. 88.It Bq Er ENOMEM 89Insufficient memory available to fulfill request. 90.It Bq Er ENOTDIR 91A component of the path prefix is not a directory. 92.Pp 93Argument 94.Va path_p 95must be a directory, and is not. 96.It Bq Er EOPNOTSUPP 97The file system does not support ACL deletion. 98.It Bq Er EPERM 99The process does not have appropriate privilege to perform the operation 100to delete an ACL. 101.It Bq Er EROFS 102The file system is read-only. 103.El 104.Sh SEE ALSO 105.Xr acl 3 , 106.Xr acl_get 3 , 107.Xr acl_set 3 , 108.Xr posix1e 3 109.Sh STANDARDS 110POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion 111of the draft continues on the cross-platform POSIX.1e implementation 112mailing list. To join this list, see the 113.Fx 114POSIX.1e implementation 115page for more information. 116.Sh HISTORY 117POSIX.1e support was introduced in 118.Fx 4.0 , 119and development continues. 120.Sh AUTHORS 121.An Robert N M Watson 122.Sh BUGS 123These features are not yet fully implemented. In particular, the shipped 124version of UFS/FFS does not support storage of additional security labels, 125and so is unable to (easily) provide support for most of these features. 126