From b186e0d9ce4a597367a18a884a088cb9c57485c6 Mon Sep 17 00:00:00 2001 From: Michael Orlitzky Date: Tue, 27 Feb 2018 09:52:40 -0500 Subject: [PATCH] doc/man/apply-default-acl.1: remove superfluous line breaks. --- doc/man/apply-default-acl.1 | 4 ---- 1 file changed, 4 deletions(-) diff --git a/doc/man/apply-default-acl.1 b/doc/man/apply-default-acl.1 index 683919b..d8d6694 100644 --- a/doc/man/apply-default-acl.1 +++ b/doc/man/apply-default-acl.1 @@ -14,7 +14,6 @@ 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; 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, @@ -22,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 -- 2.43.2