On Mon, May 15, 2017 at 06:45:21PM -0000, Scott Kitterman wrote: > I'm getting close to uploading a fix for this to Debian, so you might wait > for that.
It looks like you've implemented this using the network-online.target approach, which as you mentioned might not DTRT for the localhost-only use case. Did you decide that this is negligible? For the case of a server which always has a network connection, this works fine. For the case of a standalone system with no configured network connection, it probably also works fine. But for the case of e.g. a laptop that sometimes has network and sometimes doesn't, if the system comes up without network, postfix will not start and you will not have local delivery. Is this the behavior you expect with your change? Ultimately I want to SRU this into affected stable Ubuntu releases, so would want a regression-free change. I see you are also setting After=nss-lookup.target. For the bug reported here - which is about DNS resolution specifically - would it not suffice to have postfix declare this After=nss-lookup.target, and for systemd-resolved to be sequenced before it? -- 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/ [email protected] [email protected] -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
