From: Eric Bambach <bot403@cisu.net>
To: Bryan Christ <bryan.christ@gmail.com>
Cc: Joe Damato <ice799@gmail.com>, linux-c-programming@vger.kernel.org
Subject: Re: running out of file descriptors
Date: Mon, 16 Feb 2009 07:01:13 -0600 [thread overview]
Message-ID: <200902160701.14982.eric@cisu.net> (raw)
In-Reply-To: <444391460902152309h179bd75agdded10ca6af135d@mail.gmail.com>
On Monday 16 February 2009 01:09:42 Bryan Christ wrote:
> On Mon, Feb 16, 2009 at 12:18 AM, Joe Damato <ice799@gmail.com> wrote:
> > On Sun, Feb 15, 2009 at 9:48 PM, Bryan Christ <bryan.christ@gmail.com>
wrote:
> >> 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
>
> It seems that would be the same as setting RLIMIT_NOFILE via
> setrlimt() or the same as using the userspace tool "ulimit -n". Am I
> wrong? Isn't this the same?
>
> >> 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.
> >
> > Have you tried editing /etc/security/limits.conf (or equivalent file
> > on your system) to increase the max number of open files?
> >
> > perhaps something like:
> > * - nofile 524288
> >
> > is what you want?
> >
> > joe
The solution used to be editing the kernel and tuning NR_OPEN and NR_FILE in
/your/kernel/source/include/linux/fs.h
The kernel used to have an absolute hard limit that setrlimit and ulimit
couldn't go past but I'm not sure if this has changed.
You could try bumping those up and recompiling or at least googling along
those lines.
next prev parent reply other threads:[~2009-02-16 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 5:48 running out of file descriptors Bryan Christ
2009-02-16 6:18 ` Joe Damato
2009-02-16 7:09 ` Bryan Christ
2009-02-16 13:01 ` Eric Bambach [this message]
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=200902160701.14982.eric@cisu.net \
--to=bot403@cisu.net \
--cc=bryan.christ@gmail.com \
--cc=eric@cisu.net \
--cc=ice799@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).