Commit deb06647 authored by Michael Biebl's avatar Michael Biebl

Don't attempt config reload if dbus system bus is not running.

There is no point to attemp a reload if the system bus is not running and
we avoid a warning upon initial installation this way.

Update the comment to reflect recent changes.
parent a77718b4
dbus (1.8.6-3) UNRELEASED; urgency=medium
* Don't attempt config reload if dbus system bus is not running.
-- Michael Biebl <biebl@debian.org> Thu, 21 Aug 2014 05:56:30 +0200
dbus (1.8.6-2) unstable; urgency=medium
* debian/dbus.posinst: When triggered only poke the dbus-daemon, don't run
......
......@@ -9,13 +9,9 @@ MESSAGEHOME=/var/run/dbus
LAUNCHER=/usr/lib/dbus-1.0/dbus-daemon-launch-helper
# This is what the init script would do, but it's simpler (and less
# dependent on sysvinit vs. Upstart vs. etc.) if we do it directly. It is not
# conditional on "$1" because it's also the right thing to do for the
# /etc/dbus-1/system.d and /usr/share/dbus-1/system-services triggers.
#
# If it's not running (perhaps we're in a chroot) this will just fail
# harmlessly, so there's no need to condition on status.
# dependent on sysvinit vs. Upstart vs. etc.) if we do it directly.
reload_dbus_config() {
[ -S /var/run/dbus/system_bus_socket ] || return 0
dbus-send --print-reply --system --type=method_call \
--dest=org.freedesktop.DBus \
/ org.freedesktop.DBus.ReloadConfig > /dev/null || true
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment