DBUS入门笔记

最新推荐文章于 2025-05-28 16:52:15 发布

原创

最新推荐文章于 2025-05-28 16:52:15 发布 · 2.5k 阅读

8 ·

CC 4.0 BY-SA版权

文章标签：

#DBUS #IPC

这篇博客介绍了DBUS的基本概念，包括其三层结构和应用场景。DBUS作为Linux下的进程间通信（IPC）工具，提供异步处理、安全连接等特点。文中详细解释了Object Path、接口、代理和Bus Name等核心概念，并通过QTDBUS的remotecontrolledcar案例展示了如何使用DBUS进行通信。在Mac上，博主分享了如何配置dbus-daemon作为守护进程。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

DBUS简介

学习网址：https://dbus.freedesktop.org/doc/dbus-tutorial.html

DBUS三层：
libdbus，消息分发的守护进程Dbus daemon，应用程序框架的封装库或绑定（For example, libdbus-glib and libdbus-qt）

libdbus仅仅支持one-to-one connection

关于传递，对象是message = header (filed) + body (param)
header常包括body中的数据类型信息。

DBUS的应用场景：
同一会话中的桌面应用程序
桌面应用程序和OS（系统级别的守护进程）

DBUS可以解决传统Linux IPC不能应付的远端系统管理员问题：


           A gap in current Linux support is that policies with any sort of
           dynamic "interact with user" component aren't currently
           supported. For example, that's often needed the first time a network
           adapter or printer is connected, and to determine appropriate places
           to mount disk drives. It would seem that such actions could be
           supported for any case where a responsible human can be identified:
           single user workstations, or any system which is remotely
           administered.


            This is a classic "remote sysadmin" problem, where in this case
            hotplugging needs to deliver an event from one security domain
            (operating system kernel, in this case) to another (desktop for
            logged-in user, or remote sysadmin). Any effective response must go
            the other way: the remote domain taking some action that lets the
            kernel expose the desired device capabilities. (The action can often
            be taken asynchronously, for example letting new hardware be idle