Thank you Miguel!

This problem has been plaguing us for quite some time.

I just applied your patch and it works.

In my original bug report, I said that FcgidMaxProcessesPerClass works
if it's placed in /etc/apache2/mods-enabled/fcgid.conf but fails if it
also is placed in a VirtualHost directive.

This was incorrect. 

Prior to applying the patch, it seems as though
FcgidMaxProcessesPerClass was ignored no matter where it was placed.

After applying the patch it works both in
/etc/apache2/mods-enabled/fcgid.conf and in a VrtualHost Directive and
when placed in both (with the VirtualHost Directive taking precedence as
expected).

I'd also like to re-iterate the severity of this bug - in a shared
environment controlling the processes that can be launched by a single
virtualhost is critically important to the security of the machine.


Attachment: signature.asc
Description: Digital signature

Reply via email to