From 600bddc1ee2fb3374bc888118e2e88cf80017901 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 15 Apr 2024 10:55:13 +0000 Subject: version: 2.12.0.4 Signed-off-by: Laurent Bercot --- doc/notifywhenup.html | 2 +- doc/s6-notifyoncheck.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/notifywhenup.html b/doc/notifywhenup.html index c7a0478..762a62b 100644 --- a/doc/notifywhenup.html +++ b/doc/notifywhenup.html @@ -84,7 +84,7 @@ 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 bad mechanism, for -several +several 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: diff --git a/doc/s6-notifyoncheck.html b/doc/s6-notifyoncheck.html index a4613e9..a2c534e 100644 --- a/doc/s6-notifyoncheck.html +++ b/doc/s6-notifyoncheck.html @@ -130,7 +130,7 @@ descriptor of their choice when they're ready.

-Polling +Polling is evil. Please make sure you really have no other choice before writing a ./data/check program and using s6-notifyoncheck in your run script. If you have access to the source code of the daemon you want to check for -- cgit v1.3.1