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

Previous Next

Package: coreutils;

Reported by: Jonny Grant <jg <at> jguk.org>

Date: Sun, 31 May 2020 21:23:02 UTC

Severity: normal

Done: Bernhard Voelker <mail <at> bernhard-voelker.de>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Jonny Grant <jg <at> jguk.org>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: 41634 <at> debbugs.gnu.org
Subject: bug#41634: 'timeout' returning 124 and 133
Date: Mon, 1 Jun 2020 09:01:38 +0100


On 01/06/2020 07:53, Andreas Schwab wrote:
> On Mai 31 2020, Jonny Grant wrote:
> 
>> Could the 124 and 137 be documented on the man page?
> 
> What's wrong with the last paragraph in the DESCRIPTION section?
> 
> Andreas.
> 

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."

This other man page of timeout has a clearer list of the exit codes
https://ss64.com/bash/timeout.html

Jonny
This bug report was last modified 4 years and 293 days ago.

Previous Next

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