From: "Pito Breizh" <pito_breizh@hotmail.com>
To: netfilter@lists.netfilter.org
Subject: Memory leak problem
Date: Thu, 07 Nov 2002 07:52:51 +0000 [thread overview]
Message-ID: <F162SYe4nhrKtzcbLDi0000031a@hotmail.com> (raw)
Hello,
I've got a problem of memory leak with iptables. I'm using iptables
1.2.7a. I've linked libiptc.a and iptables.o with my application.
I'm setting up some NAT rules by using do_command and iptc_commit
functions.
I've seen a mail on netfilter-devel list (dated of 2 september) dealing
with this problems. Here is this mail :
>You expect the iptables source components to be more than a short->running
>one-shot application; you expect them to be usable in a library in a
>longer-running process. That expectation is wrong, the current userlevel
>iptables source was not designed with that goal in mind.
>This is currently tackled by some developers (not me), who are working
>on an all-new userlevel and user/kernel interface that _is_ designed
>to support efficient use from many different userlevel applications.
>However, as far as I know, this reimplementation is currently not
>in a form that you may use.
>best regards
> Patrick
First of all, I would want to know if the developers team in charge of
the developement of the new userlevel interface is on this list?
Secondly, are there news about this subject ? If developement's
resources are needed, perhaps I can help !
Best regards,
Mickael
_________________________________________________________________
MSN Messenger : discutez en direct avec vos amis !
http://www.msn.fr/msger/default.asp
next reply other threads:[~2002-11-07 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 7:52 Pito Breizh [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-27 16:59 Memory leak problem Jean Cantarutti
2002-09-27 17:05 ` Anders Fugmann
2002-09-27 16:56 Jean Cantarutti
2002-09-27 15:03 Jean Cantarutti
2002-09-27 16:07 ` Anders Fugmann
2002-09-27 16:33 ` Antony Stone
2002-09-27 16:51 ` Anthony Liu
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=F162SYe4nhrKtzcbLDi0000031a@hotmail.com \
--to=pito_breizh@hotmail.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