Hi, On Tue, Feb 16, pgajdos wrote:
I got indicies that some people do not like SUSE httpd configuration mechanism, for example wrt diverging from other distros. What do you think? Your opinion is valuable.
To recap, there are two levels: higher one represented by systemd service apache2 (and apache2@ for instances), as known as start_apache2, which takes sysconfig variables -- eventually set by yast httpd module -- into account. Lower level is represented by running just httpd, which is not influenced by sysconfig variables. This separation was driven by illogical behaviour when mixing these two approaches together.
I'm using meanwhile nginx, since this is closer to upstream. Which means third party tools, configurations and documentations work normally out of the box. And this is the biggest complain I continously get: if you diverge, you have to adjust all the third party tools, configurations and documentations, too. And that's something we don't do. So people are lost, and the comment is not "I see the advantages of your way" but "it does not work on openSUSE". So: if there are good reasons to diverge from upstream and the rest of the world, we need to make pretty clear to everybody what the advantage for them is. If we don't do this, we are just incompatible. And it doesn't matter if it is the way how we start Apache (systemd unit, as many tools start/stop/disable/enable apache), the filesystem layout of the configuartion files or how we configure it. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)