From: Rutger Helling <rhelling@mykolab.com>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: help-guix@gnu.org
Subject: Re: Don't auto-start a service in Shepherd
Date: Mon, 26 Feb 2018 11:42:05 +0100 [thread overview]
Message-ID: <20180226114205.70f8965c@mykolab.com> (raw)
In-Reply-To: <87fu5qyqe2.fsf@zancanaro.id.au>
[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]
Thanks for the replies. My use case is that I don't want to auto-start
SDDM, since I usually start GNOME (Wayland) from the TTY. However there
are certain cases where I want to start GNOME on X11, for which I do
need SDDM.
On systemd you can do "systemctl disable service", so I was wondering if
there was an equivelant command in Shepherd. Removing the
service entirely and reconfiguring every time I want to start SDDM
isn't really what I'm looking for.
I'll have a look at `auto-start?`. I think it would be nice if all
services exposed this option.
On Sun, 25 Feb 2018 09:27:49 +1100
Carlo Zancanaro <carlo@zancanaro.id.au> wrote:
> On Fri, Feb 23 2018, Rutger Helling wrote:
> > 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've just had a look at gnu/services/shepherd.scm, and it looks
> like system services can set `auto-start?` to #f when creating
> their shepherd-service, but not many expose this. I think openssh
> is the only service to expose it to the system configuration. You
> could try patching the service you want to use to expose the
> option to not automatically start it. Which service are you trying
> to disable?
>
> There's a discussion to be had about whether shepherd should
> remember disabled services across a reboot/reconfigure. I don't
> think it should, because the running services should be considered
> a part of the system specification.
>
> Carlo
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-02-26 10:42 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
2018-02-24 22:27 ` Carlo Zancanaro
2018-02-26 10:42 ` Rutger Helling [this message]
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=20180226114205.70f8965c@mykolab.com \
--to=rhelling@mykolab.com \
--cc=carlo@zancanaro.id.au \
--cc=help-guix@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.