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: Sun, 02 Sep 2018 13:43:56 +1000 [thread overview]
Message-ID: <87tvn8d0n7.fsf@zancanaro.id.au> (raw)
In-Reply-To: <87tvn9b0qh.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 340 bytes --]
On Sun, Sep 02 2018, Ludovic Courtès wrote:
> First, could you check (in a VM) whether the boot failure is
> reproducible when that patch that removes ‘EINTR-safe’ is
> applied?
As far as I can tell it's completely reproducible.
> If it’s 100% reproducible, could you share the VM’s output?
Sure. It's attached.
[-- Attachment #1.2: vm-output --]
[-- Type: application/octet-stream, Size: 42762 bytes --]
[-- Attachment #1.3: Type: text/plain, Size: 802 bytes --]
> Indeed. In addition, some low-level services such as file
> system mounts cannot be restarted without rebooting, so it’s not
> useful to mention them. Perhaps we should simply print (1) the
> list of services that were restarted, and (2) a message saying
> that users should explicitly run “herd restart SERVICE” to
> upgrade other services.
>
> WDYT?
If there are services that must never be restarted, then maybe we
don't want to indiscriminately print out a message to restart
everything. We need some way to mark services that must not be
restarted. If that's the case, then we might as well just
automatically restart the services that we can rather than
printing a message saying to do so. What do we gain by adding an
extra step to that process?
Carlo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-09-02 4: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 [this message]
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
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=87tvn8d0n7.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).