On 2013-11-22 15:36:56, Yaroslav Halchenko wrote:
> well -- is that a part of any convention (besides at your work? ;-) )
>
> I do not see in my logs any priority= listed while some other daemons do
> prepend with level:
You are absolutely correct that our (weird) configuration is not
a good argu
btw -- here it will be
https://github.com/fail2ban/fail2ban/pull/451
PS I removed loglevel completely from msg to syslog
--
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Senior Research Associate, Psychological and Brain Sciences Dept.
Dar
On Fri, 22 Nov 2013, Allan Wind wrote:
> On 2013-11-22 13:46:50, Yaroslav Halchenko wrote:
> > what about making it even better:
> > formatter = logging.Formatter("%(name)s[%(process)d]: %(levelname)-7s
> > %(message)s")
> > so we report the pid as well, stay together with the name while still
On 2013-11-22 13:46:50, Yaroslav Halchenko wrote:
> what about making it even better:
>
> formatter = logging.Formatter("%(name)s[%(process)d]: %(levelname)-7s
> %(message)s")
> so we report the pid as well, stay together with the name while still keeping
> indentation for the levelname conssite
Hi Allan,
got it... indeed we should stay compliant
what about making it even better:
formatter = logging.Formatter("%(name)s[%(process)d]: %(levelname)-7s
%(message)s")
so we report the pid as well, stay together with the name while still keeping
indentation for the levelname conssitent for e
Package: fail2ban
Version: 0.8.6-3wheezy2
Severity: minor
I configured fail2ban to log to syslog and would get events like these:
2013-11-21T04:24:01.077+00:00 pawan fail2ban.filter : INFO Log
rotati
6 matches
Mail list logo
