http://bugzilla.suse.com/show_bug.cgi?id=1014540
http://bugzilla.suse.com/show_bug.cgi?id=1014540#c1
Petr Gajdos changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |pgajdos@suse.com
Resolution|--- |WONTFIX
--- Comment #1 from Petr Gajdos ---
This Include was removed intentionally. Now you can have more apache instances
managed trough systemd, see apache2@.service.
As we do not know in advance which instance (including the main one) will have
which main configuration file and we cannot of course rely that there will be
inclusion of some sysconfig.d directory.
The sysconfig.d directory (see start_apache2) is created along main
configuration file of given instance and then is included via an option on
command line at the end of the script. This script is called via systemd
services.
So the behaviour is now a bit compact. When you want to benefit from sysconfig
files, you need to use systemd services or start_apache2 script.
When you want to run httpd manually then you are on your own and but you are
also sure that no later call of systemd service will overwrite the
configuration. Note that, when you use /etc/apache2/httpd.conf as main
configuration file, /etc/apache2/loadmodule.conf and /etc/apache2/global.conf
are included instead of their sysconfig.d counterparts.
--
You are receiving this mail because:
You are on the CC list for the bug.
