Re: How to get nginx to see higher limit for file descriptors?

From this warning it seems that you are telling Nginx to use 4096
worker processes!! Are you sure?

Yes indeed. This is intentional. Here is the relevant section:

events {
worker_connections 4096;
}

From a shell, if I do “ulimit -n 65536” and then launch nginx the
warning goes away. But if I have my init.d start nginx then it
complains that the limit is 1024.

So what I am looking for is the necessary steps to set the ulimit -n to
65536 at the system wide level so that nginx sees this higher limit when
launched form init.d. I thought I had done that properly as I listed
out in detail in my last message on the subject, but apparently that is
not sufficient. Thanks.

  ____________________________________________________________________________________

Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

On Friday 25 April 2008, Rt Ibmer wrote:

So what I am looking for is the necessary steps to set the ulimit -n to
65536 at the system wide level so that nginx sees this higher limit when
launched form init.d. I thought I had done that properly as I listed out
in detail in my last message on the subject, but apparently that is not
sufficient. Thanks.

http://wiki.codemongers.com/NginxMainModule#worker_rlimit_nofile

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs