summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBernhard Voelker <mail@bernhard-voelker.de>2020-08-12 23:59:05 +0200
committerBernhard Voelker <mail@bernhard-voelker.de>2020-08-14 00:09:17 +0200
commit0da0554e49b347edffe3dc100d6ec67d7f9e4904 (patch)
treeda0562a12c0465f4229fc5754bdf9bc802742e67
parentb9ddd2bca1032fccbb6435b1e176af6f7a7485df (diff)
downloadfindutils-0da0554e49.tar.gz
doc: clarify that 'find -perm +MODE' is unrelated to umask
* doc/find.texi (Test -perm pmode): Do the above. * NEWS: Mention the change. Reported by Mohamed Akram in https://sv.gnu.org/bugs/?58654
-rw-r--r--NEWS2
-rw-r--r--doc/find.texi4
2 files changed, 6 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index 5f74193..8619899 100644
--- a/NEWS
+++ b/NEWS
@@ -16,6 +16,8 @@ find -used works again. This predicate was not working properly since adding
the support for sub-second timestamp resolution for various predicates in
FINDUTILS_4_3_3-1 back in 2007.
+#58654: doc: clarify that 'find -perm +MODE' is unrelated to umask
+
#58458: doc: improve section 'Hard links', especially fix the description
regarding 'find -L -samefile FILE'.
diff --git a/doc/find.texi b/doc/find.texi
index 4dde015..1e4ab17 100644
--- a/doc/find.texi
+++ b/doc/find.texi
@@ -1222,6 +1222,10 @@ True if the file's mode bits match @var{pmode}, which can be
either a symbolic or numeric @var{mode} (@pxref{File Permissions})
optionally prefixed by @samp{-} or @samp{/}.
+Note that @var{pmode} starts with all file mode bits cleared, i.e.,
+does not relate to the process's file creation bit mask (also known
+as @command{umask}).
+
A @var{pmode} that starts with neither @samp{-} nor @samp{/} matches
if @var{mode} exactly matches the file mode bits.
(To avoid confusion with an obsolete GNU extension, @var{mode}