In an attempt to address the lsof problem we flagged in this thread --
http://is.gd/CqD0 -- I've been rifling through my httpd.conf looking for
unnecessary modules I can trim out of my httpd processes.
So far this has basically amounted to me eliminating things like mod_cgi,
mod_vhost_alias, mod
pen files, used for each
> page served.
>
> Mick
>
> -Original Message-
> From: palewire [mailto:ben.we...@gmail.com]
> Sent: 20 May 2009 23:55
> To: users@httpd.apache.org
> Subject: Re: [us...@httpd] What is the best way to handle "too many open
> fi
Sean --
Thanks for the lengthy and thoughtful response.
What I've found most successful so far is hunting through the lsof | grep
http and finding ways to eliminate unnecessary files. And I'm also exploring
an expansion of my production resources to include a second tier machine
that houses the
awarnier wrote:
>
> I could not say that. Only you really know which modules you load with
> the LoadModule directives, and which ones you really need for your
> configuration and applications.
>
> Taking into account that libraries (stuff like the
> /usr/lib/libkrb5.so.3.3 for instance) ar
For what it's worth, I've taken the additional step of running `lsof |grep
httpd > http.dump` and posting it online. My understanding is that this
shows all of the httpd open files that are adding up to my high totals.
http://gist.github.com/114943
If anyone who understands this better than me h
Igor Cicimov wrote:
>
> Have you considered increasing the open files limit? Have a look at the
> ulimit command. The default is sometimes not enough.
>
> Cheers,
>
> Igor
>
Thx for your time and attention.
I have considered fiddling with the open files liimits, but frankly before I
go too