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

Michael Biebl biebl at debian.org
Mon May 8 15:18:57 BST 2017

I'm missing context here. Can you go into more detail please? What exactly is the question here? 


Am 8. Mai 2017 16:07:12 MESZ schrieb Bernhard Schmidt <berni at debian.org>:
>Am 08.05.2017 um 05:59 schrieb Scott Kitterman:
>> On Sunday, May 07, 2017 10:55:58 PM Bernhard Schmidt wrote:
>>> On Sat, Apr 15, 2017 at 11:42:37PM +0200, Marcus Jodorf wrote:
>>> Hi,
>>> is there anything I can do to get this fixed for Stretch? I can
>>> pretty reliably reproduce this issue with all my upgraded Stretch
>>> systems, neither of them can send mails after a reboot until Postfix
>>> getting restarted
>>> An After=network.target should be pretty low-risk even this late in
>>> release cycle and should fix this issue.
>>> Best Regards,
>>> Bernhard
>> 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)?
>AFAICT (Ccing systemd maintainers for input) postfix.service is mostly
>used for compatibility with sysv (namely have "service postfix
>something" do something reasonably by having the postfix at .service being
>PartOf=postfix.service), but the actual decision what instance to start
>is done by the generator
>(/lib/systemd/system-generators/postfix-instance-generator) which
>directly "wants" the instance.
>IOW, I don't think postfix at .service being PartOf=postfix.service (which
>does have After=network.target) influences its ordering.
>The other quick fix for Stretch would be a "After=resolvconf.service",
>think most incarnations of this bug seen to far have been related to
>Pkg-systemd-maintainers mailing list
>Pkg-systemd-maintainers at lists.alioth.debian.org

More information about the Pkg-systemd-maintainers mailing list