From 1470e3c01d49841335e11ed7ca7898516d1b8be8 Mon Sep 17 00:00:00 2001 From: Steven Hiscocks Date: Wed, 19 Mar 2014 19:09:07 +0000 Subject: [PATCH] BF: fail2ban.conf reader expected "int" type for `loglevel` Closes #657 --- ChangeLog | 1 + fail2ban/client/fail2banreader.py | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 6f5ebe78..2016a9fd 100644 --- a/ChangeLog +++ b/ChangeLog @@ -15,6 +15,7 @@ ver. 0.9.1 (2014/xx/xx) - better, faster, stronger * badips.py action error when logging HTTP error raised with badips request * fail2ban-regex failed to work in python3 due to space/tab mix * journalmatch for recidive incorrect PRIORITY + * loglevel couldn't be changed in fail2ban.conf - New features: diff --git a/fail2ban/client/fail2banreader.py b/fail2ban/client/fail2banreader.py index f17ff92b..251c6985 100644 --- a/fail2ban/client/fail2banreader.py +++ b/fail2ban/client/fail2banreader.py @@ -45,7 +45,7 @@ class Fail2banReader(ConfigReader): return ConfigReader.getOptions(self, "Definition", opts) def getOptions(self): - opts = [["int", "loglevel", "INFO" ], + opts = [["string", "loglevel", "INFO" ], ["string", "logtarget", "STDERR"], ["string", "dbfile", "/var/lib/fail2ban/fail2ban.sqlite3"], ["int", "dbpurgeage", 86400]]