From: Jim Meyering <jim@meyering.net>
Date: Sun, 2 Mar 2003 18:04:03 +0000 (+0000)
Subject: (Exit status): New section.
X-Git-Tag: v4.5.9~85
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=345481344c5f748c95782c6160be65c94aacbba7;p=thirdparty%2Fcoreutils.git

(Exit status): New section.
---

diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 2e99d0c560..336150ff50 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -196,6 +196,7 @@ Free Documentation License''.
 
 Common Options
 
+* Exit status::                 Indicating program success or failure.
 * Backup options::              Backup options
 * Block size::                  Block size
 * Target directory::            Target directory
@@ -542,6 +543,7 @@ output and reads from standard input, and is equivalent to plain
 context that requires a file name.
 
 @menu
+* Exit status::                 Indicating program success or failure.
 * Backup options::              -b -S -V, in some programs.
 * Block size::                  BLOCK_SIZE and --block-size, in some programs.
 * Target directory::            --target-directory, in some programs.
@@ -550,6 +552,22 @@ context that requires a file name.
 @end menu
 
 
+@node Exit status
+@section Exit status
+
+Nearly every command invocation yields an integral @dfn{exit status}
+that can be used to change how other commands work.
+For the vast majority of commands, an exit status of zero indicates
+success, and a value of @samp{1} indicates failure.
+However, some of the programs documented here do produce
+different exit status values and a few associate different
+meanings with the values @samp{0} and @samp{1}.
+Here are some of the exceptions:
+@command{expr}, @command{false}, @command{nohup}, @command{printenv},
+@command{sort}, @command{test}, @command{true}, @command{tty},
+@command{uniq}.
+
+
 @node Backup options
 @section Backup options