Re: 'PIDFile=' warning and override.conf

[Richard Hector <richard@xxxxxxxxxxxxx>]

On 27/08/20 1:43 am, Lennart Poettering wrote:
> On Mi, 26.08.20 11:26, Richard Hector (richard@xxxxxxxxxxxxx) wrote:
> 
>> Hi all,
>>
>> I've got the common warning:
>>
>> /lib/systemd/system/fail2ban.service:12: PIDFile= references path below
>> legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid →
>> /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
>>
>> I made the change in the relevant override.conf file, but that doesn't
>> seem to work. Changing the 'real' one in /lib/systemd/system works.
>>
>> Is that how it's supposed to be?
>>
>> I'm using debian buster, with systemd package version 241-7~deb10u4
> 
> The warning is generated whenever a line is parsed that has the old
> legacy path for this. If you later override it this doesn't change the
> fact that earlier on the legacy path was parsed.

Thanks, that makes sense.

> There's not much point to try to fix that locally as user, it's a
> warning only after all.

In the end I made the changes in /lib/systemd/system/fail2ban.service
(including using RuntimeDirectory). Using ansible, so it's easy to reapply.

I use logcheck, and try to filter it down to what I need to see, but
prefer to fix rather than filter where I can.

Fixing in Debian would obviously be better, but given there are multiple
existing bug reports, I'm not going to get into that battle.

Thanks for your help.

Cheers,
Richard
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel