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.5 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,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 EFDE92509D for ; Sat, 6 Apr 2024 17:58:12 +0200 (CEST) Received: (qmail 21338 invoked by uid 89); 6 Apr 2024 15:58:37 -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 21325 invoked from network); 6 Apr 2024 15:58:36 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712419088; x=1713023888; darn=list.skarnet.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=lamPO+WP+NxzYY3UFm3AESb7mog2oEJcHJr/B4NqzeA=; b=ktg5dlWI0matOxNrMT8G4zbEG5L5QYDo+pT+znY0YwHKJfmzIwqDBArlHaGGLiQgYD m9bsnjLLaOwhEFj6K1J7Awml5HzZETIMoh4ZuLQ4HGI2onyLFO46GqqxLO+VAMtHZ7pJ mB8PU0ushUq1Ac9fjK/t/lH/JUh67K6618ATeunBStVz0diFW5lW9971PzcIE1S+sRDt QTe+qhNR5pKwtTlJExPD6u/cMg2VdyENyuVOKmtEzMmmbnSo199XkcNuUhxaE2+4TWM3 XIh0SQQWEn5AerNRNPYaiZP0DTsY2TEhZpXZZBt2mT7yS9Dwdzl1hhHHgLr2fEldwZLB uJgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712419088; x=1713023888; h=cc: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=lamPO+WP+NxzYY3UFm3AESb7mog2oEJcHJr/B4NqzeA=; b=mMaHq6VvcnJ+JTWVeFpMUrobpIRiJRr7se0BHR+sioZ8lD5MIuXSsJEBCxionTJyDb o1D5Pv7OMAZ+dmnchSB32okaIKcy/Qf3PY5S4UgmmqLNYKhXNECIgpTbboC07ebNmoHZ b0usW3rsoS4azpWbLEXfHG2GkcUPVj5yOFILuhMR6B61z2rLJf17VZwcvmbhDHGyRFbs pKZ+EdLd5yuUPAUpH1JpjY/OmaRqFtlKvgBPEUwH8YsJk6Y+nkKS1JgnhUIFnsW8krF6 euo4ihudE0qt2hqj1XsCklyhFR1j8hw5He4/c9jjnSW0gjDq7RDaY9p46Vtu4VXs5Gr5 IKWQ== X-Forwarded-Encrypted: i=1; AJvYcCWcMvIJ78U+L2lvhDewwVv9Q2xLa6m8lhp5PSEbVKJ8oi3Ye8R4NeCHqkxxShHwWvpst2fPqtsj2m8W0xoGaV1pO2yT2+ajooU= X-Gm-Message-State: AOJu0YwTL69oOvqY7KBfb4aRLVNlV0GS6thy8I+o29fMhb+pSZ+IRwcR XV9gktR1Eod+3BJtlOmCyalXj4rqDrGtTC5LCKsAae4wwkNNG1X9hAjaNxA4QbIFrTbCbwySlQd BVl/ZUznd4G2BHU1jMxRAlIpt+aQ= X-Google-Smtp-Source: AGHT+IH9WYWNgme5Bx9PGanCAmq1EulY/IhlPqoTQQ8UxprVJ9TheXQkGAQrKNPQTq1GnXZ2JK9R1f/+lOI1bhBDJ9w= X-Received: by 2002:a05:6870:638a:b0:229:fd96:1e6f with SMTP id t10-20020a056870638a00b00229fd961e6fmr4830701oap.24.1712419087587; Sat, 06 Apr 2024 08:58:07 -0700 (PDT) MIME-Version: 1.0 References: <87jzlgnzoh.fsf@gmail.com> In-Reply-To: From: Muhammad Mahendra Subrata Date: Sat, 6 Apr 2024 22:57:56 +0700 Message-ID: Subject: Re: s6-rc user services on Gentoo To: Guillermo Cc: supervision , skaware Content-Type: multipart/alternative; boundary="0000000000006c1edb06156fa3c9" --0000000000006c1edb06156fa3c9 Content-Type: text/plain; charset="UTF-8" On Sat, Apr 6, 2024, 19:43 Guillermo wrote: > 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. > I have been using `--print-pid=3` as readiness notification for dbus-daemon for quite a while now on my user services and I haven't had any problems with it so far. IIRC, looking at dbus-daemon code, it actually prints the socket address first then its pid. So, I use the `--print-address=` option to save the socket address to a file for consumption by s6-envdir. > --0000000000006c1edb06156fa3c9--