From: Austin Gonyou <austin@digitalroadkill.net>
To: linux-kernel@vger.kernel.org
Subject: sysctl parameter tuning part deux.
Date: 15 Jul 2002 14:51:45 -0500 [thread overview]
Message-ID: <1026762705.14226.11.camel@UberGeek> (raw)
I forgot to include a url in my last email. Sorry about that.
Here is the document I was working from:
http://www.tldp.org/LDP/solrhe/Securing-Optimizing-Linux-RH-Edition-v1.3/chap6sec72.html
one point about this in particular is the fact that this document
recommends 256 FDs for every 4M ram. I'm running a Dell 6650 with 8GB
RAM, and well, adhering to this would mean I must allocate ~500M FDs.
That seems too high for *proper* operation to me. Is there a better
method to use?
--
Austin Gonyou <austin@digitalroadkill.net>
reply other threads:[~2002-07-15 19:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1026762705.14226.11.camel@UberGeek \
--to=austin@digitalroadkill.net \
--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
all inboxes | Powered by JetHome®