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. There are (at least) three bug reports for this in the Debian tracker already :-) But it's unlikely to be fixed in stable, because it's only a warning, and not a security issue (I assume). Not to mention a bunch of the 'sloppy maintainers' are probably grumpy that they had to learn and write systemd units in the first place, when they were happy with sysvinit :-) Anyway, at this point, I'm more interested in whether there's a bug in systemd, or whether it's intentional that I can't fix this in an override file rather than having to do it under /lib, where it's going to get overwritten with any package update. Or, of course, whether I'm just doing it wrong. In this case, doing it in /lib may be ok, because I'm doing it with ansible, so I can just re-run the play if I need to fix it again. Cheers, Richard _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel