Re: why MaxRequestsPerChild is defaulted to 0 in apache2 prefork default conf?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On 13.03.2012 11:51, Alberto Fuentes wrote:
> It does not look like a sane default from my point of view...
The actual problem is not this setting, but the leaking process, then.
That's always a bug which needs to be fixed. MaxRequestsPerChild can
mitigate this problem, but it is not a solution of course.
Pretending we trust third party modules to do proper housekeeping
MaxRequestsPerChild 0 is feasible. If it is not for you, you can
always change it - that's what configuration files are for.
- --
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJPX32OAAoJEMcrUe6dgPNtZJcP/A6sS8OxR4jNs1XIHNgLDmyZ
XeCRBawcVQR53uMte/fwTWy/dCIT9aYjsNr+Z9FklUdyKddIY9ltMVtnjy5mFQL/
iM5rAUAIlPV7FQruQ+9AlG/IHrTzQgVL1Ri42XDCEc84tlRPMyOoccyDvY+YL0Ec
Lu2/Qoa6AkkYmGTAh+MjRuhjWs+qmilCjS7RBShAT4ac+h9EfHcpe0I89e0CXEqR
6yw4kpX4C9LbG3qJyoDBuyiRPODtRBSnMOAILFqDVATXrYU0JsGwiYVnorBRbvIc
9V4WBnV8QA8ZeZZe5Qlsinv/ejj9uqLgHWhaadkQrYOOSKP1iSc8DGxF9ZMR/tMA
J9r39kvyuH9uxlVqvkpF4TjyqFA1XPuJPJBADmbMsyuw3mDMopYwJUQzhFTHTGpl
dS3I3XRRwnz7ZTTcsg16xBNmgFu8BmNJyTe1igY/ONjaHVWlMoU/nRM/AS/mSCyO
Zdv/EU/C7T52VIjpdo99iWrMl14nAoFZPz+QEIM82B0shFraeOEl6SHiFBiSQ5gU
4UcHHAYpJdZ/tWGW/hMT5V3htK8IO3zK6JelgT/08BCA2+OQ49VGYKkQxIdoAkcV
Q3WdkQAg8nrAhhLf/hTycnjNg81M/XFKsgc5e7nwQIa2oBEnl6OpS4zU619MJ1dh
NwvV//84RbdKwvUo/v9X
=3KYx
-----END PGP SIGNATURE-----
Reply to: