On Thu, Aug 7, 2008 at 10:34 AM, Patrick Shanahan
* David C. Rankin
[08-07-08 03:35]: Patrick Shanahan wrote:
BUT, if you did not use "httpd.conf.local", when an update modified httpd.conf, the reference to your chosen config file would be missing. So there *is* a reason to use "httpd.conf.local".
Are you sure? I thought once you changed the sysconfig file from default to include anything else, it was flagged as don't update by package management?
You may be correct. I may be confusing the use of other *.conf.local files such as: /etc/modprobe.conf.local /etc/fail2ban/action.d/mail.conf.local among others
this is exactly what I was wanting to know ... and, now, I still am not sure whether I know it. Is it important that I tell the devs to use the .local variant of the conf files, or not? I just am not that familiar with configuring apache generally, and I certainly do not know enough either about the SUSE or the RH implementation to be able to explain what the devs will experience as a difference. Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org