Op 19/08/2013 om 12:12:49 +0000, schreef Viktor Dukhovni:
> On Mon, Aug 19, 2013 at 01:28:45PM +0200, Leo Baltus wrote:
>
> > We are upgrading our postfix instances from 2.9.6 to 2.10.1.
>
> Have you considered reading the release notes (for Postfix 2.10)?
>
Well, I did. I didn't think it would apply because we always shut down
the old version before starting the new one.
> Major changes - load-balancer support
> -------------------------------------
>
> [Incompat 20120625] The postscreen(8)-to-smtpd(8) protocol has
> changed. To avoid "cannot receive connection attributes" warnings
> and dropped connections, execute the command "postfix reload". No
> mail will be lost as long as the remote SMTP client tries again
> later.
>
> The reload should be performed immediately after installing the new
> binaries. If you prefer you can stop Postfix before the upgrade, and
> restart after (that's what I would do).
>
On re-reading I should have given it more thought.
We do not overwrite old binaries, instead we place them parallel. We
stop the old instance (postfix stop) and start (postfix start), so
postscreen and smtpd will always be running from the same software
repository. I would say that that should take care of this issue.
However, I did notice that postfix exec()'s new processes using the
path to the binaries it got from
'PATH=symlink_to_postfix/sbin postfix start'
instead of compile-time arguments DEF_COMMAND_DIR DEF_DAEMON_DIR etc.
I may have been playing with symlink_to_postfix while hunting this down.
Maybe this has changed in the past or I always misunderstood. Should I
reconsider our stopping/starting approach? Or is this unrelated?
--
Leo Baltus, internetbeheerder /\
NPO ICT Internet Services /NPO/\
Sumatralaan 45, 1217 GP Hilversum, Filmcentrum, west \ /\/
serviced...@omroep.nl, 035-6773555 \/
