From: Eric Leblond <eric@regit.org>
To: netfilter-devel@vger.kernel.org
Cc: netdev@vger.kernel.org, netfilter@vger.kernel.org,
netfilter-announce@lists.netfilter.org, lwn@lwn.net
Subject: [ANNOUNCE] ulogd 2.0.4 release
Date: Tue, 15 Apr 2014 09:56:30 +0200 [thread overview]
Message-ID: <1397548590.18685.2.camel@ice-age2.regit.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 755 bytes --]
Hi!
The Netfilter project proudly presents:
ulogd 2.0.4
ulogd is a userspace logging daemon for netfilter/iptables related
logging. This includes per-packet logging of security violations,
per-packet logging for accounting, per-flow logging and flexible
user-defined accounting.
ulogd 2.0.4 features a new JSON output plugin allowing easy integration
with log management systems.
See ChangeLog that comes attached to this email for more details.
Thanks to Gustavo Zacarias and Ken-ichirou Matsuzawa for their
contributions to this release of ulogd.
You can download it from:
http://www.netfilter.org/projects/ulogd/downloads.html
ftp://ftp.netfilter.org/pub/ulogd/
Have fun!
--
Eric Leblond <eric@regit.org>
[-- Attachment #1.2: changes-ulogd-2.0.4.txt --]
[-- Type: text/plain, Size: 747 bytes --]
Eric Leblond (13):
nacct: fix format warning
util: fix warning on format string
db: set ring default size to 0
db: cancel injection thread when terminating
db: don't loose one packet on reconnect
store Common Information Model name in ulogd key
json: introduce new JSON output plugin
ulogd: avoid potential double print of message
ulogd: add carriage return as separator
nfct: use start timestamp if provided
json: use packet timestamp if available
printpkt: oob.time.sec was not used
Set release number to 2.0.4.
Gustavo Zacarias (1):
ulogd: use AC_SEARCH_LIBS for libpthread
Ken-ichirou MATSUZAWA (1):
ulogd: fix loglevel handling
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 173 bytes --]
reply other threads:[~2014-04-15 7:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1397548590.18685.2.camel@ice-age2.regit.org \
--to=eric@regit.org \
--cc=lwn@lwn.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-announce@lists.netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).