Hi, Attila Lendvai <att...@lendvai.name> skribis:
> i have a daemon process that quits soon after it starts (when it has some > issue with its configurations). > > then i usually fix the config, and do a guix system reconfigure. but i have > noticed from the logs that this process often remains in a resawn loop, even > if i herd stop and herd disable it after the reconfigure (i.e. a shepherd > service upgrade). If it’s in a respawn loop, the problem is that ‘herd stop’ may or may not happen at the right moment, because the service oscillates between the stopped/starting/running/stopping statuses. However, ‘herd disable’ should prevent it from being respawned. (Respawning calls ‘start-service’, which cannot start a service marked as disabled.) But I don’t know, there could be a bug. Could you come up with a reduced test case (I looked at the one attached but I’m not sure which part to focus on), or do you have logs of the problem? Thanks, Ludo’.
