Timeline for Get Fail2Ban To Check findtime Every X Minutes
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 24, 2016 at 6:22 | answer | added | Alexis Wilke | timeline score: 17 | |
| Oct 20, 2016 at 10:29 | answer | added | andreatsh | timeline score: 1 | |
| Oct 14, 2016 at 3:09 | comment | added | Michael Hampton | findtime is the interval in which maxretry matches must occur for the ban to trigger. The logs are read as they're written to disk. You seem to be asking to slow that down. | |
| Oct 14, 2016 at 2:54 | comment | added | DomainsFeatured | Hi Michael, thanks for the question. I was under the impression that Fail2Ban checks logs at the same amount set by findtime. If this is not the case, do you know where to set the time interval for Fail2Ban to check a log? Also, please support the question with a vote if I provided a proper clarification. Thanks :-) | |
| Oct 13, 2016 at 17:48 | comment | added | Michael Hampton | fail2ban "checks" every time it processes a log entry. So I don't understand your question. What is it you want? | |
| Oct 13, 2016 at 15:05 | history | asked | DomainsFeatured | CC BY-SA 3.0 |