Differences

This shows you the differences between two versions of the page.

--- dbus [2025/03/23 13:40] – tmaier
+++ dbus [2025/03/23 14:21] (current) – tmaier
@@ Line 23: / Line 23: @@
   * dbus-broker only implements message mediation (bus setup and external communication needs to be handled by the //Controller//.
   * The //Controller// hands over a unix socket (as file descriptor //FD//) to the dbus-broker instance (''--controller=FD'')
-  * The unix socket is used by dbus-broker to accept control commands from the //Controller// and to create interfa
+  * The unix socket is used by dbus-broker to accept commands from the //Controller//.
+  * Example commands issued by the Controller: Create listener sockets, specify bus policy, create activatable names, react to bus events.
+dbus-broker-launch:
+  * dbus-broker-launch spawns and manages one message bus
+  * Configuration file is specified via ''--config-file'' or the default is taken from ''/usr/share/dbus-1/'' (''session.conf'' for ''--scope=user'' and ''system.conf'' as fallback)
+  * ''--scope'' defines which systemd instance (user or system) is used to start the launcher
 === dbus-broker on Arch Linux ===
@@ Line 42: / Line 48: @@
 Daemons:
-  * dunst
+  * dunst: Lightweight, customizable, scriptable, minimalistic and provides features like rules, pausing, notification history
-  * NotifyOSD / notify-osd
+  * NotifyOSD / notify-osd: Configurable, animations, sound, merging, overflow, flood prevention, do-not-disturb mode,
 Depending on the Desktop Environment, notification daemons are built-in (Cinnamon, Gnome, KDE). Notification daemons can started standalone for other environments (e.g. i3wm). Standalone is possible via XDG autostart or as DBUS service.