httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Danek Duvall <dduv...@eng.sun.com>
Subject Re: [PATCH] option to remove default listener
Date Fri, 18 May 2001 21:44:52 GMT
On Fri, May 18, 2001 at 01:59:07PM -0700, Ian Holsman wrote:

> could this be more easily achieved by putting an invalid line in the
> configure file like 
> REMOVEME_Port 80

If you do that (and hence have no Port or Listen directives), then Apache
will see that no listeners have been configured, and will create one on
port 80, which is the behavior I want to avoid.

> or even checking for a file's presence (ie.. the default apache install
> would place httpd.conf somewhere else.. your startup would check to see
> if httpd.conf is in the right place)

That's what Solaris does currently.  And if all we cared about Apache for
was the web server, then that would probably be sufficient.  But we're
beginning to write other HTTP-based services (like IPP, which I'm working
on), and we'd like to use Apache to host them.

When such a service is added via installing a package, Apache must become
enabled at that point.  Likewise, when the last such service is removed
from the system, Apache must become disabled, unless the user has
explicitly configured stuff other than one of the packaged services.

These things can't be done without help from Apache, and my patch is one
such way.  If you can think of another way to effect the same behavior, let
me know.  Renaming the config file doesn't have the correct behavior on
removing the last service, and for adding the first service puts an extra
burden on that package maintainer.

Danek

Mime
View raw message