Unfortunately this does not count the number of PHP processes, and thus is not really the smart way to do this.
The correct way would be to keep tally of the processes in Apache and match this against nproc value. Aki Tuomi On Sun, Oct 27, 2013 at 09:15:53PM -0400, Webmaster@askapache wrote: > I did recently find out a super cheap method of getting the currently running > # of procs by doing a stat on the /proc directory.. The hard links is the # > of procs. > > > On Oct 27, 2013, at 8:03 PM, "Webmaster@askapache" > > <[email protected]> wrote: > > > > Well I for one would love that feature. > > > >> On Oct 27, 2013, at 6:57 PM, Lance <[email protected]> wrote: > >> > >> I hope someone can help me with this. I've been trying to add two new > >> options to mod_suphp, basically suPHP_NProc and suPHP_NProc_Error I'm just > >> not good enough with C to get it all working correctly. > >> > >> I was wanting suPHP_NProc to set the maximum number of permitted PHP > >> processes. (I know Apache has RLimitNProc, but I was just looking to add > >> something that is suPHP specific.) > >> > >> The other option suPHP_NProc_Error I was wanting to add to let you > >> override the error code that is returned when the process limit is reached > >> instead of returning a generic 500 error code (Internal Server Error). > >> > >> Any help with this would be appreciated. > >> _______________________________________________ > >> suPHP mailing list > >> [email protected] > >> https://lists.marsching.com/mailman/listinfo/suphp > > _______________________________________________ > suPHP mailing list > [email protected] > https://lists.marsching.com/mailman/listinfo/suphp >
signature.asc
Description: Digital signature
_______________________________________________ suPHP mailing list [email protected] https://lists.marsching.com/mailman/listinfo/suphp
