httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Sutton <>
Subject Re: [PATCH] Configuration (4/4): TARGET name
Date Tue, 01 Dec 1998 22:27:47 GMT
On 1 Dec 1998, Randy Terbush wrote:
> Paul Sutton <> writes:
> > On 1 Dec 1998, Randy Terbush wrote:
> > > Marc Slemko <> writes:
> > > > I'm just not sure where the need for this is coming from and would 
> > > > really prefer trying to avoid tacking more and more stuff over top
> > > > of the current framework unless necessary.
> > > 
> > > It's needed from the standpoint that many (most?) users using Apache
> > > run several servers with different compiled configurations. It is a
> > > common problem where the config file, binary etc. is confused with
> > > another and the fact that Apache automagically reads in srm.conf and
> > > access.conf if they exist makes it even more fragile. 
> > 
> > If people are advanced enough to attemp to run multiple binaries from the
> > same serverroot directory then they should pretty much understand enough
> > to handle this themselves.
> I would argue that we need to remove a few of the pitfalls of doing it 
> so that people that are less advanced can do it easily. It is silly
> and messy to have separate serverroots when so many of the
> files/directories can be shared. The fact that Apache so willingly
> shares srm.conf and access.conf is the real problem here.

But removing the files won't stop Apache from sharing a srm.conf and
access.conf as soon as the user creates them. That would create even more
confusion, since they might have explicitly created a ResourceConfig
conf/srm.conf line in one httpd.conf and suddenly find that the other
server is reading the srm.conf file! We really have to ensure that we
install stub srm.conf and access.conf files to stop this situation
arising. If neccessary those stubs can contain warnings about using
multiple servers in the same serverroot area.

Of course in the longer term I expect everybody would support removing
completely the magically nature of srm.conf and acces.conf from the Apache
codebase. But just removing those stub files from an installation is not
going to achieve that, and may make things more confusing.

The real problem with multiple serverroots in one directory is the way
that Apache's install assumes that data, configuration and programs all go
together in the same directory area (which itself comes from the old NCSA
idea of running the serverroot in the same directory as where the source
was compiled). We do need to address this, but I think it needs a bit more
consideration and minor short-term changes such as removing the stub files
from the installation do not address the issues.

Paul Sutton, C2Net Europe          
Editor, Apache Week .. the latest Apache news

View raw message