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 ab
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, the
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 dura
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
functio
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
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.
That functionality is not repres
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 pa
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 wor
