From f54e279c91964c800cb7215ecf2de9083c5984ea Mon Sep 17 00:00:00 2001 Message-Id: From: Mark Wooding Date: Sat, 2 May 2015 17:05:20 +0100 Subject: [PATCH] mtimeout.1: Clarify handling of exit statuses. Organization: Straylight/Edgeware From: Mark Wooding --- mtimeout.1 | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/mtimeout.1 b/mtimeout.1 index 147b097..cc57a4a 100644 --- a/mtimeout.1 +++ b/mtimeout.1 @@ -120,7 +120,7 @@ The .B mtimeout program sets its exit status as follows. .TP -0\(em127 +0\(em127, 255 The child process ran to completion within the given time: .BR mtimeout 's exit status is the same as that of the child process. @@ -129,6 +129,12 @@ exit status is the same as that of the child process. The child process exited in a way which .B mtimeout could not interpret. +(Whatever status the child exits with will be propagated; +but if it exits with some status other than these then +there is a risk that it will be conflict +with a status used by +.B mtimeout +and be misinterpreted.) .TP 129\(em250 The child process was killed by a signal: the exit status is 128 higher @@ -156,9 +162,6 @@ was written to standard error. A system call made by .B mtimeout failed unexpectedly: an error message was written to standard error. -.TP -255 -Not used. . .SH BUGS Because -- [mdw]