From: Patrick McHardy <kaber@trash.net>
To: Patrick McHardy <kaber@trash.net>,
Jan Engelhardt <jengelh@medozas.de>,
pablo@netfilter.org,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: nf_conntrack.acct has no effect
Date: Tue, 17 Mar 2009 14:02:54 +0100 [thread overview]
Message-ID: <49BF9F7E.3090208@trash.net> (raw)
In-Reply-To: <20090317082425.GA25491@mail.eitzenberger.org>
Holger Eitzenberger wrote:
> On Mon, Mar 16, 2009 at 05:56:52PM +0100, Patrick McHardy wrote:
>
>> Currently the default is set based on the old config option.
>> When unset, no acct-extend is allocated for *new* conntracks.
>> The old ones that do have an acct-extend are still displayed.
>
> I think the current implementation is unfortunate, because the
> connbytes match auto-selects CONFIG_NF_CT_ACCT, and you end up having
> the message always and can't get rid of it other than patching
> it out.
Its only a compat option, it will get removed soon. 2.6.30 or 2.6.31
I'd say.
next prev parent reply other threads:[~2009-03-17 13:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 16:53 nf_conntrack.acct has no effect Jan Engelhardt
2009-03-16 16:56 ` Patrick McHardy
2009-03-16 18:01 ` Jan Engelhardt
2009-03-17 8:24 ` Holger Eitzenberger
2009-03-17 13:02 ` Patrick McHardy [this message]
2009-03-17 13:13 ` Krzysztof Oledzki
2009-03-17 13:31 ` Patrick McHardy
2009-03-17 13:32 ` Patrick McHardy
2009-03-17 13:50 ` Krzysztof Oledzki
2009-03-17 13:51 ` Patrick McHardy
2009-03-17 13:55 ` Krzysztof Oledzki
2009-03-17 13:57 ` Patrick McHardy
2009-03-17 14:18 ` Krzysztof Oledzki
2009-03-17 14:22 ` Patrick McHardy
2009-03-17 14:36 ` Krzysztof Oledzki
2009-03-17 14:38 ` Patrick McHardy
2009-03-17 13:11 ` Krzysztof Oledzki
2009-03-17 13:28 ` Jan Engelhardt
2009-03-17 13:52 ` Krzysztof Oledzki
2009-03-17 13:54 ` Patrick McHardy
2009-03-17 14:39 ` Jan Engelhardt
2009-03-17 14:41 ` Patrick McHardy
2009-03-17 15:41 ` Jan Engelhardt
2009-03-18 4:32 ` Patrick McHardy
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=49BF9F7E.3090208@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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.