On Fri, May 18, 2001 at 04:12:10PM -0700, Danek Duvall wrote:
> On Fri, May 18, 2001 at 05:59:15PM -0500, William A. Rowe, Jr. wrote:
>
> > It sounds like you would be better off installing the 'stock' apache,
> > but setting up a second .conf for the 'system services' you want to add,
> > running them to their own logs/scoreboard/pidfile.
> >
> > That way, the user doesn't mangle those services, and the two never
> > interfere with one another.
>
> Yeah, that's certainly an option, and one we may very well decide on. It
> has the advantage that it separates the 'system Apache' from the 'user
> Apache', and the two never mix, stomp on each other, &c.
>
> On the other hand, that sort of solution says to me that something is
> broken in the design of the configuration of the system. It's inelegant.
> I shouldn't *need* to have two instances of Apache running, but instead I
> should be able to have a configuration that neatly partitions services from
> each other. Cf inetd, which is essentially the same thing, except it
> doesn't provide HTTP support.
Oh no... this should be able to be done quite easily.
Use the new "include all .conf files in <this> directory" feature (it is
actually in 1.3 and 2.0). As each service is added, they drop their specific
configuration file into the directory. When the service is removed, they
remove their .conf file. The web service is just the same: add a file and
remove on deinstall.
Your .rc file can simply see if any files are present in the directory. If
there, then start httpd. If none are present, then don't start.
That should be doable today.
(I don't have details on the feature, but I remember the commit from jimjag
going in there a while back)
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
