From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: "Anthony Tonizzo" <atonizzo@gmail.com>
Cc: "eCos Disuss" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: Idle timeout and maximum # of sockets for athttpd
Date: Thu, 13 Dec 2007 15:33:00 -0000 [thread overview]
Message-ID: <c09652430712130714x3a8c261bvaf02948b8f0a1dda@mail.gmail.com> (raw)
In-Reply-To: <b437ec690712130708v1743304aof8220a664edc961@mail.gmail.com>
[the awful truth deleted]
Now I understand the awful truth. I wonder if there is anything that
could be done
to clue other athttpd users onto that they need to increase # of
sockets to avoid
the waiting problem....
--
Øyvind Harboe
http://www.zylin.com - eCos ARM & FPGA developer kit
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-12-13 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 14:33 [ECOS] " Øyvind Harboe
2007-12-13 15:24 ` [ECOS] " Anthony Tonizzo
2007-12-13 15:33 ` Øyvind Harboe [this message]
2007-12-17 16:03 ` Tom Deconinck
-- strict thread matches above, loose matches on Subject: below --
2007-12-12 15:50 Anthony Tonizzo
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=c09652430712130714x3a8c261bvaf02948b8f0a1dda@mail.gmail.com \
--to=oyvind.harboe@zylin.com \
--cc=atonizzo@gmail.com \
--cc=ecos-discuss@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).