Bug#932328: logrotate.timer "breaks" activity report of /etc/cron.daily/exim4-base

[Andreas Metzler]

On 2019-07-25 Sven Hartge <sven at svenhartge.de> wrote:
> On 19.07.19 07:29, Sven Hartge wrote:
>> On 18.07.19 20:01, Sven Hartge wrote:
>>> On 17.07.19 20:46, Sven Hartge wrote:

>>>> Possible solution (untested): Also create a exim4-base.timer and
>>>> .service and create a Before= dependency on logrotate.service.

>>> I've whipped up a little Proof-of-Concept to test this, available also
>>> at https://salsa.debian.org/hartge-guest/exim4/tree/systemd-timer

>>> I'm testing this right now on two of my systems to see how this behaves,
>>> especially the Before=logrotate.{service,timer} ordering.

>> Yes, my test was successful, by ordering the exim4-base.service
>> Before=logrotate.service, the latter only starts after the first has
>> completed.

> I've now let the tests run for the last week and I can conclude it works
> perfectly on both Buster and Unstable.

> Grüße,
> Sven.

Thank you Sven, will take a closer look soon, now that CVE-2019-13917
fixes are uploaded.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'