From: Greg Stark <gsstark@mit.edu>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: gsstark@mit.edu, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.20-ac2 Memory Leak?
Date: 18 Mar 2003 18:46:31 -0500 [thread overview]
Message-ID: <87znns9r1k.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <1048030102.1521.77.camel@tux.rsn.bth.se>
Martin Josefsson <gandalf@wlug.westbo.se> writes:
> This can be the source of your problems, connections can get very long
> timeouts and stay in ip_conntrack.
Is there a way to list the connections and confirm this is the problem?
It seems it would require an awful lot of connections to consume megabytes of
memory.
Also, I've looked high and low and can't find this anywhere, how do i tune the
timeouts connections get? I have certain protocols that potentially receive
very little traffic and I want to make sure they don't time out.
--
greg
next prev parent reply other threads:[~2003-03-18 23:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 23:17 Gregory Stark
2003-03-18 23:28 ` Martin Josefsson
2003-03-18 23:46 ` Greg Stark [this message]
2003-03-18 23:53 ` Martin Josefsson
2003-03-19 0:05 ` Greg Stark
2003-03-19 14:55 ` Greg Stark
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=87znns9r1k.fsf@stark.dyndns.tv \
--to=gsstark@mit.edu \
--cc=gandalf@wlug.westbo.se \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®