github
/
fail2ban
mirror of https://github.com/fail2ban/fail2ban
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated Developing Regex in Fail2ban (markdown)

master
Egbert 2020-09-30 18:41:24 -04:00
parent f368eea103
commit ec1e2265d8
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Developing-Regex-in-Fail2ban.md

@ -126,7 +126,7 @@ whose output shows '`[6]`' lines that have matched the date timestamp at the beg
NOTE: Common `rsyslog` syslog daemon may output regular `datepattern` or high-precision `datepattern` (via `$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat` setting in `/etc/rsyslog.conf`) and fail2ban `datepattern` gets both of these date format right.
In the rare event (and sad case) of '`[0]`' match for a date pattern hit, you can develop a new `datepattern by usng the '`--VD`' option along with '`-l HEAVYDEBUG`' option in your `fail2ban-regex`. Having a [0] means you are dealing with a log text whose `datepattern` that fail2ban has never dealt with before; you’ll need to craft your own `datepattern`.
In the rare event (and sad case) of '`[0]`' match for a date pattern hit, you can develop a new `datepattern` by usng the '`--VD`' option along with '`-l HEAVYDEBUG`' option in your `fail2ban-regex`. Having a [0] means you are dealing with a log text whose `datepattern` that fail2ban has never dealt with before; you’ll need to craft your own `datepattern`.
Such unknown `datepattern` shall be a subject for another blog, not here.