Open WhyNotHugo opened 2 years ago
Did you try /proc/self/fd/3
(as workaround)?
Almost. xdp tries to CREATE the file, and that fails. Maybe this could be handled and try to open the provided path. That's good enough for me.
Error is:
May 27 19:03:27 victory env[453446]: Failed to start proxy for unix:path=/run/user/1000/bus: Error binding to address (GUnixSocketAddress): Address already in use
Note: This error is broken! When the downstream path exists, the error prints the path of the upstream path. I should report that in a separate issue, but noticed it before.
Looking at flatpak_proxy_start
in flatpak-proxy.c
: it uses g_unix_socket_address_new
, which seems to create a new socket... not sure if it's possible to adapt that to:
I'm not sure if this would be an acceptable solution either.
I'm trying to use
xdg-dbus-proxy
with systemd socket based activation.That is, systemd creates the socket early during startup, but will initialise the proxy only after receiving the first connection to it.
Currently it is possible to specify a file path via
PATH
:In order to do socket activation, the proxy would need to listen on a file descriptor:
Regrettably, passing simply
fd:3
creates a file socket namedfd:3
. Would it be possible to also support listening of file descriptors for this kind of usage?