On Wed, Jun 24, 2015 at 8:53 AM, Chad <ccolu...@gmail.com> wrote: > Killermoehre, > Thank you for your time and reply. > > I intend to do exactly that when I start using systemd (I am still using > init.d at the moment). In fact I have already suggested that very thing on > the fail2ban mailing list so that can add it to the tree and no custom rule > is needed. To my knowlage there is not a built in/standard way to tie > init.d/iptables to init.d/fail2ban. > > The test for the chains existence is still needed in case the chain is > removed by other means (like a manual delete from the cli). > I have found that I can trust nothing and that I should check/test > everything :) when I think something is impossible or so unlikely that it > will "never happen to me" it inevitably is a problem at the worst possible > moment. I bet some of you know what I mean. > > ^C >
I think the best for you will be to read "The systemd for Administrators Blog Series", which is a section at http://www.freedesktop.org/wiki/Software/systemd/ It explains for example how to convert a sysv init script to a systemd service file, what are the changes regarding configuration files with systemd, how to improve the security of your services, analyze the startup,... It will help for the transition from sysv to systemd. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
