--- Begin Message ---
|
Subject: |
shepherd respawns a service even when it's disabled |
|
Date: |
Sun, 11 Jun 2023 18:01:24 +0000 |
the issue:
i'm in a situation where my service quits after a few seconds of CPU usage
(i.e. the default-respawn-limit is not triggered). therefore shepherd keeps
restarting it, practically in a busy loop.
suggested solution:
maybe respawn-service should check for the disabled state, so that the admin
can intervene by `herd disable myservice`.
a longer term solution could be to add a respawn-delay field for <service>, and
default it to something non-zero.
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
The mind: an excellent servant, but a dangerous master.
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#64008: shepherd respawns a service even when it's disabled |
|
Date: |
Wed, 14 Jun 2023 18:49:44 +0200 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
Hi Attila,
Attila Lendvai <attila@lendvai.name> skribis:
> i'm in a situation where my service quits after a few seconds of CPU usage
> (i.e. the default-respawn-limit is not triggered). therefore shepherd keeps
> restarting it, practically in a busy loop.
>
> suggested solution:
>
> maybe respawn-service should check for the disabled state, so that the admin
> can intervene by `herd disable myservice`.
Turns out the service controller was ignoring the ‘enabled?’ flag,
leaving it up to the caller to check it.
This is fixed by Shepherd commit
7c88d67076a0bb1d9014b3bc23ed9c68f1c702ab.
Thanks again,
Ludo’.
--- End Message ---