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

Previous Next

Package: coreutils;

Reported by: Christoph Anton Mitterer <calestyo <at> scientia.net>

Date: Mon, 11 Oct 2021 01:29:02 UTC

Severity: normal

Tags: notabug

Done: Pádraig Brady <P <at> draigBrady.com>

Bug is archived. No further changes may be made.

Full log


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

From: Christoph Anton Mitterer <calestyo <at> scientia.net>
To: Pádraig Brady <P <at> draigBrady.com>, 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: Tue, 12 Oct 2021 16:03:29 +0200
On Tue, 2021-10-12 at 14:53 +0100, Pádraig Brady wrote:
> Well DURATIONs of 0 were mentioned a little below that.

Hmm ok,... I see, since both use the symbol <duration>... and you use
the word "associated"... one could have also understood it from the
beginning like that.


> -This option has no effect if @command{timeout}'s duration is 0 which
> -disables the associated timeout.
> +This option has no effect if either the main @var{duration}
> +of the @command{timeout} command, or the @var{duration} specified
> +to this option, is 0.

Much better though IMO :-)


Thanks,
Chris.




This bug report was last modified 3 years and 282 days ago.

Previous Next


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