summaryrefslogtreecommitdiff
path: root/find/find.1
diff options
context:
space:
mode:
Diffstat (limited to 'find/find.1')
-rw-r--r--find/find.120
1 files changed, 20 insertions, 0 deletions
diff --git a/find/find.1 b/find/find.1
index 8b67ae38..f5542467 100644
--- a/find/find.1
+++ b/find/find.1
@@ -1009,6 +1009,11 @@ 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
+.B find
+encounters an error, this can sometimes cause an
+immediate exit, so some pending commands may not be run
+at all.
.IP "\-execdir \fIcommand\fR ;"
.IP "\-execdir \fIcommand\fR {} +"
@@ -1038,6 +1043,11 @@ 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
+.B find
+encounters an error, this can sometimes cause an
+immediate exit, so some pending commands may not be run
+at all.
.IP "\-fls \fIfile\fR"
True; like
@@ -1977,6 +1987,16 @@ description, but if the return value is non-zero, you should not rely
on the correctness of the results of
.BR find .
+When some error occurs,
+.B find
+may stop immeidately, without completing all the actions specified.
+For example, some starting points may not have been examined or some
+pending program invocations for
+.B \-exec ... {} +
+or
+.B \-execdir ... {} +
+may not have been performed.
+
.SH "SEE ALSO"
\fBlocate\fP(1), \fBlocatedb\fP(5), \fBupdatedb\fP(1), \fBxargs\fP(1),
\fBchmod\fP(1), \fBfnmatch\fP(3), \fBregex\fP(7), \fBstat\fP(2),