FAIL2BAN-TESTCASES(1)

πŸ’– FAIL2BAN-TESTCASES πŸ’–

okay so bestie, welcome to fail2ban-testcases β€” that's the manual page for it, section 1, and honestly it's giving "little script that could" energy. it's the test runner for Fail2Ban, and i'm gonna walk you through every single flag like we're ranking them in the group chat. no skips, no cap 🫢


✨ NAME ✨

fail2ban-testcases β€” run Fail2Ban unit-tests. that's it, that's the whole job. she runs the tests, she slays, she leaves πŸ’…

🌸 SYNOPSIS 🌸

fail2ban-testcases [OPTIONS] [regexps]

so you call her, you can throw some OPTIONS at her, and you can optionally hand her a bunch of regexps to pick which tests get the spotlight πŸ‘‘

πŸ¦‹ DESCRIPTION πŸ¦‹

literally just: a script to run the Fail2Ban tests battery. that's the entire description, the manpage said so, and i respect the minimalism honestly. she's not here to explain herself, she's here to run the whole test battery and report back πŸ”₯

πŸŽ€ OPTIONS πŸŽ€

  • --version β€” show the program's version number and exit. quick little "who am i" moment, then she's out πŸšͺ
  • -h, --help β€” show this help message and exit. your classic escape hatch, iconic, no notes πŸ’–
  • *-l *LOG_LEVEL, --log-level=LOG_LEVEL β€” sets the log level for the logger to use while the tests are running. pick how chatty the logs are during the run πŸ—£οΈ
  • -v β€” increase verbosity. one -v more, one -v more… she gets louder, bestie πŸ“’
  • *--verbosity=VERBOSITY* β€” set the numerical level of verbosity, and the range is 0..4. so like, dial it in exactly instead of spamming -v 🎚️
  • --log-direct β€” prevents lazy logging inside tests. no lazy logging allowed in this house, we log with intention ✨
  • -n, --no-network β€” do not run tests that require the network. perfect for when the wifi is being a whole situation πŸ™ˆ
  • -m, --memory-db β€” run the database tests using memory instead of a file. fast, tidy, no file mess 🌈
  • -f, --fast β€” try to increase the speed of the tests by decreasing the wait intervals and using the memory database. the zoomies flag πŸƒβ€β™€οΈπŸ’¨
  • -i, --ignore β€” negate the [regexps] filter, so it ignores the tests matching the regexps you specified. flip the vibe check: same filter, opposite meaning πŸ”„
  • -t, --log-traceback β€” enrich log messages with compressed tracebacks. more context in the logs, but squeezed 🧚
  • --full-traceback β€” either to make the tracebacks full, not compressed (which is the default). so like, uncompressed and unfiltered, the whole dramatic saga πŸ’€
ngl the -i/--ignore one is the sneaky one β€” it doesn't add a filter, it negates the [regexps] filter you passed. read it twice, bestie, i'm not kidding πŸ™

⭐ SEE ALSO ⭐

go read those too, they're the rest of the friend group 🫢


and that's the page, bestie!! πŸŽ‰ this was fail2ban-testcases version 1.1.1, dated August 2026, and yeah β€” she's short, she's sweet, she runs the whole tests battery and she does it with main character energy πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from