svn commit: r42524 - head/en_US.ISO8859-1/books/handbook/config
Warren Block
wblock at FreeBSD.org
Thu Aug 8 17:21:08 UTC 2013
Author: wblock
Date: Thu Aug 8 17:21:07 2013
New Revision: 42524
URL: http://svnweb.freebsd.org/changeset/doc/42524
Log:
Whitespace-only fixes. Translators, please ignore.
Modified:
head/en_US.ISO8859-1/books/handbook/config/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/config/chapter.xml Thu Aug 8 17:00:17 2013 (r42523)
+++ head/en_US.ISO8859-1/books/handbook/config/chapter.xml Thu Aug 8 17:21:07 2013 (r42524)
@@ -270,7 +270,6 @@
<programlisting>sshd_enable="YES"
keyrate="fast"
defaultrouter="10.1.1.254"</programlisting>
-
</listitem>
<listitem>
@@ -278,7 +277,6 @@ defaultrouter="10.1.1.254"</programlisti
<programlisting>hostname="node1.example.org"
ifconfig_fxp0="inet 10.1.1.1/8"</programlisting>
-
</listitem>
</itemizedlist>
@@ -608,9 +606,9 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin
<para>Users who wish to begin their own
<filename>crontab</filename> file from scratch, without the
- use of a template, can use <command>crontab -e</command>. This
- will invoke the default editor with an empty file. When this
- file is saved, it will be automatically installed by
+ use of a template, can use <command>crontab -e</command>.
+ This will invoke the default editor with an empty file. When
+ this file is saved, it will be automatically installed by
&man.crontab.1;.</para>
<para>In order to remove a user &man.crontab.5; completely,
@@ -633,12 +631,13 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin
<title>Using &man.rc.8; Under &os;</title>
<para>In 2002, &os; integrated the NetBSD &man.rc.8; system for
- system initialization. The files listed in <filename
- class="directory">/etc/rc.d</filename> provide basic services
- which can be controlled with the <option>start</option>,
- <option>stop</option>, and <option>restart</option> options
- to &man.service.8;. For instance, &man.sshd.8; can be restarted
- with the following command:</para>
+ system initialization. The files listed in
+ <filename class="directory">/etc/rc.d</filename> provide basic
+ services which can be controlled with the
+ <option>start</option>, <option>stop</option>, and
+ <option>restart</option> options to &man.service.8;. For
+ instance, &man.sshd.8; can be restarted with the following
+ command:</para>
<screen>&prompt.root; <userinput>service sshd restart</userinput></screen>
@@ -1262,15 +1261,15 @@ round-trip min/avg/max/stddev = 0.700/0.
host. This can happen if no default route is specified or
if a cable is unplugged. Check the output of
<command>netstat -rn</command> and make sure there is a
- valid route to the host. If there is not, read <xref
- linkend="advanced-networking"/>.</para>
+ valid route to the host. If there is not, read
+ <xref linkend="advanced-networking"/>.</para>
<para><errorname>ping: sendto: Permission denied</errorname>
error messages are often caused by a misconfigured firewall.
If a firewall is enabled on &os; but no rules have been
defined, the default policy is to deny all traffic, even
- &man.ping.8;. Refer to <xref
- linkend="firewalls"/> for more information.</para>
+ &man.ping.8;. Refer to
+ <xref linkend="firewalls"/> for more information.</para>
<para>Sometimes performance of the card is poor or below
average. In these cases, try setting the media
@@ -1314,9 +1313,9 @@ round-trip min/avg/max/stddev = 0.700/0.
given interface, there must be one address which correctly
represents the network's netmask. Any other addresses which
fall within this network must have a netmask of all
- <literal>1</literal>s, expressed as either <hostid
- role="netmask">255.255.255.255</hostid> or <hostid
- role="netmask">0xffffffff</hostid>.</para>
+ <literal>1</literal>s, expressed as either
+ <hostid role="netmask">255.255.255.255</hostid> or
+ <hostid role="netmask">0xffffffff</hostid>.</para>
<para>For example, consider the case where the
<devicename>fxp0</devicename> interface is connected to two
@@ -1324,18 +1323,18 @@ round-trip min/avg/max/stddev = 0.700/0.
netmask of <hostid role="netmask">255.255.255.0</hostid> and
<hostid role="ipaddr">202.0.75.16</hostid> with a netmask of
<hostid role="netmask">255.255.255.240</hostid>. The system
- is to be configured to appear in the ranges <hostid
- role="ipaddr">10.1.1.1</hostid> through <hostid
- role="ipaddr">10.1.1.5</hostid> and <hostid
- role="ipaddr">202.0.75.17</hostid> through <hostid
- role="ipaddr">202.0.75.20</hostid>. Only the first address
- in a given network range should have a real netmask. All the
- rest (<hostid role="ipaddr">10.1.1.2</hostid> through <hostid
- role="ipaddr">10.1.1.5</hostid> and <hostid
- role="ipaddr">202.0.75.18</hostid> through <hostid
- role="ipaddr">202.0.75.20</hostid>) must be configured with
- a netmask of <hostid
- role="netmask">255.255.255.255</hostid>.</para>
+ is to be configured to appear in the ranges
+ <hostid role="ipaddr">10.1.1.1</hostid> through
+ <hostid role="ipaddr">10.1.1.5</hostid> and
+ <hostid role="ipaddr">202.0.75.17</hostid> through
+ <hostid role="ipaddr">202.0.75.20</hostid>. Only the first
+ address in a given network range should have a real netmask.
+ All the rest (<hostid role="ipaddr">10.1.1.2</hostid> through
+ <hostid role="ipaddr">10.1.1.5</hostid> and
+ <hostid role="ipaddr">202.0.75.18</hostid> through
+ <hostid role="ipaddr">202.0.75.20</hostid>) must be configured
+ with a netmask of
+ <hostid role="netmask">255.255.255.255</hostid>.</para>
<para>The following <filename>/etc/rc.conf</filename> entries
configure the adapter correctly for this scenario:</para>
@@ -1349,7 +1348,6 @@ ifconfig_fxp0_alias4="inet 202.0.75.17 n
ifconfig_fxp0_alias5="inet 202.0.75.18 netmask 255.255.255.255"
ifconfig_fxp0_alias6="inet 202.0.75.19 netmask 255.255.255.255"
ifconfig_fxp0_alias7="inet 202.0.75.20 netmask 255.255.255.255"</programlisting>
-
</sect1>
<sect1 id="configtuning-syslog">
@@ -1396,8 +1394,8 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 n
<literal>syslogd_flags</literal> in
<filename>/etc/rc.conf</filename>. Refer to &man.syslogd.8;
for more information on the arguments, and &man.rc.conf.5;,
- <xref linkend="configtuning-core-configuration"/> and <xref
- linkend="configtuning-rcd"/> for more information about
+ <xref linkend="configtuning-core-configuration"/> and
+ <xref linkend="configtuning-rcd"/> for more information about
<filename>/etc/rc.conf</filename> and the &man.rc.8;
subsystem.</para>
</sect2>
@@ -1537,8 +1535,8 @@ cron.*
facilities, refer to &man.syslog.3; and &man.syslogd.8;.
For more information about
<filename>/etc/syslog.conf</filename>, its syntax, and more
- advanced usage examples, see &man.syslog.conf.5; and <xref
- linkend="network-syslogd"/>.</para>
+ advanced usage examples, see &man.syslog.conf.5; and
+ <xref linkend="network-syslogd"/>.</para>
</sect2>
<sect2>
@@ -1632,14 +1630,14 @@ cron.*
&man.newsyslog.8; further instructions, such as how to
compress the rotated file or to create the log file if it
is missing. The last two fields are optional, and
- specify the <acronym
- role="Process Identifier">PID</acronym> file of a process
- and a signal number to send to that process when the file
- is rotated. For more information on all fields, valid
+ specify the
+ <acronym role="Process Identifier">PID</acronym> file of a
+ process and a signal number to send to that process when the
+ file is rotated. For more information on all fields, valid
flags, and how to specify the rotation time, refer to
- &man.newsyslog.conf.5;. Since &man.newsyslog.8; is run
- from &man.cron.8;, it can not rotate files more often than
- it is run from &man.cron.8;.</para>
+ &man.newsyslog.conf.5;. Since &man.newsyslog.8; is run from
+ &man.cron.8;, it can not rotate files more often than it is
+ run from &man.cron.8;.</para>
</sect3>
</sect2>
</sect1>
@@ -1735,9 +1733,8 @@ cron.*
<primary><filename>resolv.conf</filename></primary>
</indexterm>
- <para>How a
- &os; system accesses the Internet Domain Name System
- (<acronym>DNS</acronym>) is controlled by
+ <para>How a &os; system accesses the Internet Domain Name
+ System (<acronym>DNS</acronym>) is controlled by
&man.resolv.conf.5;.</para>
<para>The most common entries to
@@ -1896,8 +1893,8 @@ kern.maxfiles: 2088 -> 5000</screen>
<para>To automatically set some variables each time the machine
boots, add them to <filename>/etc/sysctl.conf</filename>. For
- more information, refer to &man.sysctl.conf.5; and <xref
- linkend="configtuning-sysctlconf"/>.</para>
+ more information, refer to &man.sysctl.conf.5; and
+ <xref linkend="configtuning-sysctlconf"/>.</para>
<sect2 id="configtuning-sysctlconf">
<title><filename>sysctl.conf</filename></title>
@@ -1923,7 +1920,6 @@ kern.logsigexit=0
# Prevent users from seeing information about processes that
# are being run under another UID.
security.bsd.see_other_uids=0</programlisting>
-
</sect2>
<sect2 id="sysctl-readonly">
@@ -2189,16 +2185,16 @@ device_probe_and_attach: cbb0 attach ret
data blocks of a file did not find their way out of the
buffer cache onto the disk by the time of the crash,
&man.fsck.8; recognizes this and repairs the file system
- by setting the file length to
- <literal>0</literal>. Additionally, the implementation is
- clear and simple. The disadvantage is that meta-data
- changes are slow. For example, <command>rm -r</command>
- touches all the files in a directory sequentially, but each
- directory change will be written synchronously to the
- disk. This includes updates to the directory itself, to
- the inode table, and possibly to indirect blocks allocated
- by the file. Similar considerations apply for unrolling
- large hierarchies using <command>tar -x</command>.</para>
+ by setting the file length to <literal>0</literal>.
+ Additionally, the implementation is clear and simple. The
+ disadvantage is that meta-data changes are slow. For
+ example, <command>rm -r</command> touches all the files in a
+ directory sequentially, but each directory change will be
+ written synchronously to the disk. This includes updates to
+ the directory itself, to the inode table, and possibly to
+ indirect blocks allocated by the file. Similar
+ considerations apply for unrolling large hierarchies using
+ <command>tar -x</command>.</para>
<para>The second approach is to use asynchronous meta-data
updates. This is the default for a <acronym>UFS</acronym>
@@ -2266,7 +2262,7 @@ device_probe_and_attach: cbb0 attach ret
in use are marked as such in their blocks and inodes.
After a crash, the only resource allocation error that
occurs is that resources are marked as <quote>used</quote>
- which are actually <quote>free</quote>. &man.fsck.8;
+ which are actually <quote>free</quote>. &man.fsck.8;
recognizes this situation, and frees the resources that
are no longer used. It is safe to ignore the dirty state
of the file system after a crash by forcibly mounting it
@@ -2381,7 +2377,7 @@ device_probe_and_attach: cbb0 attach ret
compile software. The most important table set by
<literal>maxusers</literal> is the maximum number of
processes, which is set to
- <literal>20 + 16 * maxusers</literal>. If
+ <literal>20 + 16 * maxusers</literal>. If
<literal>maxusers</literal> is set to <literal>1</literal>,
there can only be
<literal>36</literal> simultaneous processes, including
@@ -2493,12 +2489,11 @@ device_probe_and_attach: cbb0 attach ret
</indexterm>
<para>The <varname>net.inet.ip.portrange.*</varname>
- &man.sysctl.8;
- variables control the port number ranges automatically bound
- to <literal>TCP</literal> and <literal>UDP</literal>
- sockets. There are three ranges: a low range, a default
- range, and a high range. Most network programs use the
- default range which is controlled by
+ &man.sysctl.8; variables control the port number ranges
+ automatically bound to <literal>TCP</literal> and
+ <literal>UDP</literal> sockets. There are three ranges: a
+ low range, a default range, and a high range. Most network
+ programs use the default range which is controlled by
<varname>net.inet.ip.portrange.first</varname> and
<varname>net.inet.ip.portrange.last</varname>, which default
to <literal>1024</literal> and <literal>5000</literal>,
@@ -2570,12 +2565,12 @@ device_probe_and_attach: cbb0 attach ret
conditions, but it can also result in higher &man.ping.8;
times over slow links, though still much lower than without
the inflight algorithm. In such cases, try reducing this
- parameter to <literal>15</literal>,
- <literal>10</literal>, or <literal>5</literal> and
- reducing <varname>net.inet.tcp.inflight.min</varname>
- to a value such as <literal>3500</literal> to get the
- desired effect. Reducing these parameters should be done
- as a last resort only.</para>
+ parameter to <literal>15</literal>, <literal>10</literal>,
+ or <literal>5</literal> and reducing
+ <varname>net.inet.tcp.inflight.min</varname> to a value such
+ as <literal>3500</literal> to get the desired effect.
+ Reducing these parameters should be done as a last resort
+ only.</para>
</sect3>
</sect2>
@@ -2634,9 +2629,9 @@ kern.maxvnodes: 100000</screen>
<para>Adding a new hard drive for swap gives better performance
than adding a partition on an existing drive. Setting up
- partitions and hard drives is explained in <xref
- linkend="disks-adding"/> while <xref
- linkend="configtuning-initial"/> discusses partition
+ partitions and hard drives is explained in
+ <xref linkend="disks-adding"/> while
+ <xref linkend="configtuning-initial"/> discusses partition
layouts and swap partition size considerations.</para>
<para>Use &man.swapon.8; to add a swap partition to the system.
@@ -2645,7 +2640,6 @@ kern.maxvnodes: 100000</screen>
<screen>&prompt.root; <userinput>swapon<replaceable> /dev/ada1s1b</replaceable></userinput></screen>
<warning>
-
<para>It is possible to use any partition not currently
mounted, even if it already contains data. Using
&man.swapon.8; on a partition that contains data will
@@ -2685,7 +2679,6 @@ kern.maxvnodes: 100000</screen>
<orderedlist>
<listitem>
-
<para>The <filename>GENERIC</filename> kernel already
includes the memory disk driver (&man.md.4;) required
for this operation. When building a custom kernel,
@@ -2761,8 +2754,8 @@ kern.maxvnodes: 100000</screen>
temperature increases unexpectedly.</para>
<para>This section provides comprehensive information about
- <acronym>ACPI</acronym>. References will be provided for further
- reading.</para>
+ <acronym>ACPI</acronym>. References will be provided for
+ further reading.</para>
<sect2 id="acpi-intro">
<title>What Is ACPI?</title>
@@ -2979,13 +2972,12 @@ kern.maxvnodes: 100000</screen>
<para>Most &os; developers watch &a.current;, but one should
submit problems to &a.acpi.name; to be sure it is seen. Be
patient when waiting for a response. If the bug is not
- immediately apparent, submit a
- <acronym>PR</acronym> using &man.send-pr.1;. When entering a
- <acronym>PR</acronym>, include the same information as
- requested above. This helps developers to track the problem
- and resolve it. Do not send a <acronym>PR</acronym> without
- emailing &a.acpi.name; first as it is likely that the problem
- has been reported before.</para>
+ immediately apparent, submit a <acronym>PR</acronym> using
+ &man.send-pr.1;. When entering a <acronym>PR</acronym>,
+ include the same information as requested above. This helps
+ developers to track the problem and resolve it. Do not send a
+ <acronym>PR</acronym> without emailing &a.acpi.name; first as
+ it is likely that the problem has been reported before.</para>
</sect2>
<sect2 id="ACPI-background">
@@ -3278,8 +3270,9 @@ hw.acpi.s4bios: 0</screen>
<acronym>ASL</acronym>, use &man.acpidump.8;. Include both
<option>-t</option>, to show the contents of the fixed tables,
and <option>-d</option>, to disassemble the
- <acronym>AML</acronym>. Refer to <xref
- linkend="ACPI-submitdebug"/> for an example syntax.</para>
+ <acronym>AML</acronym>. Refer to
+ <xref linkend="ACPI-submitdebug"/> for an example
+ syntax.</para>
<para>The simplest first check is to recompile the
<acronym>ASL</acronym> to check for errors. Warnings can
More information about the svn-doc-all
mailing list