current apachectl:
#
# Set this variable to a command that increases the maximum
# number of file descriptors allowed per child process. This is
# critical for configurations that use many file descriptors,
# such as mass vhosting, or a multithreaded server.
ULIMIT_MAX_FILES="ulimit -S -n `ulimit -H -n`"
# -------------------- --------------------
# |||||||||||||||||||| END CONFIGURATION SECTION ||||||||||||||||||||
# Set the maximum number of file descriptors allowed per child process.
if [ "x$ULIMIT_MAX_FILES" != "x" ] ; then
$ULIMIT_MAX_FILES
fi
Should we do the same for threads/processes? I was going to propose
this for some kind of startup code, and realized there was some old
precedent. The downside is that we don't yet know MaxClients is
large, as we could in code.
On Tue, Nov 12, 2013 at 3:00 PM, Eric Covener <cove...@gmail.com> wrote:
>>
>> IMHO this explains it as limits.conf is a configuration file for PAM. If you
>> don't use
>> any PAM methods (haven't worked out which would be needed) in the code the
>> limits will not
>> be applied after setuid. Of course pam_limits.so need to be configured for
>> session for your app
>> as well.
>
> Ah, that helps - -thanks!
--
Eric Covener
cove...@gmail.com
