From d335c9833c5a0995a7a4d87350dcd8df27a20af5 Mon Sep 17 00:00:00 2001 From: Joachim Nilsson Date: Wed, 8 Mar 2017 16:25:14 +0100 Subject: [PATCH] It is difficult to write readable technical text. Signed-off-by: Joachim Nilsson --- README.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index a32cc4f1..519e90a5 100644 --- a/README.md +++ b/README.md @@ -91,8 +91,10 @@ the familiar [/etc/rc.local](#runparts--etcrclocal) are started. tty [12345] /dev/ttyAMA0 115200 vt100 ``` -The `service` stanza, described in full in [doc/config.md](doc/config.md), -has the following components: +The `service` stanza, as well as `task`, `run`, `inetd` and others are +described in full in [doc/config.md](doc/config.md). Here's a quick +overview of some of the most common components needed to start a UNIX +daemon: ``` service [LVLS] /path/to/daemon ARGS -- Some text @@ -105,9 +107,11 @@ has the following components: `------------------------------------------------ Monitored application ``` -Many of the components are optional. What is required, however, is for the -daemon *not to fork* to and detach itself. This is usually an `-n` or `-f` -argument to the application. +Some components are optional. It is important to note, however, is for +the daemon *not to fork* and detach itself from the controlling TTY. +This is usually an `-n` or `-f` argument to the application. If the +daemon detaches itself, Finit cannot monitor it and will instead try to +restart it. For an example of a full blown embedded Linux, see [TroglOS][9], or take a look at the `contrib/` section with [Alpine Linux](contrib/alpine/),