wait doesn't wait for procsubs unless it's passed the pid as an argument
$ time { : <(sleep 1); wait; }
real: 0m0.002s, user: 0m0.000s, sys: 0m0.003s
$ time { : <(sleep 1); wait $!; }
real: 0m1.011s, user: 0m0.003s, sys: 0m0.007s
is this intended or is it a bug?
this also means it's impossible t
On 10/7/16 12:54 PM, Eric W. Robertson wrote:
> While building and testing GNU Bash 4.4 on OpenVMS, the GNU Bash test
> script issued the following difference between OpenVMS Bash produced output
> and reference output for the test sub-script tests/exp8.sub (lines 28 - 31)
>
> unset array
> declar
This was reproduced on Ubuntu 14.04 in VirtualBox. But I guess that issue
exists on other distros.
It is very timing dependent issue. Using Gdb or strace easily hide it.
Our kernel has custom LSM. so open() syscall timing might be little bit
changed some time. It has same effect as on slow devices
On 10/5/16 9:04 AM, Andriy Prystupa wrote:
> Hi,
>
>
> Error:
>
> */bash: /etc/bash.bashrc: Interrupted system call /*
>
> Reproduced on bash-4.4 via *gnome-terminal* or *terminator* terminal.
This is interesting. On what version of Unix/Linux is open(2) on a regular
file from the local fil
2016-10-08 17:33:00 +0200, Conrad Hoffmann:
[...]
> $ TEST=5; echo $((--TEST+++3)) # outputs 7
>
> However, due to the documented operator precedence, I would have
> expected that expression to be equal to:
>
> $ TEST=5; echo $((--(TEST++)+3)) # outputs 8
>
> Instead, though, it seems to be
