16 Dec
2014
16 Dec
'14
2:03 p.m.
On 16/12/14 12:43, Øyvind Kolbu wrote:
On 16.12.2014 12:23, Daniel-Constantin Mierla wrote:
Then, to clarify properly, have you
ever got it started with higher
debug level and memory operations printed to syslog?
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Those parameters are not about number of
children, but how fast to do
some operations. I had troubles with selinux, because it has some
obscure limits on how fast new connections can be opened. TLS is
using quite some memory, I wonder if selinux have a limit on how fast
one process keeps allocating... Have you tried with children=1?
Tried now with:
fork_delay=50000
modinit_delay=100000
mem_safety=1
fork=yes
children=1
Now the usual error on start, but no crash.
Also tried disabling selinux. Did not help.