httpd.conf only since Apache 1.3.?

httpd.conf only since Apache 1.3.?

Post by Rober » Mon, 24 Apr 2000 04:00:00



Hi,

Apache does only need the configuration file httpd.conf. The other ones
access.conf and srm.conf are not necesarry anymore, I know. Since which
version is this so (1.3.3?) ?

Thanks,
rob.

 
 
 

httpd.conf only since Apache 1.3.?

Post by Joshua Sliv » Mon, 24 Apr 2000 04:00:00



> Hi,
> Apache does only need the configuration file httpd.conf. The other ones
> access.conf and srm.conf are not necesarry anymore, I know. Since which
> version is this so (1.3.3?) ?

Apache has never required more than one config file (at least for as
long as I've been using it).  The only thing that has changed in
recent versions is that the example config files no longer use
access.conf and srm.conf.  There has never been any obligation
to use them, and I have been using a single config since long before
the examples were changed.  This has been true at least since 1996
as evidenced by the interesting discussion of the issue:
http://www.apache.org/info/three-config-files.html

--
Joshua Slive

http://finance.commerce.ubc.ca/~slive/

 
 
 

httpd.conf only since Apache 1.3.?

Post by B Kem » Tue, 25 Apr 2000 04:00:00


Quote:>Apache has never required more than one config file (at least for as
>long as I've been using it).  The only thing that has changed in
>recent versions is that the example config files no longer use
>access.conf and srm.conf.  There has never been any obligation
>to use them, and I have been using a single config since long before
>the examples were changed.  This has been true at least since 1996
>as evidenced by the interesting discussion of the issue:
>http://www.apache.org/info/three-config-files.html

But rather disturbingsly the standard red-hat 6.0 /6.1 uses all three.
Any ideas as to why?
 
 
 

httpd.conf only since Apache 1.3.?

Post by Joshua Sliv » Tue, 25 Apr 2000 04:00:00



>>Apache has never required more than one config file (at least for as
>>long as I've been using it).  The only thing that has changed in
> But rather disturbingsly the standard red-hat 6.0 /6.1 uses all three.
> Any ideas as to why?

I don't find it disturbing (except to the extent that Redhat tends to
*things up when they diverge from the standard apache distribution).
There is nothing wrong with using >1 config file.  It just depends
on your preference.

--
Joshua Slive

http://www.veryComputer.com/~slive/

 
 
 

httpd.conf only since Apache 1.3.?

Post by W Kem » Wed, 26 Apr 2000 04:00:00


Quote:>I don't find it disturbing (except to the extent that Redhat tends to
>screw things up when they diverge from the standard apache distribution).

What is actually disturbing is the idea that Redhat has decided to go
against what is now a standard Apache feature.
 
 
 

httpd.conf only since Apache 1.3.?

Post by Marc Slem » Wed, 26 Apr 2000 04:00:00



>>I don't find it disturbing (except to the extent that Redhat tends to
>>screw things up when they diverge from the standard apache distribution).

>What is actually disturbing is the idea that Redhat has decided to go
>against what is now a standard Apache feature.

If you are using redhat's RPM of Apache, you shouldn't let that
worry you in the least.  You have far bigger things to worry about with
their RPM last I checked...
 
 
 

httpd.conf only since Apache 1.3.?

Post by B Kem » Wed, 26 Apr 2000 04:00:00


Quote:>If you are using redhat's RPM of Apache, you shouldn't let that
>worry you in the least.  You have far bigger things to worry about with
>their RPM last I checked...

any clues? Anything else I should loose sleep over?

Instead of just trashing their httpd.confs - I make sure when I install RH6
that I leave out apache.

 
 
 

httpd.conf only since Apache 1.3.?

Post by Marc Slem » Fri, 28 Apr 2000 04:00:00



>>If you are using redhat's RPM of Apache, you shouldn't let that
>>worry you in the least.  You have far bigger things to worry about with
>>their RPM last I checked...

>any clues? Anything else I should loose sleep over?

If you are running a important production web server that has significant
demands placed on it, then perhaps.

I must caution that my comments are _NOT_ based on whatever the
current version may be, so some or all of the things I don't like
may have been fixed.  Things like signalling _all_ the child
processes by name instead of just the parent using the pid file.
This does cause problems in certain situations.  Things like
gratuitously changing defaults to make it incompatible with the
"real" Apache.  From a support perspective, it is a big pain.
People install this thing that Red Hat calls "Apache", it doesn't
work or has bugs, and people come crying to the Apache Software
Foundation.  When our distribution doesn't have that problem so we
obviously can't fix anything since it isn't broken.

Red Hat is far from being alone here, and they are better than they
were and are a lot better than some others.  But there is no substitute
for the real thing.