i use the same processor directive for several vhosts. i think it is usefull. with your idea possibly clarity in configuration will get lost.
On Tue, 1 Sep 2009 10:53:46 -0300, Marcelo Coelho <[email protected]> wrote: > Hi! > > Why is Processor directive necessary? > > <Processor bob> > User bob > Group www > </Processor> > > Why not to create a configuration like this: > > <VirtualHost X> > <IfModule peruser.c> > <ServerEnvironment> > User bob > Group www > Chroot /var/www/bob > MinProcessors 0 > MinSpareProcessors 3 > MaxProcessors 10 > </ServerEnvironment> > </IfModule> > </VirtualHost> > > Peruser can check for Virtualhosts and create new "Processor" for each > different User/Group/Chroot set. > > If another VirtualHost has the same User/Group/Chroot, it can share > the same processor. _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
