FYI - with all LoadModules activated (only one of prefork/worker) Syntax OK,
with both MPM active gives error, as expected (AH00534: httpd: Configuration error: More than one MPM loaded.) On Mon, Feb 27, 2012 at 11:26 PM, Michael Felt <mamf...@gmail.com> wrote: > so, mod_mpm_event... > > I have, with the patch just supplied for build/aix the following mods: > michael@x054:[/opt/httpd/libexec]ls -l *mpm* > -rwxr-xr-x 1 root system 53006 Feb 27 21:38 > mod_mpm_prefork.so > -rwxr-xr-x 1 root system 86085 Feb 27 21:38 mod_mpm_worker.so > michael@x054:[/opt/httpd/libexec]ls -l *event* > ls: 0653-341 The file *event* does not exist. > > What configure option will create the mod_mpm_event part? > > Understood about the shipping part! minimal. > > > On Mon, Feb 27, 2012 at 11:20 PM, Graham Leggett <minf...@sharp.fm> wrote: > >> On 28 Feb 2012, at 12:14 AM, Michael Felt wrote: >> >> > Works, but... >> > the prefork loadmodule line needed to be added manually >> >> AFAIK mod_mpm_event is the default now. >> >> > #LoadModule mpm_worker_module libexec/mod_mpm_worker.so >> > LoadModule mpm_prefork_module libexec/mod_mpm_prefork.so >> > LoadModule unixd_module libexec/mod_unixd.so >> > #LoadModule heartbeat_module libexec/mod_heartbeat.so >> > #LoadModule heartmonitor_module libexec/mod_heartmonitor.so >> > #LoadModule dav_module libexec/mod_dav.so >> > LoadModule status_module libexec/mod_status.so >> > LoadModule autoindex_module libexec/mod_autoindex.so >> > >> > from the looks of it, seemsI need to remove several # to test loading >> all modules :) >> >> To test them, you'll need to remove the commented out lines yes, but >> don't ship a default config file like that. The administrator should only >> enable the modules they need, anything more is a waste of resources on the >> server. In other words, definitely build the modules, but don't switch them >> on by default. >> >> Regards, >> Graham >> -- >> >> >