Re: 'PIDFile=' warning and override.conf

[Reindl Harald <h.reindl@xxxxxxxxxxxxx>]

Am 26.08.20 um 11:48 schrieb Richard Hector:
> On 26/08/20 9:07 pm, Reindl Harald wrote:
>>
>>
>> Am 26.08.20 um 01:26 schrieb Richard Hector:
>>> 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
>>
>> better writ ebugreports so that these sloppy mainatiners wake up and
>> read their own logfiles before throwing packages to users - it's the
>> same on Fedora and i simple don't get it
> 
> Which came first? The package that refers to the wrong directory, or the
> systemd version that changed the directory and/or started complaining
> about it? Debian stretch (systemd 232-25+deb9u12) doesn't complain.

besdies that /var/run is now for nearly a decade a symlink to /run (at
least on other distributions) first came systemd-232 and the complaints
long before the release and packagers/maintainers just need to read
their logfiles like you did
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel