On Sat, Apr 6, 2024, 19:43 Guillermo <gdiazhartu...@gmail.com> 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. >
