On Thu, Oct 29, 2020 at 01:57:33PM +0100, felix wrote:
> > I can't reproduce this using the following stripped-down reproducer:
Sorry to insist, but... This is not easy because not constant.
For this, I wrote a little script tested on several host, then searching
for installation that was not
On Wed, Oct 28, 2020 at 09:23:09AM -0400, Chet Ramey wrote:
>
> I can't reproduce this using the following stripped-down reproducer:
> trap 'echo $f ; exit' SIGINT
>
> for f in {1..1}; do
> read -t .01 v
> if [ $? -ne 142 ]; then
> echo $f: $?
> fi
> done
On 10/28/20 7:06 AM, felix wrote:
> Bash Version: 5.1
> Patch Level: 0
> Release Status: rc1
>
> Description:
> Trying to see limits of timeout with `read -t`, I encounter strange
> and unconstant result: sometime `read -t .01` don't consider
> timeout, when running fastly
Configuration Information:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security
uname output: Linux medium 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29)
x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu
Bash Version: 5.1
Patch
