Hello users of linuxquestions!

I have a problem that so far I am unable to solve.
For the lab tests I need to run about 3000 instances of a single daemon(yes!). The daemon does not consume much memory, about 20% when 2000 instances are present. However when I reach 3000 it just says -bash: fork: Cannot allocate memory. The memory aint a problem for the server it has 32gb ram.
ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 128338
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 100000
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 128338
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

anyone has ideas on how to increase the quota of daemon instances?

Thank you!

After starting the daemons, does
show them?
If yes they occupy resources in bash i.e. are not fully daemonized.

you may try to use strace to check what was the real problem.

if this is true, then could help?

jobs return nothing, to spawn copies I am using something like this in python

def startDae(config_path):
CMD = "testlab05 -f %s" % config_path
print '\n[>]', CMD
os.system(CMD)

update:
looks like I can't run it fully in the background, after doing ./testlabs05 -f config.xml&
it does not fully go into the background and jobs -l still returns nothing.
is there a way to run it as a "full time" job in a background without actually making modifications to a code?

Welcome to LQ!!! Swap ok? Look into tools like:
free; htop; vmstat; tricky ps switches, smem ...
From this web-search: linux memory usage monitor per process details
(add Goo's intitle: or DDG's t: to memory; no space after colon)

Let us know... For a LinuxPHD, use sysdig.com
(Which distro? Is sysdig in your repos?)

nohup? https://stackoverflow.com/questions/...r-i-logout-ssh
Idk; DDGoo sure does, given the 'right' keywords!!!

its not the python script that needs the upkeep but to daemonise the process of a binary.
nohup and & doesn't help.
I am sorry that it has gone to this simpler matter, will welcome all the help!
Thank's ahead.