From the docu: FcgidIdleTimeout , Application processes which have not
handled a request for this period of time will be terminated, if the
number of processses for the class exceeds FcgidMinProcessesPerClass.
The FcgidMinProcessesPerClass is default (3), so not exit with two
processes should be ok. had read the docu before.
Not tested for more processes (yet)
Left to have attention: Stopping Apache does not exit/kill the running
processes, not sure it is regression
On Sunday 06/10/2013 at 12:13, Steffen wrote:
Maybe other testers can have a look:
Tested with 2.2.25 Win32.
Stopping Apache does not exit/kill the running processes
Processes with FcgidIdleTimeout more then 300 (default) is still
there, a process has 2016 seconds and stays with 20 accesses and it
does not exit/kill:
PidActiveIdleAccessesState15682357201620Ready596023594036Ready
Ok exit, when processes reach:
FcgidInitialEnv PHP_FCGI_MAX_REQUESTS 1000
FcgidMaxRequestsPerProcess 1000
On Friday 04/10/2013 at 23:16, Jeff Trawick wrote:
Tarballs/zips are at http://httpd.apache.org/dev/dist/mod_fcgid/
Shortcut to changes:
http://httpd.apache.org/dev/dist/mod_fcgid/CHANGES-FCGID
The difference with 2.3.8 is that one of the regressions found in
2.3.8 has been reverted and and the other has been fixed.
+/-1
[ ] Release mod_fcgid 2.3.9 as GA
I'll hold the vote open for 72 hours unless something out of the
ordinary occurs.
Thanks in advance for testing!
--
Born in Roswell... married an alien...
http://emptyhammock.com/
