os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Remove obsolete question

Browse source 
Noted by:	imp
Approved by:	bcr (mentor, implicit)
This commit is contained in:
Eitan Adler 2013-02-08 00:22:46 +00:00
parent d216f6097f
commit a30cebc5e2
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=40910
1 changed files with 2 additions and 20 deletions

22
en_US.ISO8859-1/books/faq/book.xml
View file

@ -2224,23 +2224,6 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
</answer>
</qandaentry>
<qandaentry>
<question id="panic-kmemmap-too-small">
<para>My system does not have 1&nbsp;GB of RAM, and &os; still
panics with <errorname>kmem_map too
small</errorname>!</para>
</question>
<answer>
<para>The panic indicates that the system ran out of virtual
memory for network buffers (specifically, mbuf clusters).
You can increase the amount of VM available for mbuf
clusters by following the instructions in the <ulink
url="&url.books.handbook;/configtuning-kernel-limits.html#nmbclusters">Network Limits</ulink>
section of the Handbook.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="proc-table-full">
<para>Why do I get the error <errorname>maxproc limit
@ -2253,9 +2236,8 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
processes to exist at one time. The number is based on the
<varname>kern.maxusers</varname> &man.sysctl.8; variable.
<varname>kern.maxusers</varname> 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
in-kernel limits, such as network buffers.
If your machine is heavily loaded, you probably
want to increase <varname>kern.maxusers</varname>. This
will increase these other system limits in addition to the
maximum number of processes.</para>