I tried to come up with a workaround, but I couldn't find any.
Basically what I do:
env -i bash --norc --noprofile
This gives me an interactive shell, with a very clean environment (even
no PATH), that does not contain system specify "surprises".
This works.
But what I really want is to
On Sat, Jan 06, 2018 at 01:42:25AM +0200, Alfred Baroti wrote:
> Hi,
> I found this from long long time ago.
> Is this a serious bug?
[...]
This is not a serious bug at all. It's just a memory allocation failure.
> [root@n1x ~]#su nix
> nix@n1x:/root$ printf "%s\n"
> {{a..z},{A..Z},{0..9}}{{a..z}
Eduardo A. Bustamante López wrote:
> Alfred Baroti wrote:
> > Hi,
> > I found this from long long time ago.
> > Is this a serious bug?
> [...]
>
> This is not a serious bug at all. It's just a memory allocation failure.
Agreed. Not a bug at all.
> You can see that the brk() system call actually
On Sat, Jan 06, 2018 at 09:13:17PM -0700, Bob Proulx wrote:
> > You can see that the brk() system call actually succeeds.
>
> If you are running under the Linux kernel in the default configuration
> then memory overcommit is enabled.
>
> $ sysctl vm.overcommit_memory
>
> With overcommit enable
