doc/man/apply-default-acl.1: remove superfluous line breaks.

[apply-default-acl.git] / doc / man / apply-default-acl.1

diff --git a/doc/man/apply-default-acl.1 b/doc/man/apply-default-acl.1
index bfbb724a8a7bea5121daa92e4051defa6442375a..d8d66948f7acf569ea7cdb4588c94ac5201e1d39 100644 (file)
--- a/doc/man/apply-default-acl.1
+++ b/doc/man/apply-default-acl.1
@@ -12,8 +12,8 @@ apply-default-acl \- Apply default POSIX ACLs to files and directories.
 .P
 If the directory containing \fIpath\fR has a default ACL, the ACL on
 \fIpath\fR is replaced with that default. Neither symbolic nor hard
-links are followed.
-
+links are followed; symbolic links are ignored in all path components
+to avoid a dangerous race condition.
 .P
 By default, a heuristic is used to determine whether or not the
 execute bit is masked on \fIpath\fR. If \fIpath\fR is not a directory,
@@ -21,18 +21,15 @@ and no user or group has \fBeffective\fR execute permissions on
 \fIpath\fR, then the execute bit will not masked. Otherwise, it is
 left alone. In effect we pretend that the \fBx\fR permission acts like
 the \fBX\fR (note the case difference) permission of \fBsetfacl\fR.
-
 .P
 This behavior can be modified with the \fB--no-exec-mask\fR flag.
 
 .SH OPTIONS
-
 .IP \fB\-\-recursive\fR,\ \fB\-r\fR
 Apply default ACLs recursively. This works top-down, so if directory
 \fBfoo\fR is in another directory \fBbar\fR which has a default ACL,
 then \fBbar\fR's default ACL will be applied to \fBfoo\fR before the
 contents of \fBfoo\fR are processed.
-
 .IP \fB\-\-no-exec-mask\fR,\ \fB\-x\fR
 Apply the default ACL literally; that is, don't use a heuristic to
 decide whether or not to mask the execute bit. This usually results in