diff options
| -rw-r--r-- | doc/notifywhenup.html | 2 | ||||
| -rw-r--r-- | doc/s6-notifyoncheck.html | 2 |
2 files changed, 2 insertions, 2 deletions
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 <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> +<a href="//skarnet.org/lists/supervision/1606.html">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: 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. </p> <p> -<a href="//skarnet.org/cgi-bin/archive.cgi?2:mss:1607:dfblejammjllfkggpcph">Polling</a> +<a href="//skarnet.org/lists/supervision/1606.html">Polling</a> is evil. Please make sure you really have no other choice before writing a <tt>./data/check</tt> 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 |