** Changed in: fail2ban (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: fail2ban (Ubuntu Hardy)
Status: New => In Progress
--
[SRU] fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of U
ISSUE: fail2ban does not restart after reboot because of /var/run being
a tmpfs, so no pid file can be created. I have attached the debdiff
which fixes this issue. This has been backported from intrepid.
TEST CASE:
1. Install fail2ban
2. Reboot
3. Restart fail2ban after reboot see if it starts.
** Changed in: fail2ban (Ubuntu)
Status: Fix Released => Confirmed
--
fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
--
Ubuntu-server-bugs mailing
This is actually fixed in 0.8.2-3 in Intrepid, so I'm marking it as Fix
Released as per the bug triage process. If you want it in Hardy, someone
needs to add a milestone I think, and I don't know how to do that
** Changed in: fail2ban (Ubuntu)
Status: Confirmed => Fix Released
--
fail2ban
As Matt LaPlante pointed out above, this should be eligible for a SRU,
as the bug is a regression from a previous version
--
fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of Ubuntu
Server Team, which is a di
