I just spent 2 hours trying to figure out why fail2ban didn’t increment the ban count.

--- a/fail2ban/etc/fail2ban/jail.local
+++ b/fail2ban/etc/fail2ban/jail.local
@@ -1,6 +1,6 @@
 [DEFAULT]

-bantime.incremet     = true
+bantime.increment    = true
 bantime.rndtime      =
 bantime.maxtime      =
 bantime.factor       = 1

After I found that I seriously considered becoming a goose farmer.

  • frankenswine@lemmy.worldEnglish
    32·
    2 days ago

    happens to the best. if fail2ban were any more resiliently engineered it would have failed to start due to the error in the config file

    • Eager Eagle@lemmy.worldEnglish
      28·
      2 days ago

      This is such an underutilized and neglected behavior.

      The very least a config parser should do is to log a warning.

    • Pika@sh.itjust.worksEnglish
      3·
      1 day ago

      the amount of software I’ve used that lacks this type of system is aggravating. How hard is it to keep an object of property names, and if the name isn’t in it then it errors.

      this can be continued into command line as well. if flag -z doesn’t exist, you shouldn’t allow me to run a command with it. It’s clear I am trying to do something (incorrectly) thinking -z is something it isn’t, just error it and tell me that.