Date: Thu, 20 Mar 2014 15:46:05 +0000 (UTC) From: Dru Lavigne <dru@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44298 - head/en_US.ISO8859-1/books/handbook/config Message-ID: <201403201546.s2KFk5Ks093927@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Thu Mar 20 15:46:04 2014 New Revision: 44298 URL: http://svnweb.freebsd.org/changeset/doc/44298 Log: Incorporate Core Configuration as a sub-section of Using rc Under FreeBSD. Rename that section to Managing Services in FreeBSD and rename sub-section to Managing System-Specific Configuration. This revised section still needs an editorial review. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/config/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:42:22 2014 (r44297) +++ head/en_US.ISO8859-1/books/handbook/config/chapter.xml Thu Mar 20 15:46:04 2014 (r44298) @@ -105,70 +105,6 @@ </itemizedlist> </sect1> - <sect1 xml:id="configtuning-core-configuration"> - <title>Core Configuration</title> - - <indexterm> - <primary>rc files</primary> - <secondary><filename>rc.conf</filename></secondary> - </indexterm> - - <para>The principal location for system configuration information - is <filename>/etc/rc.conf</filename>. This file contains a - wide range of configuration information and it is read at - system startup to configure the system. It provides the - configuration information for the <filename>rc*</filename> - files.</para> - - <para>The entries in <filename>/etc/rc.conf</filename> override - the default settings in - <filename>/etc/defaults/rc.conf</filename>. The file containing - the default settings should not be edited. Instead, all - system-specific changes should be made to - <filename>/etc/rc.conf</filename>.</para> - - <para>A number of strategies may be applied in clustered - applications to separate site-wide configuration from - system-specific configuration in order to keep administration - overhead down. The recommended approach is to place - system-specific configuration into - <filename>/etc/rc.conf.local</filename>. For example:</para> - - <itemizedlist> - <listitem> - <para><filename>/etc/rc.conf</filename>:</para> - - <programlisting>sshd_enable="YES" -keyrate="fast" -defaultrouter="10.1.1.254"</programlisting> - </listitem> - - <listitem> - <para><filename>/etc/rc.conf.local</filename>:</para> - - <programlisting>hostname="node1.example.org" -ifconfig_fxp0="inet 10.1.1.1/8"</programlisting> - </listitem> - </itemizedlist> - - <para>Distribute <filename>/etc/rc.conf</filename> to every - system using <command>rsync</command> or a similar program, - while <filename>/etc/rc.conf.local</filename> remains - unique.</para> - - <para>Upgrading the system using &man.sysinstall.8; or - <command>make world</command> will not overwrite - <filename>/etc/rc.conf</filename>, so system configuration - information will not be lost.</para> - - <tip> - <para>The configuration in <filename>/etc/rc.conf</filename> - is parsed by &man.sh.1;. This allows system operators to - create complex configuration scenarios. Refer to - &man.rc.conf.5; for further information on this topic.</para> - </tip> - </sect1> - <sect1 xml:id="configtuning-appconfig"> <title>Application Configuration</title> @@ -499,7 +435,7 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin <sect1 xml:id="configtuning-rcd"> <info> - <title>Using &man.rc.8; Under &os;</title> + <title>Managing Services in &os;</title> <authorgroup> <author> @@ -512,8 +448,8 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin </authorgroup> </info> - <para>In 2002, &os; integrated the NetBSD &man.rc.8; system for - system initialization. The files listed in + <para>&os; uses the &man.rc.8; system of startup scripts during + system initialization and for managing services. The scripts listed in <filename>/etc/rc.d</filename> provide basic services which can be controlled with the <option>start</option>, <option>stop</option>, and @@ -651,6 +587,64 @@ sshd is running as pid 433.</screen> xlink:href="&url.articles.rc-scripting;">this article</link> for instructions on how to create custom &man.rc.8; scripts.</para> + + <sect2 xml:id="configtuning-core-configuration"> + <title>Managing System-Specific Configuration</title> + + <indexterm> + <primary>rc files</primary> + <secondary><filename>rc.conf</filename></secondary> + </indexterm> + + <para>The principal location for system configuration information + is <filename>/etc/rc.conf</filename>. This file contains a + wide range of configuration information and it is read at + system startup to configure the system. It provides the + configuration information for the <filename>rc*</filename> + files.</para> + + <para>The entries in <filename>/etc/rc.conf</filename> override + the default settings in + <filename>/etc/defaults/rc.conf</filename>. The file containing + the default settings should not be edited. Instead, all + system-specific changes should be made to + <filename>/etc/rc.conf</filename>.</para> + + <para>A number of strategies may be applied in clustered + applications to separate site-wide configuration from + system-specific configuration in order to keep administration + overhead down. The recommended approach is to place + system-specific configuration into + <filename>/etc/rc.conf.local</filename>. For example, these + entries in <filename>/etc/rc.conf</filename> apply to all systems:</para> + + <programlisting>sshd_enable="YES" +keyrate="fast" +defaultrouter="10.1.1.254"</programlisting> + + <para>Whereas these systems in + <filename>/etc/rc.conf.local</filename> apply to this system + only:</para> + + <programlisting>hostname="node1.example.org" +ifconfig_fxp0="inet 10.1.1.1/8"</programlisting> + + <para>Distribute <filename>/etc/rc.conf</filename> to every + system using <command>rsync</command> or a similar program, + while <filename>/etc/rc.conf.local</filename> remains + unique.</para> + + <para>Upgrading the system will not overwrite + <filename>/etc/rc.conf</filename>, so system configuration + information will not be lost.</para> + + <tip> + <para>The configuration in <filename>/etc/rc.conf</filename> + is parsed by &man.sh.1;. This allows system operators to + create complex configuration scenarios. Refer to + &man.rc.conf.5; for further information on this topic.</para> + </tip> + </sect2> </sect1> <sect1 xml:id="config-network-setup">
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201403201546.s2KFk5Ks093927>