Thank you indeed that sounds like a reasonable solution to overcome the problem if exists on the system. Though, the reason why fail2ban became locale aware that on some boxes log files are stored using the locale other than engligh-based, that is why (I believe) fail2ban started to set its own locale to LC_ALL
Placing LC_ALL in defaults is a good solution for those who have system
logs stored in C locale, but I would not enable it by default since then
it would defeat the whole purpose of locale-awareness of fail2ban.
Proper solution would be to set it in the config file and make it
adjustable on per-section basis. The best solution would be to
guess timestamp format and the locale ;-)
One way or another, we will get it fixed soon
Meanwhile your solution is the best to overcome the problem, thanks
On Wed, 03 May 2006, Guido Bozzetto wrote:
> A working solution is to add LC_ALL=C to /etc/default/fail2ban
> configuration file:
> echo "LC_ALL=C" >> /etc/default/fail2ban
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
pgpenRMEP9EWi.pgp
Description: PGP signature
