From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: "Back off" setting for crashing services with s6+openrc?
Date: Mon, 10 Oct 2022 16:20:53 +0000 [thread overview]
Message-ID: <em4bb43cb5-e6ec-4ddc-8ce0-0dd437a2a086@d1fbe012.com> (raw)
In-Reply-To: <424271f5-f2ab-7fe9-e795-2668cda7fe40@fourc.eu>
>To me this seems like a relevant improvement that would catch a problematic edge case issue.
I pushed such a change to the s6 git. A new numbered release should
be cut soon-ish.
--
Laurent
next prev parent reply other threads:[~2022-10-10 16:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 19:45 Tor Rune Skoglund
2022-09-22 20:21 ` John W Higgins
2022-09-23 7:29 ` Tor Rune Skoglund
2022-09-23 16:44 ` Alyssa Ross
2022-09-24 12:33 ` Oliver Schad
2022-09-26 23:00 ` Colin Booth
2022-09-30 9:34 ` Oliver Schad
2022-09-30 13:21 ` Laurent Bercot
2022-10-04 14:16 ` Tor Rune Skoglund
2022-10-10 16:20 ` Laurent Bercot [this message]
2022-10-11 0:38 ` Dewayne
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=em4bb43cb5-e6ec-4ddc-8ce0-0dd437a2a086@d1fbe012.com \
--to=ska-supervision@skarnet.org \
--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).