On 09.11.2011 21:20, William A. Rowe Jr. wrote:
On 11/9/2011 4:53 PM, Jim Jagielski wrote:
Isn't the point different? If someone enables mod_proxy then the
configure script needs to ensure that mod_slotmem is also built…
Reporter suggests that *NOT* loading mod_slotmem_shm caused the server
to start correctly; exactly the inverse of what we would expect.
No, his subject is "module proxy_balancer requires the not automatically
loaded module slotmem_shm" ("the not" and not "to not") and he writes
"Ok, so I simply removed in the installed default httpd.conf the comment
sign within the line
#LoadModule slotmem_shm_module modules/mod_slotmem_shm.so
and as expected now all works. "
I think at the moment there is some tendency to further reduce the
default active LoadModules to a very small module set (see elsethread)
and not activate the other enabled modules. Module set at build time is
only loosely coupled to needed modules at run time.
Jim's suggestion still makes sense: even if we do not activate most
modules by default, some modules have dependencies to other modules and
when a module with such a dependency is build (enabled), we could build
the dependencies automatically as well. Modules with dependencies are at
least mod_ssl (for the session cache), mod_proxy_balancer, and I think
the heartbeat stuff. Probably also ldap auth needing mod_ldap.
On the other hand we now build "most" by default and there are "all" and
"reallyall", *and* we now only activate few modules by default. So most
users should not have a real need to add individual modules to the list
of modules to build.
IMHO the automatic dependency handling in configure is not a must. We
could add after GA if users really need it.
Regards,
Rainer
