Document /etc/rc.local support

- Document /etc/rc.local support
- Update documentation around runparts(8)

Signed-off-by: Joachim Nilsson <troglobit@gmail.com>
This commit is contained in:
Joachim Nilsson committed 2016-07-15 13:53:10 +02:00
1 parent f0cda83d24
commit eb57457522
1 file changed
+25 -11
+25 -11
View File
@@ -14,7 +14,7 @@ Table of Contents
* [Features](#features) * [Features](#features)
* [/etc/finit.conf](#etcfinitconf) * [/etc/finit.conf](#etcfinitconf)
* [/etc/finit.d](#etcfinitd) * [/etc/finit.d](#etcfinitd)
* [Runparts](#runparts) * [Runparts & /etc/rc.local](#runparts---etc-rc-local)
* [Bootstrap](#bootstrap) * [Bootstrap](#bootstrap)
* [Runlevels](#runlevels) * [Runlevels](#runlevels)
* [Inetd](#inetd) * [Inetd](#inetd)
@@ -211,9 +211,17 @@ Syntax:
`initctl` tool. More on inetd below. `initctl` tool. More on inetd below.
* `runparts <DIR>` * `runparts <DIR>`
Call run-parts(8) on a directory to run start scripts. All executable Call [run-parts(8)][] on `DIR` to run start scripts. All executable
files, or scripts, in the directory are called, in alphabetic order. files, or scripts, in the directory are called, in alphabetic order.
It can be beneficial to use `S01name`, `S02othername`, etc. if there
is a dependency order between the scripts. Symlinks to existing
daemons can talso be used, but make sure they daemonize by default.
As the optional `/etc/rc.local` shell script, make sure that all your
services and programs either terminate or start in the background or
you will block Finit.
* `include <CONF>` * `include <CONF>`
Include another configuration file. Absolute path required. Include another configuration file. Absolute path required.
@@ -312,15 +320,21 @@ update your setup, or the finit configuration, accordingly.
in `/etc/finit.conf`! in `/etc/finit.conf`!
Runparts Runparts & /etc/rc.local
-------- ------------------------
At the end of the boot, when networking and all services are up, finit At the end of the boot, when networking and all services are up, finit
calls its built-in [run-parts(8)][] on the `runparts <DIR>` directory, calls its built-in [run-parts(8)][] on the `runparts <DIR>` directory,
if it exists. Similar to how the `/ec/rc.local` file works in most and `/etc/rc.local`, in that order if they exist.
other init daemons, only finit runs a directory of scripts. This
replaces the earlier support for a `/usr/sbin/services.sh` script in the ```shell
original finit. runparts /etc/rc.d/
```
No configuration stanza in `/etc/finit.conf` is required for `rc.local`.
If it exists and is an executable shell script, finit calls it at the
very end of the boot, before calling the `HOOK_SYSTEM_UP`. See more on
hooks and the system bootstrap below.
Bootstrap Bootstrap
@@ -345,9 +359,9 @@ Bootstrap
where the rest of all tasks and inetd services are started. where the rest of all tasks and inetd services are started.
16. Call 4th level hooks, `HOOK_SVC_UP` 16. Call 4th level hooks, `HOOK_SVC_UP`
17. If `runparts <DIR>` is set, [run-parts(8)][] is called on `<DIR>` 17. If `runparts <DIR>` is set, [run-parts(8)][] is called on `<DIR>`
18. Call 5th level (last) hooks, `HOOK_SYSTEM_UP` 18. Call `/etc/rc.local`, if it exists and is an executable shell script
19. Start TTYs defined in `/etc/finit.conf`, or rescue on `/dev/console` 19. Call 5th level (last) hooks, `HOOK_SYSTEM_UP`
20. Enter main monitor loop 20. Start TTYs defined in `/etc/finit.conf`, or rescue on `/dev/console`
In (10) and (15) tasks and services defined in `/etc/finit.conf` are In (10) and (15) tasks and services defined in `/etc/finit.conf` are
started. Remember, all `service` and `task` stanzas are started in started. Remember, all `service` and `task` stanzas are started in