![](https://seccdn.libravatar.org/avatar/4de30ea19d081e0cb137efdb4fd0ec19.jpg?s=120&d=mm&r=g)
On 12/26/2014 06:21 PM, Cristian Rodríguez wrote:
El 26/12/14 a las 18:45, Bruce Ferrell escribió:
I'd say that the patches to integrate systemd are was configured from yast faulty somehow...
Nope. that can't be, the module does not even read the request data..it runs one hook before requests even start to be served and the other runs a monitor that notifies systemd of the apache processes' status.
It works now because removing the old rpm disabled the old configuration files.
Did you configured apache with yast http server? did you upgraded from an old openSUSE release ? I ask because it works for me.
it was a clean install from scratch, not an upgrade. An upgrade that fails in this manner is STILL a failed install and indicative of poor QA. As I believe I mentioned, I actually tested the fault with a clean install to several VMs. The failure is seen every time. Apache in all cases was activated and configured via yast, network services/http. On my live system, I did in fact remove the stock RPMs and then cleaned ALL configurations before installing my clean RPMs. Christian, I test and install software for a living and have built literally thousands of instances of Apache going back into the early '90s in my career. A part of my diagnostics for this was to build the same version from apache.org into /usr/local/apache2 to assure the upstream distributed code was not at fault. I also used a "simple" index.html file to present the CSS files to eliminate PHP as being the fault. "Your" RPMs improperly serve the CSS. Mine do not. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org