https://bz.apache.org/bugzilla/show_bug.cgi?id=66217
--- Comment #7 from Eric Covener <[email protected]> --- (In reply to Aleksandr from comment #4) > (In reply to Eric Covener from comment #3) > > That's not how the manual describes it. I think in that case it would not > > add much to just setting ulimits in the environment that starts Apache. > > But technically, the is reading kernel's rlimits: > > AP_DECLARE(void) ap_unixd_set_rlimit(cmd_parms *cmd, struct rlimit **plimit, > const char *arg, > const char * arg2, int type) > > .... > *plimit = (struct rlimit *)apr_pcalloc(cmd->pool, sizeof(**plimit)); > limit = *plimit; > > then adjusts: > > limit->rlim_max = max > > So I would guess either this variable is supposed to either be picked up by > kernel from *plimit, or set by setrlimit, isn't it? Again, I'm not a > C/kernel developer but for some reason, RLimitMEM handler calls > ap_unixd_set_rlimit AIUI the values are read by mod_cgi/mod_cgid and passed down to the code that forks/execs CGI scripts (apr_procattr_limit_set). Nothing happens in-place for the httpd processes """ This applies to processes forked from Apache httpd children servicing requests, not the Apache httpd children themselves. This includes CGI scripts and SSI exec commands, but not any processes forked from the Apache httpd parent, such as piped logs. """ -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
