From: Colin Booth <colin@heliocat.net>
To: supervision@list.skarnet.org
Subject: Re: S6 readiness
Date: Fri, 26 Apr 2019 16:39:31 +0000 [thread overview]
Message-ID: <20190426163931.4qkzqvmkbvztbce3@cathexis.xen.prgmr.com> (raw)
In-Reply-To: <20190426172926.0ab61a99@flunder>
On Fri, Apr 26, 2019 at 05:29:26PM +0200, Oliver Schad wrote:
> Hi everybody,
>
> because we have that topic: in the case a service doesn't support
> itself the interaction with readiness, a watching peace of code would
> be nice (checking open port, checking HTTP call, ...).
>
> How to model that with s6?
>
> Best Regards
> Oli
See the s6-notifyoncheck program in the s6 suite. It emulates the check
script mechanics from runit but instead of being attached to the control
program (s6-svc) it emits readiness notifications.
>
> --
> Automatic-Server AG •••••
> Oliver Schad
> Geschäftsführer
> Turnerstrasse 2
> 9000 St. Gallen | Schweiz
>
> www.automatic-server.com | oliver.schad@automatic-server.com
> Tel: +41 71 511 31 11 | Mobile: +41 76 330 03 47
--
Colin Booth
next prev parent reply other threads:[~2019-04-26 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 15:29 Oliver Schad
2019-04-26 16:39 ` Colin Booth [this message]
2019-04-26 19:08 ` Joe M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190426163931.4qkzqvmkbvztbce3@cathexis.xen.prgmr.com \
--to=colin@heliocat.net \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).