aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChloe Kudryavtsev <toast@toast.cafe>2019-06-09 23:51:06 -0400
committerWilliam Hubbs <william.hubbs@sony.com>2019-07-26 12:52:52 -0500
commit70b8df3e9c7fed156e1a81ee7efe8a51c1010cb6 (patch)
treefe82d19037f77d2794b635bc2dd025357c2b4174
parentcac41092e4180a8d16edacab0c8552585d94328b (diff)
clarify supervise-daemon-guide
1. The given default for respawn_max is wrong. 2. The example for respawn_period is nonsensical. This fixes #311.
-rw-r--r--supervise-daemon-guide.md13
1 files changed, 9 insertions, 4 deletions
diff --git a/supervise-daemon-guide.md b/supervise-daemon-guide.md
index 8fb02f6a..e4a7c947 100644
--- a/supervise-daemon-guide.md
+++ b/supervise-daemon-guide.md
@@ -92,7 +92,8 @@ respawn_max=x
```
This is the maximum number of times to respawn a supervised process
-during the given respawn period. The default is unlimited.
+during the given respawn period.
+The default is 10. 0 means unlimited.
``` sh
respawn_period=seconds
@@ -101,6 +102,10 @@ respawn_period=seconds
This works in conjunction with respawn_max and respawn_delay above to
decide if a process should not be respawned for some reason.
-For example, if respawn_period is 60, respawn_max is 2 and respawn_delay
-is 3 and a process dies more than 4 times, the process will not be
-respawned and the supervisor will terminate.
+For example, if respawn period is 10 and respawn_max is 2, the process
+would need to die 3 times within 10 seconds to no longer be respawned.
+Note that respawn_delay will delay all of this, so in the above scenario
+a respawn_delay of greater than 5 will cause infinite respawns.
+
+By default, this is unset and respawn_max applies to the entire lifetime
+of the service.