Bug#421557: apache2: memory leak addendum

[Colin Wetherbee <cww@denterprises.org>]

Stefan Fritsch wrote:
> Try setting MaxRequestsPerChild to 1000, causing each apache process 
> to be restartet after 1000 requests (the 0 in your settings means 
> unlimited). If that doesn't help, you may want to try 250 or 100.
>
> This will reduce your performance, but it is probably still better 
> than the memory leak.

I changed MaxRequestsPerChild to 500.  As expected, the processes 
restart before they take the system down, but that's only after each 
process reaches about 25% RAM consumption.

Just a quick snapshot of my current 'top' output:

  PID USER      NI  VIRT  RES  SHR S %CPU %MEM    TIME+  P COMMAND
 3740 www-data   0  258m 221m 4544 S    0 22.0   1:13.73 0 apache2
 6696 www-data   0  123m 107m 4968 S    0 10.6   0:30.94 0 apache2
 6705 www-data   0  122m 105m 4976 S    0 10.5   0:30.23 0 apache2
 6697 www-data   0  119m 103m 4972 S    0 10.2   1:09.11 0 apache2
 6694 www-data   0  115m  99m 4976 S    0  9.8   0:27.32 0 apache2
 8339 www-data   0 53016  35m 4960 S    0  3.5   0:06.63 0 apache2
 8387 www-data   0 52416  34m 4840 S    0  3.5   0:06.20 1 apache2

Thanks for the suggestion.  This is a good work-around until the leak is 
fixed.

Colin