Don't forget to raise:
/proc/sys/fs/inode-max (should be ~4 times file-max since sockets
count against these too)
/proc/sys/net/ipv4/ip_local_port_range (I like 32768-61000)
Furthermore, the file descriptor limit of 1024 only applies to earlier 2.2
kernels; what kernel are you using? Alan Cox changed the per-process
limit to about 32k descriptors in 2.2.11 or so, as long as the
system's file limit was set high enough...
Further, ulimit limits normal users to 1024 by default; root is not
limited in the regard, and can permit users a higher "hard" ulimit -n.
Retry with the above numbers tuned.
This should allow you to bypass the leak Ryan describes.
Victor
--
Victor J. Orlikowski
======================
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
- Re: thread locking within apr file io William A. Rowe, Jr.
- Re: thread locking within apr file io Greg Ames
- Re: thread locking within apr file io William A. Rowe, Jr.
- Re: thread locking within apr file io Chuck Murcko
- Re: thread locking within apr file io rbb
- Re: thread locking within apr file io Greg Ames
- Re: thread locking within apr file io Paul J. Reder
- Re: thread locking within apr file io Justin Erenkrantz
- Re: thread locking within apr file io Justin Erenkrantz
- Re: thread locking within apr file i... rbb
- Re: thread locking within apr file i... Victor J. Orlikowski
- Re: thread locking within apr file i... David Reid
- Re: thread locking within apr file io Greg Ames
- Re: thread locking within apr file io Paul J. Reder
- Re: thread locking within apr file io Greg Ames
- Re: thread locking within apr file i... Greg Ames
- Re: thread locking within apr file io Paul J. Reder
- Re: thread locking within apr file io Bill Stoddard
- Re: thread locking within apr file i... Paul J. Reder
- Re: thread locking within apr file io Greg Stein
- Re: thread locking within apr file io Chuck Murcko
