From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 22039@debbugs.gnu.org
Subject: bug#22039: [PATCH] 'guix system reconfigure' must start/restart/stop services
Date: Thu, 20 Sep 2018 21:50:51 +1000 [thread overview]
Message-ID: <87sh24qtes.fsf@zancanaro.id.au> (raw)
In-Reply-To: <87efdov32l.fsf@gnu.org>
Hey Ludo’,
> From the POV of the Shepherd, services carry no semantics.
In Guix we have as much information as possible about the
services. We should be know which services should be upgraded
automatically, which ones we should prompt the user to upgrade,
and which ones are never safe to upgrade. Maybe we could add a
"restart-strategy" to the shepherd-service object?
> Thus I think it’s reasonable to print a message along the lines
> of:
>
> The following services were upgraded: …
> Please run “herd restart SERVICE” to stop, upgrade, and
> restart services that were not automatically upgraded.
>
> WDYT?
The main reasons I'm not super happy with this are that it's not
discoverable (which is bad for new users), and it requires
interaction (so cannot be an unattended upgrade). In particular
for discoverability, some of our services don't take advantage of
the Shepherd's ability to have multiple "provision" values. For
instance, I just have to know that to restart wicd I have to run
"herd restart networking".
Maybe this should be a separate ticket. Replacing the services and
printing a generic message will still be an improvement on what
Guix currently does, and I don't want to hold that up just because
I think we can do better.
Carlo
next prev parent reply other threads:[~2018-09-20 11:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 16:35 bug#22039: 'guix system reconfigure' must start/restart/stop services Ludovic Courtès
2016-01-08 10:04 ` Ludovic Courtès
2016-02-03 21:32 ` Ludovic Courtès
2016-02-03 21:34 ` Thompson, David
2018-01-16 11:17 ` bug#22039: ‘guix system reconfigure’ does not always load new services Ludovic Courtès
2018-08-26 12:15 ` bug#22039: [PATCH] 'guix system reconfigure' must start/restart/stop services Carlo Zancanaro
2018-09-01 10:49 ` Ludovic Courtès
2018-09-01 12:15 ` Carlo Zancanaro
2018-09-01 12:33 ` Carlo Zancanaro
2018-09-01 17:12 ` Ludovic Courtès
2018-09-02 3:43 ` Carlo Zancanaro
2018-09-02 20:39 ` Ludovic Courtès
2018-09-19 15:47 ` Ludovic Courtès
2018-09-19 20:56 ` Carlo Zancanaro
2018-09-20 9:47 ` Ludovic Courtès
2018-09-20 10:24 ` Carlo Zancanaro
2018-09-20 11:08 ` Ludovic Courtès
2018-09-20 11:50 ` Carlo Zancanaro [this message]
2018-09-21 11:58 ` Ludovic Courtès
2018-09-23 8:26 ` Efraim Flashner
2018-09-23 19:53 ` Ludovic Courtès
2018-09-23 23:06 ` Carlo Zancanaro
2018-09-24 8:58 ` Ludovic Courtès
2018-09-24 10:18 ` Carlo Zancanaro
2018-09-26 21:46 ` 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
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=87sh24qtes.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=22039@debbugs.gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).