Robie: If the service offers a mechanism to set a specific NIC to listen on, then the service should make good on that offer when it's requested. Doesn't that make sense to you?
All services that require a NIC to function should wait for that NIC to come alive. Having a service start or attempt to start before what it needs for life support is available makes no sense. Allowing a service to start on a bogus IP address provides no "service". What's the point of having a service technically up if it's deaf to traffic? I can't see where this qualifies as a wishlist item. The service advertises a feature and doesn't provide it. To me, that's a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
