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=-1.0 required=5.0 tests=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 CA0A12201F for ; Sat, 6 Apr 2024 15:57:24 +0200 (CEST) Received: (qmail 17955 invoked by uid 89); 6 Apr 2024 13:57:49 -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 17948 invoked from network); 6 Apr 2024 13:57:49 -0000 From: "Laurent Bercot" To: supervision Subject: Re: s6-rc user services on Gentoo Date: Sat, 06 Apr 2024 13:57:23 +0000 Message-Id: In-Reply-To: References: <87jzlgnzoh.fsf@gmail.com> Reply-To: "Laurent Bercot" User-Agent: eM_Client/9.2.2157.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable >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. That is true. The option is only usable as readiness notification if=20 you don't otherwise need the information. >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. That doesn't matter. The important thing with readiness is that clients need to be able to send messages to the daemon. As soon as the socket is bound, it's okay; if the daemon hasn't finished initializing yet, then that's what kernel socket buffers are for. Of course, if the daemon still needs to allocate resources and can=20 *fail* after binding the socket and printing the line, that's not good, but=20 well, it's a balance between reliability and simplicity. -- Laurent