I'm still unsure with the -o flag didn't work for me, but I was able to set a limit increase on the upstart init file that starts runsvdir. This seems to be working as expected now.
Thanks. On Fri, May 13, 2016 at 10:57 AM, Aaron Cline <aaron.cl...@gmail.com> wrote: > Hello: > > We have servers that use runit to manage our deployed processes (tomcat > and logstash). We had some issues with having too many open files in our > tomcat processes and so we're trying to increase the limit. I'm using the > /proc/<PID>/limits file to check to make sure the limits are increased. > > We've tried increasing the limits in /etc/security/limits.conf, but that > didn't seem to work for the runit processes. Then I found the chpst man > page and started adding the -o option with a higher open files number > there, but that also doesn't seem to increase the number for neither the > tomcat or logstash process according to the proc filesystem. > > Is there some other gotcha I'm missing here? > > I'm using runit 2.1.2. > > Thanks for any help. > > Aaron >
