Re: fail2ban vs. syslogd compression (to be solved soon)

To: Maxim Kammerer <mk@antira.info>
Cc: debian-security@lists.debian.org
Subject: Re: fail2ban vs. syslogd compression (to be solved soon)
From: Justin Piszcz <jpiszcz@lucidpixels.com>
Date: Thu, 6 Sep 2007 08:26:51 -0400 (EDT)
Message-id: <[🔎] Pine.LNX.4.64.0709060826150.9298@p34.internal.lan>
In-reply-to: <[🔎] b290c833aa89938bd47c05e084b271b5@localhost>
References: <[🔎] b290c833aa89938bd47c05e084b271b5@localhost>



On Thu, 6 Sep 2007, Maxim Kammerer wrote:

Just to conclude the thread: I wrote to the author, Cyril Jaquier. This was
his answer:

<snip>
I have received a patch from Stephen Gram for this. I will review this
as soon as possible and will commit this to 0.8 branch. So it should be
available in the next 0.8 release.
</snip>

I have no clue what this patch looks like.

Maxim


--
To UNSUBSCRIBE, email to debian-security-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

I read in netbsd or freebsd (or maybe it was dragonfly) they have anoption to turn it off, this will be great if it is implemented in syslogdfor Linux!


Justin.

Reply to:

References:
- fail2ban vs. syslogd compression (to be solved soon)
  - From: Maxim Kammerer <mk@antira.info>

Prev by Date: fail2ban vs. syslogd compression (to be solved soon)
Next by Date: Re: fail2ban vs. syslogd compression (to be solved soon)
Previous by thread: fail2ban vs. syslogd compression (to be solved soon)
Next by thread: Re: fail2ban vs. syslogd compression (to be solved soon)
Index(es):
- Date
- Thread