From: ludo@gnu.org (Ludovic Courtès)
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: help-guix@gnu.org, "Clément Lassieur" <clement@lassieur.org>
Subject: Re: Configuring a service but not starting it on boot
Date: Wed, 28 Nov 2018 18:20:38 +0100 [thread overview]
Message-ID: <87ftvl15ll.fsf@gnu.org> (raw)
In-Reply-To: <cu7y39dji72.fsf@systemreboot.net> (Arun Isaac's message of "Wed, 28 Nov 2018 21:41:13 +0530")
Hello Arun,
Arun Isaac <arunisaac@systemreboot.net> skribis:
>> Attached is a hack I did a while ago.
>
> Hacks like the one you showed could work, but it would be nice to have a
> general purpose #:auto-start? property common to all services. Is there
> such a feature? If not, could we implement such a feature?
The openssh service has such an option, but currently, it’s really
per-service, which isn’t great. It would be best if we had a generic
way to say which Shepherd services should be started automatically and
which shouldn’t.
Ludo’.
next prev parent reply other threads:[~2018-11-28 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 7:47 Configuring a service but not starting it on boot Arun Isaac
2018-11-28 9:34 ` Clément Lassieur
2018-11-28 16:11 ` Arun Isaac
2018-11-28 16:44 ` znavko
2018-11-28 17:20 ` Ludovic Courtès [this message]
2018-11-28 17:52 ` Arun Isaac
2018-11-29 10:49 ` Ludovic Courtès
2018-11-30 9:03 ` Arun Isaac
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftvl15ll.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=arunisaac@systemreboot.net \
--cc=clement@lassieur.org \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).