svn commit: r43917 - head/en_US.ISO8859-1/books/handbook/firewalls

[Dru Lavigne]

Author: dru
Date: Fri Feb 14 01:35:02 2014
New Revision: 43917
URL: http://svnweb.freebsd.org/changeset/doc/43917

Log:
  White space fix only. Translators can ignore.
  
  Sponsored by: iXsystems

Modified:
  head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml

Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml	Fri Feb 14 01:30:43 2014	(r43916)
+++ head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml	Fri Feb 14 01:35:02 2014	(r43917)
@@ -215,8 +215,8 @@
       integrated part of the base system.
       <application>PF</application> is a complete, full-featured
       firewall that has optional support for
-      <application>ALTQ</application> (Alternate Queuing), which provides
-      Quality of Service (<acronym>QoS</acronym>).</para>
+      <application>ALTQ</application> (Alternate Queuing), which
+      provides Quality of Service (<acronym>QoS</acronym>).</para>
 
     <para>Since the OpenBSD Project maintains the definitive
       reference for <application>PF</application> in the <link
@@ -232,25 +232,27 @@
     <sect2>
       <title>Enabling <application>PF</application></title>
 
-      <para>In order to use <application>PF</application>, its kernel module must be first
-	loaded.  This section describes the entries that can be added
-	to <filename>/etc/rc.conf</filename> in order to enable
-	<application>PF</application>.</para>
+      <para>In order to use <application>PF</application>, its kernel
+	module must be first loaded.  This section describes the
+	entries that can be added to <filename>/etc/rc.conf</filename>
+	in order to enable <application>PF</application>.</para>
 
       <para>Start by adding the following line to
 	<filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>pf_enable="YES"</programlisting>
 
-      <para>Additional options, described in &man.pfctl.8;, can be passed to
-	<application>PF</application> when it is started.  Add this entry to 
-	<filename>/etc/rc.conf</filename> and specify any
-	required flags between the two quotes (<literal>""</literal>):</para>
-      
+      <para>Additional options, described in &man.pfctl.8;, can be
+	passed to <application>PF</application> when it is started.
+	Add this entry to  <filename>/etc/rc.conf</filename> and
+	specify any required flags between the two quotes
+	(<literal>""</literal>):</para>
+
       <programlisting>pf_flags=""                     # additional flags for pfctl startup</programlisting>
 
-      <para><application>PF</application> will not start if it cannot find its
-	ruleset configuration file.  The default ruleset is already created and is named
+      <para><application>PF</application> will not start if it cannot
+	find its ruleset configuration file.  The default ruleset is
+	already created and is named
 	<filename>/etc/pf.conf</filename>.  If a custom ruleset has
 	been saved somewhere else, add a line to
 	<filename>/etc/rc.conf</filename> which specifies the full
@@ -261,29 +263,33 @@
       <para>The sample <filename>pf.conf</filename>
 	can be found in
 	<filename>/usr/share/examples/pf/</filename>.  The rest of
-	this chapter demonstrates how to create a custom ruleset.</para>
- 
-      <para>Logging support for <application>PF</application> is provided by
-	&man.pflog.4;.  To enable logging support, add this
-	line to <filename>/etc/rc.conf</filename>:</para>
+	this chapter demonstrates how to create a custom
+	ruleset.</para>
+
+      <para>Logging support for <application>PF</application> is
+	provided by &man.pflog.4;.  To enable logging support, add
+	this line to <filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>pflog_enable="YES"</programlisting>
 
       <para>The following lines can also be added in order to
 	change the default location of the log file or to specify any
-	additional flags to pass to &man.pflog.4; when it is started:</para>
+	additional flags to pass to &man.pflog.4; when it is
+	started:</para>
 
  <programlisting>pflog_logfile="/var/log/pflog"  # where pflogd should store the logfile
 pflog_flags=""                  # additional flags for pflogd startup</programlisting>
 
-      <para>Finally, if there is a <acronym>LAN</acronym> behind the firewall and packets need to
-	be forwarded for the computers on the <acronym>LAN</acronym>, or <acronym>NAT</acronym> is required,
-	add the following option:</para>
+      <para>Finally, if there is a <acronym>LAN</acronym> behind the
+	firewall and packets need to be forwarded for the computers on
+	the <acronym>LAN</acronym>, or <acronym>NAT</acronym> is
+	required, add the following option:</para>
 
       <programlisting>gateway_enable="YES"            # Enable as LAN gateway</programlisting>
 
       <para>After saving the needed edits,
-	<application>PF</application> can be started with logging support by typing:</para>
+	<application>PF</application> can be started with logging
+	support by typing:</para>
 
       <screen>&prompt.root; <userinput>service pf start</userinput>
 &prompt.root; <userinput>service pflog start</userinput></screen>