I think doing socket based activation properly is non-trivial, as there are people wanting apache to run only on non-standard ports, e.g. when deploying OpenStack services. So having a default setup that causes systemd to listen on port 80, without checking whether the apache config really does want that, would be pretty bad IMHO. Same thing for mod_ssl and port 443. And it looks to me like that is what Fedora does, so please don't just copy that behaviour.
So I would vote for doing the Type=forking solution in Xenial now in order to get the original issue fixed in time for release and develop some sensible native units later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488962 Title: systemd does not notice when services created via systemd-sysv- generator fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1488962/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
