Re: Factorised code for adding a file in /etc/apache2/conf.d/ and restarting apache ?
Stefan Fritsch <firstname.lastname@example.org> writes:
> On Sunday 06 July 2008, Russ Allbery wrote:
>> That would really upset me if I were a systems administrator. Most of
>> my Apache configurations have multiple virtual hosts, and having some
>> package randomly add itself to the namespace of every virtual host I
>> run, possibly taking over pages that were currently serving some other
>> purpose, would be extremely annoying.
> I don't think it is ideal, but it seems to be quite common. At least
> 17 packages do it this way. Therefore an administrator cannot assume
> that packages won't add apache config files anyway.
Yeah, I would probably report a bug if I ran into one that actually
grabbed URL space that I installed, but I'm probably also not the target
audience for this particular package. (Note that there are things you can
install in conf.d that are fine from that perspective, such as general
configuration for some application, that don't grab URL space.) It may
well be that for this particular package, all of the users would want
It would be nice if there were some way that packages could drop this
sort of thing into a directory equivalent to sites-evailable and then let
people enable it or disable it accordingly.
> Of course it would be a good idea to discuss this and create a
> standard policy, but this will not happen for lenny, obviously.
I wonder if we could do something leveraged off of the default site. If
you have the default site still enabled, you're probably not doing
anything particularly sophisticated and would be happy for packages to
grab space in that site. If you've disabled the default site, packages
should be more cautious about grabbing URL space.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>