From: "Brian Parris" <brian.parris@verizon.net>
To: "Kernel mailing list" <linux-kernel@vger.kernel.org>
Subject: File Descriptors
Date: Tue, 5 Dec 2000 11:22:24 -0500 [thread overview]
Message-ID: <003101c05ed7$8d91dc20$673c2904@ent.shellnet.net> (raw)
I run a shell server and I am running into a problem with not having enough
file descriptors and keep getting errors like this:
/bin/sh: error while loading shared libraries: libtermcap.so.2: cannot open
shared object file: Error 23
error 23 as defined in errno.h is file table overflow, how do I increase the
number of file descriptors available on my system, and is there an absolute
limit or a reason not to raise it to a large number? I am currently running
kernel 2.2.17 UP, any help you can provide will be greatly appreciated.
Brian Parris
brian@shellnet.net
brian.parris@verizon.net
P.S. Please cc me, i am on the list but i don't want it to get lost in the
kernel folder
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-12-05 17:56 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='003101c05ed7$8d91dc20$673c2904@ent.shellnet.net' \
--to=brian.parris@verizon.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