From unknown Sun Jun 22 11:41:16 2025 X-Loop: help-debbugs@gnu.org Subject: bug#51128: timeout --kill-after=0 seems to not send a kill 0s after the initial signal Resent-From: Christoph Anton Mitterer Original-Sender: "Debbugs-submit" Resent-CC: bug-coreutils@gnu.org Resent-Date: Mon, 11 Oct 2021 01:29:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: report 51128 X-GNU-PR-Package: coreutils X-GNU-PR-Keywords: To: 51128@debbugs.gnu.org X-Debbugs-Original-To: bug-coreutils@gnu.org Received: via spool by submit@debbugs.gnu.org id=B.16339157095162 (code B ref -1); Mon, 11 Oct 2021 01:29:02 +0000 Received: (at submit) by debbugs.gnu.org; 11 Oct 2021 01:28:29 +0000 Received: from localhost ([127.0.0.1]:56143 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mZk7A-0001LB-VU for submit@debbugs.gnu.org; Sun, 10 Oct 2021 21:28:29 -0400 Received: from lists.gnu.org ([209.51.188.17]:45530) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mZk79-0001L2-E1 for submit@debbugs.gnu.org; Sun, 10 Oct 2021 21:28:28 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:51666) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mZk79-0004f1-7v for bug-coreutils@gnu.org; Sun, 10 Oct 2021 21:28:27 -0400 Received: from beige.elm.relay.mailchannels.net ([23.83.212.16]:45515) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mZk77-0002Hb-KG for bug-coreutils@gnu.org; Sun, 10 Oct 2021 21:28:26 -0400 X-Sender-Id: instrampxe0y3a|x-authsender|calestyo@scientia.net Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 768B3921F22 for ; Mon, 11 Oct 2021 01:28:16 +0000 (UTC) Received: from mailgw-02.dd24.net (100-96-133-192.trex.outbound.svc.cluster.local [100.96.133.192]) (Authenticated sender: instrampxe0y3a) by relay.mailchannels.net (Postfix) with ESMTPA id 6B8D89221E8 for ; Mon, 11 Oct 2021 01:28:15 +0000 (UTC) X-Sender-Id: instrampxe0y3a|x-authsender|calestyo@scientia.net Received: from mailgw-02.dd24.net (mailgw-02.dd24.net [193.46.215.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.96.133.192 (trex/6.4.3); Mon, 11 Oct 2021 01:28:16 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: instrampxe0y3a|x-authsender|calestyo@scientia.net X-MailChannels-Auth-Id: instrampxe0y3a X-Whimsical-Turn: 34b5294a1716715b_1633915695979_1381591043 X-MC-Loop-Signature: 1633915695979:273565101 X-MC-Ingress-Time: 1633915695978 Received: from heisenberg.fritz.box (ppp-188-174-65-9.dynamic.mnet-online.de [188.174.65.9]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: calestyo@scientia.net) by smtp.dd24.net (Postfix) with ESMTPSA id 802FC5FC25 for ; Mon, 11 Oct 2021 01:28:12 +0000 (UTC) Message-ID: From: Christoph Anton Mitterer Date: Mon, 11 Oct 2021 03:28:12 +0200 Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.0-2 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Received-SPF: none client-ip=23.83.212.16; envelope-from=calestyo@scientia.net; helo=beige.elm.relay.mailchannels.net X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: -2.3 (--) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) 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. However, that doesn't seem to be the case. If intended, this should perhaps at least be mentioned in the manpage :-) Cheers, Chris. From unknown Sun Jun 22 11:41:16 2025 X-Loop: help-debbugs@gnu.org Subject: bug#51128: timeout --kill-after=0 seems to not send a kill 0s after the initial signal Resent-From: =?UTF-8?Q?P=C3=A1draig?= Brady Original-Sender: "Debbugs-submit" Resent-CC: bug-coreutils@gnu.org Resent-Date: Mon, 11 Oct 2021 15:50:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51128 X-GNU-PR-Package: coreutils X-GNU-PR-Keywords: To: Christoph Anton Mitterer , 51128@debbugs.gnu.org Received: via spool by 51128-submit@debbugs.gnu.org id=B51128.163396738910185 (code B ref 51128); Mon, 11 Oct 2021 15:50:02 +0000 Received: (at 51128) by debbugs.gnu.org; 11 Oct 2021 15:49:49 +0000 Received: from localhost ([127.0.0.1]:60719 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mZxYj-0002e8-Bj for submit@debbugs.gnu.org; Mon, 11 Oct 2021 11:49:49 -0400 Received: from mail-wr1-f50.google.com ([209.85.221.50]:38727) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mZxYg-0002dj-Df; Mon, 11 Oct 2021 11:49:47 -0400 Received: by mail-wr1-f50.google.com with SMTP id u18so57816952wrg.5; Mon, 11 Oct 2021 08:49:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Jg5kJT6yEq19TOLD29B5hpiSbRM18RduSv33+eAr8nU=; b=jTPeNmwrtDt1qtBJBOWL1StZh8SMnpp6lp52iJEQrKWp1aZvdqJhdi+jCnSEpf9QlT 3PK63pn8HWGjiADZhSGQUI86mC2RyuTEtn32Qvpkgl1ueJyV+hSphWv24BjKS6id9c65 b8ShCjyF+pgFwk7SI1+RA8RVC6+eo3nIWNIQXSRCsVd/TSggp3kHnlITQr1UcJqtoge5 6v+LIKolgeqxKNnkOsvfwNFS1LnZX6MDUdRLdZ+/9OI8Z2ICqJ7TD9umNzX/tJYonglS XYQEoubfIA4KIpC8vtR7CvFrm0HZ3dIA/UaCPjmMzb/+RMVuoziOcUZUqef3d405V6DS rHhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Jg5kJT6yEq19TOLD29B5hpiSbRM18RduSv33+eAr8nU=; b=3zilpEm+JgZqfjSdeeXHraguOAVbgJi7pk/Tp+kfVB+Ad67ZfjHQJiTPJGMIrcHPGn XoVIYZavdWLQF7y/W06v4tixmw8qp3K2f2WDF1EQBDqwS8cHpKOWtcJoip40l7AQxkd0 K2iz/gRLqbjQe40xido4p0orjKXjPlCTPE4PHkHLAsFOnkFj3JZkQyk+3zNi4Wad9HGp rAptUp/1weATYIbMT3sFkowpbiHXOqyLkRsOawmYBK+7mpsqfWd98zlN7TWquFrxzUHZ Ln5MleDBS5p4hDZ+bnj0sdPn2UhQ96bonJXWRad3VQ9d9T/plJP3gDAmMojOEADiYkg6 v4mg== X-Gm-Message-State: AOAM530E1NxHZdL4lX1Seivz7ndLGDNIQr03dcyKNT4JXrnPEY2t1nPv 5vbkE1LB43rEWMgZ6RKURIDoreQvHwmpYw== X-Google-Smtp-Source: ABdhPJxZwVG16G8X9QceSa4Ao+V8BPfnp/W7NiUb9PmZvJ9c6VL1FGPaHxnGzqUA5NNrC/+Ls8R/qQ== X-Received: by 2002:a05:600c:3b88:: with SMTP id n8mr21550976wms.93.1633967380093; Mon, 11 Oct 2021 08:49:40 -0700 (PDT) Received: from localhost.localdomain (86-40-129-104-dynamic.agg2.lod.rsl-rtd.eircom.net. [86.40.129.104]) by smtp.googlemail.com with UTF8SMTPSA id l2sm366038wmi.1.2021.10.11.08.49.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 11 Oct 2021 08:49:39 -0700 (PDT) References: From: =?UTF-8?Q?P=C3=A1draig?= Brady Message-ID: Date: Mon, 11 Oct 2021 16:49:38 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101 Thunderbird/84.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Score: 0.4 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.6 (/) 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. From unknown Sun Jun 22 11:41:16 2025 X-Loop: help-debbugs@gnu.org Subject: bug#51128: timeout --kill-after=0 seems to not send a kill 0s after the initial signal Resent-From: Christoph Anton Mitterer Original-Sender: "Debbugs-submit" Resent-CC: bug-coreutils@gnu.org Resent-Date: Mon, 11 Oct 2021 16:00:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51128 X-GNU-PR-Package: coreutils X-GNU-PR-Keywords: notabug To: =?UTF-8?Q?P=C3=A1draig?= Brady , 51128@debbugs.gnu.org Received: via spool by 51128-submit@debbugs.gnu.org id=B51128.163396799111169 (code B ref 51128); Mon, 11 Oct 2021 16:00:02 +0000 Received: (at 51128) by debbugs.gnu.org; 11 Oct 2021 15:59:51 +0000 Received: from localhost ([127.0.0.1]:60738 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mZxiQ-0002u5-Us for submit@debbugs.gnu.org; Mon, 11 Oct 2021 11:59:51 -0400 Received: from butterfly.birch.relay.mailchannels.net ([23.83.209.27]:55246) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mZxiO-0002tu-J6 for 51128@debbugs.gnu.org; Mon, 11 Oct 2021 11:59:49 -0400 X-Sender-Id: instrampxe0y3a|x-authsender|calestyo@scientia.net Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id BB4F57613AF; Mon, 11 Oct 2021 15:59:46 +0000 (UTC) Received: from mailgw-01.dd24.net (unknown [127.0.0.6]) (Authenticated sender: instrampxe0y3a) by relay.mailchannels.net (Postfix) with ESMTPA id BB4ED761856; Mon, 11 Oct 2021 15:59:45 +0000 (UTC) X-Sender-Id: instrampxe0y3a|x-authsender|calestyo@scientia.net Received: from mailgw-01.dd24.net (mailgw-01.dd24.net [193.46.215.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.99.42.170 (trex/6.4.3); Mon, 11 Oct 2021 15:59:46 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: instrampxe0y3a|x-authsender|calestyo@scientia.net X-MailChannels-Auth-Id: instrampxe0y3a X-Whimsical-Abiding: 1cb332575f9c45b8_1633967986547_328608617 X-MC-Loop-Signature: 1633967986547:17997231 X-MC-Ingress-Time: 1633967986546 Received: from heisenberg.fritz.box (ppp-188-174-65-9.dynamic.mnet-online.de [188.174.65.9]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: calestyo@scientia.net) by smtp.dd24.net (Postfix) with ESMTPSA id 6CCA65FC32; Mon, 11 Oct 2021 15:59:43 +0000 (UTC) Message-ID: From: Christoph Anton Mitterer Date: Mon, 11 Oct 2021 17:59:42 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.0-2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Score: -0.0 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) On Mon, 2021-10-11 at 16:49 +0100, Pádraig Brady wrote: > Well that wouldn't be that useful functionality, > as why not just send a single kill signal in that case. Well with the same argumentation one could say that timeout 0 command doesn’t execute the command at all, since why should one call it with a timeout, when there's anyway none? Also it may make "sense" if the value is configurable e.g. via some user input made before,... And in my opinion, since this behaviour is really quite unexpected (disabling an option, though explicitly setting it), it should at least also be mentioned in the manpage, too. Anyway,.. cheers, Chris. From unknown Sun Jun 22 11:41:16 2025 X-Loop: help-debbugs@gnu.org Subject: bug#51128: timeout --kill-after=0 seems to not send a kill 0s after the initial signal Resent-From: =?UTF-8?Q?P=C3=A1draig?= Brady Original-Sender: "Debbugs-submit" Resent-CC: bug-coreutils@gnu.org Resent-Date: Mon, 11 Oct 2021 20:31:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51128 X-GNU-PR-Package: coreutils X-GNU-PR-Keywords: notabug To: Christoph Anton Mitterer , 51128@debbugs.gnu.org Received: via spool by 51128-submit@debbugs.gnu.org id=B51128.163398420914219 (code B ref 51128); Mon, 11 Oct 2021 20:31:02 +0000 Received: (at 51128) by debbugs.gnu.org; 11 Oct 2021 20:30:09 +0000 Received: from localhost ([127.0.0.1]:32779 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ma1w0-0003hH-NZ for submit@debbugs.gnu.org; Mon, 11 Oct 2021 16:30:08 -0400 Received: from mail-wr1-f48.google.com ([209.85.221.48]:35834) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ma1vx-0003fK-O1 for 51128@debbugs.gnu.org; Mon, 11 Oct 2021 16:30:07 -0400 Received: by mail-wr1-f48.google.com with SMTP id g25so13402407wrb.2 for <51128@debbugs.gnu.org>; Mon, 11 Oct 2021 13:30:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=h/5/5JsKDC8bIdK/UOtijmoAoesCqdn3JWadMjBJa5s=; b=Hnbe8Kuq4whD3aMmF46R0ApmF6X/41Ea9BtX1xfKS6gdkvCivrWJOWGHKlFNyo7f4b CHEuukJVDbCqPtcr2VrpDNnsCDpOj80GVHIHcGNxlIKptEFp94gbGvd0TNuPSLPmOfl9 8ZzkgJHoxWlwzwrcRmd/SQjbdACxLqgLDpVbDbbUb9LXa7EWNBfA9AXZEtSz6fgOf1L3 Ns007QyaJS+klm6Mp7x6696S6W5ZKZ2Ue+QOBM5hPHZVYWtdRmfdea3Mbbm60D9aG7m9 SflfC09gvV5xGr4Giz87ZuwjtAaS5OY4gPppeVaNYctVRh7N+pxEdurN5eUzWPMDEW5l sWig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=h/5/5JsKDC8bIdK/UOtijmoAoesCqdn3JWadMjBJa5s=; b=2BS2NS2FZXnjjhVjdEaj3Uwqjdu/NLcXPRmX+LJfSdtM3RBxKGzUolQmvpz5wqWz28 C/rsXbsdJxS9+DPu1WnAWkhDbimofMjMdViYlbptLzuv+pSi3yBU7RR+riAb0JdWj71z kXa/44KBVM+1s8nmvGBQAng/9Opw8uuTG6iOexkw8wn3IXQDzFvr+nn5beD+McV68tIi qNDZWITwXqG6jRjtFI+fAn5Zbyw4UW9aY5mwA832Z8Xu7VldGESgHrCLL2nEjmJ0Kfwt hTkvLorKgkLO4Uem+GUXzHt3AuOiyLYKjUzZ0iiDg+XvhOz/YVUBF30ZFhvZk0ZWnn4i bbnw== X-Gm-Message-State: AOAM5333n5iA9U0BHVCSWb/eswncb7FanXI8hXcA5V1Wgh5wF3Uzhftz buNAooHGQuShMXJkb+MNdNYVvmVPbTSr9w== X-Google-Smtp-Source: ABdhPJywisU3LFCw0ALMGSH3ymgzjtwR27wKvuEs/4ucVu2Qvd98I0+99HWbccQmuzv9SAg0OHBCPw== X-Received: by 2002:a5d:5989:: with SMTP id n9mr28240752wri.89.1633984199652; Mon, 11 Oct 2021 13:29:59 -0700 (PDT) Received: from localhost.localdomain (86-40-129-104-dynamic.agg2.lod.rsl-rtd.eircom.net. [86.40.129.104]) by smtp.googlemail.com with UTF8SMTPSA id a16sm4057127wrs.30.2021.10.11.13.29.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 11 Oct 2021 13:29:59 -0700 (PDT) References: From: =?UTF-8?Q?P=C3=A1draig?= Brady Message-ID: <84bcb7de-eb32-194b-4823-a217d0ea28bc@draigBrady.com> Date: Mon, 11 Oct 2021 21:29:58 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101 Thunderbird/84.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Score: 0.4 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.6 (/) On 11/10/2021 16:59, Christoph Anton Mitterer wrote: > On Mon, 2021-10-11 at 16:49 +0100, Pádraig Brady wrote: >> Well that wouldn't be that useful functionality, >> as why not just send a single kill signal in that case. > > Well with the same argumentation one could say that timeout 0 command > doesn’t execute the command at all, since why should one call it with a > timeout, when there's anyway none? It's more consistent for a duration of 0 to disable the associated timeout. > Also it may make "sense" if the value is configurable e.g. via some > user input made before,... Exactly. A propagated user setting of 0 should be interpreted as disabling the timeouts rather than the command itself, as timing out immediately is not useful functionality. > And in my opinion, since this behaviour is really quite unexpected > (disabling an option, though explicitly setting it), it should at least > also be mentioned in the manpage, too. The man page mentions this for DURATION (and thus for both timeouts mentioned above): "A duration of 0 disables the associated timeout" thanks, Pádraig From unknown Sun Jun 22 11:41:16 2025 X-Loop: help-debbugs@gnu.org Subject: bug#51128: timeout --kill-after=0 seems to not send a kill 0s after the initial signal Resent-From: Christoph Anton Mitterer Original-Sender: "Debbugs-submit" Resent-CC: bug-coreutils@gnu.org Resent-Date: Tue, 12 Oct 2021 01:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51128 X-GNU-PR-Package: coreutils X-GNU-PR-Keywords: notabug To: =?UTF-8?Q?P=C3=A1draig?= Brady , 51128@debbugs.gnu.org Received: via spool by 51128-submit@debbugs.gnu.org id=B51128.16340017002430 (code B ref 51128); Tue, 12 Oct 2021 01:22:02 +0000 Received: (at 51128) by debbugs.gnu.org; 12 Oct 2021 01:21:40 +0000 Received: from localhost ([127.0.0.1]:33055 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ma6U8-0000d8-Lt for submit@debbugs.gnu.org; Mon, 11 Oct 2021 21:21:40 -0400 Received: from dormouse.elm.relay.mailchannels.net ([23.83.212.50]:46583) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ma6U6-0000d0-Vf for 51128@debbugs.gnu.org; Mon, 11 Oct 2021 21:21:39 -0400 X-Sender-Id: instrampxe0y3a|x-authsender|calestyo@scientia.net Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id D166FE13D3; Tue, 12 Oct 2021 01:21:37 +0000 (UTC) Received: from mailgw-02.dd24.net (unknown [127.0.0.6]) (Authenticated sender: instrampxe0y3a) by relay.mailchannels.net (Postfix) with ESMTPA id 8BD38E1334; Tue, 12 Oct 2021 01:21:36 +0000 (UTC) X-Sender-Id: instrampxe0y3a|x-authsender|calestyo@scientia.net Received: from mailgw-02.dd24.net (mailgw-02.dd24.net [193.46.215.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.99.42.170 (trex/6.4.3); Tue, 12 Oct 2021 01:21:37 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: instrampxe0y3a|x-authsender|calestyo@scientia.net X-MailChannels-Auth-Id: instrampxe0y3a X-Bitter-Coil: 3890de480cf76dac_1634001697479_1587102628 X-MC-Loop-Signature: 1634001697479:4193660495 X-MC-Ingress-Time: 1634001697479 Received: from heisenberg.fritz.box (ppp-188-174-65-9.dynamic.mnet-online.de [188.174.65.9]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: calestyo@scientia.net) by smtp.dd24.net (Postfix) with ESMTPSA id A2DD15FC25; Tue, 12 Oct 2021 01:21:34 +0000 (UTC) Message-ID: <1cbcba38f75983a57e81073f2d55188252b3e8e2.camel@scientia.net> From: Christoph Anton Mitterer Date: Tue, 12 Oct 2021 03:21:34 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.0-2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.2 (/) Hey. One more thing on this, since I've just read through: https://www.gnu.org/software/coreutils/manual/html_node/timeout-invocation.html#timeout-invocation That does IMO *not* document the behaviour: --kill-after=duration says: >This option has no effect if timeout’s duration is 0 which disables >the associated timeout. But that's about the timeout from the command itself (i.e. the 1st non- option argument), isn't it? So it means that if I have: timeout --kill-after=10 0 ./command There won't be a KILL after 10s, since the duration itself is 0. There's no word about that --kill-after=0 disabling the KILL in the duration != 0 case as in: timeout --kill-after=0 10 ./command Cheers, Chris. From unknown Sun Jun 22 11:41:16 2025 X-Loop: help-debbugs@gnu.org Subject: bug#51128: timeout --kill-after=0 seems to not send a kill 0s after the initial signal Resent-From: =?UTF-8?Q?P=C3=A1draig?= Brady Original-Sender: "Debbugs-submit" Resent-CC: bug-coreutils@gnu.org Resent-Date: Tue, 12 Oct 2021 13:54:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51128 X-GNU-PR-Package: coreutils X-GNU-PR-Keywords: notabug To: Christoph Anton Mitterer , 51128@debbugs.gnu.org Received: via spool by 51128-submit@debbugs.gnu.org id=B51128.163404680529923 (code B ref 51128); Tue, 12 Oct 2021 13:54:01 +0000 Received: (at 51128) by debbugs.gnu.org; 12 Oct 2021 13:53:25 +0000 Received: from localhost ([127.0.0.1]:40189 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1maIDd-0007mY-El for submit@debbugs.gnu.org; Tue, 12 Oct 2021 09:53:25 -0400 Received: from mail-wr1-f49.google.com ([209.85.221.49]:43703) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1maIDc-0007m1-86 for 51128@debbugs.gnu.org; Tue, 12 Oct 2021 09:53:24 -0400 Received: by mail-wr1-f49.google.com with SMTP id r7so67271012wrc.10 for <51128@debbugs.gnu.org>; Tue, 12 Oct 2021 06:53:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=dXuXdjGoizv+0tPCLYzUY1InGYlYSodMOGELG4B/oGo=; b=EDOyq+G92JZriy7l/rCLi45mb2nUShL4tHl51QPTJv0HueT1Xc7AeXoQKyxdantsax 3hrL4k4pNVaTQkAlZw0uJxwlaoNGNvR6Qed6jADUmHILbvZT9D6mCE+QEyXbJxIFtd0L +ODWFixnJcrU1uceUJczNsjmSWB2O9h8Mh6WHgFILgAiliYPjGDCwq5ZTMUvilCgY8pQ BRSvr2Gc7mYKJ0lVGEjWktXR5qtTlBcvpzOXtyKt1n+rAvlrkBcP4NEjVHjdKf/VOMnv CMWcnFFKKrS+EwqAo3YF+uYD+eD6R0O5Ob9uc+8DyHTk7BJQn3RUWBGpYg+/Nw5CIztU 4ZvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=dXuXdjGoizv+0tPCLYzUY1InGYlYSodMOGELG4B/oGo=; b=U3gPWV1reedgSyNxKy0lkTQM+59TREApUJbOG9t9wzVuvdO5D5Wn1cbksD68tv/RQB q3oIQKPwD5LuPFFypLFn+QgOmIjzoiC3GlFhUcsMmWQUZksRYRYPBaEHwXiUdcRo95mx WVsVGD9ZPOlmMwjx0f1JfX5D43h4OONZ8FNh9B5vLBRmXxmZt9SvWm/zva8Gscd8vSPK UHXX4XaYOdaBN1uIEi0YukObzyUMq8Yv/AuKj5F7vtKZY8AQZ+l/bSkjulGXQkbEIh77 FTw18oS8n4icbPaA28ipc3A48Lp6gp6YDyesyG20RKtoVmR4v2WkKWE1UxxyXIposkFr IKuw== X-Gm-Message-State: AOAM531zjRNIZMA07699zrS73tWx5lDkJXsR8yNijFjBn+afMTQX5quB fXWzfj1gxnR4PcnRXkm3uBGO0vQLs+7pOA== X-Google-Smtp-Source: ABdhPJyKvJP6ZepCbiJi2FCXfKXUX8o10Ne1cdrQWwpDxZu0oWsZkEPC1H3vtyFymKYMQAQTdSBOcA== X-Received: by 2002:a5d:64a3:: with SMTP id m3mr21627067wrp.364.1634046798367; Tue, 12 Oct 2021 06:53:18 -0700 (PDT) Received: from localhost.localdomain (86-40-129-104-dynamic.agg2.lod.rsl-rtd.eircom.net. [86.40.129.104]) by smtp.googlemail.com with UTF8SMTPSA id k8sm2704505wmr.32.2021.10.12.06.53.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 Oct 2021 06:53:18 -0700 (PDT) References: <1cbcba38f75983a57e81073f2d55188252b3e8e2.camel@scientia.net> From: =?UTF-8?Q?P=C3=A1draig?= Brady Message-ID: <0d089f9e-d02f-51b2-92c5-e82bc2dd60bc@draigBrady.com> Date: Tue, 12 Oct 2021 14:53:17 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101 Thunderbird/84.0 MIME-Version: 1.0 In-Reply-To: <1cbcba38f75983a57e81073f2d55188252b3e8e2.camel@scientia.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Score: 0.4 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.6 (/) On 12/10/2021 02:21, Christoph Anton Mitterer wrote: > Hey. > > One more thing on this, since I've just read through: > https://www.gnu.org/software/coreutils/manual/html_node/timeout-invocation.html#timeout-invocation > > That does IMO *not* document the behaviour: > > --kill-after=duration says: >> This option has no effect if timeout’s duration is 0 which disables >> the associated timeout. > > But that's about the timeout from the command itself (i.e. the 1st non- > option argument), isn't it? > > So it means that if I have: > > timeout --kill-after=10 0 ./command > > There won't be a KILL after 10s, since the duration itself is 0. Right. That is the behavior. > There's no word about that --kill-after=0 disabling the KILL in the > duration != 0 case as in: > timeout --kill-after=0 10 ./command Well DURATIONs of 0 were mentioned a little below that. But it it worth clarifying in the option description itself. So I'll make the following change: -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. cheers, Pádraig From unknown Sun Jun 22 11:41:16 2025 X-Loop: help-debbugs@gnu.org Subject: bug#51128: timeout --kill-after=0 seems to not send a kill 0s after the initial signal Resent-From: Christoph Anton Mitterer Original-Sender: "Debbugs-submit" Resent-CC: bug-coreutils@gnu.org Resent-Date: Tue, 12 Oct 2021 14:04:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51128 X-GNU-PR-Package: coreutils X-GNU-PR-Keywords: notabug To: =?UTF-8?Q?P=C3=A1draig?= Brady , 51128@debbugs.gnu.org Received: via spool by 51128-submit@debbugs.gnu.org id=B51128.16340474191916 (code B ref 51128); Tue, 12 Oct 2021 14:04:01 +0000 Received: (at 51128) by debbugs.gnu.org; 12 Oct 2021 14:03:39 +0000 Received: from localhost ([127.0.0.1]:42947 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1maINW-0000Uq-Sq for submit@debbugs.gnu.org; Tue, 12 Oct 2021 10:03:39 -0400 Received: from olivedrab.birch.relay.mailchannels.net ([23.83.209.135]:12735) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1maINT-0000U3-T1 for 51128@debbugs.gnu.org; Tue, 12 Oct 2021 10:03:38 -0400 X-Sender-Id: instrampxe0y3a|x-authsender|calestyo@scientia.net Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 6F5377C1F9F; Tue, 12 Oct 2021 14:03:33 +0000 (UTC) Received: from mailgw-01.dd24.net (unknown [127.0.0.6]) (Authenticated sender: instrampxe0y3a) by relay.mailchannels.net (Postfix) with ESMTPA id 078EB7C1FF0; Tue, 12 Oct 2021 14:03:31 +0000 (UTC) X-Sender-Id: instrampxe0y3a|x-authsender|calestyo@scientia.net Received: from mailgw-01.dd24.net (mailgw-01.dd24.net [193.46.215.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.99.42.170 (trex/6.4.3); Tue, 12 Oct 2021 14:03:33 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: instrampxe0y3a|x-authsender|calestyo@scientia.net X-MailChannels-Auth-Id: instrampxe0y3a X-Madly-Shelf: 230949707d46f27a_1634047412970_835688393 X-MC-Loop-Signature: 1634047412970:732931401 X-MC-Ingress-Time: 1634047412969 Received: from heisenberg.fritz.box (ppp-188-174-65-9.dynamic.mnet-online.de [188.174.65.9]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: calestyo@scientia.net) by smtp.dd24.net (Postfix) with ESMTPSA id 294FF5FC32; Tue, 12 Oct 2021 14:03:30 +0000 (UTC) Message-ID: <738bd67b3756fbae94a3b7fccebaeaf4f700af1e.camel@scientia.net> From: Christoph Anton Mitterer Date: Tue, 12 Oct 2021 16:03:29 +0200 In-Reply-To: <0d089f9e-d02f-51b2-92c5-e82bc2dd60bc@draigBrady.com> References: <1cbcba38f75983a57e81073f2d55188252b3e8e2.camel@scientia.net> <0d089f9e-d02f-51b2-92c5-e82bc2dd60bc@draigBrady.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.0-2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) 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 ... 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.