On 2006-06-11 00:18:07 -0400, Yaroslav Halchenko wrote: > I'm not an expert in locales but I believe that there is something > subtle in en_DK locale and python's locale module. See bug 369689. I > didn't reassign and merge this one over to python2.3 so people hitting > it in fail2ban can easily find it to don't duplicate reports
You said in bug 369689: Sorry that I missed that indeed you have en_DK as the LANG locale. fail2ban doesn't try to verify it, it tries to use it while matching the time pattern, so it is not even fail2ban but rather using "time" library during the call date = list(time.strptime(value, self.timepattern)) Why does it used the locales to recognize the date? If they are used to get the date from the log files, this is incorrect, as each daemon may have its own locales (BTW, here they don't use en_DK, which is just a locale chosen from my own config as a user and I got the error when typing "/etc/init.d/fail2ban restart" after a su). If a daemon may use a non-C locale, then there should probably be new parameters in /etc/fail2ban.conf to select the locale for each daemon. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / SPACES project at LORIA
