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.
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.
--
Joshua Slive
http://finance.commerce.ubc.ca/~slive/
But rather disturbingsly the standard red-hat 6.0 /6.1 uses all three.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
--
Joshua Slive
http://www.veryComputer.com/~slive/
What is actually disturbing is the idea that Redhat has decided to goQuote:>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.
any clues? Anything else I should loose sleep over?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...
Instead of just trashing their httpd.confs - I make sure when I install RH6
that I leave out apache.
>>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?
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.
1. translator from CERN httpd configuration rules to Apache httpd conf?
Hi!
I would like to know if there exists a translator which is able to
pass all the security rules from the CERN httpd configuration into
apache's .
Is it possible? Thanks in advance!
Montse
2. ld: output file requires libX11 error (Was: bug in slakware)
3. Test httpd.conf setup - using variables in httpd.conf
4. rsh and security - how is password option changed?
5. APACHE 1.1.1 httpd.conf and the "httpd -f ..." option
6. Inbound Moringstar from Win98
7. APACHE httpd.conf vs. httpsd.conf HELP !!!1
8. Linux system developers, WAKE UP!!!
9. Apache .conf vs. NCSA httpd .conf
10. self-compiled httpd does not start (suse 6.1 / apache 1.3.x))
11. Apache 1.3: "httpd could not be started"
12. apache 1.3, SunOS 4.1.3, httpd process locks up
13. CERN HTTPD 3.0 or NCSA HTTPD 1.3?