From: Eric Leblond <eleblond@init-sys.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: logs
Date: 20 Jan 2003 08:57:11 +0100 [thread overview]
Message-ID: <1043049437.19763.4.camel@porky> (raw)
In-Reply-To: <1043048340.20296.0.camel@bigblue>
Le lun 20/01/2003 à 08:39, Paulo Andre a écrit :
> Would like to know some views on logging netfilter, is using ulogd
> better than log...???
ulogd depends on a daemon, and daemon can fails.
But, I never see this happen. So the main issue is not this one.
With ulogd you can log directly into a SQL database, and you've got at
least an interface (written in php) to analyse your logs :
http://home.regit.org/ulogd-php.html
(end of self ad)
An other avantage of ulogd is the fact that you can use different output
in the same type (file and sql for example). Furhtermore you can say how
many packet should be log at at time and that can help to avoid I/O
overload.
--
Eric Leblond
mail : eleblond@init-sys.com
next prev parent reply other threads:[~2003-01-20 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-20 7:39 logs Paulo Andre
2003-01-20 7:57 ` Eric Leblond [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-09 22:07 logs azeem ahmad
2004-04-09 22:24 ` logs Antony Stone
2004-04-09 22:26 ` logs Jeffrey Laramie
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=1043049437.19763.4.camel@porky \
--to=eleblond@init-sys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox