From: Attila Lendvai <attila@lendvai.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: shepherd respawn frequency
Date: Sun, 02 Jul 2023 20:25:10 +0000 [thread overview]
Message-ID: <ervQPVZkOD9U7xOFlU3jQKq6B8A2uS7nrvdFDK4iKh4z96QuY8ge2j8WntZ_sbNqPVvusSvu5bMfmnkLUe6tvpetzqHIS-otyN1DLRG8NkI=@lendvai.name> (raw)
In-Reply-To: <87zg4et755.fsf@gnu.org>
> We could do that. It never occurred to me that this is something one
> would want to have though. My reasoning is that if you mark a service
> as respawnable, then you really want it to be respawned as soon as it
> fails, not 5 seconds later.
there are a large number of different applications that users may want to run as a service. i'm pretty sure a nontrivial subset of them can get into such an error loop.
this specific one is the Bee client of ethswarm.org. multiple threads are active during its startup. one of them is to connect to the blockchain node. when it's unreachable, then eventually it gives up and quits.
arguably, it would be a better behavior to keep trying indefinitely instead of quitting, but let's assume that its behavior is practically beyond our control.
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
The real voyage of discovery consists not in seeking new landscapes, but in looking with new eyes.
next prev parent reply other threads:[~2023-07-02 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 8:34 shepherd respawn frequency Attila Lendvai
2023-07-02 20:01 ` Ludovic Courtès
2023-07-02 20:11 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-07-02 20:25 ` Attila Lendvai [this message]
2023-07-03 9:08 ` Efraim Flashner
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='ervQPVZkOD9U7xOFlU3jQKq6B8A2uS7nrvdFDK4iKh4z96QuY8ge2j8WntZ_sbNqPVvusSvu5bMfmnkLUe6tvpetzqHIS-otyN1DLRG8NkI=@lendvai.name' \
--to=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.