From: Pablo Neira Ayuso <pablo@netfilter.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.1 release
Date: Mon, 8 Oct 2012 14:15:35 +0200 [thread overview]
Message-ID: <20121008121535.GA27399@1984> (raw)
[-- Attachment #1: Type: text/plain, Size: 354 bytes --]
Hi!
The Netfilter project proudly presents:
ulogd 2.0.1
This releases includes support for the nfacct extended iptables
accounting infrastructure.
See ChangeLog that comes attached to this email for more details.
You can download it from:
http://www.netfilter.org/projects/ulogd/downloads.html
ftp://ftp.netfilter.org/pub/ulogd/
Have fun!
[-- Attachment #2: changes-ulogd-2.0.1.txt --]
[-- Type: text/plain, Size: 980 bytes --]
Eric Leblond (6):
NFCT: fix crash in polling mode if used by two stacks
nfacct: add variable to not zero counter after read
pgsql schema: add nfacct table
pgsql schema: fix timestamp default value
pgsql: only disable key if it starts with underscore
nfacct: add timestamp option
Michael Tremer (1):
sqlite3: Add more logging if database initialization fails.
Pablo Neira Ayuso (9):
src: add ULOGD_DTYPE_SUM for nfacct-based accounting
output: XML: support for NFACCT input plugin
output: XML: display time for NFACCT
input: NFCT: fix compilation warning with gcc-4.7
src: fix version that -V displays
ulogd.conf: slightly expand documentation on zerocounter option for nfacct
filter: IP2HBIN: fix compilation warning with gcc-4.7
src: update copyright and authors information
bump version to 2.0.1
Thomas Jarosch (1):
ipfix: fix bracket imbalance if IPPROTO_SCTP is defined
reply other threads:[~2012-10-08 12:15 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=20121008121535.GA27399@1984 \
--to=pablo@netfilter.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).