GNU bug report logs - #70219
Bug/Issue with timeout and signals

Previous Next

Full log

Message #23 received at 70219 <at> debbugs.gnu.org (full text, mbox):

From: "Branden R. Williams" <brw <at> brandenwilliams.com>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: Chris Elvidge <celvidge001 <at> gmail.com>, 70219 <at> debbugs.gnu.org
Subject: Re: bug#70219: Bug/Issue with timeout and signals
Date: Sat, 6 Apr 2024 07:43:09 -0500

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

I understand this, but the manpage and the help file do not explain the functionally this way. The manpage suggests that the following should work:

$ timeout -k 10s sleep 10

It does not because the first argument after -k MUST be the an integer value of the signal you want to send, not the duration that the manpage and --help tell you to pass.

Regards, 

B



> On Apr 6, 2024, at 4:06 AM, Andreas Schwab <schwab <at> linux-m68k.org> wrote:
> 
> On Apr 05 2024, "Branden R. Williams" via GNU coreutils Bug Reports wrote:
> 
>> That’s not an accurate representation of what the command actually does. The argument after -k MUST be the kill signal code, without the code the command fails. The manpage and help document agree with what you are saying but the execution of the program fails.
> 
> $ timeout -k USR1 1s sleep 10
> timeout: invalid time interval ‘USR1’
> Try 'timeout --help' for more information.
> $ timeout -s KILL 1s sleep 10
> Killed
> 
> -- 
> Andreas Schwab, schwab <at> linux-m68k.org
> GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
> "And now for something completely different."

[Message part 2 (text/html, inline)]

Previous Next

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