Nick Jennings wrote:
Hi Everyone,
Thanks for your responses. I wanted to follow up because I *think* I
may have resolved the issue, not 100% sure yet, the problem could still
come back in a few months. However, even though it may have been
resolved, it doesn't really make sense to me as to why this way, and
none of the others. So I wanted to run it by here to see if anyone has
any insight.
The fix was to add a line to the /etc/init.d/httpd script.
ulimit -n 8000
A more robust place to do that is /etc/sysconfig/httpd. Many RH/F
packages have configuration information set there, and Debian does
likewise in /etc/defaults/
This raises the FD limit for the apache user right before the httpd
process is spawned.
So why didn't all the other ways I tried have any effect? This was
supposed to happen when I raised the limits in the
/etc/security/limits.conf right? Also, when I upped the limits directly
in the proc filesystem.
I'm glad it's fixed, but confused as to why nothing else seemed to work.
Also, the next time my /etc/init.d/httpd file is overwritten by a system
update the fix goes away. So how do I fix this the real way, without
hacking the init script?
Like I said.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
