From: Andreas Schwab <schwab@linux-m68k.org>
To: 70219@debbugs.gnu.org
Cc: celvidge001@gmail.com, brw@brandenwilliams.com
Subject: bug#70219: Bug/Issue with timeout and signals
Date: Sat, 06 Apr 2024 11:06:49 +0200 [thread overview]
Message-ID: <87frvyc11y.fsf@linux-m68k.org> (raw)
In-Reply-To: <29BA5949-B68B-4B9C-BD14-25ADB74475F7@brandenwilliams.com> (Branden R. Williams's message of "Fri, 5 Apr 2024 17:14:54 -0500")
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@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2024-04-06 9:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 15:19 bug#70219: Bug/Issue with timeout and signals Branden R. Williams via GNU coreutils Bug Reports
2024-04-05 21:59 ` Chris Elvidge
2024-04-05 22:14 ` Branden R. Williams via GNU coreutils Bug Reports
2024-04-06 9:06 ` Andreas Schwab [this message]
2024-04-06 12:43 ` Branden R. Williams via GNU coreutils Bug Reports
2024-04-06 14:44 ` Chris Elvidge
2024-04-06 15:50 ` Branden R. Williams via GNU coreutils Bug Reports
2024-04-06 18:30 ` Pádraig Brady
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87frvyc11y.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=70219@debbugs.gnu.org \
--cc=brw@brandenwilliams.com \
--cc=celvidge001@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).