public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tad <ecos_removethispart@ds3switch.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: Re: accept() FreeBSD hangs when out of resources
Date: Tue, 12 Jun 2007 04:05:00 -0000	[thread overview]
Message-ID: <466DE575.9010406@ds3switch.com> (raw)
In-Reply-To: <20070611230045.GI26816@lunn.ch>

Andrew Lunn wrote:
> What i would ideally like is a test case we can add to the standard
> tests. The test case should fail now, but once we have fix the problem
> we can keep the test case for regression tests.

16 rapid http POSTS to any ATHTTP server compiled with 16 max sockets 
should lock the server up forever (as long as they're 
<CYG_HTTPD_SOCKET_IDLE_TIMEOUT(300) secs so the TCP conns stay in 
ESTABLISHED rather than TIMED_WAIT)

FWIW, I raised the both MAX file NFD, NFILES? while keeping the 
MAX_SOCKETS the same with no change.

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2007-06-11 23:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 23:15 [ECOS] " Tad
2007-06-12  3:51 ` Andrew Lunn
2007-06-12  3:57   ` Tad
2007-06-12  6:54     ` Andrew Lunn
2007-06-12 15:37       ` Tad
2007-06-12 15:49         ` Lars Povlsen
2007-06-12 16:08       ` [ECOS] listen (x, 0) on new TCP incoming connections doesn't stop select()/accept() Tad
2007-06-12  4:05   ` Tad [this message]
2007-06-12 11:06     ` [ECOS] Re: Re: accept() FreeBSD hangs when out of resources Andrew Lunn
2007-06-12 11:19       ` Andrew Lunn
     [not found]         ` <466F2FC7.8060704@ds3switch.com>
2007-06-13  0:09           ` [ECOS] "Fix" for atHTTP and HTTP socket requirements with mozilla POSTS Tad

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=466DE575.9010406@ds3switch.com \
    --to=ecos_removethispart@ds3switch.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).