From: Dan Kegel <dank@kegel.com>
To: fedelman@elsitio.com.ar,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: fs.file-max
Date: Tue, 08 May 2001 07:08:40 -0700 [thread overview]
Message-ID: <3AF7FDE8.9C124AA9@kegel.com> (raw)
Federico Edelman Anaya (fedelman@elsitio.com.ar) wrote:
> What can I do to test the FD limit? ... Because, the FD limit is set in
> /proc/sys/fs/file-max, sample:
>
> echo "2048" > /proc/sys/fs/file-max
That sets the systemwide limit to 2048.
> ulimit -n 8192
That sets the per-process limit (for this process
and its children) to 2048.
> In this case ... the FD limit = 8192 :( ... when the limit should be
> 2048?
No, the two limits are independant (except, obviously, that
that process will reach the systemwide fd limit before it
exhausts its per-process fd limit).
> I wrote a perl script for the test ... anybody known a "C" program for
> test the FD limit?
http://www.kegel.com/dkftpbench/#tuning
- Dan
next reply other threads:[~2001-05-08 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 14:08 Dan Kegel [this message]
2001-05-08 11:32 ` fs.file-max Federico Edelman Anaya
-- strict thread matches above, loose matches on Subject: below --
2001-05-08 10:03 fs.file-max Federico Edelman Anaya
2001-05-08 14:37 ` fs.file-max Nathan Straz
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=3AF7FDE8.9C124AA9@kegel.com \
--to=dank@kegel.com \
--cc=fedelman@elsitio.com.ar \
--cc=linux-kernel@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