GNU bug report logs - #41634
'timeout' returning 124 and 133

Previous Next

Full log

View this message in rfc822 format

From: Pádraig Brady <P <at> draigBrady.com>
To: Bernhard Voelker <mail <at> bernhard-voelker.de>
Cc: 41634 <at> debbugs.gnu.org
Subject: bug#41634: 'timeout' returning 124 and 133
Date: Sun, 7 Jun 2020 13:13:21 +0100

[Message part 1 (text/plain, inline)]

On 06/06/2020 00:37, Bernhard Voelker wrote:
> On 2020-06-01 10:01, Jonny Grant wrote:
>> My mistake missing that. But could the 137 be listed explicitly?
>> ie.
>> "It may be  necessary  to  use the KILL (9) signal, since this signal cannot be caught, in which case the exit status is
>> 137 (128+9) rather than 124."
> 
> thanks for the suggestion.
> 
> I think this could still be improved:
> there is still the open question what happens when the KILL signal
> is sent either to timeout(1) or to COMMAND.
> The attached patch tries to clarify.

Thanks for improving that Bernhard.

It's generally easier to scan tables of values, than blocks of text.
How about we add the exit code table to the man page also?
I've adjusted your patch to do that (along with some other tweaks) in the attached.

cheers,
Pádraig

[timeout-exit-docs.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.