Fail to connect to socket, not found system_bus_socket.

Thiago Macieira thiago at kde.org
Wed Oct 3 15:14:31 UTC 2018


On Tuesday, 2 October 2018 23:12:53 PDT Lawrence D'Oliveiro wrote:
> On Tue, 02 Oct 2018 22:50:57 -0700, Thiago Macieira wrote:
> > dbus-monitor, like all applications, does not read the config file.
> > It's trying to find the system bus socket from the hardcoded path
> > that you passed during configure.
> 
> As I understand it, if the environment variable
> “DBUS_SYSTEM_BUS_ADDRESS” is set, then its value is the address of the
> system bus socket. Otherwise it defaults to
> "unix:path=/var/run/dbus/system_bus_socket".

Right. That default is set during configure, there's an option for it. If 
you're always going to use /tmp/dbus, you may want to use that.

Suggestion: update your filesystem hierarchy a little and have /run be mounted 
as a tmpfs too, or make /run a symlink to /tmp (and /var/run is a symlink to 
/run). That way, /var/run/dbus_system_socket also lives in a tmpfs.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center





More information about the dbus mailing list