On 01/09/2009, at 10:59, Stefan Klingner wrote: > i use the same processor directive for several vhosts. i think it is > usefull. with your idea possibly clarity in configuration will get > lost.
But if you use the same User/Group and, possibly, Chroot, why not let peruser care the Processes? Here is my idea: <Processor bob> User bob Group www </Processor> <VirtualHost X> <IfModule peruser.c> # This require a Processor directive ServerEnvironment bob </IfModule> </VirtualHost> <VirtualHost Y> <IfModule peruser.c> # This DOES NOT require a Processor directive, peruser will create a Processor automatically <ServerEnvironment> User john Group www Chroot /var/www/john MinProcessors 0 MinSpareProcessors 3 MaxProcessors 10 </ServerEnvironment> </IfModule> </VirtualHost> <VirtualHost Z> <IfModule peruser.c> # This SHARE the same 'bob' Processor ServerEnvironment bob </IfModule> </VirtualHost> <VirtualHost W> <IfModule peruser.c> # This SHARE the same 'john' Processor, because have the same User/ Group/Chroot <ServerEnvironment> User john Group www Chroot /var/www/john MinProcessors 0 MinSpareProcessors 3 MaxProcessors 10 </ServerEnvironment> </IfModule> </VirtualHost> _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
