No, it doesn't. We `ulimit -n 10240` in our start script and it works just
fine.
Where do you set the raised limit? Apparently upstart ignores limits.conf
and you need to set this in your job definition:
http://bryanmarty.com/2012/02/10/setting-nofile-limit-upstart/
/MR
On Wed, Nov 30, 2016 at
Here is why?
root@ovrh0301:/home/envi# 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) 772117
max locked memory (kbytes, -
