fail2ban/files/fail2ban.upstart

description "fail2ban - ban hosts that cause multiple authentication errors"

start on filesystem and started networking
stop on deconfiguring-networking

expect daemon
respawn

pre-start script
    [ -d /var/run/fail2ban ] || mkdir -p /var/run/fail2ban
end script

exec /usr/bin/fail2ban-client -x start

post-stop exec /usr/bin/fail2ban-client stop
Create fail2ban.upstart Add Upstart job. 2014-04-11 15:50:55 +00:00			`description "fail2ban - ban hosts that cause multiple authentication errors"`

			`start on filesystem and started networking`
			`stop on deconfiguring-networking`

Change Upstart job to track PID of the server This only works correctly if the client does not fork itself when starting the server (which forks twice further). 2014-04-19 21:12:20 +00:00			`expect daemon`
			`respawn`

			`pre-start script`
			`[ -d /var/run/fail2ban ] \|\| mkdir -p /var/run/fail2ban`
			`end script`

			`exec /usr/bin/fail2ban-client -x start`

Update fail2ban.upstart No longer directly exec the server, do not remove the PID file because it is unnecessary to do so. No longer respawns because Upstart can not track the process with the starter command. 2014-04-12 00:09:08 +00:00			`post-stop exec /usr/bin/fail2ban-client stop`