All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mogens Valentin <monz@danbbs.dk>
To: netfilter@lists.netfilter.org
Subject: Re: Iptables logs on High bandwidth traffic network
Date: Thu, 05 May 2005 13:24:06 +0200	[thread overview]
Message-ID: <427A0256.5080709@danbbs.dk> (raw)
In-Reply-To: <Pine.LNX.4.58.0505051010140.21324@blackhole.kfki.hu>

Jozsef Kadlecsik wrote:
> On Thu, 5 May 2005, Taylor, Grant wrote:
> 
> 
>>>Why where a FIFO and a program which parses and transmit the data to
>>>another system any faster than syslog/syslog-ng/ulogd/etc? (Why reinvent
>>>the wheel?)
>>
>>It is my belief that Syslog and the mechanism that it uses to log is not
>>meant for extreme volume of login.  As I understand it Syslog will log
>>each and every individual packet that passes through the IPTables LOG
>>target individually, thus causing a write through the kernel in to
>>SysLog space and possibly to disk for a VERY small amount of data.
> 
> 
> That depends on how syslog is configured - you can easily disable syncing
> at every log event.

Yes, but doing so may cause loss of logging, or maybe it'll just delay 
some messages due to not sync'ing at once. Lack of experience here :p
I do use the non-sync feature to some extend; doesn't seem to cause too 
much delay, though.

-- 
Kind regards,
Mogens Valentin



  reply	other threads:[~2005-05-05 11:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04 12:45 Iptables logs on High bandwidth traffic network bharathi
2005-05-04 15:59 ` Taylor, Grant
2005-05-04 22:40   ` Mogens Valentin
2005-05-04 23:13     ` Taylor, Grant
2005-05-05  6:59       ` Jozsef Kadlecsik
2005-05-05  7:24         ` Taylor, Grant
2005-05-05  8:15           ` Jozsef Kadlecsik
2005-05-05 11:24             ` Mogens Valentin [this message]
2005-05-05 11:59               ` Jozsef Kadlecsik
2005-05-05  9:37         ` Mogens Valentin
2005-05-05 10:07           ` Jozsef Kadlecsik
2005-05-04 16:39 ` Jason Opperisano
2005-05-04 17:18 ` Steven M Campbell
2005-05-04 20:37 ` Jozsef Kadlecsik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=427A0256.5080709@danbbs.dk \
    --to=monz@danbbs.dk \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.