From 2c3dbc8046f12402cf2d19b705f648b5056c4653 Mon Sep 17 00:00:00 2001
From: Steven Hiscocks <steven@hiscocks.me.uk>
Date: Fri, 13 Dec 2013 21:55:43 +0000
Subject: [PATCH] BF: In 0.9 recidive bans come from fail2ban.server.actions

Also changed journalmatch to limit to WARNING priority to avoid the
recidive + DEBUG combo issue
---
 config/filter.d/recidive.conf | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/config/filter.d/recidive.conf b/config/filter.d/recidive.conf
index 273e383f..6d513116 100644
--- a/config/filter.d/recidive.conf
+++ b/config/filter.d/recidive.conf
@@ -21,16 +21,16 @@ before = common.conf
 
 [Definition]
 
-_daemon = fail2ban\.actions
+_daemon = fail2ban\.server\.actions
 
 # The name of the jail that this filter is used for. In jail.conf, name the 
 # jail using this filter 'recidive', or change this line!
 _jailname = recidive
 
-failregex = ^(%(__prefix_line)s|,\d{3} fail2ban.actions:\s+)WARNING\s+\[(?!%(_jailname)s\])(?:.*)\]\s+Ban\s+<HOST>\s*$
+failregex = ^(%(__prefix_line)s|,\d{3} %(_daemon)s:\s+)WARNING\s+\[(?!%(_jailname)s\])(?:.*)\]\s+Ban\s+<HOST>\s*$
 
 [Init]
 
-journalmatch = _SYSTEMD_UNIT=fail2ban.service
+journalmatch = _SYSTEMD_UNIT=fail2ban.service PRIORITY=4
 
 # Author: Tom Hendrikx, modifications by Amir Caspi