On 13/03/12 18:02, Arno Töll wrote:
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.
Yup, i sure can change it. Its and editable conf file! :)
My question was about the reasoning behind changing it to 0 by default.
What are the benefits over using 10000 (the apache default).
I can tell you one contra... servers trusting third party software
(thats it, as many servers as ive come across this far) crashing over a bug.
My intention is not to flame, really. I see the parameter as safety net,
and i wonder why was it was removed, thats all... maybe there is a logic
i cant comprehend...
To tell you the truth i never worried about the parameter much. I've
never admin servers that busy to make a difference... I just worried
about it when my server crashed lately... :/
greets!
aL
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
