From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from alyss.skarnet.org (alyss.skarnet.org [95.142.172.232]) by inbox.vuxu.org (Postfix) with SMTP id 5FF35217C9 for ; Sat, 6 Apr 2024 14:43:21 +0200 (CEST) Received: (qmail 15848 invoked by uid 89); 6 Apr 2024 12:43:46 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 15834 invoked from network); 6 Apr 2024 12:43:46 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712407398; x=1713012198; darn=list.skarnet.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=eVg14r28ghBGkB+fcRf7atDH5q2A5Lsdti41EfObZ2k=; b=X0n4+a0EHjyI/uZA0stIK8pPWk+5AbHEuOiCRZh+KORm3zOsLUVYhAT3/gV/js4+1F kP+css0RgRyjjCt+Al/CMYfE21WGNZKCJHRK45JsdeUDgAgypiC+7Wgcjz6bSVLbpzmY pj7KaO4DQ7lqJOPb+GLlFGtwIDZscCmPfDvCucjg2biJgTWL+1UzsbeymaY/QYsSDhsl urRP+QT4wFOiuTWmKLJH+SYiNWoGrYZRuYeqs1dl5H+6kfmUibc31KHofbp3nN/OtuKn xp298vGzXOwFE6bBAiwmx6Q/x7ffOOflOxf2YAEXPrsKa5KqCEUN5podWuqGl8M1YWmP ez5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712407398; x=1713012198; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=eVg14r28ghBGkB+fcRf7atDH5q2A5Lsdti41EfObZ2k=; b=YRX2EPsHIQjr3MulxKucJ+biPScK6sYS1icSig7B7wM6B4Xw49CDSeXYFwMHhr+igA cIzLYYqQw3jYobh7MML0LkaM6fpPzVBfcdqMz1NcS+tyx2bGgjJLmxgfigrzhWVKlpNJ BSF8fO458HosKKqiBK8H+0si7OdO957qwBxLqt2M7VP3bGhRA5nbhNUrdPIS+csWLe/A 89x5Cany++rUCBZN8zTcC3uB8beqcFQMq07KLjOzesz0Gb66HTzwPuPX6xO8IIsbNfWQ Jn5hqX2bZ3eOKqPUU9mE5wCs0wQ6VeC8wNdKITnGQ0HxUrOM8jHaIbAxynrsvdbMMDKV 7WxA== X-Forwarded-Encrypted: i=1; AJvYcCVMRggCqyMLTS0yXZpS7KMf1A7SRuXxaUE5dvVLvjTUlYv5pd5PisaEFYX13Hj5FiKqiuY5TuRyisXJahhKvbVExgEDp3Y6ULE= X-Gm-Message-State: AOJu0YwQcqqpXeGm2dHBfucYfEIc/086RmV/UZYcvqCUaEzkdVnhrGXP ilJlz5Fm22AHi65c5Qnq2nuvoCSm9dAs7t7a1l1plpktOX4aI8ca4ASMZe8xRsuAe+MqkROVtat mJTLubTmUuppuxR50zdilNQ3b3LLoTscnWGk= X-Google-Smtp-Source: AGHT+IEqxIah8jS2HO+yOnJDoOPKgzI7fHpKX+KTvw4g/JZNtNH/yimlBDhTnclQ+Jxl7FwkZ4qf+01bdBNVGHK3p5U= X-Received: by 2002:ac8:7d92:0:b0:434:663e:e65e with SMTP id c18-20020ac87d92000000b00434663ee65emr4656366qtd.18.1712407397471; Sat, 06 Apr 2024 05:43:17 -0700 (PDT) MIME-Version: 1.0 References: <87jzlgnzoh.fsf@gmail.com> In-Reply-To: From: Guillermo Date: Sat, 6 Apr 2024 09:43:07 -0300 Message-ID: Subject: Re: s6-rc user services on Gentoo To: supervision , skaware Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable El mi=C3=A9, 3 abr 2024 a las 8:37, Laurent Bercot escribi=C3=B3: > > >2) The presence of a notification-fd file tells s6 that dbus-daemon > >can be somehow coerced into producing an s6-style readiness > >notification using file descriptor 3 without changing its code, are > >you sure that's the case with this script? My service definition for > >the system-wide message bus polls for readiness using s6-notifyoncheck > >and a dbus-send command... > > "dbus-daemon --print-address=3D3" should produce a suitable notificatio= n. > The address of the bus can only be printed once the bus exists. :) But then, there is a problem if one actually wants the server address information that --print-address provides. Alexis' 'run' script for example wants to save that to a file (apparently in a directory suitable for s6-envdir). If the output is sent to the notification pipe instead, s6-supervise will 'eat' it while waiting for the final newline character, and then the information is lost. And more generally, there's also the question about how 'ready' dbus-daemon actually is when the point in its code that prints the server address is reached. I can't really say without looking at the code; dbus-daemon has many duties once its UNIX domain socket is bound. G.