fail2ban

Author	SHA1	Message	Date
Cameron Norman	2a14e48f0b	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-22 21:55:51 -07:00
Cameron Norman	39ad5b7474	Update Upstart job: uses stop command in pre-stop, removes PID file in post-stop	2014-04-19 15:10:19 -07:00
Cameron Norman	0ef5027234	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 14:12:20 -07:00
Cameron Norman	0c8e72f452	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-11 17:09:08 -07:00
Cameron Norman	4115b62a01	Update fail2ban.upstart It was actually a little problematic :)	2014-04-11 16:49:56 -07:00
Cameron Norman	5e3f5db8b7	Create fail2ban.upstart Add Upstart job.	2014-04-11 08:50:55 -07:00