From: Petr Malat <oss@malat.biz>
To: supervision@list.skarnet.org
Subject: Re: Service watchdog
Date: Tue, 19 Oct 2021 09:41:19 +0200 [thread overview]
Message-ID: <YW52nxwaMYS76C+2@ntb.petris.klfree.czf> (raw)
In-Reply-To: <3A0AF46B-BB65-4D92-92F5-795FA3A5794D@umbrellix.net>
Yes, in my usecase this would be used at the place where sd_notify()
is used if the service runs under systemd. Then periodically executed
watchdog could check the service makes progress and react if it
doesn't.
The question is how to implement the watchdog then - it could be either
a global service or another executable in service directory, which
would be started periodically by runsv.
On Tue, Oct 19, 2021 at 07:24:38AM +0000, Ellenor Bjornsdottir wrote:
> Is this some genre of continuous readiness notification, or so?
>
> On 19 October 2021 07:20:41 UTC, Petr Malat <oss@malat.biz> wrote:
> >Hi,
> >I'm using the busybox implementation of runit to manage services and I
> >miss some kind of a watchdog in runsv. I though about extending
> >supervise/control pipe by a status command which would allow to publish
> >a status, for example 's Running'. Runsv would then append a monotonic
> >timestamp when it was received and the passed string to its argv[0]
> >making it visible in the process listing. This could be used by "check"
> >to check the service is up and also by watchdog to see it made some
> >progress since the last run.
> >Any opinions on that?
> >BR,
> > Petr
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2021-10-19 7:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 7:20 Petr Malat
2021-10-19 7:24 ` Ellenor Bjornsdottir
2021-10-19 7:41 ` Petr Malat [this message]
2021-10-19 9:47 ` Laurent Bercot
2021-10-21 9:20 ` Petr Malat
2021-10-19 17:46 ` Steve Litt
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=YW52nxwaMYS76C+2@ntb.petris.klfree.czf \
--to=oss@malat.biz \
--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).