see changelog

debian-releases/etch
Yaroslav Halchenko 2005-09-09 18:57:53 +00:00
parent ea7f23e534
commit 0415da9229
3 changed files with 43 additions and 15 deletions

View File

@ -30,14 +30,13 @@ case "$1" in
start) start)
echo -n "Starting $DESC: " echo -n "Starting $DESC: "
[ -f $PIDFILE ] && [ ! -d /proc/`cat $PIDFILE` ] && rm -f $PIDFILE [ -f $PIDFILE ] && [ ! -d /proc/`cat $PIDFILE` ] && rm -f $PIDFILE
start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid \ start-stop-daemon --start --quiet --pidfile $PIDFILE \
-b --exec $DAEMON -- $DAEMON_OPTS -b --exec $DAEMON -- $DAEMON_OPTS
echo "$NAME." echo "$NAME."
;; ;;
stop) stop)
echo -n "Stopping $DESC: " echo -n "Stopping $DESC: "
start-stop-daemon --stop --quiet --pidfile /var/run/$NAME.pid start-stop-daemon --stop --quiet --pidfile $PIDFILE
# rm -f $PIDFILE # now is removed by fail2ban itself
echo "$NAME." echo "$NAME."
;; ;;
restart|force-reload) restart|force-reload)
@ -51,10 +50,27 @@ case "$1" in
sleep 1 sleep 1
$0 start $0 start
;; ;;
status)
echo -n "Status of $DESC: "
if [ ! -e "$PIDFILE" ]; then
echo "$NAME is not running."
exit 3
fi
if [ ! -r "$PIDFILE" ]; then
echo "$PIDFILE not readable, status of $NAME unknown."
exit 4
fi
if [ -d /proc/`cat "$PIDFILE"` ]; then
echo "$NAME is running."
exit 0
else
echo "$NAME is not running but $PIDFILE exists."
exit 1
fi
;;
*) *)
N=/etc/init.d/$NAME N=/etc/init.d/$NAME
# echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2 echo "Usage: $N {start|stop|restart|force-reload|status}" >&2
echo "Usage: $N {start|stop|restart|force-reload}" >&2
exit 1 exit 1
;; ;;
esac esac

View File

@ -14,7 +14,11 @@ Only handling of ssh files is enabled by default. If you want to use
fail2ban with apache, please enable apache section manually in fail2ban with apache, please enable apache section manually in
/etc/fail2ban.conf. /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.
See TODO.Debian for more details, as well as the Debian Bug See TODO.Debian for more details, as well as the Debian Bug
Tracking system. Tracking system.
-- Yaroslav O. Halchenko <debian@onerussian.com>, Thu Aug 18 20:53:58 2005 -- Yaroslav O. Halchenko <debian@onerussian.com>, Fri Sep 9 14:55:29 2005

10
debian/changelog vendored
View File

@ -1,3 +1,12 @@
fail2ban (0.5.2-5) unstable; urgency=low
* Included a patch from Stephen Gildea to provide "status" report by
init.d script
* Included a note in README.Debian regarding the fail2ban iptable's
chains
-- Yaroslav Halchenko <debian@onerussian.com> Fri, 9 Sep 2005 14:52:24 -0400
fail2ban (0.5.2-4) unstable; urgency=low fail2ban (0.5.2-4) unstable; urgency=low
* Format of SYSLOG entries is up to the standard now * Format of SYSLOG entries is up to the standard now
@ -53,4 +62,3 @@ fail2ban (0.4.1-1) unstable; urgency=low
* First upstream release of a Debian package * First upstream release of a Debian package
-- Yaroslav Halchenko <debian@onerussian.com> Mon, 04 Jul 2005 11:47:23 +0300 -- Yaroslav Halchenko <debian@onerussian.com> Mon, 04 Jul 2005 11:47:23 +0300