About commandline tool "timeout": Start COMMAND, and kill it if still running
after DURATION.
A new team mate wasted some time to debug why
a process was killed with signal 15.
I think it would be nice to have an --verbose option, and a some
text which explains why the signal was send.
This
tag 21760 wontfix
close 21760
stop
On 26/10/15 10:30, Thomas Güttler wrote:
> About commandline tool "timeout": Start COMMAND, and kill it if still running
> after DURATION.
>
> A new team mate wasted some time to debug why
> a process was killed with signal 15.
>
> I think it would be nice to
On 10/26/2015 02:51 AM, Pádraig Brady wrote:
> From 5e3d017e7bc66cf6f666160f774944c2ff52d1ae Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?P=C3=A1draig=20Brady?=
> Date: Mon, 26 Oct 2015 01:26:04 +
> Subject: [PATCH] md5sum: quote all printed file names
>
> This is
Am 26.10.2015 um 16:51 schrieb Pádraig Brady:
> On 26/10/15 14:26, Thomas Güttler wrote:
>>
>>
>> Am 26.10.2015 um 12:44 schrieb Pádraig Brady:
>>>
>>> I've not sure there is enough distinct actions within timeout(1) to warrant
>>> --verbose?
>>> How about doing this in the script?
>>>
>>>
On 26/10/15 14:26, Thomas Güttler wrote:
>
>
> Am 26.10.2015 um 12:44 schrieb Pádraig Brady:
>>
>> I've not sure there is enough distinct actions within timeout(1) to warrant
>> --verbose?
>> How about doing this in the script?
>>
>>timeout 1s ping localhost
>>test $? = 124 && echo {
Am 26.10.2015 um 12:44 schrieb Pádraig Brady:
I've not sure there is enough distinct actions within timeout(1) to warrant
--verbose?
How about doing this in the script?
timeout 1s ping localhost
test $? = 124 && echo { 'ping timed out'; exit 1; }
The issue was already closed with