5 ms·
systemd itself provides the functionality to run commands at points during the lifecycle of a service[1]. As for the people in mixed environments, you can forw
by dignan 13y ago
systemd itself provides the functionality to run commands at points during the lifecycle of a service[1]. As for the people in mixed environments, you can forward journald to syslog [2].
[1] http://www.freedesktop.org/software/systemd/man/systemd.service.html http://www.freedesktop.org/software/systemd/man/systemd.serv...
[2] http://www.freedesktop.org/software/systemd/man/journald.conf.html http://www.freedesktop.org/software/systemd/man/journald.con...
- Sanddancer 13y agoThat's a tiny sliver of what you can do with syslog piping. For example, fail2ban works by piping the contents of the auth stream of syslog -- usually also put into auth.log -- into a script that monitors for bruteforce attempts. This kind of reactivity is a lot harder on journald configurations.
- ibotty 13y agoehm. no. it can just stream the output of `journalctl -f`. it can filter even better than before, because fail2ban usually does not care about everything in `auth.log`. i guess i don't see the problem.
- bkor 13y agoThere have been various tools which have done this. And a lot had huge security bugs. Despite what you claim, this is also easily doable with journal plus similar solutions are available for journal.