]> gitweb.michael.orlitzky.com - apply-default-acl.git/blob - doc/man/apply-default-acl.1
d8d66948f7acf569ea7cdb4588c94ac5201e1d39
[apply-default-acl.git] / doc / man / apply-default-acl.1
1 .TH apply-default-acl 1
2
3 .SH NAME
4 apply-default-acl \- Apply default POSIX ACLs to files and directories.
5
6 .SH SYNOPSIS
7
8 \fBapply-default-acl\fR [\fB-rx\fR] \fIpath\fR [\fIpath2 ...\fR]
9
10 .SH DESCRIPTION
11
12 .P
13 If the directory containing \fIpath\fR has a default ACL, the ACL on
14 \fIpath\fR is replaced with that default. Neither symbolic nor hard
15 links are followed; symbolic links are ignored in all path components
16 to avoid a dangerous race condition.
17 .P
18 By default, a heuristic is used to determine whether or not the
19 execute bit is masked on \fIpath\fR. If \fIpath\fR is not a directory,
20 and no user or group has \fBeffective\fR execute permissions on
21 \fIpath\fR, then the execute bit will not masked. Otherwise, it is
22 left alone. In effect we pretend that the \fBx\fR permission acts like
23 the \fBX\fR (note the case difference) permission of \fBsetfacl\fR.
24 .P
25 This behavior can be modified with the \fB--no-exec-mask\fR flag.
26
27 .SH OPTIONS
28 .IP \fB\-\-recursive\fR,\ \fB\-r\fR
29 Apply default ACLs recursively. This works top-down, so if directory
30 \fBfoo\fR is in another directory \fBbar\fR which has a default ACL,
31 then \fBbar\fR's default ACL will be applied to \fBfoo\fR before the
32 contents of \fBfoo\fR are processed.
33 .IP \fB\-\-no-exec-mask\fR,\ \fB\-x\fR
34 Apply the default ACL literally; that is, don't use a heuristic to
35 decide whether or not to mask the execute bit. This usually results in
36 looser-than-necessary execute permissions.