[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#51135: timeout: --foreground causes exit status 124, even if KILL wa
|
From: |
Christoph Anton Mitterer |
|
Subject: |
bug#51135: timeout: --foreground causes exit status 124, even if KILL was used |
|
Date: |
Mon, 11 Oct 2021 23:23:57 +0200 |
|
User-agent: |
Evolution 3.42.0-2 |
On Mon, 2021-10-11 at 22:20 +0100, Pádraig Brady wrote:
> For that use case it's probably best to use --preserve-status,
> in which case the 137 from the child getting the SIGKILL
> will be propagated through.
But wouldn't that make me loose the 124, if COMMAND could actually be
SIGTERMed?
- bug#51135: timeout: --foreground causes exit status 124, even if KILL was used, Christoph Anton Mitterer, 2021/10/11
- bug#51135: timeout: --foreground causes exit status 124, even if KILL was used, Pádraig Brady, 2021/10/11
- bug#51135: timeout: --foreground causes exit status 124, even if KILL was used, Christoph Anton Mitterer, 2021/10/11
- bug#51135: timeout: --foreground causes exit status 124, even if KILL was used, Pádraig Brady, 2021/10/11
- bug#51135: timeout: --foreground causes exit status 124, even if KILL was used,
Christoph Anton Mitterer <=
- bug#51135: timeout: --foreground causes exit status 124, even if KILL was used, Christoph Anton Mitterer, 2021/10/11
- bug#51135: timeout: --foreground causes exit status 124, even if KILL was used, Pádraig Brady, 2021/10/12
- bug#51135: timeout: --foreground causes exit status 124, even if KILL was used, Christoph Anton Mitterer, 2021/10/12