Dan Wilder wrote: > In what respect is ulimit superior to well-tuned --max-child-processes? > Recall we're looking at a runaway aggregate load, not a single-process > problem.
A memory leak in perl for is a good way to eat all your memory. You should use OS memory limits for your services. > softlimit appears from the documentation to be mostly a DJB extension > to the ulimit concept. Again, what does this have to do with > excessive aggregate usage? Wrong. softlimit is a program that sets rlimit()s, then runs your program. rlimit() is the same system call your shell calls when you tell it to use its ulimit.
