|
From: | John McKown |
Subject: | Re: Bash monopolizing or eating the RAM MEMORY |
Date: | Mon, 20 Mar 2017 11:59:07 -0500 |
Configuration Information [Automatically generated, do not change]:Machine: x86_64OS: linux-gnuCompiler: gccCompilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/ locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -D_GNU_SOURCE -DRECYCLES_PIDS -DDEFAULT_PATH_VALUE='/usr/ local/bin:/usr/bin' -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic uname output: Linux SPFBL-POC-CENTOS-7 3.10.0-514.2.2.el7.x86_64 #1 SMP Tue Dec 6 23:06:41 UTC 2016 x86_64 x86_64 x86_64 GNU/LinuxMachine Type: x86_64-redhat-linux-gnuBash Version: 4.2Patch Level: 46Release Status: releaseDescription:Hello bash crew.My name is Noilson Caio and i assume that there is something weird/strange in bash. I'm working with huge folder structures and a lot of files every day and the best way to describe the 'problem' is using a example.Example task: Build a folder structure using 0-9 at 2 levelsSomething like that:
[Prev in Thread] | Current Thread | [Next in Thread] |