From 5bc795c222cda1da60bd47f7e37dc1d10ecaa39a Mon Sep 17 00:00:00 2001
From: whirigoyen <whirigoyen+intra@evolix.fr>
Date: Tue, 19 Mar 2024 17:44:03 +0100
Subject: [PATCH] =?UTF-8?q?Ajout=20timeout=20purge=20sqlite=20au=20cas=20o?=
 =?UTF-8?q?=C3=B9=20"Error:=20database=20is=20locked"?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 HowtoFail2Ban.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/HowtoFail2Ban.md b/HowtoFail2Ban.md
index 66cccd77..cfc00299 100644
--- a/HowtoFail2Ban.md
+++ b/HowtoFail2Ban.md
@@ -813,7 +813,7 @@ Le contournement est de mettre en place un cron `/etc/cron.daily/fail2ban_dbpurg
 
 ~~~
 #!/bin/sh
-sqlite3 /var/lib/fail2ban/fail2ban.sqlite3 "DELETE FROM bans WHERE datetime('now', '-86400 second') > datetime(timeofban, 'unixepoch'); VACUUM;"
+sqlite3 /var/lib/fail2ban/fail2ban.sqlite3 ".timeout 5000; DELETE FROM bans WHERE datetime('now', '-86400 second') > datetime(timeofban, 'unixepoch'); VACUUM;"
 ~~~
 
 Notons que la commande `VACUUM` va copier la base en supprimant les espaces inutilisés dans la nouvelle base.