On Jan 16, 2009, at 2:36 PM, Aftab Alam - IT wrote:
Can u let me is this a error or a memory problem.
Something in your server is leaking memory: perhaps there is a module active that doesn't correctly clean up after itself. Setting the MaxRequestsPerChild to a non-zero value (but not too low, the ten thousand Eric suggests is a good starting point) will help you by causing child processes to terminate before they get too big.
Strictly spoken, this is a programming error, somewhere, but these can be very hard to track down. This is why MaxRequestsPerChild is there.
S. -- Sander Temme sctemme@xxxxxxxxxx PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
|