diff options
author | Laurent Bercot <ska-skaware@skarnet.org> | 2017-08-20 10:10:19 +0000 |
---|---|---|
committer | Laurent Bercot <ska-skaware@skarnet.org> | 2017-08-20 10:10:19 +0000 |
commit | 3d42e4b42964f4cec4e8d9f06ddf80c956dbfbb2 (patch) | |
tree | a34e86ed03c9ece253fbcae0b080f24e05ef65ad /doc/notifywhenup.html | |
parent | 0375b2b32e4683c8f7bdf104038bedde77d9827b (diff) | |
download | s6-3d42e4b42964f4cec4e8d9f06ddf80c956dbfbb2.tar.xz |
Doc updates
Diffstat (limited to 'doc/notifywhenup.html')
-rw-r--r-- | doc/notifywhenup.html | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/notifywhenup.html b/doc/notifywhenup.html index 363438b..d788938 100644 --- a/doc/notifywhenup.html +++ b/doc/notifywhenup.html @@ -79,5 +79,17 @@ to provide reliable startup notifications, and subscribers should then be content with the unreliable <tt>'u'</tt> events provided by s6-supervise. </p> +<p> +Unfortunately, a lot of long-running programs do not offer that +functionality; instead, they provide a way to poll them, an external +program that runs and checks whether the service is ready. This is a +<a href="//skarnet.org/software/s6/ftrig.html">bad</a> mechanism, for +<a href="//skarnet.org/cgi-bin/archive.cgi?2:mss:1607:dfblejammjllfkggpcph">several</a> +reasons. Nevertheless, until all daemons are patched to notify their +own readiness, s6 provides a way to run such a check program to poll +for readiness, and route its result into the s6 notification system: +<a href="s6-notifyoncheck.html">s6-notifyoncheck</a>. +</p> + </body> </html> |