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

21 lines
461 B
Plaintext
Raw Normal View History

Create fail2ban.upstart Add Upstart job.
2014-04-11 15:50:55 +00:00
description "fail2ban - ban hosts that cause multiple authentication errors"
A few final touches on the Upstart job (a) use static-network-up, since it is more generic than the started networking event (b) do not hook into network deconfiguration to speed up shutdown (c) expect fork, per the use of the "-f" option (d) use a variable for the run directory to make changing it simpler (e) handle the situation of a left over socket file (f) use the -f option to be able to track the PID
2014-04-23 04:55:51 +00:00
start on filesystem and static-network-up
stop on runlevel [016]
Create fail2ban.upstart Add Upstart job.
2014-04-11 15:50:55 +00:00
A few final touches on the Upstart job (a) use static-network-up, since it is more generic than the started networking event (b) do not hook into network deconfiguration to speed up shutdown (c) expect fork, per the use of the "-f" option (d) use a variable for the run directory to make changing it simpler (e) handle the situation of a left over socket file (f) use the -f option to be able to track the PID
2014-04-23 04:55:51 +00:00
expect fork
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
respawn
A few final touches on the Upstart job (a) use static-network-up, since it is more generic than the started networking event (b) do not hook into network deconfiguration to speed up shutdown (c) expect fork, per the use of the "-f" option (d) use a variable for the run directory to make changing it simpler (e) handle the situation of a left over socket file (f) use the -f option to be able to track the PID
2014-04-23 04:55:51 +00:00
env RUNDIR=/var/run/fail2ban
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
pre-start script
A few final touches on the Upstart job (a) use static-network-up, since it is more generic than the started networking event (b) do not hook into network deconfiguration to speed up shutdown (c) expect fork, per the use of the "-f" option (d) use a variable for the run directory to make changing it simpler (e) handle the situation of a left over socket file (f) use the -f option to be able to track the PID
2014-04-23 04:55:51 +00:00
test -d $RUNDIR || mkdir -p $RUNDIR
test ! -e $RUNDIR/fail2ban.sock || rm -f $RUNDIR/fail2ban.sock
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
end script
A few final touches on the Upstart job (a) use static-network-up, since it is more generic than the started networking event (b) do not hook into network deconfiguration to speed up shutdown (c) expect fork, per the use of the "-f" option (d) use a variable for the run directory to make changing it simpler (e) handle the situation of a left over socket file (f) use the -f option to be able to track the PID
2014-04-23 04:55:51 +00:00
exec /usr/bin/fail2ban-client -f -x start
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
Update Upstart job: uses stop command in pre-stop, removes PID file in post-stop
2014-04-19 22:10:19 +00:00
pre-stop exec /usr/bin/fail2ban-client stop
A few final touches on the Upstart job (a) use static-network-up, since it is more generic than the started networking event (b) do not hook into network deconfiguration to speed up shutdown (c) expect fork, per the use of the "-f" option (d) use a variable for the run directory to make changing it simpler (e) handle the situation of a left over socket file (f) use the -f option to be able to track the PID
2014-04-23 04:55:51 +00:00
post-stop exec rm -f $RUNDIR/fail2ban.pid