PERFORCE change 209765 for review
Rene Ladan
rene at FreeBSD.org
Wed Apr 18 08:26:17 UTC 2012
http://p4web.freebsd.org/@@209765?ac=10
Change 209765 by rene at rene_acer on 2012/04/18 08:26:11
IFC
Affected files ...
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#136 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#81 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/nanobsd/article.sgml#6 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#44 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#22 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml#23 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#137 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#74 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/boot/chapter.sgml#18 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/desktop/chapter.sgml#62 integrate
.. //depot/projects/docproj_nl/www/en/advocacy/index.sgml#4 integrate
.. //depot/projects/docproj_nl/www/en/developers.sgml#74 integrate
.. //depot/projects/docproj_nl/www/en/support/bugreports.sgml#2 integrate
.. //depot/projects/docproj_nl/www/share/sgml/news.xml#139 integrate
Differences ...
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#136 (text+ko) ====
@@ -1,4 +1,4 @@
-<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.1078 2012/04/12 20:19:17 madpilot Exp $ -->
+<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.1081 2012/04/17 16:27:03 jgh Exp $ -->
<!--
NOTE TO COMMITTERS: Contributors lists are sorted in alphabetical
order by first name.
@@ -1476,6 +1476,11 @@
</listitem>
<listitem>
+ <para>Bryan Drewery
+ <email>bryan at shatow.net</email></para>
+ </listitem>
+
+ <listitem>
<para>Byung-Hee HWANG
<email> bh at izb.knu.ac.kr</email></para>
</listitem>
@@ -4342,7 +4347,7 @@
<listitem>
<para>Jason Bacon
- <email>bacon at smithers.neuro.mcw.edu</email></para>
+ <email>jwbacon at tds.net</email></para>
</listitem>
<listitem>
@@ -9174,6 +9179,11 @@
</listitem>
<listitem>
+ <para>Shane Ambler
+ <email>freebsd at shaneware.biz</email></para>
+ </listitem>
+
+ <listitem>
<para>Shane Kinney
<email>mod6 at freebsdhackers.net</email></para>
</listitem>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#81 (text+ko) ====
@@ -1,4 +1,4 @@
-<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml,v 1.356 2012/04/13 16:47:39 monthadar Exp $ -->
+<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml,v 1.357 2012/04/15 15:42:23 sperber Exp $ -->
<!--
NOTE TO NEW COMMITTERS: Core and committers lists are sorted in
alphabetical order by last name. Please keep in mind that fact while
@@ -1083,6 +1083,10 @@
</listitem>
<listitem>
+ <para>&a.sperber;</para>
+ </listitem>
+
+ <listitem>
<para>&a.sepotvin;</para>
</listitem>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/nanobsd/article.sgml#6 (text+ko) ====
@@ -15,7 +15,7 @@
</author>
</authorgroup>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/nanobsd/article.sgml,v 1.7 2010/07/13 04:06:37 maxim Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/nanobsd/article.sgml,v 1.8 2012/04/16 16:46:20 maxim Exp $</pubdate>
<copyright>
<year>2006</year>
@@ -477,7 +477,7 @@
<title>Using &man.nc.1;</title>
<para>Try this example if the remote host is not running neither
- &man.ftp.1; or &man.sshd.8; service:</para>
+ &man.ftpd.8; or &man.sshd.8; service:</para>
<procedure>
<step>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#44 (text+ko) ====
@@ -31,7 +31,7 @@
<corpauthor>The &os; Documentation Project</corpauthor>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1145 2012/03/29 00:53:50 gjb Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1146 2012/04/14 13:52:52 eadler Exp $</pubdate>
<copyright>
<year>1995</year>
@@ -77,7 +77,6 @@
&tm-attrib.sparc;
&tm-attrib.sun;
&tm-attrib.usrobotics;
- &tm-attrib.xfree86;
&tm-attrib.general;
</legalnotice>
@@ -4400,7 +4399,7 @@
tree.</para>
<para>This is particularly a problem for &os; users who
- utilize &man.cvsup.1; (or &man.csup.1;) to track the Ports
+ utilize &man.csup.1; to track the Ports
Collection but choose not to install certain categories by
specifying them in <filename>refuse</filename>. In theory,
one should be able to refuse categories, but in practice
@@ -5238,15 +5237,6 @@
</varlistentry>
<varlistentry>
- <term>ReiserFS</term>
-
- <listitem>
- <para>&os; includes a read-only ReiserFS driver. For
- more information, see &man.mount.reiserfs.8;.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
<term>ZFS</term>
<listitem>
@@ -6313,7 +6303,7 @@
</question>
<answer>
- <para>Use &man.killall.1;.</para>
+ <para>Use &man.pkill.1;.</para>
</answer>
</qandaentry>
@@ -6356,21 +6346,6 @@
world.</para>
</answer>
</qandaentry>
-
- <qandaentry>
- <question id="where-is-makedev">
- <para>What happened to
- <filename>/dev/MAKEDEV</filename>?</para>
- </question>
-
- <answer>
- <para>&os; 5.<replaceable>X</replaceable> and beyond use
- the &man.devfs.8; device-on-demand system. Device drivers
- automatically create new device nodes as they are needed,
- obsoleting <filename>/dev/MAKEDEV</filename>.</para>
- </answer>
- </qandaentry>
-
<qandaentry>
<question id="add-pty">
<para>How do I add pseudoterminals to the system?</para>
@@ -6765,85 +6740,6 @@
</qandaentry>
<qandaentry>
- <question id="which-X">
- <para>Which X implementations are available for &os;?</para>
- </question>
-
- <answer>
- <para>Historically, the default implementation of X on &os;
- has been &xfree86; which is maintained by <ulink
- url="http://www.xfree86.org">The XFree86 Project, Inc.</ulink>
- This software was installed by default on &os; versions up
- until 4.10 and 5.2. Although &xorg; itself maintained an
- implementation during that time period, it was basically
- only provided as a reference platform, as it had suffered
- greatly from bitrot over the years.</para>
-
- <para>However, early in 2004, some XFree86 developers left
- that project over issues including the pace of code changes,
- future directions, and interpersonal conflicts, and are now
- contributing code directly to &xorg; instead. At that time,
- &xorg; updated its source tree to the last &xfree86; release
- before its subsequent licensing change (<application>XFree86
- version 4.3.99.903</application>), incorporated many changes
- that had previously been maintained separately, and has
- released that software as
- <application>X11R6.7.0</application>. A separate but
- related project, <ulink
- url="http://www.freedesktop.org/wiki/">freedesktop.org</ulink>
- (or <literal>fd.o</literal> for short), is working on
- rearchitecting the original &xfree86; code to offload more
- work onto the graphics cards (with the goal of increased
- performance) and make it more modular (with the goal of
- increased maintainability, and thus faster releases as well
- as easier configuration). &xorg; intends to incorporate the
- <literal>freedesktop.org</literal> changes in its future
- releases.</para>
-
- <para>As of July 2004, in &os.current;,
- &xfree86; has been replaced with &xorg; as the default
- implementation. Since then the default X11 implementation
- in &os; is &xorg;.</para>
-
- <para>For further information, read the <ulink
- url="&url.books.handbook;/x11.html">X11</ulink> section of
- the &os; Handbook.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question id="xfree86-split">
- <para>Why did the X projects split, anyway?</para>
- </question>
-
- <answer>
- <para>The answer to this question is outside the scope of this
- FAQ. Note that there are voluminous postings in various
- mailing list archives on the Internet; please use your
- favorite search engine to investigate the history instead of
- asking this question on the &os; mailing lists. It may even
- be the case that only the participants will ever know for
- certain.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question id="why-choose-xorg">
- <para>Why did &os; choose to go with the &xorg; ports by
- default?</para>
- </question>
-
- <answer>
- <para>The &xorg; developers claimed that their goal is to
- release more often and incorporate new features more
- quickly. If they are able to do so, this will be very
- attractive. Also, their software still uses the traditional
- X license, while &xfree86; is using their modified
- one.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question id="running-X">
<para>I want to run X, how do I go about it?</para>
</question>
@@ -7226,7 +7122,7 @@
<qandaentry>
<question id="xfree86-root">
- <para>Before, I was able to run &xfree86; as a regular user.
+ <para>Before, I was able to run &xorg; as a regular user.
Why does it now say that I must be
<username>root</username>?</para>
</question>
@@ -7234,18 +7130,9 @@
<answer>
<para>All X servers need to be run as
<username>root</username> in order to get direct access to
- your video hardware. Older versions of &xfree86; (<=
- 3.3.6) installed all bundled servers to be automatically run
- as <username>root</username> (setuid to
- <username>root</username>). This is obviously a security
- hazard because X servers are large, complicated programs.
- Newer versions of &xfree86; do not install the servers
- setuid to <username>root</username> for just this
- reason.</para>
+ your video hardware.</para>
- <para>Obviously, running an X server as the
- <username>root</username> user is not acceptable, nor a good
- idea security-wise. There are two ways to be able to use X
+ <para>There are two ways to be able to use &xorg;
as a regular user. The first is to use
<command>xdm</command> or another display manager (e.g.,
<command>kdm</command>); the second is to use the
@@ -7257,7 +7144,7 @@
sessions; it is essentially the graphical counterpart of
&man.getty.8; and &man.login.1;. For more information on
<command>xdm</command> see <ulink
- url="http://www.xfree86.org/sos/resources.html">the &xfree86; documentation</ulink>,
+ url="http://www.x.org/wiki/UserDocumentation">the &xorg; documentation</ulink>,
and the <link
linkend="xdm-boot">the FAQ entry</link> on it.</para>
@@ -8159,37 +8046,6 @@
to <literal>0</literal>.</para>
</answer>
</qandaentry>
-
- <qandaentry>
- <question id="cvsup-missing-libs">
- <para>I have just installed <application>CVSup</application>
- but trying to execute it produces errors. What is
- wrong?</para>
- </question>
-
- <answer>
- <para>First, see if the error message you are receiving is
- like the one shown below.</para>
-
- <programlisting>/usr/libexec/ld-elf.so.1: Shared object "libXaw.so.6" not found</programlisting>
-
- <para>Errors like these are caused by installing the <filename
- role="package">net/cvsup</filename> port on a machine which
- does not have the <application>&xorg;</application> suite.
- If you want to use the <acronym>GUI</acronym> included with
- <application>CVSup</application> you will need to install
- <application>&xorg;</application> now. Alternatively if you
- just wish to use <application>CVSup</application> from a
- command line you should delete the package previously
- installed. Then install the <filename
- role="package">net/cvsup-without-gui</filename> or the
- <filename role="package">net/csup</filename> port. If you
- have a recent &os; release you may use &man.csup.1;. This
- is covered in more detail in the <ulink
- url="&url.books.handbook;/cvsup.html">CVSup section</ulink>
- of the Handbook.</para>
- </answer>
- </qandaentry>
</qandaset>
</chapter>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#22 (text+ko) ====
@@ -1,28 +1,28 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.254 2012/03/26 16:56:36 eadler Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.257 2012/04/18 05:54:17 wblock Exp $
-->
<chapter id="config-tuning">
<chapterinfo>
<authorgroup>
<author>
- <firstname>Chern</firstname>
+ <firstname>Chern</firstname>
<surname>Lee</surname>
<contrib>Written by </contrib>
</author>
</authorgroup>
<authorgroup>
<author>
- <firstname>Mike</firstname>
+ <firstname>Mike</firstname>
<surname>Smith</surname>
<contrib>Based on a tutorial written by </contrib>
</author>
</authorgroup>
<authorgroup>
<author>
- <firstname>Matt</firstname>
+ <firstname>Matt</firstname>
<surname>Dillon</surname>
<contrib>Also based on tuning(7) written by </contrib>
</author>
@@ -37,12 +37,11 @@
<indexterm><primary>system configuration</primary></indexterm>
<indexterm><primary>system optimization</primary></indexterm>
- <para>One of the important aspects of &os; is system configuration.
- Correct system configuration will help prevent headaches during future upgrades.
- This chapter will explain much of the &os; configuration process,
- including some of the parameters which
- can be set to tune a &os; system.
- </para>
+ <para>One of the important aspects of &os; is system
+ configuration. Correct system configuration will help prevent
+ headaches during future upgrades. This chapter will explain
+ much of the &os; configuration process, including some of the
+ parameters which can be set to tune a &os; system.</para>
<para>After reading this chapter, you will know:</para>
@@ -51,24 +50,33 @@
<para>How to efficiently work with
file systems and swap partitions.</para>
</listitem>
+
<listitem>
- <para>The basics of <filename>rc.conf</filename> configuration and
- <filename class="directory">/usr/local/etc/rc.d</filename> startup systems.</para>
+ <para>The basics of <filename>rc.conf</filename> configuration
+ and <filename
+ class="directory">/usr/local/etc/rc.d</filename> startup
+ systems.</para>
</listitem>
+
<listitem>
<para>How to configure and test a network card.</para>
</listitem>
+
<listitem>
- <para>How to configure virtual hosts on your network devices.</para>
+ <para>How to configure virtual hosts on your network
+ devices.</para>
</listitem>
+
<listitem>
<para>How to use the various configuration files in
<filename class="directory">/etc</filename>.</para>
</listitem>
+
<listitem>
- <para>How to tune &os; using <command>sysctl</command>
- variables.</para>
+ <para>How to tune &os; using <command>sysctl</command>
+ variables.</para>
</listitem>
+
<listitem>
<para>How to tune disk performance and modify kernel
limitations.</para>
@@ -82,8 +90,10 @@
<para>Understand &unix; and &os; basics (<xref
linkend="basics">).</para>
</listitem>
+
<listitem>
- <para>Be familiar with the basics of kernel configuration/compilation
+ <para>Be familiar with the basics of kernel
+ configuration/compilation
(<xref linkend="kernelconfig">).</para>
</listitem>
</itemizedlist>
@@ -97,66 +107,75 @@
<indexterm><primary>partition layout</primary></indexterm>
<indexterm>
- <primary><filename class="directory">/etc</filename></primary>
+ <primary><filename class="directory">/etc</filename></primary>
</indexterm>
<indexterm>
- <primary><filename class="directory">/var</filename></primary>
+ <primary><filename class="directory">/var</filename></primary>
</indexterm>
<indexterm>
- <primary><filename class="directory">/usr</filename></primary>
+ <primary><filename class="directory">/usr</filename></primary>
</indexterm>
<sect3>
<title>Base Partitions</title>
- <para>When laying out file systems with &man.bsdlabel.8;
- or &man.sysinstall.8;, remember that hard
- drives transfer data faster from the outer
- tracks to the inner.
- Thus smaller and heavier-accessed file systems
- should be closer to the outside of the drive, while
- larger partitions like <filename class="directory">/usr</filename> should be placed
- toward the inner parts of the disk. It is a good idea to create
- partitions in an order similar to: root, swap,
- <filename class="directory">/var</filename>, <filename class="directory">/usr</filename>.</para>
+ <para>When laying out file systems with &man.bsdlabel.8; or
+ &man.sysinstall.8;, remember that hard drives transfer data
+ faster from the outer tracks to the inner. Thus smaller and
+ heavier-accessed file systems should be closer to the
+ outside of the drive, while larger partitions like
+ <filename class="directory">/usr</filename> should be placed
+ toward the inner parts of the disk. It is a good idea to
+ create partitions in an order similar to: root, swap,
+ <filename class="directory">/var</filename>,
+ <filename class="directory">/usr</filename>.</para>
- <para>The size of the <filename class="directory">/var</filename> partition
- reflects the intended machine usage.
- The <filename class="directory">/var</filename> file system is used to hold
- mailboxes, log files, and printer spools. Mailboxes and log
- files can grow to unexpected sizes depending
- on how many users exist and how long log
- files are kept. Most users will rarely need more than about a
- gigabyte of free disk space in <filename class="directory">/var</filename>.</para>
+ <para>The size of the
+ <filename class="directory">/var</filename> partition
+ reflects the intended machine usage. The
+ <filename class="directory">/var</filename> file system is
+ used to hold mailboxes, log files, and printer spools.
+ Mailboxes and log files can grow to unexpected sizes
+ depending on how many users exist and how long log files are
+ kept. Most users will rarely need more than about a
+ gigabyte of free disk space in
+ <filename class="directory">/var</filename>.</para>
<note>
- <para>There are a few times that a lot of disk space is required
- in <filename class="directory">/var/tmp</filename>. When new software is installed
- with &man.pkg.add.1; the packaging tools extract a temporary copy
- of the packages under <filename class="directory">/var/tmp</filename>. Large
- software packages, like <application>Firefox</application>,
- <application>OpenOffice</application> or <application>LibreOffice</application>
- may be tricky to install if there is not enough disk space under
+ <para>There are a few times that a lot of disk space is
+ required in
+ <filename class="directory">/var/tmp</filename>. When new
+ software is installed with &man.pkg.add.1; the packaging
+ tools extract a temporary copy of the packages under
+ <filename class="directory">/var/tmp</filename>. Large
+ software packages, like
+ <application>Firefox</application>,
+ <application>OpenOffice</application> or
+ <application>LibreOffice</application> may be tricky to
+ install if there is not enough disk space under
<filename class="directory">/var/tmp</filename>.</para>
</note>
- <para>The <filename class="directory">/usr</filename> partition holds many
- of the files required to support the system, including the &man.ports.7;
- collection (recommended) and the source code (optional). Both the
- ports and the sources of the base system are optional at install
- time, but we recommend at least 2 gigabytes for this
- partition.</para>
+ <para>The <filename class="directory">/usr</filename>
+ partition holds many of the files required to support the
+ system, including the &man.ports.7; collection (recommended)
+ and the source code (optional). Both the ports and the
+ sources of the base system are optional at install time, but
+ we recommend at least 2 gigabytes for this partition.</para>
<para>When selecting partition sizes, keep the space
requirements in mind. Running out of space in
one partition while barely using another can be a
hassle.</para>
- <note><para>Some users have found that &man.sysinstall.8;'s
+ <note>
+ <para>Some users have found that &man.sysinstall.8;'s
<literal>Auto-defaults</literal> partition sizer will
- sometimes select smaller than adequate <filename class="directory">/var</filename>
- and <filename class="directory">/</filename> partitions. Partition wisely and
- generously.</para></note>
+ sometimes select smaller than adequate
+ <filename class="directory">/var</filename> and
+ <filename class="directory">/</filename> partitions.
+ Partition wisely and generously.</para>
+ </note>
</sect3>
<sect3 id="swap-design">
@@ -165,64 +184,60 @@
<indexterm><primary>swap sizing</primary></indexterm>
<indexterm><primary>swap partition</primary></indexterm>
- <para>As a rule of thumb, the swap partition should be
- about double the size of system memory (RAM). For example,
- if the machine has 128 megabytes of memory,
- the swap file should be 256 megabytes. Systems with
- less memory may perform better with more swap.
- Less than 256 megabytes of swap is not recommended and
- memory expansion should be considered.
- The kernel's VM paging algorithms are tuned to
- perform best when the swap partition is at least two times the
- size of main memory. Configuring too little swap can lead to
- inefficiencies in the VM page scanning code and might create
- issues later if more memory is added.</para>
+ <para>As a rule of thumb, the swap partition should be about
+ double the size of system memory (RAM). For example, if the
+ machine has 128 megabytes of memory, the swap file
+ should be 256 megabytes. Systems with less memory may
+ perform better with more swap. Less than 256 megabytes
+ of swap is not recommended and memory expansion should be
+ considered. The kernel's VM paging algorithms are tuned to
+ perform best when the swap partition is at least two times
+ the size of main memory. Configuring too little swap can
+ lead to inefficiencies in the VM page scanning code and
+ might create issues later if more memory is added.</para>
- <para>On larger systems with multiple SCSI disks (or
- multiple IDE disks operating on different controllers), it is
- recommend that a swap is configured on each drive (up
- to four drives). The swap partitions should be
- approximately the same size. The kernel can handle arbitrary
- sizes but internal data structures scale to 4 times the
- 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, even if swap is not
- used much. It might be easier to recover
- from a runaway program before being forced to reboot.</para>
+ <para>On larger systems with multiple SCSI disks (or multiple
+ IDE disks operating on different controllers), it is
+ recommend that a swap is configured on each drive (up to
+ four drives). The swap partitions should be approximately
+ the same size. The kernel can handle arbitrary sizes but
+ internal data structures scale to 4 times the 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, even if swap is not used
+ much. It might be easier to recover from a runaway program
+ before being forced to reboot.</para>
</sect3>
<sect3>
<title>Why Partition?</title>
- <para>Several users think a single large partition will be fine,
- but there are several reasons why this is a bad idea.
+ <para>Several users think a single large partition will be
+ fine, but there are several reasons why this is a bad idea.
First, each partition has different operational
- characteristics and separating them allows the file system to
- tune accordingly. For example, the root
- and <filename class="directory">/usr</filename> partitions are read-mostly, without
- much writing. While a lot of reading and writing could
- occur in <filename class="directory">/var</filename> and
+ characteristics and separating them allows the file system
+ to tune accordingly. For example, the root and
+ <filename class="directory">/usr</filename> partitions are
+ read-mostly, without much writing. While a lot of reading
+ and writing could occur in
+ <filename class="directory">/var</filename> and
<filename class="directory">/var/tmp</filename>.</para>
<para>By properly partitioning a system, fragmentation
- introduced in the smaller write heavy partitions
- will not bleed over into the mostly-read partitions.
- Keeping the write-loaded partitions closer to
- the disk's edge,
- will
+ introduced in the smaller write heavy partitions will not
+ bleed over into the mostly-read partitions. Keeping the
+ write-loaded partitions closer to the disk's edge, will
increase I/O performance in the partitions where it occurs
- the most. Now while I/O
- performance in the larger partitions may be needed,
- shifting them more toward the edge of the disk will not
- lead to a significant performance improvement over moving
+ the most. Now while I/O performance in the larger
+ partitions may be needed, shifting them more toward the edge
+ of the disk will not lead to a significant performance
+ improvement over moving
<filename class="directory">/var</filename> to the edge.
Finally, there are safety concerns. A smaller, neater root
- partition which is mostly read-only has a greater
- chance of surviving a bad crash.</para>
+ partition which is mostly read-only has a greater chance of
+ surviving a bad crash.</para>
</sect3>
</sect2>
-
</sect1>
<sect1 id="configtuning-core-configuration">
@@ -234,20 +249,20 @@
</indexterm>
<para>The principal location for system configuration information
- is within <filename>/etc/rc.conf</filename>. This file
- contains a wide range of configuration information, principally
- used at system startup to configure the system. Its name
- directly implies this; it is configuration information for the
+ is within <filename>/etc/rc.conf</filename>. This file contains
+ a wide range of configuration information, principally used at
+ system startup to configure the system. Its name directly
+ implies this; it is configuration information for the
<filename>rc*</filename> files.</para>
<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
- should not be copied verbatim to <filename class="directory">/etc</filename> - it
- contains default values, not examples. All system-specific
- changes should be made in the <filename>rc.conf</filename>
- file itself.</para>
+ <filename>rc.conf</filename> file to override the default
+ settings from <filename>/etc/defaults/rc.conf</filename>. The
+ defaults file should not be copied verbatim to
+ <filename class="directory">/etc</filename> - it contains
+ default values, not examples. All system-specific changes
+ should be made in the <filename>rc.conf</filename> file
+ itself.</para>
<para>A number of strategies may be applied in clustered
applications to separate site-wide configuration from
@@ -258,27 +273,33 @@
example:</para>
<itemizedlist>
- <listitem><para><filename>/etc/rc.conf</filename>:</para>
+ <listitem>
+ <para><filename>/etc/rc.conf</filename>:</para>
- <programlisting>sshd_enable="YES"
+ <programlisting>sshd_enable="YES"
keyrate="fast"
-defaultrouter="10.1.1.254"</programlisting></listitem>
+defaultrouter="10.1.1.254"</programlisting>
+
+ </listitem>
+
+ <listitem>
+ <para><filename>/etc/rc.conf.local</filename>:</para>
- <listitem><para><filename>/etc/rc.conf.local</filename>:</para>
+ <programlisting>hostname="node1.example.org"
+ifconfig_fxp0="inet 10.1.1.1/8"</programlisting>
-<programlisting>hostname="node1.example.org"
-ifconfig_fxp0="inet 10.1.1.1/8"</programlisting></listitem>
+ </listitem>
</itemizedlist>
<para>The <filename>rc.conf</filename> file can then be
distributed to every system using <command>rsync</command> or a
- similar program, while the <filename>rc.conf.local</filename> file
- remains unique.</para>
+ similar program, while the <filename>rc.conf.local</filename>
+ file remains unique.</para>
- <para>Upgrading the system using &man.sysinstall.8;
- or <command>make world</command> will not overwrite the
- <filename>rc.conf</filename>
- file, so system configuration information will not be lost.</para>
+ <para>Upgrading the system using &man.sysinstall.8; or
+ <command>make world</command> will not overwrite the
+ <filename>rc.conf</filename> file, so system configuration
+ information will not be lost.</para>
<tip>
<para>The <filename>/etc/rc.conf</filename> configuration file
@@ -301,21 +322,22 @@
<indexterm><primary>/usr/local/etc</primary></indexterm>
<para>Typically, these files are installed in
- <filename class="directory">/usr/local/etc</filename>. In the case where an
- application has a large number of configuration files, a
- subdirectory will be created to hold them.</para>
+ <filename class="directory">/usr/local/etc</filename>. In the
+ case where an application has a large number of configuration
+ files, a subdirectory will be created to hold them.</para>
<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
- are no existing
- configuration files for the application, they will be created by
- copying the <filename>.default</filename> files.</para>
+ 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
- <filename class="directory">/usr/local/etc/apache</filename>:</para>
+ <filename
+ class="directory">/usr/local/etc/apache</filename>:</para>
-<literallayout class="monospaced">-rw-r--r-- 1 root wheel 2184 May 20 1998 access.conf
+ <literallayout class="monospaced">-rw-r--r-- 1 root wheel 2184 May 20 1998 access.conf
-rw-r--r-- 1 root wheel 2184 May 20 1998 access.conf.default
-rw-r--r-- 1 root wheel 9555 May 20 1998 httpd.conf
-rw-r--r-- 1 root wheel 9555 May 20 1998 httpd.conf.default
@@ -326,19 +348,19 @@
-rw-r--r-- 1 root wheel 7980 May 20 1998 srm.conf
-rw-r--r-- 1 root wheel 7933 May 20 1998 srm.conf.default</literallayout>
- <para>The file sizes show that only the <filename>srm.conf</filename>
- file has been changed. A later update of the <application>Apache</application> port would not
+ <para>The file sizes show that only the
+ <filename>srm.conf</filename> file has been changed. A later
+ update of the <application>Apache</application> port would not
overwrite this changed file.</para>
-
</sect1>
<sect1 id="configtuning-starting-services">
<sect1info>
<authorgroup>
- <author>
- <firstname>Tom</firstname>
- <surname>Rhodes</surname>
- <contrib>Contributed by </contrib>
+ <author>
+ <firstname>Tom</firstname>
+ <surname>Rhodes</surname>
+ <contrib>Contributed by </contrib>
</author>
</authorgroup>
</sect1info>
@@ -348,27 +370,28 @@
<indexterm><primary>services</primary></indexterm>
<para>Many users choose to install third party software on &os;
- from the Ports Collection. In many of these situations it
- may be necessary to configure the software in a manner which
- will allow it to be started upon system initialization. Services,
+ from the Ports Collection. In many of these situations it may
+ be necessary to configure the software in a manner which will
+ allow it to be started upon system initialization. Services,
such as <filename role="package">mail/postfix</filename> or
- <filename role="package">www/apache22</filename> are just two
- of the many software packages which may be started during system
+ <filename role="package">www/apache22</filename> are just two of
+ the many software packages which may be started during system
initialization. This section explains the procedures available
for starting third party software.</para>
<para>In &os;, most included services, such as &man.cron.8;, are
started through the system start up scripts. These scripts may
differ depending on &os; or vendor version; however, the most
- important aspect to consider is that their start up configuration
- can be handled through simple startup scripts.</para>
+ important aspect to consider is that their start up
+ configuration can be handled through simple startup
+ scripts.</para>
<sect2>
<title>Extended Application Configuration</title>
- <para>Now that &os; includes <filename>rc.d</filename>, configuration
- of application startup has become easier, and more
- featureful. Using the key words discussed in the
+ <para>Now that &os; includes <filename>rc.d</filename>,
+ configuration of application startup has become easier, and
+ more featureful. Using the key words discussed in the
<link linkend="configtuning-rcd">rc.d</link> section,
applications may now be set to start after certain other
services for example <acronym>DNS</acronym>; may permit extra
@@ -402,9 +425,9 @@
<para>This script will ensure that the provided
<application>utility</application> will be started after the
- <literal>DAEMON</literal> pseudo-service. It also provides a method
- for setting and tracking the <acronym>PID</acronym>, or process
- <acronym>ID</acronym> file.</para>
+ <literal>DAEMON</literal> pseudo-service. It also provides a
+ method for setting and tracking the <acronym>PID</acronym>, or
+ process <acronym>ID</acronym> file.</para>
<para>This application could then have the following line placed
in <filename>/etc/rc.conf</filename>:</para>
@@ -415,7 +438,8 @@
command line arguments, inclusion of the default functions
provided in <filename>/etc/rc.subr</filename>, compatibility
with the &man.rcorder.8; utility and provides for easier
- configuration via the <filename>rc.conf</filename> file.</para>
+ configuration via the <filename>rc.conf</filename>
+ file.</para>
</sect2>
<sect2>
@@ -423,38 +447,37 @@
<para>Other services, such as <acronym>POP</acronym>3 server
daemons, <acronym>IMAP</acronym>, etc. could be started using
- &man.inetd.8;. This involves installing the service
- utility from the Ports Collection with a configuration line
- added to the <filename>/etc/inetd.conf</filename> file,
- or by uncommenting one of the current configuration lines. Working
+ &man.inetd.8;. This involves installing the service utility
+ from the Ports Collection with a configuration line added to
+ the <filename>/etc/inetd.conf</filename> file, or by
+ uncommenting one of the current configuration lines. Working
with <application>inetd</application> and its configuration is
described in depth in the
<link linkend="network-inetd">inetd</link> section.</para>
<para>In some cases it may make more sense to use the
&man.cron.8; daemon to start system services. This approach
- has a number of advantages because <command>cron</command> runs
- these processes as the <filename>crontab</filename>'s file
- owner. This allows regular users to start and maintain some
- applications.</para>
+ has a number of advantages because <command>cron</command>
+ runs these processes as the <filename>crontab</filename>'s
+ file owner. This allows regular users to start and maintain
+ some applications.</para>
<para>The <command>cron</command> utility provides a unique
- feature, <literal>@reboot</literal>, which may be used in place
- of the time specification. This will cause the job to be run
- when &man.cron.8; is started, normally during system
+ feature, <literal>@reboot</literal>, which may be used in
+ place of the time specification. This will cause the job to
+ be run when &man.cron.8; is started, normally during system
initialization.</para>
-
</sect2>
</sect1>
<sect1 id="configtuning-cron">
<sect1info>
<authorgroup>
- <author>
- <firstname>Tom</firstname>
- <surname>Rhodes</surname>
- <contrib>Contributed by </contrib>
- <!-- 20 May 2003 -->
+ <author>
+ <firstname>Tom</firstname>
+ <surname>Rhodes</surname>
+ <contrib>Contributed by </contrib>
+ <!-- 20 May 2003 -->
</author>
</authorgroup>
</sect1info>
@@ -463,41 +486,42 @@
<indexterm><primary>cron</primary>
<secondary>configuration</secondary></indexterm>
- <para>One of the most useful utilities in &os; is &man.cron.8;. The
- <command>cron</command> utility runs in the background and constantly
- checks the <filename>/etc/crontab</filename> file. The <command>cron</command>
- utility also checks the <filename class="directory">/var/cron/tabs</filename> directory, in
- search of new <filename>crontab</filename> files. These
- <filename>crontab</filename> files store information about specific
- functions which <command>cron</command> is supposed to perform at
- certain times.</para>
+ <para>One of the most useful utilities in &os; is &man.cron.8;.
+ The <command>cron</command> utility runs in the background and
+ constantly checks the <filename>/etc/crontab</filename> file.
+ The <command>cron</command> utility also checks the
+ <filename class="directory">/var/cron/tabs</filename> directory,
+ in search of new <filename>crontab</filename> files. These
+ <filename>crontab</filename> files store information about
+ specific functions which <command>cron</command> is supposed to
+ perform at certain times.</para>
- <para>The <command>cron</command> utility uses two different
- types of configuration files, the system crontab and user
- crontabs. These formats only differ in the sixth field and
- later. In the system crontab, <command>cron</command> will run
- the command as the user specified in the sixth field. In a user
- crontab, all commands run as the user who created the crontab,
- so the sixth field is the last field; this is an important
- security feature. The final field is always the command
- to run.</para>
+ <para>The <command>cron</command> utility uses two different types
+ of configuration files, the system crontab and user crontabs.
+ These formats only differ in the sixth field and later. In the
+ system crontab, <command>cron</command> will run the command as
+ the user specified in the sixth field. In a user crontab, all
+ commands run as the user who created the crontab, so the sixth
+ field is the last field; this is an important security feature.
+ The final field is always the command to run.</para>
<note>
- <para>User crontabs allow individual users to schedule tasks without the
- need for <username>root</username> privileges. Commands in a user's crontab run with the
- permissions of the user who owns the crontab.</para>
+ <para>User crontabs allow individual users to schedule tasks
+ without the need for <username>root</username> privileges.
+ Commands in a user's crontab run with the permissions of the
+ user who owns the crontab.</para>
- <para>The <username>root</username> user can have a user crontab just like
- any other user. The <username>root</username> user crontab is
- separate from <filename>/etc/crontab</filename> (the system
- crontab). Because the system crontab effectively
- invokes the specified commands as root there is usually no need to
- create a user crontab for <username>root</username>.</para>
+ <para>The <username>root</username> user can have a user crontab
+ just like any other user. The <username>root</username> user
+ crontab is separate from <filename>/etc/crontab</filename>
+ (the system crontab). Because the system crontab effectively
+ invokes the specified commands as root there is usually no
+ need to create a user crontab for
+ <username>root</username>.</para>
</note>
- <para>Let us take a look at the <filename>/etc/crontab</filename> file
- (the system crontab):</para>
-
+ <para>Let us take a look at the <filename>/etc/crontab</filename>
+ file (the system crontab):</para>
<programlisting># /etc/crontab - root's crontab for &os;
#
@@ -512,61 +536,72 @@
#minute hour mday month wday who command <co id="co-field-descr">
#
#
-*/5 * * * * root /usr/libexec/atrun <co id="co-main">
-</programlisting>
+*/5 * * * * root /usr/libexec/atrun <co id="co-main"></programlisting>
>>> TRUNCATED FOR MAIL (1000 lines) <<<
More information about the p4-projects
mailing list