|
From: | GNU bug Tracking System |
Subject: | bug#41634: closed ('timeout' returning 124 and 133) |
Date: | Sun, 07 Jun 2020 13:46:02 +0000 |
Your message dated Sun, 7 Jun 2020 15:45:27 +0200 with message-id <2927acbe-2a08-ef91-ae22-1c5ca3f94374@bernhard-voelker.de> and subject line Re: bug#41634: 'timeout' returning 124 and 133 has caused the debbugs.gnu.org bug report #41634, regarding 'timeout' returning 124 and 133 to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 41634: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=41634 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: 'timeout' returning 124 and 133 Date: Sun, 31 May 2020 22:22:47 +0100 Hello User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
I'm using timeout with another program that doesn't have a timeout mechanism. Saw surprisingly timeout often returns 124
I was a bit surprised the return code as a signal was not 143 (128+ 15) for SIGTERM. I must be missing something.
This article says 124 for SIGTERM, and as expected 137 for SIGKILL (128+9)
https://www.howtogeek.com/423286/how-to-use-the-timeout-command-on-linux/
The man page says "Start COMMAND, and kill it if still running after DURATION.", it sounds like it's doing 'kill -s
SIGTERM' after DURATION. Then if -k argument it is doing 'kill -s SIGKILL'
Could the 124 and 137 be documented on the man page?
Regards, Jonny
--- End Message ---
--- Begin Message ---Subject: Re: bug#41634: 'timeout' returning 124 and 133 Date: Sun, 7 Jun 2020 15:45:27 +0200 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1 On 2020-06-07 15:34, Pádraig Brady wrote: > [...] it is better to add the comma there [...] thanks, pushed with that change: https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=189776ff3b Marking this as done. Have a nice day, Berny
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |