From 35541ca643547bf5aad140028ca6f45db96a2557 Mon Sep 17 00:00:00 2001 From: Davin McCall Date: Sun, 4 Mar 2018 02:28:54 +0000 Subject: [PATCH] Minor fixes to README. --- README | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README b/README index e129fba..6b084e8 100644 --- a/README +++ b/README @@ -68,7 +68,7 @@ solutions, like D-Bus, do exist). A _scripted_ service has separate commands for startup and (optional) shutdown. Scripted services can be used for tasks such as mounting file -systems that don't need a persisten process, and in some cases can be used +systems that don't need a persistent process, and in some cases can be used for daemon processes (although Dinit will not be able to supervise a process that is registered as a scripted service). @@ -76,8 +76,9 @@ A _bgprocess_ service is a mix between a process service and a scripted service. A command is used to start the service, and once started, the process ID is expected to be available in a file which Dinit can then read. Many existing daemons can operate in this way. The process can only be -supervised if Dinit runs as the system "init" (PID 1) - otherwise Dinit can -not reliably know when the process has terminated. +supervised if Dinit runs as the system "init" (PID 1), or can otherwise mark +itself as a subreaper (which is possible on Linux, FreeBSD and DragonFlyBSD) - +otherwise Dinit can not reliably know when the process has terminated. (Note, use of bgprocess services type requires care. The file from which the PID is read is trusted; Dinit may send signals to the specified PID. It -- 2.25.1