* David C. Rankin
The name choice is simply to help me remember that my local specific config is in the .local file. Also, when doing package updates, the httpd.conf can be overwritten with an update whereas the .local file will not be touched. I could have called it:
my.feeble.attempt.at.httpd.conf
and as long as I modified /etc/sysconfig/apache2 to read:
APACHE_CONF_INCLUDE_FILES="my.feeble.attempt.at.httpd.conf"
instead of
APACHE_CONF_INCLUDE_FILES="httpd.conf.local"
it wouldn't make any difference. The key is simply remember to tell apache what additional files to include.
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". -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org