Rewrite a few sentences for clarity.
Use the &unix entity (which renders a (r)) Add more technical information about rcorder(8).
This commit is contained in:
parent
488bb1762e
commit
2f4175262a
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=17020
1 changed files with 28 additions and 10 deletions
|
@ -537,21 +537,30 @@ HOME=/var/log
|
|||
<indexterm><primary>rc under FreeBSD 5.X</primary></indexterm>
|
||||
|
||||
<para>FreeBSD has recently integrated the NetBSD
|
||||
<filename>rc.d</filename> system, deprecating the old method.
|
||||
<filename>rc.d</filename> system for system initialization.
|
||||
Users will notice the files listed in the
|
||||
<filename>/etc/rc.d</filename> directory. Many of these files
|
||||
are for basic services which can be started with the
|
||||
<option>start</option>, <option>stop</option>,
|
||||
<option>kill</option>, and <option>restart</option> options.
|
||||
For instance, to restart &man.sshd.8;, the command:</para>
|
||||
For instance, &man.sshd.8; can be restarted with the following
|
||||
command :</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>/etc/rc.d/sshd restart</userinput></screen>
|
||||
|
||||
<para>would be issued. This is the basic layout for every
|
||||
service. Services are not required to be started manually, as
|
||||
they are still called from the <filename>/etc/rc.conf</filename>
|
||||
file with the basic <option>YES</option> and <option>NO</option>
|
||||
choices.<para>
|
||||
<para>The procedure is similar for other services. Of course,
|
||||
services are usually started automatically as specified in
|
||||
&man.rc.conf.5;. For example, enabling the Network Address
|
||||
Translation daemon at startup is as simple as adding the
|
||||
following line to <filename>/etc/rc.conf</filename>:</para>
|
||||
|
||||
<programlisting>natd_enable="YES"</programlisting>
|
||||
|
||||
<para>If a <option>natd_enable="NO"</option> line is already
|
||||
present, then simply change the <option>NO</option> to
|
||||
<option>YES</option>. The rc scripts will automatically load
|
||||
any other dependent services during the next reboot, as
|
||||
described below.</para>
|
||||
|
||||
<para>As of this writing, the files located in
|
||||
<filename>rc.d</filename> are:</para>
|
||||
|
@ -591,8 +600,17 @@ devd kadmind network_ipv6 rtadvd ypxfrd</programl
|
|||
<para>Therefore this file is used for background file system
|
||||
checks, which are done only during system initialization.</para>
|
||||
|
||||
<para>Order of execution is based on a series of words located at
|
||||
the script beginning, these words are:</para>
|
||||
<para>Many system services depend on other services to function
|
||||
properly. For example, NIS and other RPC-based services may
|
||||
fail to start until after the <command>rpcbind</command>
|
||||
(portmapper) service has started. To resolve this issue,
|
||||
information about dependencies and other meta-data is included
|
||||
in the comments at the top of each startup script. The
|
||||
&man.rcorder.8; script is then used to parse these comments
|
||||
during system initialization to determine the order in which
|
||||
system services should be invoked to satisfy the dependencies.
|
||||
The following words may be included at the top of each startup
|
||||
file :</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
@ -614,7 +632,7 @@ devd kadmind network_ipv6 rtadvd ypxfrd</programl
|
|||
|
||||
<para>Using this method an administrator can easily control system
|
||||
services without the hassle of <quote>runlevels</quote> like
|
||||
some other UNIX operating systems.</para>
|
||||
some other &unix; operating systems.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="config-network-setup">
|
||||
|
|
Loading…
Reference in a new issue