Once upon a time, Nick Jennings <[EMAIL PROTECTED]> said: > 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.
/etc/security/limits.conf applies to logins, and user "apache" isn't logging in. The /proc limits apply to the total kernel open files count, not the per-process limit. > 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? Put it in /etc/sysconfig/httpd. One thing to note: when I've hit this before and raised the limit, PHP got unhappy. I didn't investigate why (I worked around it), but it may be something to keep an eye out for if you are running PHP. -- Chris Adams <[EMAIL PROTECTED]> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
