From: Paul Sopka <psopka@sopka.ch>
To: supervision@list.skarnet.org,
charlesc-supervision-skarnet.org@pyropus.ca
Subject: Re: Have an external script wait for a oneshot service
Date: Wed, 4 Dec 2024 18:12:07 +0100 [thread overview]
Message-ID: <8687a3d9-95e4-445d-82e2-9d1e3a490fec@sopka.ch> (raw)
In-Reply-To: <cc68fceb-c47f-483c-bf6f-45676037b939@pyropus.ca>
[-- Attachment #1.1.1: Type: text/plain, Size: 1120 bytes --]
Thank you for your answer!
> I could be mistaken, but I thought one-shots were specifically designed for
> fire-and-forget use,
I would argue that the following speaks against this:
- s6-rc tracks the state of oneshots already in that you can not run
"s6-rc start <oneshot>" multiple times without "s6-rc stop
<oneshot>" in between.
- Longrun service A can depend on a oneshot B in that it is only ran
once B is finished.
- It is useful to know whether and when a oneshot task is finished.
By the above I would argue that oneshots are on equal footing with
and of equal importance as longruns, not just "fire-and-forget" and
therefore would profit from an equally powerful readiness api.
> and that if you want to monitor it that way, you should
> use a regular service.
This is not possible, since what I depend on is a script that does its
thing and exits.
I would need to add a "sleep infinity" or better, a posix compatible
alternative at its end,
which would cause a useless dangling longrun being supervised and logged
- a waste of resources.
Regards
Paul Sopka
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3195 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2024-12-04 17:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 15:28 Paul Sopka
2024-12-04 15:38 ` Charles Cazabon via supervision
2024-12-04 17:12 ` Paul Sopka [this message]
2024-12-04 21:47 ` Hoël Bézier
2024-12-04 20:00 ` Brett Neumeier via supervision
2024-12-04 20:05 ` Paul Sopka
2024-12-04 20:18 ` Brett Neumeier via supervision
2024-12-04 20:59 ` Paul Sopka
2024-12-04 21:58 ` Re[2]: " Laurent Bercot
2024-12-05 5:59 ` Tanuj Bagaria
2024-12-05 6:54 ` Paul Sopka
2024-12-05 8:05 ` Re[2]: " Laurent Bercot
2024-12-05 13:52 ` Paul Sopka
2024-12-05 19:44 ` Re[2]: " Laurent Bercot
2024-12-05 21:10 ` Paul Sopka
2024-12-05 21:42 ` Brett Neumeier via supervision
2024-12-06 5:32 ` Paul Sopka
2024-12-05 23:03 ` Re[2]: " Laurent Bercot
2024-12-06 12:41 ` Paul Sopka
2024-12-06 15:43 ` Re[2]: " Laurent Bercot
2024-12-06 16:11 ` Hoël Bézier
2024-12-06 17:14 ` Paul Sopka
2024-12-07 23:46 ` Jan Braun
2024-12-05 21:24 ` Jan Braun
2024-12-05 23:15 ` Re[2]: " Laurent Bercot
2024-12-04 20:09 ` Tanuj Bagaria
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=8687a3d9-95e4-445d-82e2-9d1e3a490fec@sopka.ch \
--to=psopka@sopka.ch \
--cc=charlesc-supervision-skarnet.org@pyropus.ca \
--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).