On 2006-05-31 1218, Yaroslav Halchenko wrote: > On Wed, 31 May 2006, Anders Breindahl wrote: > > On 2006-05-31 1032, Yaroslav Halchenko wrote: > > > Hi Anders, > > > > No, fail2ban doens't try every locale possible... you must have en_DK > > > setup somewhere... can you grep for it in your environment and simply in > > > /etc/ to figure it out? > > > No, I meant that fail2ban would like to ``verify'' a locale setting. The > > fact is, that I have set my system locale to en_DK (which should be > > stated under ``System information'' of the bug report). > > > Now, when fail2ban sees en_DK it refuses to do its job. That's the > > problem, AFAICT. > > Hi Anders, > > 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)) > > I believe this is where exception is originally thrown. > > Do you really have that locale installed correctly? > > Since you specified it to be used for LANG I assume that you have > installed it correctly (to reconfigure "dpkg-reconfigure locales" should > do it I believe) > > Otherwise (if everything is set correctly) it might be a bug of time > module then....
Native Dane, used that very same locale for all my systems untill UTF-8 came into my life. So I'd say that I'm confident that it's configured correctly. I have this working remedy of overwriting the LANG varible on the commandline, so I won't be investigating further. Now, however, it's known and you should be able to upstream the bug -- right? Regards, skrewz. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
