bug#70219: Bug/Issue with timeout and signals

2024-04-05 Thread Branden R. Williams
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

bug#70219: Bug/Issue with timeout and signals

2024-04-05 Thread Branden R. Williams
suggesting using a default SIGTERM if the -k or --kill-after= is passed so that the duration is the actual argument that follows. If you wanted to alter the signal, that’s where the -s flag comes in. > On Apr 5, 2024, at 4:59 PM, Chris Elvidge wrote: > > > > On 05/04/2024 at 1

bug#70219: Bug/Issue with timeout and signals

2024-04-06 Thread Branden R. Williams
ct. > > > 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 beca

bug#70219: Bug/Issue with timeout and signals

2024-04-06 Thread Branden R. Williams
duration that the manpage and --help tell you to pass. Regards, B > On Apr 6, 2024, at 4:06 AM, Andreas Schwab wrote: > > On Apr 05 2024, "Branden R. Williams" via GNU coreutils Bug Reports wrote: > >> That’s not an accurate representation of what the command act