From debbugs-submit-bounces@debbugs.gnu.org Mon May 23 22:27:35 2022 Received: (at 55444) by debbugs.gnu.org; 24 May 2022 02:27:35 +0000 Received: from localhost ([127.0.0.1]:50554 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ntKGf-0003Et-Qz for submit@debbugs.gnu.org; Mon, 23 May 2022 22:27:35 -0400 Received: from mail-qv1-f45.google.com ([209.85.219.45]:33696) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ntKGe-0003Eg-2A for 55444@debbugs.gnu.org; Mon, 23 May 2022 22:27:28 -0400 Received: by mail-qv1-f45.google.com with SMTP id j3so13444968qvn.0 for <55444@debbugs.gnu.org>; Mon, 23 May 2022 19:27:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=1tLRQpoc992jlCtVz7ebfrUTJrXqky181uW6QKe65AE=; b=Z113bcH4fOZm34AlmANKjZFFjwJoMZgprPfM1npQpXBYjq2OeLRFomT7lGyLZjCOoD oMpflo7hBOMb3u7EvS15uqAkzt6+Mms6vz0CB07eYwFnEGKbFAE0wnT9CP5PULYllOy1 P9U9Vh4IEOi2hYSUDmDURMxfg0JU3p0i0lAO24v8FHKsi1gp5VWSG0JrEj/qIAxm7Nwa TU2P+UJoWG/nrEXB0MgjbWwoWz/PLXKH2LTGSU/aHzTAd1PTZjawgGEWbkFNDBDRCN88 O8cg0jQVyM9i5vY/l5ygFR2JDdMg0B6nyFxEJ8KWhuejUC1/9NJgEx0JwvPV1MljtNz6 0YKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=1tLRQpoc992jlCtVz7ebfrUTJrXqky181uW6QKe65AE=; b=FuM4D3VWXbuRSvJjsC4zh8v4+N2OntAXfTT82RTcb2p5+tczrFflNrRIewuwe8of1o 60mqFpMf6JNFCjgZN+cVa766pJSWUl3KrNnGc0qAbZw8SHWXeYrn5E0OsaikBDnp7uxw Um0RPCxdJjv78c2m1wBc2kkzO12SIY1Y+0e/KXJdAKhtdxwgpM5ClYwJqMyLnz5ZTCr1 CY96RQ448o6bhwNXoQ/MS3eAGLHoxatFpl9FxjZyjVxjGOvNO6qb6w8bzA+5Yw30H9BX /nTLFCwRMFSqhs841fAGZXSopd1AExSygdZh+Neb1bYkzkLBxwVtyfO2kTFY/wSsI0Pq Mw6A== X-Gm-Message-State: AOAM532zC5bEtIpe5ygldgyuh45V+LUydUjb5ymjwig1wNqZS7U46F5s gxVaIHbcfN4X81/gmVUSPKOF8IjRBx+i2Q== X-Google-Smtp-Source: ABdhPJx5sUvnig41MUJdlpc7C1yWgOtQF7cbv0VlECEV6tmpRVewvtuxMaZx9en4bPFjEpCGZykD9w== X-Received: by 2002:a0c:f0c3:0:b0:461:d824:c66e with SMTP id d3-20020a0cf0c3000000b00461d824c66emr19632296qvl.111.1653359242065; Mon, 23 May 2022 19:27:22 -0700 (PDT) Received: from hurd (dsl-157-33.b2b2c.ca. [66.158.157.33]) by smtp.gmail.com with ESMTPSA id e18-20020ac84b52000000b002f93e856eccsm1157904qts.32.2022.05.23.19.27.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 23 May 2022 19:27:21 -0700 (PDT) From: Maxim Cournoyer To: Ludovic =?utf-8?Q?Court=C3=A8s?= Subject: Re: bug#55444: elogind startup race between shepherd and dbus-daemon References: <877d6lc28o.fsf@inria.fr> Date: Mon, 23 May 2022 22:27:20 -0400 In-Reply-To: <877d6lc28o.fsf@inria.fr> ("Ludovic =?utf-8?Q?Court=C3=A8s=22?= =?utf-8?Q?'s?= message of "Mon, 16 May 2022 10:26:15 +0200") Message-ID: <87y1yr4qd3.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 55444 Cc: 55444@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Hi, Ludovic Court=C3=A8s writes: > Hello! > > Currently (40a729a0e6f1d660b942241416c1e2c567616d4d), shepherd and > dbus-daemon compete to start elogind: shepherd tries to start it > eagerly, and dbus-daemon starts it on-demand upon bus activation. > > Sometimes dbus-daemon wins, and thus shepherd tries a few times to start > it anyway, leading to the infamous: > > elogind is already running as PID 123 Do we have a system test that sometimes reproduce it, or at least the above message? I have some branch where I introduce some D-Bus synchronization primitives I had started to fix https://issues.guix.gnu.org/issue/52051, which ended up being fixed differently (bumping the timeout value); perhaps it could be of use here. Thanks, Maxim