fail2ban/files
Michael Orlitzky e6a9f109c5 files/fail2ban-openrc.init: force the socket location in the service script.
The socket location needs to be set in the service script for the same
reason that the PID file location does: because the service script is
taking responsibility for ensuring that its parent directory exists
and has the correct permissions. We can't do that if the end user is
allowed to move the PID file or socket somewhere else (without parsing
the config file, which has other security implications).
2021-05-14 07:50:28 -04:00
..
cacti
logwatch
monit
nagios
bash-completion added new logtarget "SYSOUT" to log from fail2ban working in foreground as systemd-service (in opposite to "STDOUT" don't log time-stamps). 2017-11-26 23:03:29 +01:00
debian-initd
fail2ban-logrotate
fail2ban-openrc.conf files/fail2ban-openrc.conf: add back the "-x" example. 2021-05-14 07:38:00 -04:00
fail2ban-openrc.init files/fail2ban-openrc.init: force the socket location in the service script. 2021-05-14 07:50:28 -04:00
fail2ban-tmpfiles.conf
fail2ban.service.in added new logtarget "SYSOUT" to log from fail2ban working in foreground as systemd-service (in opposite to "STDOUT" don't log time-stamps). 2017-11-26 23:03:29 +01:00
fail2ban.upstart
gen_badbots
ipmasq-ZZZzzz_fail2ban.rul
macosx-initd
redhat-initd
solaris-fail2ban.xml
solaris-svc-fail2ban
suse-initd