On Tuesday, January 03, 2017 08:43:15 PM you wrote: > @Scott: > https://git.launchpad.net/postfix/commit/?h=stable/v3.1&id=1a190cf17cc02 > looks rather complicated and also creates an unmanaged config file. Why > not just always add those After= to the .service? If resolved is not > enabled, then After=systemd-resolved is a no-op (it's only ordering, not > a dependency -- that would be Requires= or Wants=). > > Also, not sure why you added network-online.target, but if you actually > do want to wait for the network then you also need a corresponding Wants > =network-online.target (see man systemd.special).
Thanks. It depends on how postfix is configured (via Debconf) if these are needed or not. I think ordering is all we need since, in some cases we've seen issues with the current service file. In some configurations neither network-online.targe nor systemd-resolved are needed. I did, in a later commit, remove the config file on purge, so that's fixed. Scott K -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649453 Title: systemd starts postfix before resolver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1649453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
