Various fixes to the "config and tuning" section of the Handbook.

* Reword the paragraph before a set of tunables for Linux, as
    it wasa bit confusing.

  * Correct the name of 'kern.maxfiles' (it was 'kern.maxfile')
    before, and reword the text around it to remove the need for
    a possessive "'s", which would look funny after 'maxfiles'.

  * Finish properly a sentence which was missing a fullstop.

Submitted by:	ganbold &at; micom ˙ mng ˙ net
This commit is contained in:
Giorgos Keramidas 2006-11-22 16:17:01 +00:00
parent 47b9e44bce
commit b93e6b5358
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=29124

View file

@ -1686,9 +1686,9 @@ cron.* /var/log/cron
form. The specified values are set after the system goes into
multi-user mode. Not all variables are settable in this mode.</para>
<para>A sample <filename>sysctl.conf</filename> turning off logging
of fatal signal exits and letting Linux programs know they are really
running under &os;:</para>
<para>To turn off logging of fatal signal exits and let Linux
programs know they are really running under &os;, the following
tunables can be set in <filename>sysctl.conf</filename>:</para>
<programlisting>kern.logsigexit=0 # Do not log fatal signal exits (e.g. sig 11)
compat.linux.osname=&os;
@ -2148,8 +2148,8 @@ device_probe_and_attach: cbb0 attach returned 12</screen>
require many thousands of file descriptors, depending on the
kind and number of services running concurrently.</para>
<para>In older FreeBSD releases, <varname>kern.maxfile</varname>'s default
value is derived from the <option>maxusers</option> option in your
<para>In older FreeBSD releases, the default value of <varname>kern.maxfiles</varname>
is derived from the <option>maxusers</option> option in your
kernel configuration file. <varname>kern.maxfiles</varname> grows
proportionally to the value of <option>maxusers</option>. When
compiling a custom kernel, it is a good idea to set this kernel
@ -3157,7 +3157,7 @@ make ACPI_DEBUG=1</userinput></screen>
This example enables debug messages for all
<acronym>ACPI-CA</acronym> components and all
<acronym>ACPI</acronym> hardware drivers
(<acronym>CPU</acronym>, <acronym>LID</acronym>, etc.) It will
(<acronym>CPU</acronym>, <acronym>LID</acronym>, etc.). It will
only output error messages, the least verbose level.</para>
<programlisting>debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS"