Questions about DBus and Polkit configuration

Randy McMurchy randy at linuxfromscratch.org
Sat Dec 4 08:12:28 PST 2010


Hi all,

I would like someone who is comfortable with D-Bus and PolicyKit (Wayne,
are you out there?) to confirm the following notes that I think should be
added to the Gnome GConf instructions:

1) If ${GNOME_PREFIX} is not /usr, then the following lines should be added
to the /etc/dbus-1/system-local.conf file creation instructions:

  <!-- Search for .service files in /opt/gnome/2.30.2/share/dbus-1/system-services -->
  <servicedir>/opt/gnome/2.30.2/share/dbus-1/system-services</servicedir>

2) If ${GNOME_PREFIX} is not /usr, then an /etc/dbus-1/session-local.conf
file should be created using these instructions:

cat > /etc/dbus-1/session-local.conf << "EOF"
<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>

  <!-- Search for .service files in /opt/gnome/2.30.2/share/dbus-1/services -->
  <servicedir>/opt/gnome/2.30.2/share/dbus-1/services</servicedir>

</busconfig>
EOF

#'s 1 and 2 are required so that the service directories are found by
the MessageBus (D-Bus) if ${GNOME_PREFIX} is not /usr.

3) If ${GNOME_PREFIX} is not /usr, then a file
(/opt/gnome/share/polkit-1/actions/org.gnome.gconf.defaults.policy) is
created. I am not sure that the file in that location (alternate GNOME
prefix) will be found by PolicyKit (polkit, actually). The man page for
polkit(8) says that policy files belong in /usr/share/polkit-1/actions
and does not specify any way to include alternate directories.

Question on #3 is: Is there a way to include alternate "action" directories,
or should a symlink be created to /usr or will PolicyKit find it
automatically in the alternate location?

-- 
Randy

rmlscsi: [bogomips 1003.28] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3]
[GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686]
09:56:02 up 32 days, 16:50, 1 user, load average: 0.42, 0.11, 0.03



More information about the blfs-dev mailing list