diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2020-10-09 17:09:42 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska-skaware@skarnet.org> | 2020-10-09 17:09:42 +0000 |
| commit | 163b9d565057c7e55912b40f98fc190da85f142f (patch) | |
| tree | 086b8dbb4d48c4ba551f73a71673c28ce37631d4 | |
| parent | b8c19a579f778a4b607528877e62a07ecc6c33b4 (diff) | |
| download | s6-163b9d565057c7e55912b40f98fc190da85f142f.tar.xz | |
Add keywords to new sections
| -rw-r--r-- | doc/notifywhenup.html | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/notifywhenup.html b/doc/notifywhenup.html index f7d4ce8..a979f94 100644 --- a/doc/notifywhenup.html +++ b/doc/notifywhenup.html @@ -91,7 +91,7 @@ for readiness, and route its result into the s6 notification system: <a href="s6-notifyoncheck.html">s6-notifyoncheck</a>. </p> -<h2> How to use a check program with s6 </h2> +<h2> How to use a check program with s6 (i.e. readiness checking via polling) </h2> <ul> <li> Let's say you have a daemon <em>foo</em>, started under s6 via a @@ -121,8 +121,7 @@ mark <em>foo</em> as ready. </li> </ul> </li> </ul> -<h2> How to design a daemon so it uses the s6 notification mechanism -<em>without</em> resorting to polling </h2> +<h2> How to design a daemon so it uses the s6 mechanism <em>without</em> resorting to polling (i.e. readiness notification) </h2> <p> The <a href="s6-notifyoncheck.html">s6-notifyoncheck</a> mechanism was |