Re: Increase default nofile ulimit

2014-06-15 Thread Robie Basak
On Mon, Jun 09, 2014 at 12:10:40PM +0100, Robie Basak wrote: > AIUI, there are security implications for raising this limit system-wide > by default, since applications that use select() are often broken and > will become vulnerable with a higher limit. > > See > https://lists.ubuntu.com/archives/

Re: Increase default nofile ulimit

2014-06-09 Thread John Moser
On 06/09/2014 07:10 AM, Robie Basak wrote: > AIUI, there are security implications for raising this limit system-wide > by default, since applications that use select() are often broken and > will become vulnerable with a higher limit. > > See > https://lists.ubuntu.com/archives/ubuntu-devel/2010-S

Re: Increase default nofile ulimit

2014-06-09 Thread Robie Basak
AIUI, there are security implications for raising this limit system-wide by default, since applications that use select() are often broken and will become vulnerable with a higher limit. See https://lists.ubuntu.com/archives/ubuntu-devel/2010-September/031446.html for the previous discussion. s

Increase default nofile ulimit

2014-06-08 Thread John Moser
The default nofile ulimit is 1024 soft, 4096 hard. As you know, the soft limit is *the* limit. A hard limit specifies how high a process may increase the ulimit; many processes don't attempt this. Apache on CentOS 6, for example, will easily run over the 1024 soft limit after just 55 server side