> On Mar 27, 2019, at 3:01 PM, Viktor Dukhovni <[email protected]>
> wrote:
>
> There's likely a bug. We should either simulate a synthetic nexthop
> ($myhostname?) for unix-domain destinations, and then do nexthop
> reuse (and perhaps do no caching by endpoint address for unix-domain
> destinations), or go back to using re-use by endpoint address.
> Currently there's a mismatch, and we're keeping connections alive
> that can't be reused.
And of course the nexthop can't be "$myhostname". If there are multiple
LMTP unix-domain socket destinations, we must not mix them up, so the
nexthop needs to be just the socket pathname.
--
Viktor.
