summaryrefslogtreecommitdiff
path: root/files
diff options
context:
space:
mode:
authorHank Leininger <hlein@korelogic.com>2016-12-28 11:14:32 -0500
committerHank Leininger <hlein@korelogic.com>2016-12-28 11:14:32 -0500
commit9fbf713d7dc662ca6707682a676f4964b15e61ac (patch)
tree058d9777fe8cef9e25773d755a065b47a3d87ce1 /files
parent31a1560eaae663cb3b740829e3262198a909d1c4 (diff)
downloadfail2ban-9fbf713d7dc662ca6707682a676f4964b15e61ac.tar.gz
Wait up to 30 seconds on "stop" to avoid errors.
The fail2ban server can take several seconds to shut down. This can make Gentoo's start-stop-service time out and decide that stopping has failed, even if it actually succeeds a few seconds later. The default timeout for start-stop-service if --retry is not specified appears to be 5 seconds. Increase that to 30 seconds to be sure that if fail2ban-server is going to be able to stop, it has time to do so.
Diffstat (limited to 'files')
-rwxr-xr-xfiles/gentoo-initd2
1 files changed, 1 insertions, 1 deletions
diff --git a/files/gentoo-initd b/files/gentoo-initd
index c5b5b702..c4d8675c 100755
--- a/files/gentoo-initd
+++ b/files/gentoo-initd
@@ -41,7 +41,7 @@ start() {
stop() {
ebegin "Stopping fail2ban"
- start-stop-daemon --stop --pidfile /var/run/fail2ban/fail2ban.pid \
+ start-stop-daemon --stop --pidfile /var/run/fail2ban/fail2ban.pid --retry 30 \
-- ${FAIL2BAN} stop
eend $? "Failed to stop fail2ban"
}