unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: 22039@debbugs.gnu.org
Subject: bug#22039: [PATCH] 'guix system reconfigure' must start/restart/stop services
Date: Mon, 24 Sep 2018 10:58:58 +0200	[thread overview]
Message-ID: <877ejbxodp.fsf@gnu.org> (raw)
In-Reply-To: <87lg7ru83l.fsf@zancanaro.id.au> (Carlo Zancanaro's message of "Mon, 24 Sep 2018 09:06:38 +1000")

Hi Carlo,

Carlo Zancanaro <carlo@zancanaro.id.au> skribis:

> On Fri, Sep 21 2018, Ludovic Courtès wrote:
>> What would you put there?  Do you have concrete examples?
>
> I would have three possible values: 'never, 'always, 'manual.
>
> 'never would mean that the service should never be restarted. This is
> for things like udev, or the filesystems, which should never be
> restarted on a running system.
>
> 'always would mean that the service is always safe to restart. I don't
> immediately know what services would fit in this category (maybe sshd,
> given Efraim's comment; maybe ntpd? I'm sure there are others). Things
> like nginx will probably not fall into this category, because they
> involve some downtime when restarting. Reloading their configuration
> (via a "reload" action, or similar) is not enough because the binary
> and/or libraries might have changed (and, in the worst case, might
> have an incompatible configuration format, although I would expect
> that to be exceedingly rare).
>
> 'manual would mean that the service should be restarted, but it need
> to be done at an appropriate time. This should prompt the user with
> the names of the services, and we should provide an option to guix
> system reconfigure to restart these services as part of the
> reconfigure. We could call the option "--restart-services".

OK, I see.

>> We can go with your patch and a message along the lines of what we
>> discussed above, and then work on the improvements you mentioned,
>> one at a time.  That way we’ll have the warm feeling of having
>> achieved something, even if there’s more to come.  :-)
>
> I won't be able to look at writing the code for this for a few weeks,
> but hopefully I'll get to it around mid- to late-October.

If that’s fine with you, I can apply the patch you initially posted so
we can start taking advantage of it (I’d like to push a Guix release by
the end of October.)  WDYT?

Thanks!

Ludo’.

  reply	other threads:[~2018-09-24  9:00 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
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 [this message]
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=877ejbxodp.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=22039@debbugs.gnu.org \
    --cc=carlo@zancanaro.id.au \
    /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).