Location of system socket

Felipe Gasper felipe at felipegasper.com
Sun Dec 16 21:20:04 UTC 2018

> On Dec 16, 2018, at 4:12 PM, Lawrence D'Oliveiro <ldo at geek-central.gen.nz> wrote:
> On Sun, 16 Dec 2018 12:33:24 -0500, Felipe Gasper wrote:
>> What is the best way to find the system bus socket’s location if,
>> e.g., a custom location is compiled into libdbus?
> Thinking about it, the default value hard-coded into libdbus cannot be
> changed. Changing it breaks the protocol.
> Why? Because not all bus peers on a system have to be using libdbus.
> There are other alternative implementations of the D-Bus protocol. In
> order for them to interoperate, they all have to agree on what the
> protocol is. This includes finding the addresses for connecting to the
> D-Bus daemon. Therefore, the default values hard-coded into libdbus
> have to be considered part of the D-Bus protocol.

Thank you for everyone’s responses thus far.

So, to give a bit more context:

My MacPorts dbus install puts the system socket at /opt/local/var/run/dbus/system_bus_socket. That path is hard-coded into libdbus but doesn’t appear to be available to any other client library.

Is this a bug in the MacPorts installation, then?


More information about the dbus mailing list