From: Anders Fugmann <afu@fugmann.dhs.org>
To: Jean Cantarutti <jcantarutti@subtel.cl>, netfilter@lists.netfilter.org
Subject: Re: Memory leak problem
Date: Fri, 27 Sep 2002 19:05:36 +0200 [thread overview]
Message-ID: <3D948FE0.3050405@fugmann.dhs.org> (raw)
In-Reply-To: 7F2740B50D94FD4B9EAF9AAC33016C3C45383C@lascar
Jean Cantarutti wrote:
> Netfilter is the only proccess running in that machine (I think).
> kernel version: 2.4.18-3
> gcc version: 2.96
> Red Hat Linux 7.3 2.96-110
>
Please repeat how you observe the leak, and what tools you are using in
order to do so. Also give some printouts from the system, in order for
us to verify the leak.
Regards
Anders Fugmann
next prev parent reply other threads:[~2002-09-27 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 16:59 Memory leak problem Jean Cantarutti
2002-09-27 17:05 ` Anders Fugmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-07 7:52 Pito Breizh
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=3D948FE0.3050405@fugmann.dhs.org \
--to=afu@fugmann.dhs.org \
--cc=jcantarutti@subtel.cl \
--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