White space fix only. Translators can ignore.
Sponsored by: iXsystems
This commit is contained in:
parent
c82f32dbfa
commit
550aaef939
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=44301
1 changed files with 53 additions and 52 deletions
|
@ -406,13 +406,12 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin <co xml:id="co-env"/>
|
|||
</info>
|
||||
|
||||
<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
|
||||
<option>restart</option> options to &man.service.8;. For
|
||||
instance, &man.sshd.8; can be restarted with the following
|
||||
command:</para>
|
||||
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 <option>restart</option> options to
|
||||
&man.service.8;. For instance, &man.sshd.8; can be restarted
|
||||
with the following command:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>service sshd restart</userinput></screen>
|
||||
|
||||
|
@ -544,64 +543,66 @@ 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>
|
||||
<sect2 xml:id="configtuning-core-configuration">
|
||||
<title>Managing System-Specific Configuration</title>
|
||||
|
||||
<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>
|
||||
<indexterm>
|
||||
<primary>rc files</primary>
|
||||
<secondary><filename>rc.conf</filename></secondary>
|
||||
</indexterm>
|
||||
|
||||
<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>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>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>
|
||||
<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>
|
||||
|
||||
<programlisting>sshd_enable="YES"
|
||||
<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>
|
||||
<para>Whereas these systems in
|
||||
<filename>/etc/rc.conf.local</filename> apply to this system
|
||||
only:</para>
|
||||
|
||||
<programlisting>hostname="node1.example.org"
|
||||
<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>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>
|
||||
<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>
|
||||
<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">
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue