to add, I believe that even when there are no physical NICs, there is always a loopback interface on every machine, and this would trigger as soon as the loopback interface is configured (127.0.0.1) .
I can't think of a situation where someone would install apache on a device that has no network stack built into the kernel, so it's hard for me to think of a situation where the network-online.target will present a problem. Also, the solution to make the service to start on network-online.target works for people using the apache configuration that ubuntu ships by default (per my test with a VM). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786675 Title: Apache will not start on boot if bound to a fixed IP address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1786675/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
