From b5adc0dc6764e955db49508b24e8d63fb0783ee6 Mon Sep 17 00:00:00 2001 From: "Kyle J. McKay" Date: Tue, 19 Apr 2016 22:42:35 -0700 Subject: [PATCH] apache.conf.in: clarify mod_fcgid comments and fix a typo Signed-off-by: Kyle J. McKay --- apache.conf.in | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/apache.conf.in b/apache.conf.in index 7b9b676..3e479e8 100644 --- a/apache.conf.in +++ b/apache.conf.in @@ -293,20 +293,21 @@ - # mod_cgid benefits from some additional config for gitweb.cgi + # mod_fcgid benefits from some additional config for gitweb.cgi # gitweb.cgi has a hard-coded maximum of 100 requests - # and we do not want to give up too soon in case Git is lagging + # and we do not want to give up too soon in case Git is lagging. # Note that adding a 'MaxProcesses ...' option here may be valuable # to limit the maximum number of gitweb.cgi processes that can be # spawned (default is 100) -- perhaps to something much lower such # as 1 or 2 times the number of CPU cores. Also note that in the # unlikely event all the children finish their 100 requests at the - # same time, the server's FcgidSpawnScoreUpLimit should be set - # to at least 3 times the MaxProcesses value chosen to allow them - # all to respawn immediately. It MUST be at least twice the chosen - # MaxProcesses value (assuming FcgidTerminationScore is still the - # default 2) in order to allow any child to respawn at all without - # a delay. + # same time, the server's FcgidSpawnScoreUpLimit (which defaults + # to 10 if not set) should be set to at least 3 times the + # MaxProcesses value chosen to allow them all to respawn + # immediately. FcgidSpawnScoreUpLimit MUST be at least twice the + # chosen MaxProcesses value (assuming FcgidTerminationScore is + # still set to the default 2) in order to allow any child at all to + # respawn immediately in this case without a delay. FcgidCmdOptions @@cgiroot@@/gitweb.cgi \ MaxRequestsPerProcess 100 IOTimeout 300 -- 2.11.4.GIT