github
/
fail2ban
mirror of https://github.com/fail2ban/fail2ban
1
0
Fork 0
Code Issues Releases Wiki Activity

fresh changes I forgotten to submit :-/

debian-releases/etch
Yaroslav Halchenko 2005-09-11 19:22:54 +00:00
parent 12ddba6cf2
commit f0e4ef017c
2 changed files with 44 additions and 46 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
config/debian-initd
View File

@ -40,11 +40,6 @@ case "$1" in
echo "$NAME."
;;
restart|force-reload)
#
# If the "reload" option is implemented, move the "force-reload"
# option to the "reload" entry above. If not, "force-reload" is
# just the same as "restart".
#
echo -n "Restarting $DESC: "
( $0 stop )
sleep 1

7
debian/README.Debian vendored
View File

@ -15,8 +15,11 @@ fail2ban with apache, please enable apache section manually in
/etc/fail2ban.conf.
Currently no checks if an iptables queue generated at the beginning
(fail2ban-http and fail2ban-ssh) exists. So if your firewall resets
the iptable rules -- it is your responsibility to restart fail2ban.
(fail2ban-http and fail2ban-ssh) exists. So if your firewall resets the iptable
rules -- it is your responsibility to restart fail2ban. Also you can
augment fwban and fwunban rules and include as first lines full
definitions of fwstart. That is nasty solution and probably it will get
resolved in the future.
See TODO.Debian for more details, as well as the Debian Bug
Tracking system.