Update and clarify proc-table-full to conform with reality.

Discussed with:	alfred
Approved by:	bcr (mentor)
This commit is contained in:
Eitan Adler 2013-01-17 03:32:42 +00:00
parent efe20f3349
commit 9b37d4613c
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=40668

View file

@ -2473,8 +2473,9 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
<qandaentry>
<question id="proc-table-full">
<para>Why do I get the error <errorname>kernel: proc: table is
full</errorname>?</para>
<para>Why do I get the error <errorname>maxproc limit
exceeded by uid %i, please see tuning(7) and
login.conf(5)</errorname>?</para>
</question>
<answer>
@ -2501,20 +2502,13 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
this tunable needs adjustment it needs to be defined in
<filename>/boot/loader.conf</filename>. The tunable will
not get adjusted until the system is rebooted. For more
information about tuning tunables, you should see the
&man.loader.conf.5; and &man.sysctl.conf.5; manual pages.
information about tuning tunables, see
&man.loader.conf.5;.
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 change permanent place the proper value
in <filename>/etc/sysctl.conf</filename>. More information
about system tuning with &man.sysctl.8; can be found at the
<ulink
url="&url.books.handbook;/configtuning-sysctl.html">Tuning with sysctl</ulink>
section of the Handbook.</para>
</answer>
</qandaentry>