Wietse Venema wrote in <4mdf5130zdzj...@spike.porcupine.org>: |Wietse Venema: |> Viktor Dukhovni: |>> On Thu, Sep 29, 2022 at 05:14:12PM +0200, michae...@rocketmail.com \ |>> wrote: |>> |>>> systemd's start command is |>>> |>>> ExecStart=/usr/sbin/postfix start ... |>>> .. and when trying to "postfix -vvv start" at shell, postfix starts! |>>> |>>> But takes very, very long. So I'll search for increasing timeouts \ |>>> for systemd service units, next. ... |> We could make the 20050117 behavior configurable, but then it |> would have to be on by default, because no-one would turn it on. | |Some results from email archive digging: | |The system start-up latency concern was brought up by someone from |SUSE. I was unable to get confirmation that my change made things |better, and some other people didn't like it because it would delay |the detection of some errors. All that seems to be the reason move |these Postfix start-up checks back into the foreground. | |There was a conflict early on with the patch for multi-instance |support, but that may not have been the reason to move these Postfix |start-up checks back into the foreground.
Disclaimer: no idea. But on FreeBSD (only VM here for some years) on fresh install i always have sendmail hang minutes upon startup (i interrupt to come to login, which thankfully works), because it is of the opinion that the hostname is not valid on the network, or something. I do not have the same problem with postfix though. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
