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

22 lines
781 B
INI
Raw Normal View History

Add systemd unit file and tmpfiles.d configuration files
2013-03-15 20:37:11 +00:00
[Unit]
ENH: Add iptables and firewalld to "After" for systemd service file. Also remove no longer supported syslog.target. Closes #658
2014-03-22 17:28:49 +00:00
Description=Fail2Ban Service
Add documentation link to systemd service file So systemctl help fail2ban.service works Signed-off-by: Ruben Kerkhof <ruben@rubenkerkhof.com>
2014-03-24 14:20:49 +00:00
Documentation=man:fail2ban(1)
closes #2313: missing dependency to nftables.service
2019-01-06 16:03:09 +00:00
After=network.target iptables.service firewalld.service ip6tables.service ipset.service nftables.service
PartOf=iptables.service firewalld.service ip6tables.service ipset.service nftables.service
Add systemd unit file and tmpfiles.d configuration files
2013-03-15 20:37:11 +00:00
[Service]
systemd service update: - starting service in normal mode (without forking) - does not restart if service exited normally (exit-code 0, e.g. stopped via fail2ban-client) - does not restart if service can not start (exit-code 255, e.g. wrong configuration, etc.) - service can be additionally started/stopped with commands (fail2ban-client, fail2ban-server)
2016-11-22 10:14:27 +00:00
Type=simple
fail2ban.service systemd unit template: don't add user site directory to python system path (avoids accessing of `/root/.local` directory, prevents SE linux audit warning at daemon startup, gh-2688)
2020-04-15 15:35:04 +00:00
Environment="PYTHONNOUSERSITE=1"
amend to #2174 for fail2ban.service, fix legacy path, closes gh-2474
2019-07-17 11:38:42 +00:00
ExecStartPre=/bin/mkdir -p /run/fail2ban
- `files/fail2ban.service` renamed as template to `files/fail2ban.service.in`; - setup process generates `build/fail2ban.service` from `files/fail2ban.service.in` using distribution related bin-path; - bug-fixing by running setup with option `--dry-run` (note: specify option `--dry-run` before `install`, like `python setup.py --dry-run install`); - test cases extended to cover dry-run.
2017-08-23 10:55:36 +00:00
ExecStart=@BINDIR@/fail2ban-server -xf start
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 22:03:29 +00:00
# if should be logged in systemd journal, use following line or set logtarget to sysout in fail2ban.local
# ExecStart=@BINDIR@/fail2ban-server -xf --logtarget=sysout start
- `files/fail2ban.service` renamed as template to `files/fail2ban.service.in`; - setup process generates `build/fail2ban.service` from `files/fail2ban.service.in` using distribution related bin-path; - bug-fixing by running setup with option `--dry-run` (note: specify option `--dry-run` before `install`, like `python setup.py --dry-run install`); - test cases extended to cover dry-run.
2017-08-23 10:55:36 +00:00
ExecStop=@BINDIR@/fail2ban-client stop
ExecReload=@BINDIR@/fail2ban-client reload
amend to #2174 for fail2ban.service, fix legacy path, closes gh-2474
2019-07-17 11:38:42 +00:00
PIDFile=/run/fail2ban/fail2ban.pid
systemd service update: - starting service in normal mode (without forking) - does not restart if service exited normally (exit-code 0, e.g. stopped via fail2ban-client) - does not restart if service can not start (exit-code 255, e.g. wrong configuration, etc.) - service can be additionally started/stopped with commands (fail2ban-client, fail2ban-server)
2016-11-22 10:14:27 +00:00
Restart=on-failure
RestartPreventExitStatus=0 255
Add systemd unit file and tmpfiles.d configuration files
2013-03-15 20:37:11 +00:00
[Install]
Add After, PIDFile, and change WantedBy to multi-user.target in fail2ban.server
2013-04-17 15:27:06 +00:00
WantedBy=multi-user.target