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

[Erik C.J. Laan]

On 7/19/19 8:00 AM, Erik C.J. Laan wrote:
> On 7/19/19 7:29 AM, 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.
>>
>> Grüße,
>> Sven.
>>
> This morning I installed the .timer and .service files manually on 3 
> machines, and ran systemctl enable exim4-base.timer and systemctl 
> start exim4-base.timer. One of these machines is my hoe mail server 
> (+- 100 mails/day), the other 2 are clients that usually only mail me 
> a daily report.
>
> With kind regards, Erik Laan,
>
I discovered I also had to use the newest version of 
/etc/cron.daily/exim4-base, otherwise it would be run twice a day. After 
installing the updated /etc/cron.daily/exim4-base too it works like a 
charm. Thanks for the solution.

-- 
Met vriendelijke groeten/With kind regards, Erik Laan.