[fx: tries installing fail2ban on clean system] You're right and my original description is wrong. /var/run/fail2ban gets created during install but if subsequently destroyed (as must have happened to me, oops, careless) it is not recreated on runtime. Will change description.
Bug still stands. (While we're on the subject of fail2ban bugs, could you have a look at bug #234122 and confirm if you agree? Ta.) ** Summary changed: - Installing fail2ban doesn't create /var/run/fail2ban directory + fail2ban doesn't recreate /var/run/fail2ban directory if destroyed ** Description changed: Binary package hint: fail2ban - Installing fail2ban 0.8.2-2 under Hardy doesn't create the directory - /var/run/fail2ban/ . As a result, the program cannot create it's .sock + Installing fail2ban 0.8.2-2 under Hardy create the directory + /var/run/fail2ban/ . + + However, if the directory is destroyed, it is not recreated when + fail2ban is restarted. As a result, the program cannot create it's .sock and .pid files in the default locations. This means it cannot run, and when run with /etc/init.d/fail2ban start simply reports "failed" or nothing at all. /etc/init.d/fail2ban status then says "fail2ban is not running" -- fail2ban doesn't recreate /var/run/fail2ban directory if destroyed https://bugs.launchpad.net/bugs/234076 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
