GNU bug report logs - #51128
timeout --kill-after=0 seems to not send a kill 0s after the initial signal

Previous Next

Full log

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

From: Pádraig Brady <P <at> draigBrady.com>
To: Christoph Anton Mitterer <calestyo <at> scientia.net>, 51128 <at> debbugs.gnu.org
Subject: Re: bug#51128: timeout --kill-after=0 seems to not send a kill 0s
 after the initial signal
Date: Mon, 11 Oct 2021 16:49:38 +0100

tag 51128 notabug
close 51128
stop

On 11/10/2021 02:28, Christoph Anton Mitterer wrote:
> Hey.
> 
> The timeout(1) manpage says:
>         -k, --kill-after=DURATION
>                also send a KILL signal if COMMAND is still running
>                this long after the initial signal was sent
> 
> My naive assumption would have been that --kill-after=0 means that a
> signal is sent immediately after the original one.

Well that wouldn't be that useful functionality,
as why not just send a single kill signal in that case.

> However, that doesn't seem to be the case.
> 
> 
> If intended, this should perhaps at least be mentioned in the manpage
> :-)

It is intended that a 0 duration disables that timeout.
It is mentioned in the full documentation at:
https://www.gnu.org/software/coreutils/timeout
The man pages don't try to document every nuance.

cheers,
Pádraig.

Previous Next

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