From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] multiple pings cause panic
Date: Mon, 19 Apr 2010 02:23:52 +0200 [thread overview]
Message-ID: <bd3b88825b4af6d308914bfb485c6efc@gmx.de> (raw)
In-Reply-To: <ae24cc03d1ed549c7f22fea9af04a950@kw.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
i dont think you need that. devip calls a protocol specific
garbage collector procedure that will close these hanging
connections for you if it runs out of connections.
/sys/src/9/ip/tcp.c:/^tcpgc
well, the test is a little bit more complicated as it takes
a minimum inactivity time into account.
made a patch that changes the panic into a print:
/n/sources/patch/devip-allconvused-panic
--
cinap
[-- Attachment #2: Type: message/rfc822, Size: 3087 bytes --]
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] multiple pings cause panic
Date: Sun, 18 Apr 2010 19:52:04 -0400
Message-ID: <ae24cc03d1ed549c7f22fea9af04a950@kw.quanstro.net>
On Sun Apr 18 16:41:17 EDT 2010, geoff@plan9.bell-labs.com wrote:
> There are limits on the number of concurrent conversations per
> protocol. For UDP, it's currently 1024, for TCP it's currently 1024
> on terminals and 4096 on cpu servers. For ICMP, it's currently 128;
> you may want to raise that. To find the current limits,
>
> grep '>nc = ' /sys/src/9/ip/*.c
it's surprisingly easy to burn through connections since connections
can hang out in Finwait2 for a long time, burning up packets and
connections:
; cpu -c 'cd /net.alt/tcp; x=1??? echo $x($#x)'
1175
i haven't had time to take a look at this issue, but i wonder if acks
during Finwait2 are resetting the timer. this is definately related
to smtp &/| pop.
i sometimes use this script as hostowner to clear out these
connections
x=`{grep -l Finwait2 */status|sed 's:/status::g'}
for(i in $x)
if(~ `{cat $i^/local} *!110 *!25)
>$i^/ctl echo hangup
- erik
next prev parent reply other threads:[~2010-04-19 0:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 19:36 James Chapman
2010-04-18 20:32 ` erik quanstrom
2010-04-18 20:54 ` James Chapman
2010-04-18 21:19 ` erik quanstrom
2010-04-18 20:39 ` geoff
2010-04-18 23:52 ` erik quanstrom
2010-04-19 0:23 ` cinap_lenrek [this message]
2010-04-19 0:27 ` erik quanstrom
2010-04-19 1:19 ` cinap_lenrek
2010-04-19 1:27 ` andrey mirtchovski
2010-04-19 2:53 ` erik quanstrom
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=bd3b88825b4af6d308914bfb485c6efc@gmx.de \
--to=cinap_lenrek@gmx.de \
--cc=9fans@9fans.net \
/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).