Docs: Replace hardcoded journald logpath with systemd backend

The file at /var/log/messages is not universal for every
distribution. Fail2ban can access journald logs directly
by using the systemd backend.
master
networkException 3 years ago
parent 66ea28b50a
commit f80e04a8c5
No known key found for this signature in database
GPG Key ID: C1F2658DC370C8FC

@ -513,8 +513,8 @@ follow these steps:
[bad-auth] [bad-auth]
enabled = true enabled = true
backend = systemd
filter = bad-auth filter = bad-auth
logpath = /var/log/messages
bantime = 604800 bantime = 604800
findtime = 300 findtime = 300
maxretry = 10 maxretry = 10
@ -565,7 +565,7 @@ Restart the Fail2Ban service.
sudo systemctl restart fail2ban sudo systemctl restart fail2ban
*Issue reference:* `85`_, `116`_, `171`_, `584`_, `592`_, `1727`_. *Issue reference:* `85`_, `116`_, `171`_, `584`_, `592`_, `1727`_, `1857`_.
Users can't change their password from webmail Users can't change their password from webmail
`````````````````````````````````````````````` ``````````````````````````````````````````````

@ -0,0 +1 @@
Update fail2ban documentation to use systemd backend instead of filepath for journald
Loading…
Cancel
Save