From owner-freebsd-doc@FreeBSD.ORG Wed May 28 13:22:31 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9617F37B401 for ; Wed, 28 May 2003 13:22:31 -0700 (PDT) Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id B516A43F85 for ; Wed, 28 May 2003 13:22:30 -0700 (PDT) (envelope-from trhodes@FreeBSD.org) Received: from mobile.pittgoth.com (acs-24-154-229-196.zoominternet.net [24.154.229.196]) by pittgoth.com (8.12.9/8.12.9) with SMTP id h4SKMTHW003816 for ; Wed, 28 May 2003 16:22:29 -0400 (EDT) (envelope-from trhodes@FreeBSD.org) Date: Wed, 28 May 2003 16:09:49 -0400 From: Tom Rhodes To: FreeBSD-doc@FreeBSD.org Message-Id: <20030528160949.79ba5c08.trhodes@FreeBSD.org> X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Another patch :) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2003 20:22:32 -0000 Gang, This patch was submitted to me. I've made a few simple changes and to me it looks good. Some of you, however, may want to read over it before I invoke cvs. Thanks, -- Tom Rhodes NOTE: This is my second patch, I'll assume I can commit them both if I hear nothing in a respectable period of time. Index: config/chapter.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v retrieving revision 1.105 diff -u -d -r1.105 chapter.sgml --- config/chapter.sgml 27 May 2003 20:27:26 -0000 1.105 +++ config/chapter.sgml 27 May 2003 22:08:17 -0000 @@ -593,6 +593,55 @@ any other dependent services during the next reboot, as described below. + Since the rc.d system is primarily + intended to start/stop services at system startup/shutdown time; + the standard , + and options will only + perform their action if the appropriate + /etc/rc.conf variables are set. For + instance the above sshd restart command will + only work if sshd_enable is set to + in /etc/rc.conf. To + , or + a service regardless of the settings in + /etc/rc.conf, the commands should be + prefixed with force. For instance to restart + sshd regardless of the current + /etc/rc.conf setting, execute the following + command: + + &prompt.root; /etc/rc.d/sshd forcerestart + + Its easy to check if a service is enabled in + /etc/rc.conf by running the appropriate + rc.d script with the option + . Thus, an administrator can check that + sshd is in fact enabled in + /etc/rc.conf, by running: + + &prompt.root; /etc/rc.d/sshd rcvar +# sshd +$sshd_enable=YES + + + The second line (# sshd) is the output + from the sshd command; not a root + console. + + + To determine if a service is running, a + option is available. For instance to + verify that sshd is actually started: + + &prompt.root; /etc/rc.d/sshd status +sshd is running as pid 433. + + It is also possible to a service. + This will attempt to send a signal to an individual service, forcing the + service too reload it's configuration files. In most cases this + means sending the service a SIGHUP + signal. + The rcNG structure is not only used for network services, it also contributes to most of the system initialization. For instance, consider the bgfsck file. When @@ -637,6 +686,10 @@ Using this method an administrator can easily control system services without the hassle of runlevels like some other &unix; operating systems. + + Additional information about the &os; 5.X + rc.d system can be found in the &man.rc.8; + and &man.rc.subr.8; manual pages.