Sergey G. Brester

Let us define the order of RFEs regarding the precedence questions by ourselves, please. There are several other open tasks and feature requests with higher or same priority, that I'd...

In https://github.com/fail2ban/fail2ban/issues/2256#issuecomment-439941726 I asked about 3 ways how it would "fixable". Well, not quite correct - https://github.com/fail2ban/fail2ban/issues/3027#issuecomment-846267332 could be another one. Which one would you prefer?

> If so, is there some way we can make sure all of the events are processed before deleting the watch? Sure, one can retard watch deletion a bit. Just...

> Same here. The "issue" is already confirmed... And as one can see still open (since there is no simple solution for that, because the warning is throwing from pyinotify...

> We received this warning as well in our logs. Is anyone working on a fix? It is just a warning (not error), and because you know now why it...

I have a small f2b-extenstion doing similar, but: - currently it works only with/over my observer module, what included in PR #716 (branch sebres:ban-time-incr); and makes sense only there, because...

@szepeviktor it is configurable, at the moment is possible: - custom command to tranfer a bulk stream to f2b-client on each target server; - ssh with public/private key (or without...

I think it could be done without (python) coding. Just adding filters, actions here and there. Yep, and have an endless cycle (as soon as each server forwards it further...

@szepeviktor Yes, of course it will work, but it is rather a workaround as solution. Think for example about of any registered server in cluster may be down or by...

It is still a separate branch, but I'll merge it to master now. And yes, it was not released in 25.01.