[In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
Synopsis: The RLimit* directives are bizarre Comment-Added-By: marc Comment-Added-When: Thu Dec 10 12:02:38 PST 1998 Comment-Added: No, they are the way they are on purpose. The idea is that user written code shouldn't have certain limits, but it doesn't necessarily make sense to impose those same limits on Apache processes. This should be better documented and there should be a way to put limits on the Apache child processes. For memory limits, you can just do the ulimits before starting the parent, but that doesn't work for CPU limits since then the parent could eventually be killed. I think a module that can set the ulimits when each child starts is probably the easiest solution; I probably need one for something else anyway, so I'll look at making one and perhaps including it with Apache.
