Hi Andreas, Am 08.05.2017 um 19:15 schrieb Andreas Henriksson: > Hello Scott, Bernhard, > > On Sun, May 07, 2017 at 11:59:10PM -0400, Scott Kitterman wrote: >> On Sunday, May 07, 2017 10:55:58 PM Bernhard Schmidt wrote: >>> [...] >> postfix.service has After=network.target. Why isn't that enough (I have not >> had a lot of time to investigate this, but I have not given on up getting a >> fix into stretch)? > > I think the main issue here is that people are confused about what > network.target actually is/means. > > For example this snippet is part of the original bug report: > The file /lib/systemd/system/postfix@.service needs to have the line > "After=network.target" to make sure that all the network interfaces are > raised > [...] > > The above description is completely false! > This is *not* what network.target does/means! > > For further explanation and suggestions for solutions see: > https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
I'm well aware of this, but in this particular case network.target is probably what we want. It is ordered after networking.service which raises the interfaces configured by ifupdown. After network.target the majority of "server" installations will have statically configured interfaces present and a usable resolv.conf. This is also true for systemd-networkd. This might still be broken for people using NetworkManager, but I doubt those will have postfix explicitly bound to a static IP address anyway. And it won't be worse for them than the current situation. Bernhard
