FS#22926 - [fail2ban] Does not work if /var/run mounted on tmpfs

Attached to Project: Community Packages
Opened by Tim (tes) - Thursday, 17 February 2011, 14:14 GMT
Last edited by Jelle van der Waa (jelly) - Thursday, 29 December 2011, 08:45 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jelle van der Waa (jelly)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

When /var/run is mounted on tmpfs, obviously the fail2ban directory is not there on boot.

Creating this directory when the daemon starts (if necessary) fixes the problem.
This task depends upon

Closed by  Jelle van der Waa (jelly)
Thursday, 29 December 2011, 08:45 GMT
Reason for closing:  Fixed
Additional comments about closing:  re-open if the version from [community] doesn't work
Comment by Jelle van der Waa (jelly) - Sunday, 10 April 2011, 12:31 GMT
should be fixed in [testing]
Comment by maddog39 (maddog39) - Wednesday, 21 December 2011, 18:45 GMT
This bug has returned very recently with a change to initscripts it seems. Refer to the following forums thread:

https://bbs.archlinux.org/viewtopic.php?id=132153
Comment by Clément (cdemoulins) - Friday, 23 December 2011, 00:19 GMT
/var/run is linked to /run that is mount using tmpfs.
So after each reboot the directory must be recreated.

Loading...