From: Bryan Christ <bryan.christ@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: running out of file descriptors
Date: Sun, 15 Feb 2009 23:48:57 -0600 [thread overview]
Message-ID: <444391460902152148u11d4a973ka5a630898405d1c6@mail.gmail.com> (raw)
I am writing a multi-threaded application which services hundreds of
remote connections for data transfer. Several instances of this
program are run simultaneously. The problem is that whenever the
total number of active user connections (cumulative total of all open
sockets tallied from all process instances) reaches about 700 the
system appears to run out of file descriptors. I have tried raising
the open files limit via "ulimit -n" and by using the setrlimit()
facility. Neither of these seem to help. I am currently having to
limit the number of processes running on the system to 2 instances
allowing no more than 256 connections each. In this configuration the
sever will run for days without failure until I stop it. If I try to
add a third process or restart one of the process with a higher
connection limit, bad things will start happening at about 700 open
sockets.
Thanks in advance to anyone who can help.
--
Bryan
<><
next reply other threads:[~2009-02-16 5:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 5:48 Bryan Christ [this message]
2009-02-16 6:18 ` running out of file descriptors Joe Damato
2009-02-16 7:09 ` Bryan Christ
2009-02-16 13:01 ` Eric Bambach
2009-02-16 17:35 ` Bryan Christ
2009-02-16 21:43 ` Glynn Clements
2009-02-17 18:51 ` Bryan Christ
2009-02-18 7:07 ` Holger Kiehl
2009-02-16 13:06 ` Glynn Clements
2009-02-16 17:39 ` Bryan Christ
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=444391460902152148u11d4a973ka5a630898405d1c6@mail.gmail.com \
--to=bryan.christ@gmail.com \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).