Sorry for the late response.
The suggested solution:
logrotate configuration must run 'fail2ban-client set logtarget
/var/log/fail2ban.log' instead of 'invoke-rc.d --quiet fail2ban reload'
Seems to be working as well.
I think will stick with it (but keep the socket under /var/run).
Thanks a lot!
--On Mittwoch, 9. September 2009 00:40 -0400 Yaroslav Halchenko
<deb...@onerussian.com> wrote:
btw -- does solution suggested in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537773
helps to resolve your issue as well?
On Tue, 08 Sep 2009, Yaroslav Halchenko wrote:
Hi Karsten,
Thanks for the follow up... can't say that I am too happy to receive it
though ;)
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
Mit freundlichen Gruessen,
Karsten Lindemann
--
ZYRES digital media systems GmbH
Eschersheimer Landstr. 5-7 60322 Frankfurt am Main
Mobil +49 (0)179 38 39 115
Phone +49 (0)69 98 55 99 - 0
Fax +49 (0)69 98 55 99 - 11
http://www.zyres.com
Firmensitz: Eschersheimer Landstr. 5-7 60322 Frankfurt am Main
Registergericht: Amtsgericht Frankfurt am Main, HRB 76374
Geschäftsführer: Martin Wepper, Sebastian Schirmer
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
