I was surprised to discover this:
$ time ./bash -c : $(seq 1000)
0.01s wall 0.00s user 0.00s system
$ time ./bash -c : $(seq 1)
0.40s wall 0.39s user 0.00s system
$ time ./bash -c : $(seq 2)
1.32s wall 1.31s user 0.01s system
$ time ./bash -c : $(seq 4)
4.57s wall 4.54s user 0.02s
On Sat, Feb 3, 2018 at 4:55 PM, Chet Ramey wrote:
> On 2/3/18 12:20 PM, Blake Burkhart wrote:
> > Within rbash, attempting to open a socket using /dev/tcp with <> fails as
> > expected due to output redirection being disabled:
> >
> > rbash-4.4$ exec
On 2/3/18 12:20 PM, Blake Burkhart wrote:
> Within rbash, attempting to open a socket using /dev/tcp with <> fails as
> expected due to output redirection being disabled:
>
> rbash-4.4$ exec 3<>/dev/tcp/www.gnu.org/80
> rbash: /dev/tcp/www.gnu.org/80: restricted: cannot redirect output
>
>
Within rbash, attempting to open a socket using /dev/tcp with <> fails as
expected due to output redirection being disabled:
rbash-4.4$ exec 3<>/dev/tcp/www.gnu.org/80
rbash: /dev/tcp/www.gnu.org/80: restricted: cannot redirect output
However, I noticed that output redirection is not disabled on
Hi,
I'd like to second this feature request.
As Daniel mentioned, the biggest problem with the current single
variable approach that it's hardly usable due to lack of coordination
between distributions as well as apps that wish to modify
PROMPT_COMMAND. Let's look at it at more details.
There
Hi,
I can reproduce this problem with 4.4.12 on Ubuntu Artful (in
gnome-terminal, xterm, urxvt - so it doesn't seem to matter). I cannot
reproduce with devel bash.
(Sorry if this email doesn't show up nicely in the thread index, I
have no clue how to properly reply to an email just by seeing it