Shorten some sentences and keep the focus on
rc.d style scripts rather than rcNG scripts. Discussed with: trhodes
This commit is contained in:
parent
4861882e8d
commit
fd66232eb9
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=22624
1 changed files with 8 additions and 12 deletions
|
@ -341,10 +341,8 @@
|
||||||
such as <filename role="package">mail/postfix</filename> or
|
such as <filename role="package">mail/postfix</filename> or
|
||||||
<filename role="package">www/apache13</filename> are just two
|
<filename role="package">www/apache13</filename> are just two
|
||||||
of the many software packages which may be started during system
|
of the many software packages which may be started during system
|
||||||
initialization. Thus it is only fair that an explanation be
|
initialization. This section explains the procedures available
|
||||||
provided on the procedures available for working with third
|
for starting third party software.</para>
|
||||||
party software, in the rare cases something goes wrong and the
|
|
||||||
application does not start up properly.</para>
|
|
||||||
|
|
||||||
<para>In &os;, most included services, such as &man.cron.8;, are
|
<para>In &os;, most included services, such as &man.cron.8;, are
|
||||||
started through the system start up scripts. These scripts may
|
started through the system start up scripts. These scripts may
|
||||||
|
@ -352,10 +350,9 @@
|
||||||
important aspect to consider is that their start up configuration
|
important aspect to consider is that their start up configuration
|
||||||
can be handled through simple startup scripts.</para>
|
can be handled through simple startup scripts.</para>
|
||||||
|
|
||||||
<para>Since the advent of rcNG, it became clear that system
|
<para>Before the advent of rcNG, applications would drop a
|
||||||
initialization for third party utilities could be simplified.
|
simple start up script into the
|
||||||
For years applications would drop a simple start up script into
|
<filename role="directory">/usr/local/etc/rc.d</filename>
|
||||||
the <filename role="directory">/usr/local/etc/rc.d</filename>
|
|
||||||
directory which would be read by the system initialization
|
directory which would be read by the system initialization
|
||||||
scripts. These scripts would then be executed during the latter
|
scripts. These scripts would then be executed during the latter
|
||||||
stages of system start up.</para>
|
stages of system start up.</para>
|
||||||
|
@ -364,10 +361,9 @@
|
||||||
old configuration style into the new system, the fact remains
|
old configuration style into the new system, the fact remains
|
||||||
that some third party utilities still require a script simply
|
that some third party utilities still require a script simply
|
||||||
dropped into the aforementioned directory. The subtle differences
|
dropped into the aforementioned directory. The subtle differences
|
||||||
in the scripts depend whether or not rcNG is being used. Any
|
in the scripts depend whether or not rcNG is being used. Prior
|
||||||
version of &os; prior to 5.1 will not require the extra bit of
|
to &os; 5.1 the old configuration style is used and in
|
||||||
configuration; indeed, in almost all cases the soon to be
|
almost all cases a new style script would do just fine.</para>
|
||||||
recognized script would do just fine.</para>
|
|
||||||
|
|
||||||
<para>While every script must meet some minimal requirements, most
|
<para>While every script must meet some minimal requirements, most
|
||||||
of the time these requirements are &os; version
|
of the time these requirements are &os; version
|
||||||
|
|
Loading…
Reference in a new issue