We've been doing that too. We just ran up against a case where it's not an option - a very large deployment that can't realistically accommodate the memory requirements of so many forked workers. Threaded workers, no problem.
More distributions appear to be picking MPM-worker as their default behavior, so this seems to be a good opportunity to make our filters more robust. -- Jorj On Oct 29, 2014, at 9:10 AM, Liam Hoekenga <li...@umich.edu> wrote: > We just tell people to use prefork. > > Liam > > On Wed, Oct 29, 2014 at 8:56 AM, Jorj Bauer <j...@isc.upenn.edu> wrote: > Hi all, > > Over the past week, I've been working on multi-threaded support for the > Apache2 filter. Is anyone else running with the worker or event MPMs that > also has thread-safe patches for the filters? > > Right now the patches are rough, but functional; quite a bit of cleanup is > required. If other folks have similar thread-safe patches I'd be interested > in trying to pull them together in to one coherent patch. > > -- Jorj > > > ------------------------------------------------------------------------------ > _______________________________________________ > Cosign-discuss mailing list > Cosign-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/cosign-discuss > ------------------------------------------------------------------------------ _______________________________________________ Cosign-discuss mailing list Cosign-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cosign-discuss
