Disabling Shepherd services across reboots?

Disabling Shepherd services across reboots?

[Felix Lechner via Development of GNU Guix and the GNU System distribution.]

Hi,

Is there a way to disable Shepherd services across reboots without
reconfiguring the system?  If not, what is the purpose of 'herd disable'
vs 'herd stop'?

My background is I have a system I cannot currently reconfigure.  (I use
experimental features from a development version of the Shepherd as a
Scheme noobie.)  A Shepherd timer pulls rsync data every five minutes.
That timer fails due to a corruption issue in an Sqlite3 database, which
sends me an email. I disabled the service, but yesterday I had two power
outages. Each time, the emails came back.

I believe the popular expectation might be that 'herd disable' disables
a Shepherd service until the system is reconfigured.

Kind regards,
Felix

Re: Disabling Shepherd services across reboots?

[Ludovic Courtès]

Hi,

Felix Lechner via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org> skribis:

> Is there a way to disable Shepherd services across reboots without
> reconfiguring the system?

No, it’s not supported (I never thought about this use case).

> If not, what is the purpose of 'herd disable' vs 'herd stop'?

A service that is disabled cannot be started until it is explicitly
re-enabled.  For instance, a service that keeps respawning is
automatically disabled.

Ludo’.