[syslog-ng] Fixed number fd-limit doesn't scale

Balazs Scheidler bazsi at balabit.hu
Fri Jan 23 13:22:33 CET 2009


On Fri, 2009-01-23 at 12:49 +0100, Corinna Vinschen wrote:
> On Jan 22 21:06, Balazs Scheidler wrote:
> > On Mon, 2009-01-19 at 11:42 +0100, Corinna Vinschen wrote:
> > > The above patch sets limit.rlim_cur to limit.rlim_max and limit.rlim_max
> > > is the maximum a process can get anyway.  On my Linux box, the default
> > > values for rlim_cur is 1024 and rlim_max is 8192.  So the above code
> > > raises the current limit to the max of 8192.  That's what you want,
> > > right?
> > 
> > On my Linux box, getrlimit() returns 1024 even for rlim_max:
> > 
> > getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=1024}) = 0
> > 
> > This is probably a system setting and the difference is because I run
> > Ubuntu and you probably run RedHat. 
> > 
> > # ulimit -H -n 8192
> > 
> > getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=8*1024}) = 0
> > 
> > But it is certainly possible to raise this limit even further than 1024
> > or 8192, I've run programs with limits over 65536 in some cases and on
> > Linux, it works well. Of course it requires superuser privileges, but
> > this code runs as root during startup, even if you specify -u/-g
> > options.
> > 
> > Do you have another recommendation apart from using __CYGWIN__ ?
> 
> Well, no.  If you use it, please set the default to 256 on Cygwin.

I've just pushed a patch to do this.

-- 
Bazsi



More information about the syslog-ng mailing list