2022-10-17 08:40:09 +00:00
|
|
|
#!/bin/bash
|
2020-09-05 14:19:12 +00:00
|
|
|
|
2017-08-07 15:39:40 +00:00
|
|
|
# You cannot start fail2ban in some foreground mode and
|
|
|
|
# it's more or less important that docker doesn't kill
|
|
|
|
# fail2ban and its chilren if you stop the container.
|
|
|
|
#
|
|
|
|
# Use this script with supervisord and it will take
|
|
|
|
# care about starting and stopping fail2ban correctly.
|
|
|
|
#
|
|
|
|
# supervisord config snippet for fail2ban-wrapper:
|
|
|
|
#
|
|
|
|
# [program:fail2ban]
|
|
|
|
# process_name = fail2ban
|
|
|
|
# command = /path/to/fail2ban-wrapper.sh
|
|
|
|
# startsecs = 0
|
|
|
|
# autorestart = false
|
|
|
|
#
|
|
|
|
|
|
|
|
trap "/usr/bin/fail2ban-client stop" SIGINT
|
|
|
|
trap "/usr/bin/fail2ban-client stop" SIGTERM
|
|
|
|
trap "/usr/bin/fail2ban-client reload" SIGHUP
|
|
|
|
|
|
|
|
/usr/bin/fail2ban-client start
|
|
|
|
sleep 5
|
|
|
|
|
|
|
|
# wait until fail2ban is dead (triggered by trap)
|
2020-09-23 19:53:07 +00:00
|
|
|
while kill -0 "$(< /var/run/fail2ban/fail2ban.pid)"
|
2020-09-05 14:19:12 +00:00
|
|
|
do
|
2017-08-07 15:39:40 +00:00
|
|
|
sleep 5
|
|
|
|
done
|
|
|
|
|