> And also when > the process dies how do I make sure it releases the resource it had > acquired.
>>This will happen automatically for most resources. Is there some >>particular problem you are having? Thanks for the update.My observation even after using MaxRequestPerChild param setting to non zero.What I see the process gets killed but there is no increase in free memory. Another observation is RSS size of Apache process is around 15MB but free -m gives much more resource occupied considering only Apache is running in the particular box. Regards -A On Fri, Mar 21, 2008 at 12:47 AM, Joshua Slive <[EMAIL PROTECTED]> wrote: > On Wed, Mar 19, 2008 at 5:11 PM, Arnab Ganguly <[EMAIL PROTECTED]> > wrote: > > Hi All, > > How do I restrain Apache process to grow to a certain limit? > > There is no function internal to apache to do that. You can probably > use ulimit in the script that starts apache. Of course, the processes > will die very ungracefully if they hit the OS limit. > > You may want to look at MaxRequestsPerChild if you have buggy/leaky > modules. > > > And also when > > the process dies how do I make sure it releases the resource it had > > acquired. > > This will happen automatically for most resources. Is there some > particular problem you are having? > > > What is the impact of the parameter MaxMemFree ? > > This won't do very much in normal use. Apache will try to free memory > back to the OS if it winds up with a bunch of unoccupied memory. The > OS may or may not reuse it. And in a busy server, it is unlikely that > particular processes will wind up allocating a bunch of memory and > then later not need it. > > Joshua. > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: [EMAIL PROTECTED] > " from the digest: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
