[systemd-devel] default dbus socket path being /run

Lennart Poettering lennart at poettering.net
Tue Dec 17 12:19:35 PST 2013


On Tue, 17.12.13 20:46, Umut Tezduyar (umut at tezduyar.com) wrote:

> 
> On Tue, Dec 17, 2013 at 8:26 PM, Lennart Poettering
> <lennart at poettering.net> wrote:
> > On Tue, 17.12.13 20:23, Umut Tezduyar Lindskog (umut.tezduyar at axis.com) wrote:
> >
> >> Hi,
> >>
> >> Now that dbus sockets are by default expected to be in /run by systemd; /var/run by other dbus libraries, we have to use env variables to tell one of them the correct socket path.
> >>
> >> Both systemd and glib (gio) are hardcoding the default dbus socket path and having an override with environment variable. Since the default values for both libraries are different, we have to specify either systemd's applications or glibs applications the correct dbus socket.
> >>
> >> Wouldn't it be the best to make default dbus socket path a ./configure option? Or maybe ask dbus with pkgconf first and fall back to a default value?
> >
> > /var/run is the legacy alias for /run. In systemd we won't use /var/run
> 
> Hi. I am suggesting to make it a configure option not to make it
> /var/run. And same suggestion is valid for glib. Dbus
> (http://dbus.freedesktop.org) has a configure option to change the
> socket path for those who want to put their socket to an
> /alternate_path.

Hmm, D-Bus and glib both try to be compatible with various older
systems, so connecting to /var/run appears to be the safe choice.

That said, I am pretty sure it would be a good idea to patch make them
avoid /var/run on systems where that's just legacy for /run.

Lennart

-- 
Lennart Poettering, Red Hat


More information about the systemd-devel mailing list