svn commit: r44299 - in head/en_US.ISO8859-1/books/handbook: config ports
Dru Lavigne
dru at FreeBSD.org
Thu Mar 20 15:55:59 UTC 2014
Author: dru
Date: Thu Mar 20 15:55:58 2014
New Revision: 44299
URL: http://svnweb.freebsd.org/changeset/doc/44299
Log:
Incorporate Application Configuration into 5.7 Post-Installation
Considerations.
Sponsored by: iXsystems
Modified:
head/en_US.ISO8859-1/books/handbook/config/chapter.xml
head/en_US.ISO8859-1/books/handbook/ports/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/config/chapter.xml Thu Mar 20 15:46:04 2014 (r44298)
+++ head/en_US.ISO8859-1/books/handbook/config/chapter.xml Thu Mar 20 15:55:58 2014 (r44299)
@@ -105,49 +105,6 @@
</itemizedlist>
</sect1>
- <sect1 xml:id="configtuning-appconfig">
- <title>Application Configuration</title>
-
- <para>Typically, installed applications have their own
- configuration files and syntax. It is important that these
- files be kept separate from the base system, so that they may be
- easily located and managed by the package management
- tools.</para>
-
- <indexterm><primary>/usr/local/etc</primary></indexterm>
-
- <para>Typically, these files are installed in
- <filename>/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 suffix such as <filename>.sample</filename>.
- If there are no existing configuration files for the
- application, they can be created by copying the sample
- files.</para>
-
- <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
--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
--rw-r--r-- 1 root wheel 12205 May 20 1998 magic
--rw-r--r-- 1 root wheel 12205 May 20 1998 magic.default
--rw-r--r-- 1 root wheel 2700 May 20 1998 mime.types
--rw-r--r-- 1 root wheel 2700 May 20 1998 mime.types.default
--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 <filename>srm.conf</filename>
- has been changed. A later update of the
- <application>Apache</application> port would not overwrite
- this changed file.</para>
- </sect1>
-
<sect1 xml:id="configtuning-starting-services">
<info>
<title>Starting Services</title>
Modified: head/en_US.ISO8859-1/books/handbook/ports/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Thu Mar 20 15:46:04 2014 (r44298)
+++ head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Thu Mar 20 15:55:58 2014 (r44299)
@@ -1711,8 +1711,14 @@ ports-mgmt/pkg
<listitem>
<para>Most applications install at least one default
configuration file in <filename>/usr/local/etc</filename>.
- The configuration files should be reviewed and possibly
- edited to meet the system's needs.</para>
+ In the case where an application has a large number of
+ configuration files, a subdirectory will be created to hold
+ them. Often, sample configuration files are installed which
+ end with a suffix such as <filename>.sample</filename>. The
+ configuration files should be reviewed and possibly
+ edited to meet the system's needs. To edit a sample file,
+ first copy it without the <filename>.sample</filename>
+ extension.</para>
</listitem>
<listitem>
More information about the svn-doc-head
mailing list