httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dean gaudet <dgaudet-list-new-ht...@arctic.org>
Subject Re: [PATCH] option to remove default listener
Date Sat, 26 May 2001 00:20:22 GMT
do you use include directives or something to include partial configs for
each of the services you want to activate?

can your package manager handle multiple packages owning a file, say
/etc/apache_enabled ?  if so then it should be trivial to create
/etc/apache_enabled in every one of your packages that needs apache.
presumably if your package manager handles multiple owners of the same
file it keeps reference counts or something and will deal with deleting
/etc/apache_enabled when there are no more owners.

-dean

On Fri, 18 May 2001, Danek Duvall wrote:

> On Fri, May 18, 2001 at 03:28:36PM -0700, Roy T. Fielding wrote:
>
> > That doesn't make any sense.  If you don't want to start httpd, then
> > don't run httpd at all.
>
> We have no way of knowing whether or not httpd should be started from
> outside Apache.  Certainly we know that it *shouldn't* be started if the
> config file isn't in place -- like I said, that's what happens in Solaris
> now.
>
> But because we want to use Apache for things other than a web server,
> Apache needs to come configured and ready to run, but enabled only when
> there are services which have been configured to run.  For my purposes,
> this means that Apache's configuration tells it to listen on some port, and
> nothing but running Apache can tell me that.
>
> Perhaps a patch to spit out a list of configured listeners and exit (sort
> of like -t -D DUMP_VHOSTS) would be preferable?
>
> Danek
>


Mime
View raw message