httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Bloom" <...@covalent.net>
Subject RE: [PATCH] simplified apachectl that passes through options to httpd
Date Fri, 24 May 2002 17:26:07 GMT
> From: William A. Rowe, Jr. [mailto:wrowe@rowe-clan.net]
> 
> At 11:18 AM 5/24/2002, you wrote:
> >On Fri, May 24, 2002 at 11:10:25AM -0500, William A. Rowe, Jr. wrote:
> > > If you configure your machine for SSL, then run it as SSL
already!!!
> > > Why are we trying to say "you've installed and configured SSL, so
now
> > > you have to turn it on explicitly everytime you start up."  Which
most
> > > will take as meaning "I have apache2 installed, so now all I need
to
> do
> > > is to startssl and everything will work."
> >
> >Simple: We have static and dynamic modules. Static modules can't turn
> >off their LoadModule lines, so we can't use that to turn on and off
the
> >functionality in those modules. -DSSL is the runtime switch that
mod_ssl
> >uses to enable SSL functionality.
> 
> That isn't a reason to create -k startssl to duplicate -k start -D SSL
> 
> ...in fact, if you have a problem with not being able to disable a
module
> in
> Apache2, then fix the essential problem, which is disabling modules.
> That was the feature 'broken' in Apache 2.

I'm missing why that is considered broken.  If you are compiling your
own server, then you should only statically compile the modules that you
want to use.  If you are using a binary dist, then I don't know of any
binary dists that use static modules instead of dynamic ones.  Is there
actually a case where somebody has wanted to be able to disable a module
and been unable to?

Ryan



Mime
View raw message