Sergey G. Brester

> f2b-screen-out.txt > That's the full screen out. No, it is not. As I requested more information, I was still speaking about `fail2ban.log`. Also if you starting fail2ban in foreground...

if the TZ (`GMT+1`) is your system time zone (note the sommer saving time) you don't need to parse it at all, it is enough to specify the datepattern matching...

> So for my understanding Fail2ban is using the Python strftime() function? fail2ban uses its own processing (a bit modified `strftime.TimeRE` with more optimal patterns), where pattern will be converted...

No idea it will be logged this way, but... please don't use capturing groups here, so because each letter is a token in regex, it is enough to change: ```diff...

Couldn't it be solved by this setting: ```diff - protocol = all + protocol = { tcp, udp } ``` ?

> except when two bans have the exact same time stamp. Although I understand the intention, I'd like to know, what exactly (error?) happens in this case.

No, I see what the PR does... I meant without the PR. Anyway I guess your original issue could be fixed easier using parameter `norestored = 1`. See https://github.com/fail2ban/fail2ban/issues/2129#issuecomment-391684114 for...

Ok, then I suggest to rewrite the PR adding parameter `norestored = 1`. This was designated exactly for such purposes.

> Do you still maintain older releases? If yes, this might be a good fix to add to those. No, I don't think @fail2ban/maintainers still hold on older releases... and...

Anyway I'll provide here the possible patch for 0.9 (a bit modified for simplification): ```diff -actionban = curl --fail --data-urlencode "server=" --data "apikey=" --data "service=" --data "ip=" --data-urlencode "logs=" --data...