mirror of https://github.com/fail2ban/fail2ban
a40245010f
* Robust startup: if iptables module gets fully initialized after startup of fail2ban, fail2ban will do "maxreinit" attempts to initialize its own firewall. It will sleep between attempts for "polltime" number of seconds (closes: #334272). * To overcome possible conflict with other firewall solutions and as a secondary solution for the bug 334272, fail2ban startup is moved during bootup to the latest (S99) sequenece position. That should not cause any discomfort I believe. |
||
---|---|---|
.. | ||
__init__.py | ||
configreader.py |