This bug was fixed in the package fail2ban - 0.8.2-3
---------------
fail2ban (0.8.2-3) unstable; urgency=low
* Changes propagated from upstream trunk (future 0.8.3):
- Fixed "fail2ban-client get <jail> logpath". Bug #1916986.
- Changed some log level.
- Added "Day/Month/Year Hour:Minute:Second" date template. Thanks to
Dennis Winter.
- Fixed PID file while started in daemon mode. Thanks to Christian
Jobic who submitted a similar patch (closes: #479703)
- Added gssftpd filter. Thanks to Kevin Zembower.
- Process failtickets as long as failmanager is not empty.
* Assure that /var/run/fail2ban exists upon start (LP: #222804, #223706)
-- Ubuntu Archive Auto-Sync <[EMAIL PROTECTED]> Wed, 07 May 2008
06:55:47 +0100
** Changed in: fail2ban (Ubuntu)
Status: New => Fix Released
--
fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
