summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKamil Dudka <kdudka@redhat.com>2016-04-17 22:36:13 +0200
committerBernhard Voelker <mail@bernhard-voelker.de>2016-04-18 11:47:47 +0200
commitae424b959c5e9bd23f9f686cb34653bc4cd1270e (patch)
tree6fee39347014f46ac6ea8ab065412ba214e85ba7
parent9333e22e91b68107a9608b80d611ef9b8b2286e1 (diff)
downloadfindutils-ae424b95.tar.gz
doc: clarify exit status handling of -exec command {} +
* find/find.1 (-exec): Explain how exit status is propagated if the -exec command {} + syntax is used. (-execdir): Likewise. Reported at https://bugzilla.redhat.com/1325049
-rw-r--r--find/find.16
1 files changed, 6 insertions, 0 deletions
diff --git a/find/find.1 b/find/find.1
index 7b626b5..8958085 100644
--- a/find/find.1
+++ b/find/find.1
@@ -1077,6 +1077,9 @@ command line is built in much the same way that
.B xargs
builds its command lines. Only one instance of `{}' is allowed within
the command. The command is executed in the starting directory. If
+any invocation returns a non-zero value as exit status, then
+.B find
+returns a non-zero exit status. If
.B find
encounters an error, this can sometimes cause an
immediate exit, so some pending commands may not be run
@@ -1112,6 +1115,9 @@ appropriately-named file in a directory in which you will run
The same applies to having entries in
.B $PATH
which are empty or which are not absolute directory names. If
+any invocation returns a non-zero value as exit status, then
+.B find
+returns a non-zero exit status. If
.B find
encounters an error, this can sometimes cause an
immediate exit, so some pending commands may not be run