Remove contractions. Minor grammatical cleanup.
This commit is contained in:
Ceri Davies
parent
21a8077d8a
commit
4ab2404ae0
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=15854
1 changed files with 12 additions and 12 deletions
|
|
@ -176,7 +176,7 @@
|
|||
largest swap partition. Keeping the swap partitions near the
|
||||
same size will allow the kernel to optimally stripe swap space
|
||||
across disks.
|
||||
Large swap sizes are fine, regardless if it's not
|
||||
Large swap sizes are fine, even if swap is not
|
||||
used much. It might be easier to recover
|
||||
from a runaway program before being forced to reboot.</para>
|
||||
</sect3>
|
||||
|
|
@ -372,7 +372,7 @@ exit 0
|
|||
the above sample script to be picked up and run at the proper time during
|
||||
system startup, you should save it to a file called
|
||||
<filename>FooBar.sh</filename> in
|
||||
<filename>/usr/local/etc/rc.d</filename> and make sure it's
|
||||
<filename>/usr/local/etc/rc.d</filename> and make sure it is
|
||||
executable. You can make a shell script executable with &man.chmod.1;
|
||||
as shown below:</para>
|
||||
|
||||
|
|
@ -686,7 +686,7 @@ ifconfig_dc1="inet 10.0.0.1 netmask 255.255.255.0 media 10baseT/UTP"</programlis
|
|||
you have to try two things. First, ping the interface itself,
|
||||
and then ping another machine on the LAN.</para>
|
||||
|
||||
<para>First let's test the interface:</para>
|
||||
<para>First test the local interface:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>ping -c5 192.168.1.3</userinput>
|
||||
PING 192.168.1.3 (192.168.1.3): 56 data bytes
|
||||
|
|
@ -859,7 +859,7 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
|
|||
fortunately quite simple. For a 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 1's.</para>
|
||||
netmask of all <literal>1</literal>s.</para>
|
||||
|
||||
<para>For example, consider the case where the
|
||||
<devicename>fxp0</devicename> interface is
|
||||
|
|
@ -1344,7 +1344,7 @@ kern.maxfiles: 2088 -> 5000</screen>
|
|||
<varname>vm.swap_idle_threshold2</varname> allows you to depress
|
||||
the priority of memory pages associated with idle processes more
|
||||
quickly then the normal pageout algorithm. This gives a helping
|
||||
hand to the pageout daemon. do not turn this option on unless
|
||||
hand to the pageout daemon. Do not turn this option on unless
|
||||
you need it, because the tradeoff you are making is essentially
|
||||
pre-page memory sooner rather than later; thus eating more swap
|
||||
and disk bandwidth. In a small system this option will have a
|
||||
|
|
@ -1398,8 +1398,8 @@ kern.maxfiles: 2088 -> 5000</screen>
|
|||
works (especially with modern drives). Newer versions of FreeBSD
|
||||
(5.0+) should use the <varname>kern.cam.scsi_delay</varname>
|
||||
boot time tunable. The tunable, and kernel config option accept
|
||||
values in terms of <emphasis>milliseconds</emphasis> and NOT
|
||||
<emphasis>seconds</emphasis></para>
|
||||
values in terms of <emphasis>milliseconds</emphasis> and <emphasis>not</emphasis>
|
||||
<emphasis>seconds</emphasis>.</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
|
|
@ -1648,7 +1648,7 @@ kern.maxfiles: 2088 -> 5000</screen>
|
|||
(e.g. &man.sendmail.8;, or <application>Apache</application>) but
|
||||
will often have a directive in it's configuration file to adjust
|
||||
the queue size. Large listen queues also do a better job of
|
||||
avoiding Denial of Service <abbrev>DoS</abbrev> attacks.</para>
|
||||
avoiding Denial of Service (<abbrev>DoS</abbrev>) attacks.</para>
|
||||
</sect3>
|
||||
|
||||
</sect2>
|
||||
|
|
@ -1713,7 +1713,7 @@ kern.maxfiles: 2088 -> 5000</screen>
|
|||
consider firewall effects when changing the port range. Some
|
||||
firewalls may block large ranges of ports (usually low-numbered
|
||||
ports) and expect systems to use higher ranges of ports for
|
||||
outgoing connections -- for this reason it is recommended that
|
||||
outgoing connections — for this reason it is recommended that
|
||||
<varname>net.inet.ip.portrange.first</varname> be lowered.</para>
|
||||
</sect3>
|
||||
|
||||
|
|
@ -1741,7 +1741,7 @@ kern.maxfiles: 2088 -> 5000</screen>
|
|||
<varname>net.inet.tcp.inflight_debug</varname> to
|
||||
<literal>0</literal> (disable debugging), and for production use
|
||||
setting <varname>net.inet.tcp.inflight_min</varname> to at least
|
||||
<literal>6144</literal> may be beneficial. Note however, that
|
||||
<literal>6144</literal> may be beneficial. However, note that
|
||||
setting high minimums may effectively disable bandwidth limiting
|
||||
depending on the link. The limiting feature reduces the amount of
|
||||
data built up in intermediate route and switch packet queues as
|
||||
|
|
@ -1772,8 +1772,8 @@ kern.maxfiles: 2088 -> 5000</screen>
|
|||
<sect1 id="adding-swap-space">
|
||||
<title>Adding Swap Space</title>
|
||||
|
||||
<para>No matter how well you plan, sometimes a system doesn't run
|
||||
as you expect. If you find you need more swap space, it's
|
||||
<para>No matter how well you plan, sometimes a system does not run
|
||||
as you expect. If you find you need more swap space, it is
|
||||
simple enough to add. You have three ways to increase swap
|
||||
space: adding a new hard drive, enabling swap over NFS, and
|
||||
creating a swap file on an existing partition.</para>
|
||||
|
|
|
|||
Loading…
Reference in a new issue