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.
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
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.