Bug 238120

Summary: httpd update creates unwanted /etc/httpd/conf.d/*.conf files
Product: [Fedora] Fedora Reporter: Vlado Potisk <reg.bugs>
Component: httpdAssignee: Joe Orton <jorton>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-04-30 09:12:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vlado Potisk 2007-04-27 10:03:59 UTC 
Description of problem:
The httpd program reads all /etc/httpd/conf.d/*.conf files when starting
(according to the README there). That's why I assume that the normal way to
disable any of these files is to remove or rename them. However update creates
them again and thus alters the configuration in an unexpected way.

Version-Release number of selected component (if applicable):
httpd-2.2.4-1.fc6

How reproducible:
Always

Steps to Reproduce:
1. install httpd, but not the latest version
2. delete e.g. /etc/httpd/conf.d/proxy_ajp.conf
3. yum update
4. restart httpd
  
Actual results:
The unwanted /etc/httpd/conf.d/proxy_ajp.conf re-appears. On my server the httpd
failed to start due to missing modules that I commented out in the config file
but which are required by proxy_ajp.

Expected results:
/etc/httpd/conf.d/*.conf files should be created as .rpmnew files if the
original file does not exist.
Comment 1 Joe Orton 2007-04-30 09:12:39 UTC 
Sorry about that, but this is expected behaviour with RPM (perhaps unfortunate
in this case).   The way to reliably prevent the ajp module loading would be to
do something like:

  # echo > /etc/httpd/conf.d/proxy_ajp.conf
Comment 2 Vlado Potisk 2007-04-30 09:44:38 UTC 
Thank you for quick response. Even if it is not a bug, I would suggest to append
a note about this to /etc/httpd/conf.d/README.