From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andy Wingo <wingo@igalia.com>
Subject: Re: [PATCHES] Update elogind to 219.13
Date: Mon, 07 Mar 2016 12:03:54 +0100
Message-ID: <87si025z39.fsf@igalia.com>
References: <877fhf8n4f.fsf@pobox.com> <87a8mbe1cl.fsf@gnu.org>
	<871t7m7jqx.fsf@igalia.com> <87pov6vc6j.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59474)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wingo@igalia.com>) id 1acsxI-0007Zi-7u
	for guix-devel@gnu.org; Mon, 07 Mar 2016 06:04:05 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <wingo@igalia.com>) id 1acsxE-0000Vg-WE
	for guix-devel@gnu.org; Mon, 07 Mar 2016 06:04:04 -0500
In-Reply-To: <87pov6vc6j.fsf@gnu.org> ("Ludovic =?utf-8?Q?Court=C3=A8s=22'?=
	=?utf-8?Q?s?= message of "Mon, 07 Mar 2016 11:01:56 +0100")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org

On Mon 07 Mar 2016 11:01, ludo@gnu.org (Ludovic Court=C3=A8s) 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