From 9887003b25355c94c46e05985b9738297df6f1a8 Mon Sep 17 00:00:00 2001 From: Joachim Wiberg Date: Mon, 2 Jan 2023 00:30:19 +0100 Subject: [PATCH] doc: clarify and fix confusing pid:/run/bar.pid example Signed-off-by: Joachim Wiberg --- doc/config.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/doc/config.md b/doc/config.md index 9610b4f2..bd257154 100644 --- a/doc/config.md +++ b/doc/config.md @@ -529,10 +529,17 @@ modified with an optional `pid:`-argument: pid[:[/path/to/]filename[.pid]] -For example, by adding `pid:/run/foo.pid` to the service `/sbin/bar`, +For example, by adding `pid:/run/bar.pid` to the service `/sbin/bar`, that PID file will, not only be created and removed automatically, but also be used by the Finit condition subsystem. So a service/run/task -can depend on ``. +can depend on ``, like this foo will not be started until bar +has started: + + service pid:/run/bar.pid bar -- Bar Service + service foo -- Foo Service + +Needless to say, it is better if `bar` creates its own PID file when it +has completed starting up and is ready for service. As an alternative "readiness" notification, Finit supports both systemd and s6 style notification. This can be enabled by using the `notify`