From: Wolfgang Apolinarski <wolfgang.apolinarski@googlemail.com>
To: development@lists.ipfire.org
Subject: Apache 2.4 and apr patches
Date: Wed, 23 Aug 2017 21:38:03 +0200 [thread overview]
Message-ID: <001c01d31c47$569d4700$03d7d500$@googlemail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
Hi!
I updated the patches and made some adjustments, please check and test the new versions!
Regarding the Apache 2.4 configuration, MaxRequestWorkers is the new MaxClients (it limits the total number of threads available), ThreadsPerChild standard value is 25, 16 should be enough for ipfire, since MaxRequestWorkers is computed by ServerLimit (default: 16) * ThreadsPerChild. MaxSpareThreads must be at least the sum of MinSpareThreads+ThreadsPerChild.
This should be very similar to the existing prefork configuration. If possible, please test it thoroughly.
Best regards,
Wolfgang
reply other threads:[~2017-08-23 19:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001c01d31c47$569d4700$03d7d500$@googlemail.com' \
--to=wolfgang.apolinarski@googlemail.com \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox