Bug#854475: postfix: systemd needs postfix at .service to have "After=network.target"

Nuno Paquete nunopaquete at gmail.com
Mon May 15 07:35:25 BST 2017

Hi guys.

I'm trying to unsubscribe this newsletter but I'm not getting success.
Can someone Help?

Many thanks in advance.

Em 14/05/2017 16:33, "Michael Biebl" <biebl at debian.org> escreveu:

> Am 14.05.2017 um 17:02 schrieb Michael Biebl:
> > - debian/postfix.postinst: drop the postfix.service.d/override.conf and
> > make sure to remove that conffile on upgrades
> Seems due to some C&P failure I duplicated this point. I wanted to
> clarify that postfix.service.d/override.conf is not actually a conffile,
> as it's generated dynamically.
> As for my reasons to not generate this configuration dynamically:
> - It's less opaque. I was puzzled for a moment where this drop-in was
> coming from
> - It makes it easier to override postfix at .service. Atm you e.g. don't
> respect if the admin removed that drop-in deliberately and you always
> recreate it.
> - It's more robust in case of local modifications which don't use
> dpkg-reconfigure.
> - 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.
> - The behaviour is more consistent with the old SysV init script which
> had Required-Start: $network (The $network LSB facility translates to
> network-online.target)
> Michael
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20170515/e21c51d3/attachment-0002.html>

More information about the Pkg-systemd-maintainers mailing list