httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <rainer.j...@kippdata.de>
Subject Re: undesired modules loading
Date Sat, 18 Aug 2012 20:45:41 GMT
Hi Roy,

On 18.08.2012 22:07, Roy T. Fielding wrote:
> I built 2.4.3 with the options
>
> ./configure \
>              --prefix=$tdir \
>              --with-apr=$adir \
>              --with-apr-util=$adir \
>              --without-ssl \
>              --without-crypto \
>              --disable-cache \
>              --without-distcache \
>              --enable-maintainer-mode
                ^^^^^^^^^^^^^^^^^^^^^^^^

see below

> but then noticed in the error_log some garbage about
>
> [Sat Aug 18 12:26:23.182875 2012] [ssl:warn] [pid 82399:tid 140735220779360] AH01873:
Init: Session Cache is not configured [hint: SSLSessionCache]
> [Sat Aug 18 12:26:23.183039 2012] [lbmethod_heartbeat:notice] [pid 82399:tid 140735220779360]
AH02282: No slotmem from mod_heartmonitor
>
> which is undoubtedly because several modules are being built and loaded
> that depend on certain options but do not get disabled by the lack
> of those options in configure.
>
> IMO, none of the following modules should be configured by default:
>
> LoadModule file_cache_module modules/mod_file_cache.so
...
> LoadModule dav_fs_module modules/mod_dav_fs.so
>
> The vast majority of installations do not want a f*(^ing proxy.
> Building them is fine -- these should be commented out in the
> installed httpd.conf unless --with-proxy is enabled.

Yes, before 2.4.0 we introduced exactly this difference. All modules 
that were build get a LoadModule line in the installed config, but most 
are commented out. I don't have the list of modles active by default at 
hand though.

> At the very least, modules dependent on SSL must not be loaded if
> --without-ssl is the configure option.
>
> I don't consider this a showstopper for 2.4.3, but I do think they
> are bugs in trunk and 2.4.x.

Partial answer: the current semantics of maintainer-mode is (per 
configure help):

"Turn on debugging and compile time warnings and load all compiled modules"

In fact configure should output

"Maintainer mode setting "LOAD_ALL_MODULES" to yes"

It seems you can switch of this side effect of maintainer mode by 
explicitly adding "--enable-load-all-modules=no" to your configure 
flags. This is the default except for when building in maintainer mode.

Regards,

Rainer

Mime
View raw message