|
Hi,
On Fri, Feb 26, 2021 at 09:08:18AM +0100, Marc Haber wrote:
Worse. If the receiving side does post-DATA checking of the message, and
systemd sends SIGKILL to the exim process on the sending side, the
receiving side might continue delivery without the sending side noticing
the confirmation (it's already dead by then). During the next exim queue
run, the message will be delivered a second time.
In this case, 5 seconds of extra wait would probably not be enough.
This entry in the systemd 250 NEWS gives me hope this might be fixed in a nice way eventually:
* A new service unit file setting ExitType= has been added that
specifies when to assume a service has exited. By default systemd
only watches the main process of a service. By setting
ExitType=cgroup it can be told to wait for the last process in a
cgroup instead.
I'll probably experiment with it once systemd 250 lands in testing, unless someone beats me to it.
|