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 <sch...@linux-m68k.org> 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, sch...@linux-m68k.org
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
