From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 22039@debbugs.gnu.org
Subject: bug#22039: [PATCH] 'guix system reconfigure' must start/restart/stop services
Date: Sun, 23 Sep 2018 21:53:51 +0200 [thread overview]
Message-ID: <87lg7srnw0.fsf@gnu.org> (raw)
In-Reply-To: <20180923082613.GA1226@macbook41> (Efraim Flashner's message of "Sun, 23 Sep 2018 11:26:13 +0300")
Hi,
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Fri, Sep 21, 2018 at 01:58:03PM +0200, Ludovic Courtès wrote:
[...]
>> Note that FHS distros don’t do better: either the service is
>> hot-replaceable (nginx; I don’t know of any other) or can at least
>> reload its config (sshd, etc.), and then it’s dynamically upgraded, or
>> it’ll be upgraded next time you restart it.
>>
>> That’s because fundamentally only the user can tell whether now is a
>> good time to restart, say, sshd.
>
> Not exactly the point, but Debian regularly restarts sshd for me on a
> remote box (somehow) without me losing the connection.
Good point! I think sshd opens child processes for new sessions, and
thanks to that it falls into the category of service that can be
hot-replaced.
For hot-swappable daemons, I think we should provide a specific ‘reload’
or ‘upgrade’ action as was discussed at
<https://issues.guix.info/issue/26830>. That way, to figure out the
right strategy, we would just check whether the service supports that
action.
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-09-23 19:54 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 [this message]
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=87lg7srnw0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22039@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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).