all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCHES] Update elogind to 219.13
Date: Mon, 07 Mar 2016 12:03:54 +0100	[thread overview]
Message-ID: <87si025z39.fsf@igalia.com> (raw)
In-Reply-To: <87pov6vc6j.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 07 Mar 2016 11:01:56 +0100")

On Mon 07 Mar 2016 11:01, ludo@gnu.org (Ludovic Courtès) writes:

> BTW, a few days ago we were discussing on IRC the fact that elogind
> would start before dbus-daemon, and thus get respawned a couple of times
> at system startup, etc.  Yesterday, with commit 956ad60, I changed it to
> be started through D-Bus activation, so we should be safe now.

FWIW I am not sure that this is the right solution.  Logind has some
other interfaces (notably the /run/systemd file system and the cgroups)
and it really wants to be running from beginning to end.  If it's
bus-activated, could it be killed at some point if it's inactive?  If so
that would be bad I think.

Maybe it's OK.  It certainly solves the race, in some way.  I think
before a "guix system reconfigure" would restart logind, also; is that
still the case?  Which is better?  Very murky to me.

Andy

  reply	other threads:[~2016-03-07 11:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-06 18:41 [PATCHES] Update elogind to 219.13 Andy Wingo
2016-03-06 21:35 ` Ludovic Courtès
2016-03-07  8:52   ` Andy Wingo
2016-03-07 10:01     ` Ludovic Courtès
2016-03-07 11:03       ` Andy Wingo [this message]
2016-03-07 12:09         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87si025z39.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=guix-devel@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.