Date: Thu, 8 Nov 2001 11:55:27 -0500 (EST) From: mwlucas@blackhelicopters.org To: FreeBSD-gnats-submit@freebsd.org Subject: docs/31857: new FAQ: proc: table is full Message-ID: <200111081655.LAA09458@blackhelicopters.org>
index | next in thread | raw e-mail
>Number: 31857
>Category: docs
>Synopsis: new FAQ: proc: table is full
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Thu Nov 08 09:00:03 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Michael Lucas
>Release: FreeBSD 3.5-STABLE i386
>Organization:
None
>Environment:
this morning's -doc tree
>Description:
From the "I can't belive this isn't in the FAQ yet!" department.
>How-To-Repeat:
read -questions.
>Fix:
*** en_US.ISO8859-1/books/faq/book.sgml-dist Thu Nov 8 07:46:11 2001
--- en_US.ISO8859-1/books/faq/book.sgml Thu Nov 8 11:51:39 2001
***************
*** 3878,3883 ****
--- 3878,3926 ----
</qandaentry>
<qandaentry>
+ <question id="proc-table-full">
+ <para>Why do I get the error <errorname>/kernel: proc: table
+ is full</errorname>?</para>
+ </question>
+
+ <answer>
+ <para>The FreeBSD kernel will only allow a certain number of
+ processes to exist at one time. The number is based on
+ the <literal>MAXUSERS</literal> option in the kernel
+ configuration. <literal>MAXUSERS</literal> also affects
+ various other in-kernel limits, such as network buffers
+ (see <link linkend="panic-kmemmap-too-small">this</link>
+ earlier question). If your machine is heavily loaded, you
+ probably want to increase <literal>MAXUSERS</literal>.
+ This will increase these other system limits in addition
+ to the maximum number of processes.</para>
+
+ <para>After FreeBSD 4.4, <literal>MAXUSERS</literal> became
+ a tunable value that could be set with
+ <varname>kern.maxusers</varname> in
+ <filename>/boot/loader.conf</filename>. In earlier
+ versions of FreeBSD, you need to adjust
+ <literal>MAXUSERS</literal> in your kernel
+ configuration.</para>
+
+ <para>If your machine is lightly loaded, and you are simply
+ running a very large number of processes, you can adjust
+ this with the <varname>kern.maxproc</varname> sysctl. If
+ these processes are being run by a single user, you will
+ also need to adjust <varname>kern.maxprocperuid</varname>
+ to be one less than your new
+ <varname>kern.maxproc</varname> value. (It must be at
+ least one less because one system program, &man.init.8;,
+ must always be running.)</para>
+
+ <para>To make a sysctl permanent across reboots, set this in
+ <filename>/etc/sysctl.conf</filename> in recent versions
+ of FreeBSD, or <filename>/etc/rc.local</filename> in older
+ versions.</para>
+ </answer>
+ </qandaentry>
+
+ <qandaentry>
<question id="cmap-busy-panic">
<para>Why do I get an error reading <errorname>CMAP
busy</errorname> when rebooting with a new
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111081655.LAA09458>