From 36de18ec553908b5ca54b5a53f3fe21fdb1edf47 Mon Sep 17 00:00:00 2001 From: Joachim Wiberg Date: Tue, 9 Feb 2021 20:48:18 +0100 Subject: [PATCH] Clarify PID conditions and non-standard PID file locations a bit Signed-off-by: Joachim Wiberg --- doc/config.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/doc/config.md b/doc/config.md index 4e4ff69f..cf721428 100644 --- a/doc/config.md +++ b/doc/config.md @@ -192,7 +192,14 @@ Syntax The `<...>` is the condition for starting `ospfd`. In this example Finit waits for another service, `/sbin/zebra`, to have created its - PID file in `/var/run/zebra.pid` before starting `ospfd`. + PID file in `/var/run/zebra.pid` before starting `ospfd`. Modern + setups omit the absolute path and Quagga places its PID files in a + subdirectory, `/run/quagga/zebra.pid`. In which case the example is + slightly different: + +```shell + service [2345] ospfd -- OSPF daemon +``` Some services do not maintain a PID file and rather than patching each application Finit provides a workaround. A `pid` keyword can be set