Incorporate Application Configuration into 5.7 Post-Installation
Considerations. Sponsored by: iXsystems
This commit is contained in:
parent
a76bcc2552
commit
9db6e7e54c
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=44299
2 changed files with 8 additions and 45 deletions
|
@ -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>
|
||||
|
|
|
@ -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>
|
||||
|
|
Loading…
Reference in a new issue