From owner-svn-doc-all@FreeBSD.ORG Thu Mar 20 15:46:05 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 58916D99; Thu, 20 Mar 2014 15:46:05 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 44BAD75A; Thu, 20 Mar 2014 15:46:05 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s2KFk5bL093928; Thu, 20 Mar 2014 15:46:05 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s2KFk5Ks093927; Thu, 20 Mar 2014 15:46:05 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201403201546.s2KFk5Ks093927@svn.freebsd.org> From: Dru Lavigne Date: Thu, 20 Mar 2014 15:46:05 +0000 (UTC) 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 X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Mar 2014 15:46:05 -0000 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 @@ - - Core Configuration - - - rc files - rc.conf - - - The principal location for system configuration information - is /etc/rc.conf. 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 rc* - files. - - The entries in /etc/rc.conf override - the default settings in - /etc/defaults/rc.conf. The file containing - the default settings should not be edited. Instead, all - system-specific changes should be made to - /etc/rc.conf. - - 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 - /etc/rc.conf.local. For example: - - - - /etc/rc.conf: - - sshd_enable="YES" -keyrate="fast" -defaultrouter="10.1.1.254" - - - - /etc/rc.conf.local: - - hostname="node1.example.org" -ifconfig_fxp0="inet 10.1.1.1/8" - - - - Distribute /etc/rc.conf to every - system using rsync or a similar program, - while /etc/rc.conf.local remains - unique. - - Upgrading the system using &man.sysinstall.8; or - make world will not overwrite - /etc/rc.conf, so system configuration - information will not be lost. - - - The configuration in /etc/rc.conf - 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. - - - Application Configuration @@ -499,7 +435,7 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin - Using &man.rc.8; Under &os; + Managing Services in &os; @@ -512,8 +448,8 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin - In 2002, &os; integrated the NetBSD &man.rc.8; system for - system initialization. The files listed in + &os; uses the &man.rc.8; system of startup scripts during + system initialization and for managing services. The scripts listed in /etc/rc.d provide basic services which can be controlled with the , , and @@ -651,6 +587,64 @@ sshd is running as pid 433. xlink:href="&url.articles.rc-scripting;">this article for instructions on how to create custom &man.rc.8; scripts. + + + Managing System-Specific Configuration + + + rc files + rc.conf + + + The principal location for system configuration information + is /etc/rc.conf. 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 rc* + files. + + The entries in /etc/rc.conf override + the default settings in + /etc/defaults/rc.conf. The file containing + the default settings should not be edited. Instead, all + system-specific changes should be made to + /etc/rc.conf. + + 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 + /etc/rc.conf.local. For example, these + entries in /etc/rc.conf apply to all systems: + + sshd_enable="YES" +keyrate="fast" +defaultrouter="10.1.1.254" + + Whereas these systems in + /etc/rc.conf.local apply to this system + only: + + hostname="node1.example.org" +ifconfig_fxp0="inet 10.1.1.1/8" + + Distribute /etc/rc.conf to every + system using rsync or a similar program, + while /etc/rc.conf.local remains + unique. + + Upgrading the system will not overwrite + /etc/rc.conf, so system configuration + information will not be lost. + + + The configuration in /etc/rc.conf + 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. + +