Pádraig Brady <P@HIDDEN>
to control <at> debbugs.gnu.org.
Full text available.Pádraig Brady <P@HIDDEN>
to control <at> debbugs.gnu.org.
Full text available.Received: (at 70219) by debbugs.gnu.org; 6 Apr 2024 18:30:38 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Sat Apr 06 14:30:37 2024 Received: from localhost ([127.0.0.1]:40940 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1rtAoG-0007JV-82 for submit <at> debbugs.gnu.org; Sat, 06 Apr 2024 14:30:37 -0400 Received: from mail-wm1-x332.google.com ([2a00:1450:4864:20::332]:52649) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <pixelbeat@HIDDEN>) id 1rtAoA-0007I1-96; Sat, 06 Apr 2024 14:30:34 -0400 Received: by mail-wm1-x332.google.com with SMTP id 5b1f17b1804b1-4162ec14805so17058485e9.1; Sat, 06 Apr 2024 11:30:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712428218; x=1713033018; darn=debbugs.gnu.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=2AiKiwawCOpChr1FyoxJqs+hxEl1minkL+YKE1zoV8U=; b=BavGgeqaCeK+z6vwRLkSaZpDNEe5u2htM/9AUhzl23hH5akuoINxIww3+tael6hHxx QoRbrlxE0TxNdPWTCoyA/lw7/fUAyTZuIy6F740dIaAI1Qlx0zSeXCLbng5XvT+VEEDH ZjwtLtfVdqEV8TsBwxgl7JRDkHKKIVfEAI7rKvEHTIoG2aA+MqXjgAV+EgTNn+Vyzcbk q2gE2WgNmFcwiJUFGYpumaQ5SfG7Jah4I0pgiVY2sbQhqb681UyAt906EjROqhwrYNhk gnefklsRnWpm9/hl89fEZ3cjwhB/agJlioAIiWw/bMM3KM/IYxw4k80nVxPjN9GRgj25 t3Uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712428218; x=1713033018; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=2AiKiwawCOpChr1FyoxJqs+hxEl1minkL+YKE1zoV8U=; b=v5p/zFgp9a+2FT51pBxvjBHscmE9TNWnVAn6uS8bloufOXKuFY5EXaqJCw6qo8BffX frPvg+CnXJ3K5f1+xhzkQ2gHPf0kI36ThLKd6l4g/028C5awPtclvQ7LcoIW7+BC287p AQm5j9W07ktIPae2aPQgNDwfUlbAcaXxGOmozRT8SDZny7FOe7tGHZUtPrQp2PrVbIVQ mmQXVlBEPA1nlDgXTkjhxAYRfOjCCSVf9b6IQ7XEl1pjxG5e5D0op2JvJJ/9aLDvE0zM gwFVtsk9HCaWODTIvZ3HRaktngciuzMxI2+wtJDtcsJECIfNoS/vQ+vBKYwqRgKpZ/P4 u36Q== X-Forwarded-Encrypted: i=1; AJvYcCWWQNuXKDJ+fZIWNRc9uc50mUHiOajr+55VYU9D2pwy9c9SBVa99GUYbanX2AGUXs+k5RN1eQ4Ae6FD0JX962PWGcLOnzhOAQ== X-Gm-Message-State: AOJu0Yz5F9s5HbHAeWZRWqMtvbYQqaEqZWyB4pz4dIU9W10GbFrOANs4 wzAM6XITD/1+ZGVyNXxX1wt8kaHtAkod/4n/k8xoi3V/CetTzm4fi7woeyzE X-Google-Smtp-Source: AGHT+IFtusJdPWAbZpgsY/ILsPbGqRPrRZmG4Rmf6kneiAbZilZawZP96dGiNkE/Jl0vrk7/Uc+SLA== X-Received: by 2002:a05:600c:3146:b0:416:4a4a:8cc9 with SMTP id h6-20020a05600c314600b004164a4a8cc9mr679969wmo.27.1712428217615; Sat, 06 Apr 2024 11:30:17 -0700 (PDT) Received: from [192.168.1.39] ([86.44.211.146]) by smtp.googlemail.com with ESMTPSA id z2-20020a05600c0a0200b0041624ddff48sm10889256wmp.28.2024.04.06.11.30.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 06 Apr 2024 11:30:17 -0700 (PDT) Message-ID: <18192d17-a6b3-6282-c07a-f71e035dcbff@HIDDEN> Date: Sat, 6 Apr 2024 19:30:08 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: bug#70219: Bug/Issue with timeout and signals Content-Language: en-US To: "Branden R. Williams" <brw@HIDDEN> References: <ADBC15C8-7D3B-464D-9253-79EEF4091A3F@HIDDEN> <265efe1a-e937-6f70-1c14-054de8ed1a72@HIDDEN> <29BA5949-B68B-4B9C-BD14-25ADB74475F7@HIDDEN> <87frvyc11y.fsf@HIDDEN> <D3F30E0A-F489-4193-88C8-9D4EDA18B338@HIDDEN> <475472dc-f7ec-7c23-ff2e-a3bb6725092d@HIDDEN> <D518A695-C456-4D0B-868B-68081002B76E@HIDDEN> From: =?UTF-8?Q?P=C3=A1draig_Brady?= <P@HIDDEN> In-Reply-To: <D518A695-C456-4D0B-868B-68081002B76E@HIDDEN> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Score: 0.3 (/) X-Debbugs-Envelope-To: 70219 Cc: 70219 <at> debbugs.gnu.org X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -0.7 (/) tag 70219 notabug close 70219 stop On 06/04/2024 16:50, Branden R. Williams via GNU coreutils Bug Reports wrote: > -k, --kill-after=DURATION > also send a KILL signal if COMMAND is still running > this long after the initial signal was sent If you read the above carefully, please note the words _also_ and _initial_. I.e. -k will cause _another_ signal to be sent, iff the first doesn't terminate the command. Hopefully this example with all pertinent options explains things. I.e. the first signal sent after 1s is ignored, and the second kill signal sent after another 2s forcefully kills the command. $ date +%s; timeout -k 2s -s0 1s sleep inf; date +%s 1712427916 Killed 1712427919 cheers, Pádraig
bug-coreutils@HIDDEN:bug#70219; Package coreutils.
Full text available.
Received: (at 70219) by debbugs.gnu.org; 6 Apr 2024 17:09:38 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sat Apr 06 13:09:38 2024
Received: from localhost ([127.0.0.1]:40887 helo=debbugs.gnu.org)
by debbugs.gnu.org with esmtp (Exim 4.84_2)
(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
id 1rt9Xt-0000xz-Qh
for submit <at> debbugs.gnu.org; Sat, 06 Apr 2024 13:09:38 -0400
Received: from altair.brw.net ([102.129.185.67]:54032 helo=mail.kickinit.net)
by debbugs.gnu.org with esmtp (Exim 4.84_2)
(envelope-from <brw@HIDDEN>) id 1rt8Jp-0005i0-6k
for 70219 <at> debbugs.gnu.org; Sat, 06 Apr 2024 11:51:04 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brandenwilliams.com;
s=202404; t=1712418648;
bh=BWmlrcb+Vfoq6mdK+FfD1YPoavC3Hm+0B5Y0sEVrTG8=;
h=From:Subject:Date:In-Reply-To:Cc:To:References:From;
b=NYTTsGAeRdLl1H3M7w5/UTRKENqUjfQ24ovDcL71XXgeX7vrzRV/lNHd5maDJ5q4F
rr24cfGJiOwDe6De8291iVJooTdV/0glmvLdBBzFtLinfCbq0UZvZJsPxmEiyxQrLJ
VFMMbsWfDgL3WRSdOtQJGrcyl4Tiwrar9MV3Cqd/PG5j0dHFomEaud1PmMNy6F8MnV
Et4n44TYAhh/ucopxVURwxWYqqJ0WTZAcwSQ/0bN7UPbyM8tcsW3SLN+E+576MfQLj
Oljwr1bQVbgvn0yFzpm6kkOOcc49LyP3lKZvK1bPsO0oVHY4d/g7mySvW07HZNttS/
h/pp0T0Bseo5Q==
Received: from smtpclient.apple (unknown [47.185.185.34])
(Authenticated sender: brw)
by mail.kickinit.net (Postfix) with ESMTPSA id 6BC2736919F;
Sat, 6 Apr 2024 10:50:48 -0500 (CDT)
From: "Branden R. Williams" <brw@HIDDEN>
Message-Id: <D518A695-C456-4D0B-868B-68081002B76E@HIDDEN>
Content-Type: multipart/alternative;
boundary="Apple-Mail=_C56D8345-7A71-4CA3-A23F-4263BADEA594"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Subject: Re: bug#70219: Bug/Issue with timeout and signals
Date: Sat, 6 Apr 2024 10:50:38 -0500
In-Reply-To: <475472dc-f7ec-7c23-ff2e-a3bb6725092d@HIDDEN>
To: Chris Elvidge <celvidge001@HIDDEN>
References: <ADBC15C8-7D3B-464D-9253-79EEF4091A3F@HIDDEN>
<265efe1a-e937-6f70-1c14-054de8ed1a72@HIDDEN>
<29BA5949-B68B-4B9C-BD14-25ADB74475F7@HIDDEN>
<87frvyc11y.fsf@HIDDEN>
<D3F30E0A-F489-4193-88C8-9D4EDA18B338@HIDDEN>
<475472dc-f7ec-7c23-ff2e-a3bb6725092d@HIDDEN>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
X-Spam-Score: 0.0 (/)
X-Debbugs-Envelope-To: 70219
X-Mailman-Approved-At: Sat, 06 Apr 2024 13:09:26 -0400
Cc: Andreas Schwab <schwab@HIDDEN>, 70219 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>,
<mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>,
<mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)
--Apple-Mail=_C56D8345-7A71-4CA3-A23F-4263BADEA594
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
Working from the code published here: =
https://github.com/coreutils/coreutils/blob/master/src/timeout.c
If you look at the code, you can see the kill_after variable set on line =
486 if the switch is there. In the cleanup() function on line 202, it =
looks for that variable to be st on line 212, then sets the kill signal =
to be SIGKILL and sets the timeout. But on line 578, the timeout is =
overridden anyway by the timeout variable obtained from the argv on line =
520. So as I stated previously, if the goal of the -k is to send =
SIGKILL, it should not be a kill_after or require any seconds to be =
sent. What is happening on line 485 is it is capturing what SHOULD be =
the duration passed to =E2=80=9Ctimeout=E2=80=9D to kill_after, and then =
the timeout that is attempted to be grabbed in line 520 is literally the =
command you are wanting to run the timeout against.
It does not appear to matter what you pass into -k as it is never used =
in practice. -k does not do this:
-k, --kill-after=3DDURATION
also send a KILL signal if COMMAND is still running
this long after the initial signal was sent
It=E2=80=99s a logic bug. The -k flag should not take a duration, but =
just set the kill signal to SIGKILL. See this example where the 2s is =
captured on line 486 leaving nothing for line 520.
$ timeout -k 2s ping 8.8.8.8
timeout: invalid time interval =E2=80=98ping=E2=80=99
Try 'timeout --help' for more information.
See these examples of passing garbage into the -k flag:
$ timeout -k 2s 2s ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=3D1 ttl=3D114 time=3D2.02 ms
64 bytes from 8.8.8.8: icmp_seq=3D2 ttl=3D114 time=3D1.92 ms
$ timeout -k 32s 2s ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=3D1 ttl=3D114 time=3D2.37 ms
64 bytes from 8.8.8.8: icmp_seq=3D2 ttl=3D114 time=3D1.94 ms
$ timeout -k 92s 2s ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=3D1 ttl=3D114 time=3D1.94 ms
64 bytes from 8.8.8.8: icmp_seq=3D2 ttl=3D114 time=3D8.38 ms
$ timeout -k 9265535s 2s ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=3D1 ttl=3D114 time=3D8.77 ms
64 bytes from 8.8.8.8: icmp_seq=3D2 ttl=3D114 time=3D11.8 ms
$ timeout 2s ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=3D1 ttl=3D114 time=3D1.94 ms
64 bytes from 8.8.8.8: icmp_seq=3D2 ttl=3D114 time=3D2.00 ms
Regards,
B
> On Apr 6, 2024, at 9:44=E2=80=AFAM, Chris Elvidge =
<celvidge001@HIDDEN> wrote:
>=20
> Branden,
>=20
> Then how come timeout -k 10s 20s ping 8.8.8.8 works?
> 10s is DEFINITELY NOT an integer. 20s in the timeout value.
>=20
> I still think your reasoning is suspect.
>=20
>=20
> On 06/04/2024 at 13:43, Branden R. Williams wrote:
>> 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=E2=80=AFAM, Andreas Schwab =
<schwab@HIDDEN> wrote:
>>>=20
>>> On Apr 05 2024, "Branden R. Williams" via GNU coreutils Bug Reports =
wrote:
>>>=20
>>>> That=E2=80=99s 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.
>>>=20
>>> $ timeout -k USR1 1s sleep 10
>>> timeout: invalid time interval =E2=80=98USR1=E2=80=99
>>> Try 'timeout --help' for more information.
>>> $ timeout -s KILL 1s sleep 10
>>> Killed
>>>=20
>>> --=20
>>> Andreas Schwab, schwab@HIDDEN
>>> GPG Key fingerprint =3D 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 =
A9DA AEC1
>>> "And now for something completely different."
>=20
>=20
> --=20
>=20
> Chris Elvidge
>=20
> 5 Ebor Park, Appleton Roebuck, York, Nor
--Apple-Mail=_C56D8345-7A71-4CA3-A23F-4263BADEA594
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><div>Working =
from the code published here: <a =
href=3D"https://github.com/coreutils/coreutils/blob/master/src/timeout.c">=
https://github.com/coreutils/coreutils/blob/master/src/timeout.c</a></div>=
<div><br></div>If you look at the code, you can see the kill_after =
variable set on line 486 if the switch is there. In the cleanup() =
function on line 202, it looks for that variable to be st on line 212, =
then sets the kill signal to be SIGKILL and sets the timeout. But on =
line 578, the timeout is overridden anyway by the timeout variable =
obtained from the argv on line 520. So as I stated previously, if the =
goal of the -k is to send SIGKILL, it should not be a kill_after or =
require any seconds to be sent. What is happening on line 485 is it is =
capturing what SHOULD be the duration passed to =E2=80=9Ctimeout=E2=80=9D =
to kill_after, and then the timeout that is attempted to be grabbed in =
line 520 is literally the command you are wanting to run the timeout =
against.<div><br></div><div>It does not appear to matter what you pass =
into -k as it is never used in practice. -k does not do =
this:</div><div><br></div><div> -k, =
--kill-after=3DDURATION</div><div> =
also send a KILL signal if COMMAND is still =
running</div><div> =
this long after the initial signal was =
sent</div><div><br></div><div>It=E2=80=99s a logic bug. The -k flag =
should not take a duration, but just set the kill signal to SIGKILL. See =
this example where the 2s is captured on line 486 leaving nothing for =
line 520.</div><div><div><br></div><div>$ timeout -k 2s ping =
8.8.8.8</div><div><div>timeout: invalid time interval =
=E2=80=98ping=E2=80=99</div><div>Try 'timeout --help' for more =
information.</div></div><div><br></div><div>See these examples of =
passing garbage into the -k flag:</div><div><br></div><div><div>$ =
timeout -k 2s 2s ping 8.8.8.8</div><div>PING 8.8.8.8 (8.8.8.8) 56(84) =
bytes of data.</div><div>64 bytes from 8.8.8.8: icmp_seq=3D1 ttl=3D114 =
time=3D2.02 ms</div><div>64 bytes from 8.8.8.8: icmp_seq=3D2 ttl=3D114 =
time=3D1.92 ms</div><div><br></div><div>$ timeout -k 32s 2s ping =
8.8.8.8</div><div>PING 8.8.8.8 (8.8.8.8) 56(84) bytes of =
data.</div><div>64 bytes from 8.8.8.8: icmp_seq=3D1 ttl=3D114 time=3D2.37 =
ms</div><div>64 bytes from 8.8.8.8: icmp_seq=3D2 ttl=3D114 time=3D1.94 =
ms</div><div><br></div><div>$ timeout -k 92s 2s ping =
8.8.8.8</div><div>PING 8.8.8.8 (8.8.8.8) 56(84) bytes of =
data.</div><div>64 bytes from 8.8.8.8: icmp_seq=3D1 ttl=3D114 time=3D1.94 =
ms</div><div>64 bytes from 8.8.8.8: icmp_seq=3D2 ttl=3D114 time=3D8.38 =
ms</div><div><br></div><div>$ timeout -k 9265535s 2s ping =
8.8.8.8</div><div>PING 8.8.8.8 (8.8.8.8) 56(84) bytes of =
data.</div><div>64 bytes from 8.8.8.8: icmp_seq=3D1 ttl=3D114 time=3D8.77 =
ms</div><div>64 bytes from 8.8.8.8: icmp_seq=3D2 ttl=3D114 time=3D11.8 =
ms</div><div><br></div><div>$ timeout 2s ping 8.8.8.8</div><div>PING =
8.8.8.8 (8.8.8.8) 56(84) bytes of data.</div><div>64 bytes from 8.8.8.8: =
icmp_seq=3D1 ttl=3D114 time=3D1.94 ms</div><div>64 bytes from 8.8.8.8: =
icmp_seq=3D2 ttl=3D114 time=3D2.00 =
ms</div></div><div><br></div><div><br></div><div><div><div dir=3D"auto" =
style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: =
space; line-break: after-white-space;"><div style=3D"color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><div =
style=3D"color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; overflow-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;">Regards,<br><br>B<br></div></div></div>
</div>
<div><br><blockquote type=3D"cite"><div>On Apr 6, 2024, at 9:44=E2=80=AFAM=
, Chris Elvidge <celvidge001@HIDDEN> wrote:</div><br =
class=3D"Apple-interchange-newline"><div><div>Branden,<br><br>Then how =
come timeout -k 10s 20s ping 8.8.8.8 works?<br>10s is DEFINITELY NOT an =
integer. 20s in the timeout value.<br><br>I still think your reasoning =
is suspect.<br><br><br>On 06/04/2024 at 13:43, Branden R. Williams =
wrote:<br><blockquote type=3D"cite">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:<br>$ timeout -k 10s sleep =
10<br>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.<br>Regards,<br>B<br><blockquote =
type=3D"cite">On Apr 6, 2024, at 4:06=E2=80=AFAM, Andreas Schwab =
<schwab@HIDDEN> wrote:<br><br>On Apr 05 2024, "Branden R. =
Williams" via GNU coreutils Bug Reports wrote:<br><br><blockquote =
type=3D"cite">That=E2=80=99s 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.<br></blockquote><br>$ timeout -k USR1 1s sleep 10<br>timeout: =
invalid time interval =E2=80=98USR1=E2=80=99<br>Try 'timeout --help' for =
more information.<br>$ timeout -s KILL 1s sleep 10<br>Killed<br><br>-- =
<br>Andreas Schwab, schwab@HIDDEN<br>GPG Key fingerprint =3D =
7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1<br>"And now for =
something completely different."<br></blockquote></blockquote><br><br>-- =
<br><br>Chris Elvidge<br><br>5 Ebor Park, Appleton Roebuck, York, =
Nor<br></div></div></blockquote></div><br></div></div></body></html>=
--Apple-Mail=_C56D8345-7A71-4CA3-A23F-4263BADEA594--
bug-coreutils@HIDDEN:bug#70219; Package coreutils.
Full text available.Received: (at 70219) by debbugs.gnu.org; 6 Apr 2024 17:09:37 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Sat Apr 06 13:09:37 2024 Received: from localhost ([127.0.0.1]:40883 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1rt9Xq-0000xQ-On for submit <at> debbugs.gnu.org; Sat, 06 Apr 2024 13:09:37 -0400 Received: from altair.brw.net ([102.129.185.67]:53248 helo=mail.kickinit.net) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <brw@HIDDEN>) id 1rt5OP-0000fe-5H for 70219 <at> debbugs.gnu.org; Sat, 06 Apr 2024 08:43:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brandenwilliams.com; s=202404; t=1712407400; bh=1UBGSD6SPhahQ4u2yqZMiLK1Q4sWvKCmjlWCws063og=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=qm71PS5eXPdn3ddjgSNGMEjMjsagk4ZiBz/AGDfQwl9OuDHJVT4cCipWIkrCIpnWX oE/gMFeg6QA5VOyqPg3P4BCYMylkuI6WeLoV8OiaEBDUb1PJU0KeEPO0t/uslvzhz+ r84wWxyqBpnyBgXF1CaVlocPtfW5rO6wbDet5rAAm9okqIeJjXrNnoGeJBlKE6ekoQ zgRMYFcegvRuiyp4F5CSWFbR5/WZt1ML84T+FjOF46dimDUnoUZTgWLYaP0rLHHNcB uPFkGH3LXzKsn4k3M23KyZYH3rhZhTniqM5lCTRC4n/dcAeAyRsnpql9RAQOjxmbS7 8PuFnFoS8Fucw== Received: from smtpclient.apple (unknown [47.185.185.34]) (Authenticated sender: brw) by mail.kickinit.net (Postfix) with ESMTPSA id 61F5B36919F; Sat, 6 Apr 2024 07:43:20 -0500 (CDT) From: "Branden R. Williams" <brw@HIDDEN> Message-Id: <D3F30E0A-F489-4193-88C8-9D4EDA18B338@HIDDEN> Content-Type: multipart/alternative; boundary="Apple-Mail=_7D890561-CE64-4C59-9359-311921B7CFF9" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\)) Subject: Re: bug#70219: Bug/Issue with timeout and signals Date: Sat, 6 Apr 2024 07:43:09 -0500 In-Reply-To: <87frvyc11y.fsf@HIDDEN> To: Andreas Schwab <schwab@HIDDEN> References: <ADBC15C8-7D3B-464D-9253-79EEF4091A3F@HIDDEN> <265efe1a-e937-6f70-1c14-054de8ed1a72@HIDDEN> <29BA5949-B68B-4B9C-BD14-25ADB74475F7@HIDDEN> <87frvyc11y.fsf@HIDDEN> X-Mailer: Apple Mail (2.3774.500.171.1.1) X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 70219 X-Mailman-Approved-At: Sat, 06 Apr 2024 13:09:26 -0400 Cc: Chris Elvidge <celvidge001@HIDDEN>, 70219 <at> debbugs.gnu.org X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -1.0 (-) --Apple-Mail=_7D890561-CE64-4C59-9359-311921B7CFF9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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,=20 B > On Apr 6, 2024, at 4:06=E2=80=AFAM, Andreas Schwab = <schwab@HIDDEN> wrote: >=20 > On Apr 05 2024, "Branden R. Williams" via GNU coreutils Bug Reports = wrote: >=20 >> That=E2=80=99s 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. >=20 > $ timeout -k USR1 1s sleep 10 > timeout: invalid time interval =E2=80=98USR1=E2=80=99 > Try 'timeout --help' for more information. > $ timeout -s KILL 1s sleep 10 > Killed >=20 > --=20 > Andreas Schwab, schwab@HIDDEN > GPG Key fingerprint =3D 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA = AEC1 > "And now for something completely different." --Apple-Mail=_7D890561-CE64-4C59-9359-311921B7CFF9 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"content-type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;">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:<div><br></div><div>$ timeout -k 10s sleep 10<br = id=3D"lineBreakAtBeginningOfMessage"><div> <div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, = 0); letter-spacing: normal; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; word-spacing: 0px; = -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: = break-word; -webkit-nbsp-mode: space; line-break: = after-white-space;"><div style=3D"color: rgb(0, 0, 0); letter-spacing: = normal; text-align: start; text-indent: 0px; text-transform: none; = white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: = after-white-space;"><div style=3D"color: rgb(0, 0, 0); letter-spacing: = normal; text-align: start; text-indent: 0px; text-transform: none; = white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: = after-white-space;"><br></div><div style=3D"color: rgb(0, 0, 0); = letter-spacing: normal; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; word-spacing: 0px; = -webkit-text-stroke-width: 0px; overflow-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;">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.</div><div style=3D"color: rgb(0, 0, 0); = letter-spacing: normal; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; word-spacing: 0px; = -webkit-text-stroke-width: 0px; overflow-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;"><br></div><div = style=3D"color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; = text-indent: 0px; text-transform: none; white-space: normal; = word-spacing: 0px; -webkit-text-stroke-width: 0px; overflow-wrap: = break-word; -webkit-nbsp-mode: space; line-break: = after-white-space;">Regards, </div><div style=3D"color: rgb(0, 0, = 0); letter-spacing: normal; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; word-spacing: 0px; = -webkit-text-stroke-width: 0px; overflow-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;"><br></div><div = style=3D"color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; = text-indent: 0px; text-transform: none; white-space: normal; = word-spacing: 0px; -webkit-text-stroke-width: 0px; overflow-wrap: = break-word; -webkit-nbsp-mode: space; line-break: = after-white-space;">B<br><br><br></div></div></div> </div> <div><br><blockquote type=3D"cite"><div>On Apr 6, 2024, at 4:06=E2=80=AFAM= , Andreas Schwab <schwab@HIDDEN> wrote:</div><br = class=3D"Apple-interchange-newline"><div><div>On Apr 05 2024, "Branden = R. Williams" via GNU coreutils Bug Reports wrote:<br><br><blockquote = type=3D"cite">That=E2=80=99s 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. = <br></blockquote><br>$ timeout -k USR1 1s sleep 10<br>timeout: invalid = time interval =E2=80=98USR1=E2=80=99<br>Try 'timeout --help' for more = information.<br>$ timeout -s KILL 1s sleep 10<br>Killed<br><br>-- = <br>Andreas Schwab, schwab@HIDDEN<br>GPG Key fingerprint =3D = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1<br>"And now for = something completely = different."<br></div></div></blockquote></div><br></div></body></html>= --Apple-Mail=_7D890561-CE64-4C59-9359-311921B7CFF9--
bug-coreutils@HIDDEN:bug#70219; Package coreutils.
Full text available.Received: (at 70219) by debbugs.gnu.org; 6 Apr 2024 14:44:34 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Sat Apr 06 10:44:34 2024 Received: from localhost ([127.0.0.1]:40559 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1rt7HW-0005p9-AZ for submit <at> debbugs.gnu.org; Sat, 06 Apr 2024 10:44:34 -0400 Received: from mail-wm1-x329.google.com ([2a00:1450:4864:20::329]:59490) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <celvidge001@HIDDEN>) id 1rt7HR-0005od-Sm for 70219 <at> debbugs.gnu.org; Sat, 06 Apr 2024 10:44:33 -0400 Received: by mail-wm1-x329.google.com with SMTP id 5b1f17b1804b1-41551639550so22018485e9.2 for <70219 <at> debbugs.gnu.org>; Sat, 06 Apr 2024 07:44:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712414658; x=1713019458; darn=debbugs.gnu.org; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:cc:references:to:subject:from:to:cc :subject:date:message-id:reply-to; bh=Zu1ScxBvBKnOvEt+uKb9LsnuR3Ry0ejA1R/rQ4wb7do=; b=JHlbNfoIkzkxOyKO67FTj68GdvypufTNV9EOTV4lAcpY4uc3jFno16vMgRv77jdiAR LAy3vNshRzDuvSTN+aQ2pEKGF/kA8t/X2qeBvgIg822oK6pR6UxRs2N9An7b7E0/xQVS lRbCTNts9phMuVzo7jTg05l1SaYZ34hCyjiRESGteXDaUkztIsddKkmUnLMi7NTpzB/v +FcLmarPlyAk6mhla/3Ky6be3FXQ/j+goEUci8ARMmlnj9N2HolkldREQvvcUJy5EybN BJ7HwaG6AEDTHpVwj07ofGYh7z9c73aeOFqI6XwoC65Zz/ZbE82WwzMxBYL16D4tMijS s62A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712414658; x=1713019458; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:cc:references:to:subject :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Zu1ScxBvBKnOvEt+uKb9LsnuR3Ry0ejA1R/rQ4wb7do=; b=ECpkka14uX4a/nmemBzZT6RQkWg9DctOo7q9ihH1WUsd6cp9XCLXOiGbA2Pp4dNJWr Tpcko7WPPB1lVWNJLuHlNEhy4zGaKE2F+lOL3nJmYLIi+iz7pZRHzSkqmCD+amvmGuvT toIH1Ww1Q3ki7PldI79eY6CCT4s16hjCpesZ5gb3X1pFcjclPC06B07j1c+Inn7HjRwD 4m7N5WR7qmRM8Gm5wQV3zI6oP5jXSyG/EMNrwyWAuQEUdY0ckMJpUOlVCjAt4Mvd6ptV lvp93+0RYDG0aZNLHreE//j8UfZxDloAYyrXxZ3/7heW7yA+jAeEt0FmOABEdTg7FNRy D6AQ== X-Gm-Message-State: AOJu0YzhzTpcZf1oq7oebqiL/jBxR8Ki9rl40elUTA6odxQC3cCB3gjF dOxaVxB/V0/uO0VeLyjjuA1pAV+GxuMPKLPVNX7yqd6OP/SWcj09 X-Google-Smtp-Source: AGHT+IFLxRd2gJCzzEg5y2v0ExFAJyThfZRd4D425LJ4082iNpn/7XHRyO8jsZpvvYhawZf1r2Wa6A== X-Received: by 2002:a05:600c:3551:b0:414:cc98:6093 with SMTP id i17-20020a05600c355100b00414cc986093mr3837878wmq.10.1712414657436; Sat, 06 Apr 2024 07:44:17 -0700 (PDT) Received: from [192.168.23.101] (92.40.168.66.threembb.co.uk. [92.40.168.66]) by smtp.gmail.com with ESMTPSA id l25-20020a1c7919000000b004161cb3e794sm5355782wme.1.2024.04.06.07.44.16 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Apr 2024 07:44:17 -0700 (PDT) Subject: Re: bug#70219: Bug/Issue with timeout and signals To: "Branden R. Williams" <brw@HIDDEN> References: <ADBC15C8-7D3B-464D-9253-79EEF4091A3F@HIDDEN> <265efe1a-e937-6f70-1c14-054de8ed1a72@HIDDEN> <29BA5949-B68B-4B9C-BD14-25ADB74475F7@HIDDEN> <87frvyc11y.fsf@HIDDEN> <D3F30E0A-F489-4193-88C8-9D4EDA18B338@HIDDEN> From: Chris Elvidge <celvidge001@HIDDEN> Message-ID: <475472dc-f7ec-7c23-ff2e-a3bb6725092d@HIDDEN> Date: Sat, 6 Apr 2024 15:44:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 Lightning/5.4 MIME-Version: 1.0 In-Reply-To: <D3F30E0A-F489-4193-88C8-9D4EDA18B338@HIDDEN> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-Spam-Score: 0.8 (/) X-Debbugs-Envelope-To: 70219 Cc: Andreas Schwab <schwab@HIDDEN>, 70219 <at> debbugs.gnu.org X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -0.2 (/) Branden, Then how come timeout -k 10s 20s ping 8.8.8.8 works? 10s is DEFINITELY NOT an integer. 20s in the timeout value. I still think your reasoning is suspect. On 06/04/2024 at 13:43, Branden R. Williams wrote: > 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@HIDDEN> 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@HIDDEN >> GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 >> "And now for something completely different." > -- Chris Elvidge 5 Ebor Park, Appleton Roebuck, York, Nor
bug-coreutils@HIDDEN:bug#70219; Package coreutils.
Full text available.Received: (at 70219) by debbugs.gnu.org; 6 Apr 2024 09:07:04 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Sat Apr 06 05:07:04 2024 Received: from localhost ([127.0.0.1]:38266 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1rt20t-0007dU-Qh for submit <at> debbugs.gnu.org; Sat, 06 Apr 2024 05:07:04 -0400 Received: from mail-out.m-online.net ([212.18.0.9]:45080) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <whitebox@HIDDEN>) id 1rt20o-0007cf-NP for 70219 <at> debbugs.gnu.org; Sat, 06 Apr 2024 05:07:02 -0400 Received: from frontend01.mail.m-online.net (unknown [192.168.8.182]) by mail-out.m-online.net (Postfix) with ESMTP id 4VBTxk70rDz1qsP8; Sat, 6 Apr 2024 11:06:50 +0200 (CEST) Received: from localhost (dynscan1.mnet-online.de [192.168.6.68]) by mail.m-online.net (Postfix) with ESMTP id 4VBTxk5ndsz1qqlS; Sat, 6 Apr 2024 11:06:50 +0200 (CEST) X-Virus-Scanned: amavis at mnet-online.de Received: from mail.mnet-online.de ([192.168.8.182]) by localhost (dynscan1.mail.m-online.net [192.168.6.68]) (amavis, port 10024) with ESMTP id g5DIVyQOrGEi; Sat, 6 Apr 2024 11:06:49 +0200 (CEST) X-Auth-Info: CaT1WjFVgfq0/WkjrdbjeDXQ7cFx1AYpXCHgqpTcol7zuuRX+dR5odbJb6yi958c Received: from tiger.home (aftr-62-216-202-57.dynamic.mnet-online.de [62.216.202.57]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.mnet-online.de (Postfix) with ESMTPSA; Sat, 6 Apr 2024 11:06:49 +0200 (CEST) Received: by tiger.home (Postfix, from userid 1000) id 805FB2736E0; Sat, 6 Apr 2024 11:06:49 +0200 (CEST) From: Andreas Schwab <schwab@HIDDEN> To: "Branden R. Williams" via GNU coreutils Bug Reports <bug-coreutils@HIDDEN> Subject: Re: bug#70219: Bug/Issue with timeout and signals In-Reply-To: <29BA5949-B68B-4B9C-BD14-25ADB74475F7@HIDDEN> (Branden R. Williams's message of "Fri, 5 Apr 2024 17:14:54 -0500") References: <ADBC15C8-7D3B-464D-9253-79EEF4091A3F@HIDDEN> <265efe1a-e937-6f70-1c14-054de8ed1a72@HIDDEN> <29BA5949-B68B-4B9C-BD14-25ADB74475F7@HIDDEN> X-Yow: ONE: I will donate my entire ``BABY HUEY'' comic book collection to the downtown PLASMA CENTER.. TWO: I won't START a BAND called ``KHADAFY & THE HIT SQUAD''.. THREE: I won't ever TUMBLE DRY my FOX TERRIER again!! Date: Sat, 06 Apr 2024 11:06:49 +0200 Message-ID: <87frvyc11y.fsf@HIDDEN> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam-Score: -0.5 (/) X-Debbugs-Envelope-To: 70219 Cc: Chris Elvidge <celvidge001@HIDDEN>, 70219 <at> debbugs.gnu.org, "Branden R. Williams" <brw@HIDDEN> X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -1.5 (-) 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@HIDDEN GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
bug-coreutils@HIDDEN:bug#70219; Package coreutils.
Full text available.
Received: (at submit) by debbugs.gnu.org; 6 Apr 2024 09:07:11 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sat Apr 06 05:07:11 2024
Received: from localhost ([127.0.0.1]:38269 helo=debbugs.gnu.org)
by debbugs.gnu.org with esmtp (Exim 4.84_2)
(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
id 1rt211-0007eJ-2J
for submit <at> debbugs.gnu.org; Sat, 06 Apr 2024 05:07:11 -0400
Received: from lists.gnu.org ([2001:470:142::17]:50954)
by debbugs.gnu.org with esmtp (Exim 4.84_2)
(envelope-from <whitebox@HIDDEN>) id 1rt20z-0007dS-9H
for submit <at> debbugs.gnu.org; Sat, 06 Apr 2024 05:07:09 -0400
Received: from eggs.gnu.org ([2001:470:142:3::10])
by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.90_1) (envelope-from <whitebox@HIDDEN>)
id 1rt20n-0000S5-2I
for bug-coreutils@HIDDEN; Sat, 06 Apr 2024 05:06:57 -0400
Received: from mail-out.m-online.net ([212.18.0.9])
by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.90_1) (envelope-from <whitebox@HIDDEN>)
id 1rt20k-00011P-VS
for bug-coreutils@HIDDEN; Sat, 06 Apr 2024 05:06:56 -0400
Received: from frontend01.mail.m-online.net (unknown [192.168.8.182])
by mail-out.m-online.net (Postfix) with ESMTP id 4VBTxk70rDz1qsP8;
Sat, 6 Apr 2024 11:06:50 +0200 (CEST)
Received: from localhost (dynscan1.mnet-online.de [192.168.6.68])
by mail.m-online.net (Postfix) with ESMTP id 4VBTxk5ndsz1qqlS;
Sat, 6 Apr 2024 11:06:50 +0200 (CEST)
X-Virus-Scanned: amavis at mnet-online.de
Received: from mail.mnet-online.de ([192.168.8.182])
by localhost (dynscan1.mail.m-online.net [192.168.6.68]) (amavis, port 10024)
with ESMTP id g5DIVyQOrGEi; Sat, 6 Apr 2024 11:06:49 +0200 (CEST)
X-Auth-Info: CaT1WjFVgfq0/WkjrdbjeDXQ7cFx1AYpXCHgqpTcol7zuuRX+dR5odbJb6yi958c
Received: from tiger.home (aftr-62-216-202-57.dynamic.mnet-online.de
[62.216.202.57])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
(No client certificate requested)
by mail.mnet-online.de (Postfix) with ESMTPSA;
Sat, 6 Apr 2024 11:06:49 +0200 (CEST)
Received: by tiger.home (Postfix, from userid 1000)
id 805FB2736E0; Sat, 6 Apr 2024 11:06:49 +0200 (CEST)
From: Andreas Schwab <schwab@HIDDEN>
To: "Branden R. Williams" via GNU coreutils Bug Reports <bug-coreutils@HIDDEN>
Subject: Re: bug#70219: Bug/Issue with timeout and signals
In-Reply-To: <29BA5949-B68B-4B9C-BD14-25ADB74475F7@HIDDEN>
(Branden R. Williams's message of "Fri, 5 Apr 2024 17:14:54 -0500")
References: <ADBC15C8-7D3B-464D-9253-79EEF4091A3F@HIDDEN>
<265efe1a-e937-6f70-1c14-054de8ed1a72@HIDDEN>
<29BA5949-B68B-4B9C-BD14-25ADB74475F7@HIDDEN>
X-Yow: ONE: I will donate my entire ``BABY HUEY'' comic book collection
to the downtown PLASMA CENTER..
TWO: I won't START a BAND called ``KHADAFY & THE HIT SQUAD''..
THREE: I won't ever TUMBLE DRY my FOX TERRIER again!!
Date: Sat, 06 Apr 2024 11:06:49 +0200
Message-ID: <87frvyc11y.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Received-SPF: pass client-ip=212.18.0.9; envelope-from=whitebox@HIDDEN;
helo=mail-out.m-online.net
X-Spam_score_int: -22
X-Spam_score: -2.3
X-Spam_bar: --
X-Spam_report: (-2.3 / 5.0 requ) BAYES_00=-1.9,
HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7,
RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Spam-Score: 1.2 (+)
X-Spam-Report: Spam detection software, running on the system "debbugs.gnu.org",
has NOT identified this incoming email as spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: 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 [...]
Content analysis details: (1.2 points, 10.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
1.0 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail)
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
0.2 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level
mail domains are different
X-Debbugs-Envelope-To: submit
Cc: Chris Elvidge <celvidge001@HIDDEN>, 70219 <at> debbugs.gnu.org,
"Branden R. Williams" <brw@HIDDEN>
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>,
<mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>,
<mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: 0.2 (/)
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@HIDDEN
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
bug-coreutils@HIDDEN:bug#70219; Package coreutils.
Full text available.Received: (at 70219) by debbugs.gnu.org; 6 Apr 2024 06:38:47 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Sat Apr 06 02:38:47 2024 Received: from localhost ([127.0.0.1]:38015 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1rszhN-00077Z-9x for submit <at> debbugs.gnu.org; Sat, 06 Apr 2024 02:38:47 -0400 Received: from altair.brw.net ([102.129.185.67]:47748 helo=mail.kickinit.net) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <brw@HIDDEN>) id 1rsrq9-0004lv-3m for 70219 <at> debbugs.gnu.org; Fri, 05 Apr 2024 18:15:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brandenwilliams.com; s=202404; t=1712355305; bh=RKOTBrzv5W7RyAa1wyK/eFAXyRMzK9s3lQ9wgRZ04m0=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=kp40maZIcVhe7zJDaL84tbZ7xQvUXXwhbKAzkyhaNgRhsnWoKT7GFDMqDmVi2boRl ocDteb/cd8mmJY3LAs+xx01e51+iBkVq+BYyh6e112u75ihAF7O/P7PwbYmjVneQ7d a/WKVVFLrgapeAJTwCTddbBB6iG7ZdlpmxRCh9Boq5O5gXnVApqSAyXQIeLDt6g/Jw mgZa8UR4c9sfuropfBvuNNtQ9JzJu+dSUrrs93A4UtjQulZUOXlto4qNfd8Rbn168q d3ufI1iRPHxsAeazpx3QVXDhKk2ndfuDj/uZrXUra3jkex8QG+DnC7NvsOTnjHjhCl 0S8NS6Nsdq9Gg== Received: from smtpclient.apple (unknown [47.185.166.250]) (Authenticated sender: brw) by mail.kickinit.net (Postfix) with ESMTPSA id 12F7C36919F; Fri, 5 Apr 2024 17:15:04 -0500 (CDT) From: "Branden R. Williams" <brw@HIDDEN> Message-Id: <29BA5949-B68B-4B9C-BD14-25ADB74475F7@HIDDEN> Content-Type: multipart/alternative; boundary="Apple-Mail=_84209169-8B31-4E43-985D-2C5704E5ABD6" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\)) Subject: Re: bug#70219: Bug/Issue with timeout and signals Date: Fri, 5 Apr 2024 17:14:54 -0500 In-Reply-To: <265efe1a-e937-6f70-1c14-054de8ed1a72@HIDDEN> To: 70219 <at> debbugs.gnu.org References: <ADBC15C8-7D3B-464D-9253-79EEF4091A3F@HIDDEN> <265efe1a-e937-6f70-1c14-054de8ed1a72@HIDDEN> X-Mailer: Apple Mail (2.3774.500.171.1.1) X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 70219 X-Mailman-Approved-At: Sat, 06 Apr 2024 02:38:41 -0400 Cc: Chris Elvidge <celvidge001@HIDDEN> X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -1.0 (-) --Apple-Mail=_84209169-8B31-4E43-985D-2C5704E5ABD6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 That=E2=80=99s 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.=20 That functionality is not represented in the manpage or --help. If you = used -k 10 10s it would send a SIGTERM vs SIGKILL. The point is that the = argument immediately after the -k or --kill-after=3D is the kill signal = code, not the duration. The manpage and help file suggest that it should = be the duration. That=E2=80=99s why I am suggesting using a default SIGTERM if the -k or = --kill-after=3D is passed so that the duration is the actual argument = that follows. If you wanted to alter the signal, that=E2=80=99s where = the -s flag comes in. > On Apr 5, 2024, at 4:59=E2=80=AFPM, Chris Elvidge = <celvidge001@HIDDEN> wrote: >=20 >=20 >=20 > On 05/04/2024 at 16:19, Branden R. Williams via GNU coreutils Bug = Reports wrote: >> I was integrating the timeout command into a shell script and = realized the manpage & the --help docs do not accurately describe how = the tool works. In addition, there appears to be a bug related to = arguments passed. I am running version 9.1. >> According to the help screen, this command should work: >> timeout -k 10s ping = https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__example.com&d=3DDwIC= aQ&c=3DeuGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=3D1o61i4CUhS9OzzVMraH= h20b966TBpqSO4_0GGRNaLWA&m=3DaJDfsufl90pc4lE-vjk1Oo94O1RIrEP39t_G7X5-pvl_5= ZXtR-2jcnl0a5OxJgGu&s=3DVjTsmLfaTKmXMJL0S6OXC7PHTK-rxRwmG7skx4FheqY&e=3D = <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__example.com_&d=3DDw= ICaQ&c=3DeuGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=3D1o61i4CUhS9OzzVMr= aHh20b966TBpqSO4_0GGRNaLWA&m=3DaJDfsufl90pc4lE-vjk1Oo94O1RIrEP39t_G7X5-pvl= _5ZXtR-2jcnl0a5OxJgGu&s=3Di2LYw6g0va2Fbz-arA9sTJOn7_G1uY3hN2Pf5pLautc&e=3D= > >> It fails, however, because the next argument after invoking -k is the = kill signal you want to send. The command (to send a SIGKILL) must be: >=20 > As I understand it, the argument after -k (or --kill-after=3D) is the = time to wait and send the kill signal if the timeout fails. > So this line: >=20 >> timeout -k 9 10s ping = https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__example.com&d=3DDwIC= aQ&c=3DeuGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=3D1o61i4CUhS9OzzVMraH= h20b966TBpqSO4_0GGRNaLWA&m=3DaJDfsufl90pc4lE-vjk1Oo94O1RIrEP39t_G7X5-pvl_5= ZXtR-2jcnl0a5OxJgGu&s=3DVjTsmLfaTKmXMJL0S6OXC7PHTK-rxRwmG7skx4FheqY&e=3D = <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__example.com_&d=3DDw= ICaQ&c=3DeuGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=3D1o61i4CUhS9OzzVMr= aHh20b966TBpqSO4_0GGRNaLWA&m=3DaJDfsufl90pc4lE-vjk1Oo94O1RIrEP39t_G7X5-pvl= _5ZXtR-2jcnl0a5OxJgGu&s=3Di2LYw6g0va2Fbz-arA9sTJOn7_G1uY3hN2Pf5pLautc&e=3D= > >=20 > sends a kill signal 9 seconds after the timeout, if the timeout hasn't = worked. >=20 > The -s option is to change the signal sent (as below). >=20 >> I believe the kill after functionality and docs should be modified to = send a default signal of SIGTERM without an additional argument so the = first iteration above would work. Then you could explain that if you = wanted to send a DIFFERENT signal, use the -s flag that is there to pass = one. But according to the docs, the first command SHOULD work. Even = using the --kill-after=3D syntax passes in the kill signal into that = argument, not the actual time. >> Thank you for your consideration and for maintaining such a critical = set of tools! >> Regards, >> B >=20 >=20 > --=20 >=20 > Chris Elvidge >=20 --Apple-Mail=_84209169-8B31-4E43-985D-2C5704E5ABD6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"content-type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;">That=E2=80=99s = 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. <div><br></div><div>That functionality is not represented in = the manpage or --help. If you used -k 10 10s it would send a SIGTERM vs = SIGKILL. The point is that the argument immediately after the -k or = --kill-after=3D is the kill signal code, not the duration. The manpage = and help file suggest that it should be the = duration.</div><div><br></div><div>That=E2=80=99s why I am suggesting = using a default SIGTERM if the -k or --kill-after=3D is passed so that = the duration is the actual argument that follows. If you wanted to alter = the signal, that=E2=80=99s where the -s flag comes in.<br = id=3D"lineBreakAtBeginningOfMessage"><div> <div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, = 0); letter-spacing: normal; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; word-spacing: 0px; = -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: = break-word; -webkit-nbsp-mode: space; line-break: = after-white-space;"><div style=3D"color: rgb(0, 0, 0); letter-spacing: = normal; text-align: start; text-indent: 0px; text-transform: none; = white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: = after-white-space;"><div style=3D"color: rgb(0, 0, 0); letter-spacing: = normal; text-align: start; text-indent: 0px; text-transform: none; = white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: = after-white-space;"><br></div></div></div> </div> <div><br><blockquote type=3D"cite"><div>On Apr 5, 2024, at 4:59=E2=80=AFPM= , Chris Elvidge <celvidge001@HIDDEN> wrote:</div><br = class=3D"Apple-interchange-newline"><div><div><br><br>On 05/04/2024 at = 16:19, Branden R. Williams via GNU coreutils Bug Reports = wrote:<br><blockquote type=3D"cite">I was integrating the timeout = command into a shell script and realized the manpage & the --help = docs do not accurately describe how the tool works. In addition, there = appears to be a bug related to arguments passed. I am running version = 9.1.<br>According to the help screen, this command should work:<br><span = class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>timeout = -k 10s ping = https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__example.com&d=3D= DwICaQ&c=3DeuGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=3D1o61i4C= UhS9OzzVMraHh20b966TBpqSO4_0GGRNaLWA&m=3DaJDfsufl90pc4lE-vjk1Oo94O1RIr= EP39t_G7X5-pvl_5ZXtR-2jcnl0a5OxJgGu&s=3DVjTsmLfaTKmXMJL0S6OXC7PHTK-rxR= wmG7skx4FheqY&e=3D = <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__example.com_&= ;d=3DDwICaQ&c=3DeuGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=3D1o= 61i4CUhS9OzzVMraHh20b966TBpqSO4_0GGRNaLWA&m=3DaJDfsufl90pc4lE-vjk1Oo94= O1RIrEP39t_G7X5-pvl_5ZXtR-2jcnl0a5OxJgGu&s=3Di2LYw6g0va2Fbz-arA9sTJOn7= _G1uY3hN2Pf5pLautc&e=3D><br>It fails, however, because the next = argument after invoking -k is the kill signal you want to send. The = command (to send a SIGKILL) must be:<br></blockquote><br>As I understand = it, the argument after -k (or --kill-after=3D) is the time to wait and = send the kill signal if the timeout fails.<br>So this = line:<br><br><blockquote type=3D"cite"><span class=3D"Apple-tab-span" = style=3D"white-space:pre"> </span>timeout -k 9 10s ping = https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__example.com&d=3D= DwICaQ&c=3DeuGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=3D1o61i4C= UhS9OzzVMraHh20b966TBpqSO4_0GGRNaLWA&m=3DaJDfsufl90pc4lE-vjk1Oo94O1RIr= EP39t_G7X5-pvl_5ZXtR-2jcnl0a5OxJgGu&s=3DVjTsmLfaTKmXMJL0S6OXC7PHTK-rxR= wmG7skx4FheqY&e=3D = <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__example.com_&= ;d=3DDwICaQ&c=3DeuGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=3D1o= 61i4CUhS9OzzVMraHh20b966TBpqSO4_0GGRNaLWA&m=3DaJDfsufl90pc4lE-vjk1Oo94= O1RIrEP39t_G7X5-pvl_5ZXtR-2jcnl0a5OxJgGu&s=3Di2LYw6g0va2Fbz-arA9sTJOn7= _G1uY3hN2Pf5pLautc&e=3D><br></blockquote><br>sends a kill signal = 9 seconds after the timeout, if the timeout hasn't worked.<br><br>The -s = option is to change the signal sent (as below).<br><br><blockquote = type=3D"cite">I believe the kill after functionality and docs should be = modified to send a default signal of SIGTERM without an additional = argument so the first iteration above would work. Then you could explain = that if you wanted to send a DIFFERENT signal, use the -s flag that is = there to pass one. But according to the docs, the first command SHOULD = work. Even using the --kill-after=3D syntax passes in the kill signal = into that argument, not the actual time.<br>Thank you for your = consideration and for maintaining such a critical set of = tools!<br>Regards,<br>B<br></blockquote><br><br>-- <br><br>Chris = Elvidge<br><br></div></div></blockquote></div><br></div></body></html>= --Apple-Mail=_84209169-8B31-4E43-985D-2C5704E5ABD6--
bug-coreutils@HIDDEN:bug#70219; Package coreutils.
Full text available.Received: (at 70219) by debbugs.gnu.org; 5 Apr 2024 21:59:54 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Fri Apr 05 17:59:53 2024 Received: from localhost ([127.0.0.1]:37676 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1rsrbF-0003jt-Ji for submit <at> debbugs.gnu.org; Fri, 05 Apr 2024 17:59:53 -0400 Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]:48489) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <celvidge001@HIDDEN>) id 1rsrbB-0003jd-PD for 70219 <at> debbugs.gnu.org; Fri, 05 Apr 2024 17:59:52 -0400 Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-a5199906493so213539166b.1 for <70219 <at> debbugs.gnu.org>; Fri, 05 Apr 2024 14:59:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712354378; x=1712959178; darn=debbugs.gnu.org; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject:from:to:cc :subject:date:message-id:reply-to; bh=ER2U9zqbLRZjc0u/nsvUBY2wjcsNup2jO2ZZNbJGx/A=; b=TGLdlt/Q5LrnST4dnB5YxCFyzxzRl+hY5dDidJhciq/OKfYocmYZkCDVe0i7U8bYs0 0YvXaT823LwTg3fxAW016R9YqwH7c1fx1ONz85fooWuC3FgfXEhvF+JUP6B+tVrTDDQG xvUKYHZsvcTHsw+B0nvuFWS4h6IhU03PADQtV27NoZawFqQGpizjhp62DeW4VNCl4ibw 0239vcS4uNUVuVM/CY19LNWVfKx3iHAZH6rOesolUSdiv3n7ahcLcCiyJE111N6O025O SNpvmzOGKqrxoR3APQ+RIB0NixaNhupXFE/QX4jFO1jZ+95LLzpgj6+Bd51RRpWutDAp 6ttA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712354378; x=1712959178; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ER2U9zqbLRZjc0u/nsvUBY2wjcsNup2jO2ZZNbJGx/A=; b=Vl5GpWPFu5hmqAf4ltsPM+2TBQ/BtI3ETuoJ7qRi/I3pLLI6+Q6jRdnmtk/ApntHQL +BBNFyqSRrhtlPFxtnOWQ3fbJ2fWfTb45VAcQa5vusv2v7U+G3PHOW0oEhUJRP97o/wJ 2DzMs9woBRZ7wQnDDyX0BvN7aONvFfiwc/3vnK726lPQZ0XjwNWrIkGqkWNnTJp+9hOH f9attTzfwnuK5CDh9CjrPLP/dIx1m4ESIZunX/rUuSK1u2A4H83xo8aE8C8EuHz/cGI3 CdoGSkSfXT4S9ZnhvtISrPi8k/aUa0vNuaMbcGSxMRgcKiEk61IRyjt0SBzbMWRIA6Rd QGag== X-Forwarded-Encrypted: i=1; AJvYcCVEtoLIQajoVaCWKRdaWnpM1suAY8jEOZosa+JxuqbwEjt67IIABMg75zpa7KIz/UPQCOHeQv6VoStQ5yRjmTLHZPKKewc= X-Gm-Message-State: AOJu0YwplzeeUkU7uo51bYCo/Iy0VW0Z/NpgEHgBmBnqyD5NRzNXQCH7 hLtu8Jjrum27eS+eKmhdhKwQ43XHq/zjRQeR/W+OK6sF8DZEK7FJbLrxvwCE X-Google-Smtp-Source: AGHT+IHVDTMpW2eLLo1Xfup0AuFe9FWcuvraKr1Krjw8Q8Aobb2bdXfyT02QkU4xbK07QoSQeoUm2A== X-Received: by 2002:a17:906:e285:b0:a51:a09c:16ae with SMTP id gg5-20020a170906e28500b00a51a09c16aemr1640018ejb.71.1712354377521; Fri, 05 Apr 2024 14:59:37 -0700 (PDT) Received: from [192.168.23.101] (92.40.204.1.threembb.co.uk. [92.40.204.1]) by smtp.gmail.com with ESMTPSA id dm10-20020a170907948a00b00a3efa4e033asm1262713ejc.151.2024.04.05.14.59.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Apr 2024 14:59:37 -0700 (PDT) Subject: Re: bug#70219: Bug/Issue with timeout and signals To: "Branden R. Williams" <brw@HIDDEN>, 70219 <at> debbugs.gnu.org References: <ADBC15C8-7D3B-464D-9253-79EEF4091A3F@HIDDEN> From: Chris Elvidge <celvidge001@HIDDEN> Message-ID: <265efe1a-e937-6f70-1c14-054de8ed1a72@HIDDEN> Date: Fri, 5 Apr 2024 22:59:33 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 Lightning/5.4 MIME-Version: 1.0 In-Reply-To: <ADBC15C8-7D3B-464D-9253-79EEF4091A3F@HIDDEN> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Spam-Score: 0.8 (/) X-Debbugs-Envelope-To: 70219 X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -0.2 (/) On 05/04/2024 at 16:19, Branden R. Williams via GNU coreutils Bug Reports wrote: > I was integrating the timeout command into a shell script and realized the manpage & the --help docs do not accurately describe how the tool works. In addition, there appears to be a bug related to arguments passed. I am running version 9.1. > > According to the help screen, this command should work: > > timeout -k 10s ping example.com <http://example.com/> > > It fails, however, because the next argument after invoking -k is the kill signal you want to send. The command (to send a SIGKILL) must be: > As I understand it, the argument after -k (or --kill-after=) is the time to wait and send the kill signal if the timeout fails. So this line: > timeout -k 9 10s ping example.com <http://example.com/> > sends a kill signal 9 seconds after the timeout, if the timeout hasn't worked. The -s option is to change the signal sent (as below). > I believe the kill after functionality and docs should be modified to send a default signal of SIGTERM without an additional argument so the first iteration above would work. Then you could explain that if you wanted to send a DIFFERENT signal, use the -s flag that is there to pass one. But according to the docs, the first command SHOULD work. Even using the --kill-after= syntax passes in the kill signal into that argument, not the actual time. > > Thank you for your consideration and for maintaining such a critical set of tools! > > Regards, > > B > > -- Chris Elvidge
bug-coreutils@HIDDEN:bug#70219; Package coreutils.
Full text available.Received: (at submit) by debbugs.gnu.org; 5 Apr 2024 18:00:30 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Fri Apr 05 14:00:30 2024 Received: from localhost ([127.0.0.1]:37487 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1rsnrX-0003JH-Tm for submit <at> debbugs.gnu.org; Fri, 05 Apr 2024 14:00:29 -0400 Received: from lists.gnu.org ([2001:470:142::17]:40374) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <brw@HIDDEN>) id 1rslMS-0005DU-VL for submit <at> debbugs.gnu.org; Fri, 05 Apr 2024 11:20:13 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <brw@HIDDEN>) id 1rslMG-0004GO-Md for bug-coreutils@HIDDEN; Fri, 05 Apr 2024 11:20:00 -0400 Received: from altair.brw.net ([102.129.185.67] helo=mail.kickinit.net) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <brw@HIDDEN>) id 1rslME-0005Fd-MC for bug-coreutils@HIDDEN; Fri, 05 Apr 2024 11:20:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brandenwilliams.com; s=202404; t=1712330390; bh=iAs4Yzb38+nF5goPcUg0q9GmGIp+LXtiRiN+hDSDv90=; h=From:Subject:Date:To:From; b=U31mXDJ+hLAj7i+6VXXAd1ZbSU60stYedtbpX+9UZBrVVcR4jR/zjAvfBqyogrdwy CNGjWtb0BFXPcqFLmqJSmM+c9nUXAsYcu5pQ0xqYk6NKz5jeUY5lcTttBGteeoZiKb r04+829n0ekAlBfK+MFa+coo0iEvOh2bU60i0EidZ3i2A2i8TBivpng8UIeWl/431s dFg0ZxG7H3Qp6iUObhmQP6ysLg3Z4KAsCVXxPC5KE8XZpytdzIbP7pdiX4A5HVdj2C 9eu5rt64WULgYGDUpm4eDYtkfAC9mfbkU4KtTpZyAr+6Mnj03lRMQpzjKFY0/P5DNg Z/C0ERTm81HUg== Received: from smtpclient.apple (unknown [47.185.185.34]) (Authenticated sender: brw) by mail.kickinit.net (Postfix) with ESMTPSA id 4835836919F for <bug-coreutils@HIDDEN>; Fri, 5 Apr 2024 10:19:50 -0500 (CDT) From: "Branden R. Williams" <brw@HIDDEN> Content-Type: multipart/alternative; boundary="Apple-Mail=_CAAC9918-1C6A-4E03-8B56-85F1C7A890C9" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\)) Subject: Bug/Issue with timeout and signals Message-Id: <ADBC15C8-7D3B-464D-9253-79EEF4091A3F@HIDDEN> Date: Fri, 5 Apr 2024 10:19:39 -0500 To: bug-coreutils@HIDDEN X-Mailer: Apple Mail (2.3774.500.171.1.1) Received-SPF: pass client-ip=102.129.185.67; envelope-from=brw@HIDDEN; helo=mail.kickinit.net X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: submit X-Mailman-Approved-At: Fri, 05 Apr 2024 14:00:27 -0400 X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -1.0 (-) --Apple-Mail=_CAAC9918-1C6A-4E03-8B56-85F1C7A890C9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I was integrating the timeout command into a shell script and realized = the manpage & the --help docs do not accurately describe how the tool = works. In addition, there appears to be a bug related to arguments = passed. I am running version 9.1. According to the help screen, this command should work: timeout -k 10s ping example.com <http://example.com/> It fails, however, because the next argument after invoking -k is the = kill signal you want to send. The command (to send a SIGKILL) must be: timeout -k 9 10s ping example.com <http://example.com/> I believe the kill after functionality and docs should be modified to = send a default signal of SIGTERM without an additional argument so the = first iteration above would work. Then you could explain that if you = wanted to send a DIFFERENT signal, use the -s flag that is there to pass = one. But according to the docs, the first command SHOULD work. Even = using the --kill-after=3D syntax passes in the kill signal into that = argument, not the actual time. Thank you for your consideration and for maintaining such a critical set = of tools!=20 Regards, B --Apple-Mail=_CAAC9918-1C6A-4E03-8B56-85F1C7A890C9 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii <html><head><meta http-equiv=3D"content-type" content=3D"text/html; = charset=3Dus-ascii"></head><body style=3D"overflow-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;"><div>I was = integrating the timeout command into a shell script and realized the = manpage & the --help docs do not accurately describe how the tool = works. In addition, there appears to be a bug related to arguments = passed. I am running version 9.1.</div><div><br></div><div>According to = the help screen, this command should = work:</div><div><br></div><div><span class=3D"Apple-tab-span" = style=3D"white-space:pre"> </span>timeout -k 10s ping <a = href=3D"http://example.com">example.com</a></div><div><br></div><div>It = fails, however, because the next argument after invoking -k is the kill = signal you want to send. The command (to send a SIGKILL) must = be:</div><div><br></div><div><div><span class=3D"Apple-tab-span" = style=3D"white-space: pre;"> </span>timeout -k 9 10s ping <a = href=3D"http://example.com">example.com</a></div><div><br></div><div>I = believe the kill after functionality and docs should be modified to send = a default signal of SIGTERM without an additional argument so the first = iteration above would work. Then you could explain that if you wanted to = send a DIFFERENT signal, use the -s flag that is there to pass one. But = according to the docs, the first command SHOULD work. Even using the = --kill-after=3D syntax passes in the kill signal into that argument, not = the actual time.</div><div><br></div><div>Thank you for your = consideration and for maintaining such a critical set of = tools! </div><div> <div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, = 0); letter-spacing: normal; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; word-spacing: 0px; = -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: = break-word; -webkit-nbsp-mode: space; line-break: = after-white-space;"><div style=3D"color: rgb(0, 0, 0); letter-spacing: = normal; text-align: start; text-indent: 0px; text-transform: none; = white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: = after-white-space;"><div style=3D"color: rgb(0, 0, 0); letter-spacing: = normal; text-align: start; text-indent: 0px; text-transform: none; = white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: = after-white-space;"><br>Regards,<br><br>B<br></div></div></div> </div> <br></div></body></html>= --Apple-Mail=_CAAC9918-1C6A-4E03-8B56-85F1C7A890C9--
"Branden R. Williams" <brw@HIDDEN>:bug-coreutils@HIDDEN.
Full text available.bug-coreutils@HIDDEN:bug#70219; Package coreutils.
Full text available.
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997 nCipher Corporation Ltd,
1994-97 Ian Jackson.