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

Nuke trailing whitespace.

Browse source 
Approved by:	roam
This commit is contained in:
Sean Chittenden 2003-03-04 19:04:44 +00:00
parent 4f8ba48dd5
commit a0436c0236
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=16195
1 changed files with 68 additions and 68 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

136
en_US.ISO8859-1/books/handbook/config/chapter.sgml
View file

@ -149,7 +149,7 @@
</sect3>
<sect3 id="swap-design">
<title>Swap Partition</title>
<title>Swap Partition</title>
<indexterm><primary>swap sizing</primary></indexterm>
<indexterm><primary>swap partition</primary></indexterm>
@ -229,7 +229,7 @@
directly implies this; it is configuration information for the
<filename>rc*</filename> files.</para>
<para>An administrator should make entries in the
<para>An administrator should make entries in the
<filename>rc.conf</filename> file to
override the default settings from
<filename>/etc/defaults/rc.conf</filename>. The defaults file
@ -268,7 +268,7 @@
remains unique.</para>
<para>Upgrading the system using &man.sysinstall.8;
or <command>make world</command> will not overwrite the
or <command>make world</command> will not overwrite the
<filename>rc.conf</filename>
file, so system configuration information will not be lost.</para>
@ -292,12 +292,12 @@
<para>Normally, when a port or package is installed, sample
configuration files are also installed. These are usually
identified with a <filename>.default</filename> suffix. If there
identified with a <filename>.default</filename> suffix. If there
are no existing
configuration files for the application, they will be created by
copying the <filename>.default</filename> files.</para>
<para>For example, consider the contents of the directory
<para>For example, consider the contents of the directory
<filename>/usr/local/etc/apache</filename>:</para>
<literallayout class="monospaced">-rw-r--r-- 1 root wheel 2184 May 20 1998 access.conf
@ -341,7 +341,7 @@
part of the installation of the package, and will be removed
when the package is removed.</para>
<para>A generic startup script in
<para>A generic startup script in
<filename>/usr/local/etc/rc.d</filename> looks like:</para>
<programlisting>#!/bin/sh
@ -394,9 +394,9 @@ exit 0
generally regarded as the location of last resort; if there is a
better place to start a service, do it there.</para>
<note><para>Do <emphasis>not</emphasis> place any commands in
<note><para>Do <emphasis>not</emphasis> place any commands in
<filename>/etc/rc.conf</filename>. To start daemons, or
run any commands at boot time, place a script in
run any commands at boot time, place a script in
<filename>/usr/local/etc/rc.d</filename> instead.</para>
</note>
@ -405,7 +405,7 @@ exit 0
least being that because &man.cron.8; runs these processes as the
owner of the <command>crontab</command>, services may be started
and maintained by non-<username>root</username> users.</para>
<para>This takes advantage of a feature of &man.cron.8;: the
time specification may be replaced by <literal>@reboot</literal>,
which will
@ -861,7 +861,7 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
Any other addresses which fall within this network must have a
netmask of all <literal>1</literal>s.</para>
<para>For example, consider the case where the
<para>For example, consider the case where the
<devicename>fxp0</devicename> interface is
connected to two networks, the <hostid role="ipaddr">10.1.1.0</hostid>
network with a netmask of <hostid role="netmask">255.255.255.0</hostid>
@ -900,7 +900,7 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
<tbody>
<row>
<entry><filename>/etc</filename></entry>
<entry>Generic system configuration information; data here is
<entry>Generic system configuration information; data here is
system-specific.</entry>
</row>
<row>
@ -909,7 +909,7 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
</row>
<row>
<entry><filename>/etc/mail</filename></entry>
<entry>Extra &man.sendmail.8; configuration, other
<entry>Extra &man.sendmail.8; configuration, other
MTA configuration files.
</entry>
</row>
@ -925,7 +925,7 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
here.</entry>
</row>
<row>
<entry><filename>/usr/local/etc</filename></entry>
<entry><filename>/usr/local/etc</filename></entry>
<entry>Configuration files for installed applications.
May contain per-application subdirectories.</entry>
</row>
@ -962,12 +962,12 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
<para>The most common entries to <filename>resolv.conf</filename> are:
</para>
<informaltable frame="none">
<tgroup cols="2">
<tbody>
<row>
<entry><literal>nameserver</literal></entry>
<entry><literal>nameserver</literal></entry>
<entry>The IP address of a name server the resolver
should query. The servers are queried in the order
listed with a maximum of three.</entry>
@ -994,8 +994,8 @@ nameserver 147.11.100.30</programlisting>
<note><para>Only one of the <literal>search</literal> and
<literal>domain</literal> options should be used.</para></note>
<para>If you are using DHCP, &man.dhclient.8; usually rewrites
<filename>resolv.conf</filename> with information received from the
<para>If you are using DHCP, &man.dhclient.8; usually rewrites
<filename>resolv.conf</filename> with information received from the
DHCP server.</para>
</sect3>
@ -1003,7 +1003,7 @@ nameserver 147.11.100.30</programlisting>
<title><filename>/etc/hosts</filename></title>
<indexterm><primary>hosts</primary></indexterm>
<para><filename>/etc/hosts</filename> is a simple text
database reminiscent of the old Internet. It works in
conjunction with DNS and NIS providing name to IP address
@ -1047,7 +1047,7 @@ nameserver 147.11.100.30</programlisting>
<para><filename>/etc/hosts</filename> takes on the simple format
of:</para>
<programlisting>[Internet address] [official hostname] [alias1] [alias2] ...</programlisting>
<para>For example:</para>
@ -1060,14 +1060,14 @@ nameserver 147.11.100.30</programlisting>
<sect2>
<title>Log File Configuration</title>
<indexterm><primary>log files</primary></indexterm>
<sect3>
<title><filename>syslog.conf</filename></title>
<indexterm><primary>syslog.conf</primary></indexterm>
<para><filename>syslog.conf</filename> is the configuration file
for the &man.syslogd.8; program. It indicates which types
of <command>syslog</command> messages are logged to particular
@ -1113,7 +1113,7 @@ cron.* /var/log/cron
<title><filename>newsyslog.conf</filename></title>
<indexterm><primary>newsyslog.conf</primary></indexterm>
<para><filename>newsyslog.conf</filename> is the configuration
file for &man.newsyslog.8;, a program that is normally scheduled
to run by &man.cron.8;. &man.newsyslog.8; determines when log
@ -1130,7 +1130,7 @@ cron.* /var/log/cron
they are to be touched. Log files can be rearranged and/or
archived when they have either reached a certain size, or at a
certain periodic time/date.</para>
<programlisting># configuration file for newsyslog
# &dollar;FreeBSD&dollar;
#
@ -1163,8 +1163,8 @@ cron.* /var/log/cron
<indexterm><primary>sysctl.conf</primary></indexterm>
<indexterm><primary>sysctl</primary></indexterm>
<para><filename>sysctl.conf</filename> looks much like
<filename>rc.conf</filename>. Values are set in a
<para><filename>sysctl.conf</filename> looks much like
<filename>rc.conf</filename>. Values are set in a
<literal>variable=value</literal>
form. The specified values are set after the system goes into
multi-user mode. Not all variables are settable in this mode.</para>
@ -1184,38 +1184,38 @@ compat.linux.osrelease=4.3-STABLE</programlisting>
<indexterm><primary>sysctl</primary></indexterm>
<indexterm><primary>Tuning with sysctl</primary></indexterm>
<para>&man.sysctl.8; is an interface that allows you to make changes
to a running FreeBSD system. This includes many advanced
options of the TCP/IP stack and virtual memory system that can
dramatically improve performance for an experienced system
administrator. Over five hundred system variables can be read
and set using &man.sysctl.8;.</para>
<para>At its core, &man.sysctl.8; serves two functions: to read and
to modify system settings.</para>
<para>To view all readable variables:</para>
<screen>&prompt.user; <userinput>sysctl -a</userinput></screen>
<para>To read a particular variable, for example,
<varname>kern.maxproc</varname>:</para>
<screen>&prompt.user; <userinput>sysctl kern.maxproc</userinput>
kern.maxproc: 1044</screen>
<para>To set a particular variable, use the intuitive
<replaceable>variable</replaceable>=<replaceable>value</replaceable>
syntax:</para>
<screen>&prompt.root; <userinput>sysctl kern.maxfiles=5000</userinput>
kern.maxfiles: 2088 -> 5000</screen>
<para>Settings of sysctl variables are usually either strings,
numbers, or booleans (a boolean being <literal>1</literal> for yes
or a <literal>0</literal> for no).</para>
<sect2 id="sysctl-readonly">
<sect2info>
<authorgroup>
@ -1228,27 +1228,27 @@ kern.maxfiles: 2088 -> 5000</screen>
</authorgroup>
</sect2info>
<title>&man.sysctl.8; read only</title>
<para>In some cases it may be desirable to modify read-only &man.sysctl.8;
values. While this is not recommended, it is also sometimes unavoidable.</para>
<para>For instance on some laptop models the &man.cardbus.4; device will
not probe memory ranges, and fail with errors which look similar to:</para>
<screen>cbb0: Could not map register memory</screen>
<screen>device_probe_and_attach: cbb0 attach returned 12</screen>
<para>Cases like the one above usually require the modification of some
default &man.sysctl.8; settings which are set read only. To overcome
these situations a user can put &man.sysctl.8; <quote>OIDs</quote>
in their local <filename>/boot/loader.conf.local</filename>. Default
settings are located in the <filename>/boot/defaults/loader.conf</filename>
file.</para>
<para>Fixing the problem mentioned above would require a user to set
<option>hw.pci.allow_unsupported_io_range=1</option> in the aforementioned
file. Now &man.cardbus.4; will work properly.</para>
</sect2>
</sect1>
@ -1257,14 +1257,14 @@ kern.maxfiles: 2088 -> 5000</screen>
<sect2>
<title>Sysctl Variables</title>
<sect3>
<title><varname>vfs.vmiodirenable</varname></title>
<indexterm>
<primary><varname>vfs.vmiodirenable</varname></primary>
</indexterm>
<para>The <varname>vfs.vmiodirenable</varname> sysctl variable
may be set to either 0 (off) or 1 (on); it is 1 by default. This variable controls how
directories are cached by the system. Most directories are
@ -1285,14 +1285,14 @@ kern.maxfiles: 2088 -> 5000</screen>
performance even with the wasted memory but you should
experiment to find out.</para>
</sect3>
<sect3>
<title><varname>vfs.write_behind</varname></title>
<indexterm>
<primary><varname>vfs.write_behind</varname></primary>
</indexterm>
<para>The <varname>vfs.write_behind</varname> sysctl variable
defaults to <literal>1</literal> (on). This tells the file system
to issue media writes as full clusters are collected, which
@ -1302,38 +1302,38 @@ kern.maxfiles: 2088 -> 5000</screen>
processes and under certain circumstances you may wish to turn it
off.</para>
</sect3>
<sect3>
<title><varname>vfs.hirunningspace</varname></title>
<indexterm>
<primary><varname>vfs.hirunningspace</varname></primary>
</indexterm>
<para>The <varname>vfs.hirunningspace</varname> sysctl variable
determines how much outstanding write I/O may be queued to disk
controllers system-wide at any given instance. The default is
usually sufficient but on machines with lots of disks you may
want to bump it up to four or five <emphasis>megabytes</emphasis>.
want to bump it up to four or five <emphasis>megabytes</emphasis>.
Note that setting too high a value (exceeding the buffer cache's
write threshold) can lead to extremely bad clustering
performance. Do not set this value arbitrarily high! Higher
write values may add latency to reads occurring at the same time.
</para>
<para>There are various other buffer-cache and VM page cache
related sysctls. We do not recommend modifying these values. As
of FreeBSD 4.3, the VM system does an extremely good job of
automatically tuning itself.</para>
</sect3>
<sect3>
<title><varname>vm.swap_idle_enabled</varname></title>
<indexterm>
<primary><varname>vm.swap_idle_enabled</varname></primary>
</indexterm>
<para>The <varname>vm.swap_idle_enabled</varname> sysctl variable
is useful in large multi-user systems where you have lots of
users entering and leaving the system and lots of idle processes.
@ -1355,7 +1355,7 @@ kern.maxfiles: 2088 -> 5000</screen>
<sect3>
<title><varname>hw.ata.wc</varname></title>
<indexterm>
<primary><varname>hw.ata.wc</varname></primary>
</indexterm>
@ -1378,12 +1378,12 @@ kern.maxfiles: 2088 -> 5000</screen>
the kernel variable back to 1. This must be done from the
boot loader at boot time. Attempting to do it after the
kernel boots will have no effect.</para>
<para>For more information, please see &man.ata.4;.</para>
</sect3>
<sect3>
<title><option>SCSI_DELAY</option>
<title><option>SCSI_DELAY</option>
(<varname>kern.cam.scsi_delay</varname>)</title>
<indexterm>
@ -1408,7 +1408,7 @@ kern.maxfiles: 2088 -> 5000</screen>
<indexterm><primary>Soft Updates</primary></indexterm>
<indexterm><primary>tunefs</primary></indexterm>
<para>The &man.tunefs.8; program can be used to fine-tune a
file system. This program has many different options, but for
now we are only concerned with toggling Soft Updates on and
@ -1425,7 +1425,7 @@ kern.maxfiles: 2088 -> 5000</screen>
at filesystem creation time, through use of the <literal>-U</literal>
option to &man.newfs.8;.</para></note>
<para>Soft Updates drastically improves meta-data performance, mainly
<para>Soft Updates drastically improves meta-data performance, mainly
file creation and deletion, through the use of a memory cache. We
recommend to use Soft Updates on all of your file systems. There
are two downsides to Soft Updates that you should be aware of: First,
@ -1440,13 +1440,13 @@ kern.maxfiles: 2088 -> 5000</screen>
<sect3>
<title>More details about Soft Updates</title>
<indexterm><primary>Soft Updates (Details)</primary></indexterm>
<para>There are two traditional approaches to writing a file systems meta-data
back to disk. (Meta-data updates are updates to
non-content data like inodes or directories.)</para>
<para>Historically, the default behavior was to write out
meta-data updates synchronously. If a directory had been
changed, the system waited until the change was actually
@ -1520,7 +1520,7 @@ kern.maxfiles: 2088 -> 5000</screen>
pending meta-data operations can be quickly either rolled-back
or completed from the logging area after the system comes
up again, resulting in a fast filesystem startup.</para>
<para>Kirk McKusick, the developer of Berkeley FFS,
solved this problem with Soft Updates: all pending
meta-data updates are kept in memory and written out to disk
@ -1589,7 +1589,7 @@ kern.maxfiles: 2088 -> 5000</screen>
<title>Tuning Kernel Limits</title>
<indexterm><primary>Tuning kernel limits</primary></indexterm>
<sect2 id="file-process-limits">
<title>File/Process Limits</title>
@ -1599,7 +1599,7 @@ kern.maxfiles: 2088 -> 5000</screen>
<indexterm>
<primary><varname>kern.maxfiles</varname></primary>
</indexterm>
<para><varname>kern.maxfiles</varname> can be raised or
lowered based upon your system requirements. This variable
indicates the maximum number of file descriptors on your
@ -1732,7 +1732,7 @@ kern.maxfiles: 2088 -> 5000</screen>
to calculate the bandwidth delay product for each connection and
limit the amount of data queued to the network to just the amount
required to maintain optimum throughput.</para>
<para>This feature is useful if you are serving data over modems,
Gigabit Ethernet, or even high speed WAN links (or any other link
with a high bandwidth delay product), especially if you are also
@ -1915,7 +1915,7 @@ kern.maxfiles: 2088 -> 5000</screen>
</author>
</authorgroup>
</sect1info>
<title>ACPI and FreeBSD</title>
<para>It is very important to utilize hardware resources in an
@ -1954,7 +1954,7 @@ kern.maxfiles: 2088 -> 5000</screen>
<sect2 id="acpi-config">
<title>Configuring <acronym>ACPI</acronym></title>
<para>The <filename>acpi.ko</filename> driver is loaded by default
at start up by the &man.loader.8; and should <emphasis>not</emphasis>
be compiled into the kernel. The reasoning behind this is that modules
@ -1980,11 +1980,11 @@ kern.maxfiles: 2088 -> 5000</screen>
which is the same action as:</para>
<screen>&prompt.root; <userinput>halt -p</userinput></screen>
<para>The other options are available. Check out the &man.acpiconf.8;
manual page for more information.</para>
</sect2>
<sect2 id="acpi-debug">
<title>Debugging <acronym>ACPI</acronym></title>