ver si el tiempo de ejecución máximo de ejecución es limitante que:
[[email protected] conf]$ ulimit -all
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 16114
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 16114
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Tenga en cuenta que el tamaño de pila, de forma predeterminada, se limita a 10 MiB. Así que para aumentar la cantidad hasta 64 MiB:
[[email protected] conf]$ ulimit -s 64M
-bash: ulimit: 64M: invalid number
[[email protected] conf]$ ulimit -s 65536
[[email protected] conf]$ ulimit -all
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 16114
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 65536
cpu time (seconds, -t) unlimited
max user processes (-u) 16114
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
intentar establecer 'rlimit_stack' después de [Pila Clash] (http://www.openwall.com/lists/oss-security/2017/06/19/1) remediaciones pueden resultar en falla o problemas relacionados. Consulte también Red Hat [Número 1463241] (https://bugzilla.redhat.com/show_bug.cgi?id=1463241) – jww