* doc/find.texi: Point out that xargs does not launch commands via the
shell and does not use the "128 + signal" convention used for $? in
the shell.
* xargs/xargs.1: Likewise.
---
doc/find.texi | 5 +++--
xargs/xargs.1 | 8 ++++++--
2 files changed, 9 insertions(+), 4 deletions(-)
diff --git a/doc/find.texi b/doc/find.texi
index f693db8c..71b80f53 100644
--- a/doc/find.texi
+++ b/doc/find.texi
@@ -3996,9 +3996,10 @@ if the command is not found
if some other error occurred.
@end table
-Exit codes greater than 128 are used by the shell to indicate that
-a program died due to a fatal signal.
+The commands run by @code{xargs} are not invoked via the shell. The
+shell's @math{128 + n} convention for reporting that a process had
+been killed by a signal is not used by @code{xargs}.
@menu
* xargs options::
diff --git a/xargs/xargs.1 b/xargs/xargs.1
index 377a1855..9f750c43 100644
--- a/xargs/xargs.1
+++ b/xargs/xargs.1
@@ -549,8 +549,12 @@ if some other error occurred.
.RE
.
.P
-Exit codes greater than 128 are used by the shell to indicate that
-a program died due to a fatal signal.
+The commands run by
+.B xargs
+are not invoked via the shell.
+The shell's (128 + signal) convention for reporting that a process had
+been killed by a signal is not used by
+.BR xargs .
.
.SH "STANDARDS CONFORMANCE"
The long-standing
--
2.47.3
