On Mon, May 15, 2017 at 09:59:22PM -0700, Steve Langasek wrote: > > - The penalty of pulling in network-online.target is simply that for the > > local case postfix is started a bit later then necessary during boot.
> There's no reason that this *should* be true for an intermittently-online > machine. The network-online.target is specifically defined so that services > are not started until the network connection is actually up; or put another > way, if a system is booted and can't get a network connection, those > services are not started. We don't just start them at some random point, > that would defeat the purpose. So, I just noticed that NetworkManager-wait-online uses --timeout: ExecStart=/usr/bin/nm-online -s -q --timeout=30 which means this delays services at most 30 seconds at boot. And you can ignore my blather about this preventing services from running. Sorry! (I'm not convinced that having a timeout is actually sensible behavior, but, well, it's what's implemented.) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519331 Title: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1519331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
