On Mon, 26 Aug 2019 at 07:18:47 +, Damyan Ivanov wrote:
> Some times (observed on slow virtual hardware) logrotate.service fails to
> start
> during boot, because the fail2ban logrotate configuration calls
> fail2ban-client
> flushlogs and that fails because fail2ban is not yet started.
>
Hello
I tried with your proposition and lintian isn't happy:
W: fail2ban: systemd-service-file-refers-to-unusual-wantedby-target
logrotate.service [usr/lib/systemd/system/fail2ban.service]
N:
N: The specified systemd service file declares an unusual WantedBy=
N: relationship.
N:
N: Most
Package: fail2ban
Version: 0.10.2-2.1
Severity: important
Tags: patch
Control: affects -1 logrotate
Hi,
Some times (observed on slow virtual hardware) logrotate.service fails to start
during boot, because the fail2ban logrotate configuration calls fail2ban-client
flushlogs and that fails
3 matches
Mail list logo