all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Rutger Helling <rhelling@mykolab.com>
Cc: help-guix@gnu.org
Subject: Re: Don't auto-start a service in Shepherd
Date: Sat, 24 Feb 2018 23:15:06 +0100	[thread overview]
Message-ID: <87lgfiox05.fsf@gmail.com> (raw)
In-Reply-To: <20180223102236.0aef2eac@mykolab.com> (Rutger Helling's message of "Fri, 23 Feb 2018 10:22:36 +0100")

[-- Attachment #1: Type: text/plain, Size: 995 bytes --]

Rutger Helling <rhelling@mykolab.com> writes:

> Hello Guix,
>
> Is there a way to prevent auto-starting a service in Shepherd? I find
> that if I use "herd disable service" it still automatically starts the
> service on a reboot/reconfigure.

I do not know of a way, but perhaps somebody else does.  What is your
use case?  I'm curious to know why you want to disable the service, but
not remove it.

For now, you might be able to accomplish what you want by doing this.
Remove the service from your operating system configuration file, run
"guix system reconfigure", and then reboot into the new system
generation.  Once you're done with whatever you're doing, you can
permanently return to the previous system generation by running "guix
system roll-back", followed by a reboot.  Alternatively, you can
re-introduce the service into your operating system configuration file,
and "roll forward" by running "guix system reconfigure" again.

Hope that helps!

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-02-24 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-23  9:22 Don't auto-start a service in Shepherd Rutger Helling
2018-02-24 22:15 ` Chris Marusich [this message]
2018-02-24 22:27 ` Carlo Zancanaro
2018-02-26 10:42   ` Rutger Helling
2018-03-02 13:44     ` Ludovic Courtès

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=87lgfiox05.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=rhelling@mykolab.com \
    /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.